7.2 Warnings Related to Communication and Commands
7.2.3 Monitoring Communication Data on Occurrence of an Alarm or Warning
7-6
On reception of a normal command after a command error has occurred, CMD_ALM (A.94
and A.95
) is cleared automatically.
7.2.3
Monitoring Communication Data on Occurrence of an
Alarm or Warning
You can monitor the command data that is received when an alarm or warning occurs, such as
a data setting warning (A.94
) or a command warning (A.95
) by using the following parame-
ters. The following is an example of the data when an alarm or warning has occurred in the nor-
mal state.
Command Data Monitor during Alarm/Warning: Pn890 to Pn8A6
Response Data Monitor during Alarm/Warning: Pn8A8 to Pn8BE
Note: Data is stored in little endian byte order and displayed in the hexadecimal.
Com-
mand
Warning
A
The command sequence is incor-
rect.
Review the command
sending sequence of
the controller. (Refer
to the conditions of
each command.)
A.95A
Cleared
auto-
matically
–
8
An unsupported command has
been received.
A.95b
A
Latch command interferes.
A.95d
B
Subcommand and main com-
mand interfere.
A.95E
8
An illegal command has been
received.
A.95F
C
A command not allowed in this
communication phase has been
received.
A.97A
Continued from previous page.
Category
Alarm in Response
SERVOPACK Side
Remark
CMD_
ALM
Meaning
Remedy
Warning
Code
Warning
Code
Reset
Command Byte Sequence
Command Data Storage When an Alarm or Warning Occurs
CMD
RSP
0
Pn890 = n.
XX
Pn8A8 = n.
XX
1
Pn890 = n.
XX
Pn8A8 = n.
XX
2
Pn890 = n.
XX
Pn8A8 = n.
XX
3
Pn890 = n.XX
Pn8A8 = n.XX
4 to 7
Pn892
Pn8AA
8 to 11
Pn894
Pn8AC
12 to 15
Pn896
Pn8AE
16 to 19
Pn898
Pn8B0
20 to 23
Pn89A
Pn8B2
24 to 27
Pn89C
Pn8B4
28 to 31
Pn89E
Pn8B6
32 to 35
Pn8A0
Pn8B8
36 to 39
Pn8A2
Pn8BA
40 to 43
Pn8A4
Pn8BC
44 to 47
Pn8A6
Pn8BE