Rockwell Automation 2755-SNx Adaptascan Bar Code Readers - Manual (Page 192)

10–30 Communicating with an SLC 5/03 Processor on a DeviceNet Network using Explicit Messaging
Publication 2755-6.8
As transactions are removed from the queue and response transaction
blocks are returned to the processor, additional transaction blocks
can be issued in their place, as long as the total does not exceed ten.
•
The scanner module supports one transaction block per upload
and download.
•
Request Transaction Blocks can only be queued for slave devices
of the scanner module and must appear in the scanner module’s
scan list.
•
If a slave device is not communicating at the time the scanner
module processes its Request Transaction Block, the scanner
module will return an error status for that transaction.
•
At a minimum, the scanner module supports the following
DeviceNet services in Request Transaction Blocks.
Service Name Service Code Example
Get_Attribute_Single 0E
hex
Upload a single parameter value from a device
Set_Attribute_Single 10
hex
Download a single parameter value to a device
Get_Attribute_All 01
hex
Upload all parameter values from a device
Set_Attribute_All 02
hex
Download all parameter values to a device
•
All transaction blocks are processed, therefore, an unused
transaction block must be left blank.
•
Client/Server commands and requests with transaction IDs that
are in use are ignored by the scanner module.
•
If a slave device returns a DeviceNet error in response to the
request downloaded from the processor, the scanner recognizes
the error as a successful transaction (status code =1).
A failure to respond to the request within the number of retries or
timeout period specified for the Explicit Message Connection is
recognized by the scanner module as an error. The error code is
returned in the status attribute of the transaction header.