Page
26
AN-X-GENI
January 2008
Even if other ControlLogix processors have exclusive owner connections
to other slots on the AN-X and are in run mode, AN-X does not scan the
network.
You can override this behaviour by including a line with the keyword
ScanGeniProg in the configuration file. This causes the AN-X-GENI
module to continue to communicate with the Genius network when the
ControlLogix processor is in program mode but set all outputs to 0.
Similarly ControlLogix processors with exclusive owner connections to
other AN-X slots will also update. If the exclusive owner connection to
slot 0 stops, AN-X stops all communication with the Genius network.
WARNING!
This option is included for debugging since it allows inputs to update in
the ControlLogix. It should NOT be used in normal operation.
Other Mappable Data
In addition to the I/O data, there are other items that can be mapped to
connection input data.
If you create the ControlLogix configuration automatically when you
autoconfigure the Genius network, these items are mapped by default to
ClxSlot 15.
TIP
If you map the diagnostic data to a separate connection, use a long RPI
to reduce the Ethernet traffic, since the diagnostics do not need to be
updated as frequently as I/O data.
Diagnostic Counters
The AN-X-GENI maintains the following diagnostic counters.
Counter
Offset
Description
TxFrames
0
Transmitted network frames
TxMsgs
1
Transmitted network messages (datagrams)
RxFrames
2
Received network frames
RxMsgs
3
Received network messages (datagrams)
RxDup
4
Received duplicate frames
RxCrcErr
5
Received frames with a CRC error
RxStopErr
6
Received frames with a stop error
RxAbortErr
7
Received frames with an abort error
Summary of Contents for AN-X-GENI
Page 59: ...AN X GENI Page 55 January 2008...
