ProSoft Technology MVI69-DNPSNET - Manual (Page 60)

MVI69-DNPSNET ♦ CompactLogix or MicroLogix Platform Diagnostics and Troubleshooting
Distributed Network Protocol Interface Module
Page 60 of 119 ProSoft Technology, Inc.
November 3, 2008
4.2.4 Error Status Table
The program maintains an error/status table that is transferred to the processor
in each read block. Ladder logic should be programmed to accept this block of
data and place it in the module's controller tag. You can use the error/status data
to determine the "health" of the module.
The data in the block is structured as shown in the following table.
Word Variable Name Description
0 Scan Counter Program scan counter incremented each time the
program loop is executed.
1 to 2 Product Name (ASCII) These two words contain the product name of the
module in ASCII format.
3 to 4 Revision (ASCII) These two words contain the product revision level of the
firmware in ASCII format.
5 to 6 Operating System Revision
(ASCII) These two words contain the module's internal operating
system revision level in ASCII format.
7 to 8 Production Run Number
(ASCII) These two words contain the production 'batch' number
for the particular chip in the module in ASCII format.
9 Read Block Count Total number of blocks transferred from the module to
the processor.
10 Write Block Count Total number of blocks transferred from the processor to
the module.
11 Parse Block Count Total number of blocks parsed by the module that were
received from the processor.
12 Block number error Number of BTW requests that resulted in an incorrect
BTW identification code.
13 DNP Slave Port total
number of message frames
received by slave This value represents the total number of message
frames that have matched this slaves address on this
port. This count includes message frames which the
slave may or may not be able to parse and respond.
14 DNP Slave Port total
number of response
message frames sent from
slave This value represents the number of good (non-error)
responses that the slave has sent to the master on this
port. The presumption is that if the slave is responding,
the message was good. Note: This is a frame count.
15 DNP Slave Port total
number of message frames
seen by slave This value represents the total number of message
frames received by the slave, regardless of the slave
address.
16 DNP Slave synchronization
error count (Physical Layer
Error) This value counts the number of times a sync error
occurs. The error occurs when extra bytes are received
before the start bytes (0x05 and 0x64) are received.
17 DNP Slave overrun error
count (Physical Layer
Error) This value counts the number of times the overrun error
occurs. This error occurs when the mainline Data Link
Layer routine cannot read the data received on the
communication port before it is overwritten.
18 DNP Slave length error
count (Physical Layer
Error) This value counts the number of times an invalid length
byte is received. If the length of the message does not
match the length value in the message, this error occurs.
19 DNP Slave bad CRC error
(Data Link Layer Error) This value counts the number of times a bad CRC value
is received in a message.