Module specific counters – Rockwell Automation AutoMax ControlNet Communication Interface Module User Manual
Page 65

AutoMax ControlNet Module Page
65
Publication number DSMBCN-UM001B-EN-P February 2003
Name
Location Description
with the network, configured length doesn’t
match the actual length, unconfigured
repeaters, etc.
RxAbort
9357
Frame Received – Aborted
Lonely
9358
The MBCN did not hear anyone else on the
network for 1.75 seconds
DupNode
9359
The MBCN heard a frame whose source
address is the same as the MBCN’s address
NoiseHits
9360
A signal was heard from the network but not
long enough to be valid
Collisions
9361
The MBCN thought it was its turn to transmit,
but another node was already transmitting
ModMacID
9362
Address of the current moderator
NonLowMods
9363
Moderator heard from a address which is not
the lowest on the network
RogueCount
9364
The MBCN’s network parameters don't match
the network’s
UnHeardMod
9365
The MBCN has not heard a moderator frame
for 3 NUTs
Figure 25 Standard ControlNet Diagnostic Counters
Module Specific Counters
The following counters are not part of the ControlNet specification but
are included in the MBCN to provide additional network information.
Name
Location Description
RxOverRun
9376
Frames coming in faster than the MBCN can
deal with them
SchLenErr
9377
Invalid Length in scheduled receive frame
FifoSynErr
9378
Synchronization Error - Invalid Rx Frame
FifoLenErr
9379
FIFO Length Error - Invalid Rx Frame
FifoTagErr
9380
FIFO Tag Error - Invalid Rx Frame
MsgsSentOk
9381
High Level Messages Sent OK - high level
means actual messages, not null packets,
network overhead, and so on
MsgsRecdOk
9382
High Level Messages Received OK
CmdRecdOk
9383
High Level Commands Received OK
CmdSentOk
9384
High Level Commands Sent OK