Rockwell Automation 1753-DNSI DeviceNet Safety Scanner for GuardPLC Controllers - Manual (Page 63)

1 Publication 1753-UM002A-EN-P - July 2005
Chapter
7
Associate the Scanner and Controller and
Download the DeviceNet Network
Configuration
To allow the scanner and the controller to communicate you can
associate their configurations using the Automatically Update Signals
feature or you can manually manage the association. Both options are
found on the GuardPLC tab of the Scanner Properties page in
RSNetWorx for DeviceNet.
Once you’ve made the association between the scanner and
controller, download the DeviceNet network configuration.
This chapter covers:
• the Scanner Signals File
• the Target Connections File
• the Automatically Update Signals procedure
• the manual association procedure
• downloading the DeviceNet network configuration
Scanner Signals File The Scanner Signals File (.ssf) contains standard and safety level input
and output data. RSNetWorx for DeviceNet creates a Scanner Signals
File to define the layout of the data tables exchanged with the
controller via HSP, including detailed signal information
(1)
and the
HSP Signature. The data table contents include the data areas
allocated to the DeviceNet I/O nodes to which the scanner connects,
as well as data areas allocated to RSLogix Guard PLUS! application
signals that are identified in the controllers Target Connections file
(.tcf) and made available to DeviceNet peers that connect to the
scanner.
TIP
We recommend using the Automatically Update
Signals feature because it eliminates the need to
manually import signals and export connections
after every configuration change.
(1) Not all standard I/O devices may provide these detailed I/O assembly definitions. Contact your device vendor
for updated EDS files.
Standard devices that do not support these detailed I/O assembly definitions may include an UNKNOWN data
type. Use the Define Data button on the Standard Data, Signal Connections screen in RSLogix Guard PLUS! to
define these data types.