Description of Fault Codes
‑84‑
Cause
Troubleshooting
Solution
3. The slave controller
integrated circuit is
damaged.
If the fault persists after the
master is replaced, measure
the synchronization signal
generated by the slave
controller integrated circuit
with an oscilloscope. If there
is no signal, the slave
controller integrated circuit
is damaged.
Contact Inovance for
replacing the slave
controller integrated circuit.
4.The MCU pins are
damaged.
Test the synchronization
signal generated by the
slave controller integrated
circuit with an oscilloscope.
If there is a signal, the pins
of the MCU integrated circuit
are damaged.
Contact Inovance for
replacing the MCU chip.
● EE09.5: PDO mapping beyond the limit
Description:
The mapping objects in TPDO or RPDO exceeds 40 bytes.
Cause
Troubleshooting
Solution
The mapping objects in
TPDO or RPDO exceeds 40
bytes.
Check the number of self‑
indexes configured in 1600h
or 1A00h.
The mapping objects in
TPDO or RPDO must not
exceed 40 bytes.
● EE11.0: ESI check error
Description:
PROFINET communication failed to load the XML file.
Cause
Troubleshooting
Solution
1. The XML configuration file
is not downloaded.
Check whether the XML
version displayed in H0E.96
is normal.
Download the XML file.
2. The servo drive is faulty.
The XML file is modified
unexpectedly.
The XML version number is
not empty.
H0E. 37 is set to 1 and power
on and off again.
● EE11.1: EEPROM read failure
Description:
Communication with the external EEPROM failed.
Cause
Troubleshooting
Solution
Reading of PROFINET data in
EEPROM failed.
This fault persists after the
servo drive is powered off
and on several times.
Replace the servo drive.
● EE11.2: EEPROM update failure
To Next Page
Loading...
