Rockwell Automation 1734-XXXX POINT I/O and ArmorPOINT I/O DeviceLogix User Manual - Manual (Page 58)

Publication 1734-UM015A-EN-E - November 2009
56 Configuring POINT I/O and ArmorPOINT I/O DeviceLogix modules using RSNetworx for DeviceNet
Select bit0 of byte0. With up to 24 bytes of data available for mapping, the last
entry is "Peer#0 (Byte 23, Bit7)." 192 bits per peer can be used for a total of
1536 data bits.
You are highly encouraged to use the connection status bits to verify that the
device is receiving valid data from the peer. They are located under the Status
Input category of the "bit input" I/O tags.
In our example, "Peer#0 Data Valid" will be set to 1 when the POINT I/O
DeviceLogix module is consuming data from the peer that is timely (which is,
within the EPR timeout) and of the correct length. No other checking is done
on the data by the module.
"Peer#0 Exists" is set to 1 when a peer connection has been configured.
Analog data can also be used in a peer connection. If a 1734-IE4C module is
located in the third slot, you can configure the POINT I/O DeviceLogix
module like this:
Parameter
number Parameter
name Parameter description Default value
32 Peer#0 MacID Slot number 3
40 Peer#0 Size Input data size 12 bytes
66 Peer#0 EPR Expected packet rate 500 ms