Rockwell Automation DeviceLogix System User Manual - Manual (Page 187)

Publication RA-UM003B-EN-P - February 2010 187
RSNetWorx for DeviceNet Software and the DeviceLogix Editors Appendix B
The following list contains several important details about network
inputs.
• If an output is not used in the local logic, there is an assumed
connection to a corresponding bit in the consumed data. In the
illustration below, this connection is shown explicitly for outputs
1, 3, 4, 5, 6, 7. Note this connection does not need to be made
graphically with the configuration tool. The
DeviceLogix-enabled module assumes this connection until it is
broken by making a connection to some other piece of
information. If no connection is made to this output, it continues
to take its control from the master controller via its network
input.
• Network inputs can be used as input to more than one entity.
• When an output is bound to logic, its corresponding network
input can be used somewhere else or not used at all.
• As mentioned earlier, the number of network inputs is not
directly associated with the number of hardware outputs present
on the device.
• For devices that support analog functions, the assembly may
also include analog data types (DINT, REAL, etc.).
• Network I/O extends the capabilities of I/O modules by
allowing them to produce and consume the data needed in their
application. Network I/O is critical to the effective use of
DeviceLogix-enabled devices in a networked control system
because of its ability to exchange information between the local
control and external events being monitored by the master
controller.