Data Structure Of Emergency Request Message - Delta AS Series Operation Manual

Send Quote Requests to info@automatedpt.com
Example 1: Stop slave of No. 3 through NMT

Request data:
PLC device
D25000
D25001
D25002
D25003
D25004

Response data:
PLC device
D24000
D24001
D24002

10.4.3 Data Structure of EMERGENCY Request Message

The Emergency request message communicates the slave error and alarm information.
The following table shows the data format of the Emergency request message.
PLC device
D25000
D25001
D25002
D25003~D25031

Command: Fixed to 01.

ReqID: the request ID. Whenever an Emergency message is sent, the message is given a ReqID for
the CANopen master to identify. Before another Emergency request message is sent out, the original
ID number must be changed. In other words, change the value of ReqID. The ReqID range is
between 00–FF (Hex) to trigger the sending the Emergency request message.

Node ID: the node address of the target equipment on CANopen network.
The following table shows data format of the Emergency response message.
PLC device
D24000
D24001
D24002
D24003
D24004
D24005
High byte(Hex)
ReqID =01
Message
Reserved =0
header
Type =03
Reserved
Message
data
Reserved
High byte(Hex)
ResID=01
Message
Reserved =0
header
Reserved =0
ReqID
Message
Reserved
header
Type (Fixed to 04)
Message
data
High byte(Hex)
ResID
Message
Reserved
header
Type (Fixed to 04)
Total number of data
Message
Datum 1
data
Datum 3
Send Quote Requests to info@automatedpt.com
Call +1(800)985-6929 To Order or Order Online At Deltaacdrives.com
Call +1(800)985-6929 To Order or Order Online At Deltaacdrives.com
Request message
Command =01
Size =04
Node ID =03
NMT service code =02
Node ID =03
Response message
Status code =01
Reserved =0
Node ID =03
Request message
High byte
Command (Fixed to 1)
Size (Fixed to 0)
Node ID
Reserved
Response message
Status code
Size Fixed to 2A
Node ID
Number of data stored
Datum 0
Datum 2
Low byte(Hex)
Low byte(Hex)
Low byte
Low byte(Hex)