10–29
Communicating with an SLC 5/03 Processor on a DeviceNet Network using Explicit Messaging
Publication 2755-6.8
Message lengths and slave device types impact transaction message
completion times. If the processor has queued multiple Explicit
Message Transactions to the scanner module for multiple slave
devices, the transactions with the slaves may not complete in the
order in which the requests were received. The slave responses are
queued to the 32 word M1 file transfer in the order in which they are
received. As response transaction blocks are uploaded, the
processor’s program matches the responses to the requests using the
TXID field.
Request
Transaction
Block
Response
Transaction
Block
Ladder Scans
Process Requests
and Responses
Request
Transaction
Blocks
Response
Transaction
Blocks
Scanner
Response
Queue
Scanner
Request
Queue
Execute
Done or
Error-detected
M0 file transfer
Processor
Scanner Module
DeviceNet
Explicit Message
Requests and
Responses
DeviceNet Network
Slave
Device
M1 file transfer
Explicit Message Program Control Limitations
•
The processor is always the DeviceNet client and the slave is
always the DeviceNet server.
•
A maximum of 10 Explicit Message Request Transaction Blocks
with the execute command can be queued to the scanner module
at any time. For example, 10 M0 file transfers containing one
transactions each, can be queued at any time. The scanner
module receives and deletes any additional client/server requests
with the execute command over the maximum of 10.
