Alarms and warnings
−
205
−
7Inspection,troubleshootingandremedialactions
2.3 Communication errors
Up to 10 communication errors are saved in the RAM in order of the latest to the oldest and you can check using the
MEXE02
or via RS-485 communication.
Communication error records
Up to 10 communication errors are saved in the RAM in order of the latest to oldest.
Communication error records saved in the RAM can be read or cleared when performing any of the following.
•
Read the communication error records by the monitor command via RS-485 communication.
•
C
lear the communication error records by the maintenance command via RS-485 communication.
•
Clear the communication error records by the status monitor of the
MEXE02
.
Note
You can also clear the communication records by turning off the driver power.
Communication error list
Code Communication error type Cause Remedial action
84h RS-485 communication error
One of the following errors was detected.
· Framing error
· BCC error
•
Check the connection between the
master controller and driver.
•
Check the setting of RS-485
communication.
88h Command not yet defined
The command requested by the master
could not be executed because of being
undefined.
•
Check the setting value for the
com
mand.
•
C
heck the flame configuration.
89h
Execution disable due to user
I/F communication in progress
The command requested by the master
could not be executed since the
OPX-2A
or
MEXE02
was communicating with the
driver.
Wait until the processing for the
OPX-2A
or
MEXE02
will be completed.
8Ah
Non-volatile memory processing
in progress
The command could not be executed
because the driver was processing the non-
volatile mem
ory.
·
Internal processing was in progress.
(S-BSY is ON.)
· An EEPROM error alarm was present.
•
Wait until the internal processing will
complete.
•
When the EEPROM error was
generated, initialize the parameter
using the
OPX-2A
,
MEXE02
or RS-
485 communication.
8Ch Outside setting range
The setting data requested by the master
could not be executed due to outside the
range.
Check the setting data.
8Dh Command execu
te disabl
e
When the command could not be executed,
it tried to do it.
Check the driver status.