5-6 DeviceNet™ Commissioning
5. When the new node address has been successfully applied, the
“Current Device Settings” section of the window is updated as
follows. If an error occurs, check to make sure the device is prop-
erly powered up and connected to the network.
6. Click Close to exit the node commissioning tool.
7. Choose “Single Pass Browse” from the “Network” menu to
update RSNetWorx and verify that the node address is set cor-
rectly.
System Configuration Selection of produced and consumed I/O assemblies (sometimes
referred to as input and output assemblies) define the format of I/O
message data that is exchanged between the ArmorStart and other
devices on the network. The consumed information is generally used
to command the state of its outputs, and produced information
typically contains the state of the inputs and the current fault status of
the device.
The default consumed and produced assemblies are shown below; for
additional formats refer to Appendix B, page B-1. The ArmorStart
default configuration varies depending on the type of starter.
Choosing the size and format of the I/O data that is exchanged by the
ArmorStart is done by choosing a consumed assembly instance
number. This instance number is written to the Consumed IO Assy
parameter. The different instances/formats allow user programming
flexibility and network optimization.
Important: The Consumed and Produced IO Assy parameter values
can not be changed while the ArmorStart is online with a
scanner. Any attempts to change the value of this
parameter while online with a scanner will result in the
error message “Object State Conflict”.
To Next Page
Loading...
Need help?
General
