56 Rockwell Automation Publication 2080-UM004C-EN-E - March 2015
Appendix 5 DeviceNet Plug-in – 2080-DNET20
Send Explicit Messages to
2080-DNET20 Plug-in Using
Micro800 Pass Through
MSG_CIPGENERIC instruction can be used to send Explicit messages to the
2080-DNET20 plug-in and the Slave nodes on the DeviceNet network.
In MSG_CIPGENERIC, configure the target path as mentioned below:
• To access the plug-in, the format of the target path is “1, Slot number”.
• To access a Slave device through the plug-in, the format of the target path is
“1, Slot number, 2, DeviceNet node address”.
For example, if the 2080-DNET20 plug-in is connected at physical slot 3 and the
Slave device of address 40 is present in the DeviceNet network, then:
• Using MSG_CIPGENERIC to access the plug-in, the target path would
be “1, 3”.
• Using MSG_CIPGENERIC to access the Slave node through the plug-in,
the target path would be “1, 3, 2, 40”.
Note that the number “1” refers to the Virtual backplane port number and “2”
refers to the 2080-DNET20 plug-in's DeviceNet port number. These are fixed
values. The slot number starts from 1 up to the maximum number of slots
physically present in the controller.
When the controller pass through feature is used in the following example:
Micro850 –> Micro820 [192.168.1.100] –> 2080-DNET20 plug-in
[Slot 3] –> Slave device [Node 40]
• Using MSG_CIPGENERIC starting from Micro850 to access the plug-
in, the target path would be “4, 192.168.1.100, 1, 3”
1 Transaction completed successfully.
2 Transaction in progress (not ready).
4 Error – node offline
5 Error – DeviceNet port disabled/offline
6 Error – Transaction TXID unknown
7 Error – Duplicate TXID
9 Error – Scanner out of buffers
12 Error – Response data too large for block
14 Error – Invalid size specified
15 Error – Device timed out
16 Block queued.
17 Block allocated
18 Connection in progress
3, 8, 10, 11, 13, 19...255 Reserved
Explicit Message Status Codes
To Next Page
Loading...
Need help?
General
