Description of Fault Codes
‑93‑
Cause
Confirming Method
Solution
1. The communication
synchronization clock is
configured improperly.
Use another master (such as
Beckhoff or Omron PLC) and
perform tests to compare
between different masters.
Rectify improper
configurations.
2. The communication IN
and OUT ports are
connected inversely.
Check the connection of the
IN and OUT ports.
Connect the IN and OUT
ports in the correct
sequence.
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
Cause:
The mapping objects in TPDO or RPDO exceeds 40 bytes.
Cause
Confirming Method
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.
● EE10.0: Protection against MailBox setting error
Cause
Confirming Method
Solution
1 The master station is
configured incorrectly.
2. The slave XML file is
incorrect.
Fault code is displayed on
the panel.
Check the configuration of
SM0 and SM1 channels for
errors.
● EE10.1: SM2 setting error