Ken Roach
Lifetime Supporting Member + Moderator
The "Scanlist" configuration method of DeviceNet is very old-fashioned and comes from the heritage of how DeviceNet was grafted onto the PLC-5 and SLC-500 as an expansion module with a large PLC memory data table.
You don't see ordinary DeviceNet I/O modules in the RSLogix 5000 tree with DeviceNet like you do with ControlNet and EtherNet/IP. The exception is safety modules; the Safety connection works differently than ordinary DeviceNet general-purpose I/O connections.
Instead you configure the scanlist entries in the Scanner, then "map" the data into the PLC I/O data tables or Module I/O Tags.
There's a semi-automatic way to create device-specific data tables using the DeviceNet Tag Creation Tool. I don't recommend it for just this small network.
Instead look at the Scanlist and be sure the I/O connection is created and that its resulting Input and Output bytes are mapped into the Input and Output data tags of the CompactLogix.
You don't see ordinary DeviceNet I/O modules in the RSLogix 5000 tree with DeviceNet like you do with ControlNet and EtherNet/IP. The exception is safety modules; the Safety connection works differently than ordinary DeviceNet general-purpose I/O connections.
Instead you configure the scanlist entries in the Scanner, then "map" the data into the PLC I/O data tables or Module I/O Tags.
There's a semi-automatic way to create device-specific data tables using the DeviceNet Tag Creation Tool. I don't recommend it for just this small network.
Instead look at the Scanlist and be sure the I/O connection is created and that its resulting Input and Output bytes are mapped into the Input and Output data tags of the CompactLogix.