ProSoft Technology MVI94-DNP User Manual
Page 94

Reference
MVI94-DNP ♦ Flex I/O
User Manual
DNP 3.0 Server over Ethernet Communication Module
Page 94 of 131
ProSoft Technology, Inc.
December 17, 2010
5.4.5 IIN Bits
MVI94-DNP Module Internal Indication Bits (IIN Bits) for DNP Slave Port
The internal indication bits are stored in a word that follows the function code in
all response messages. These bits report status and error information to the
master DNP device. Below is a description of the word:
First Byte
Bit
Description
0
All stations message received. Set when a request is received with the destination address
set to 0xffff. Cleared after next response. Used to let master station know broadcast
received.
1
Class 1 data available. Set when class 1 data is ready to be sent from the slave to the
master. Master should request class 1 data when this bit is set.
2
Class 2 data available. Set when class 2 data is ready to be sent from the slave to the
master. Master should request class 2 data when this bit is set.
3
Class 3 data available. Set when class 3 data is ready to be sent from the slave to the
master. Master should request class 3 data when this bit is set.
4
Time synchronization required from master. The master should write the date and time when
this bit is set. After receiving the write command the bit will be cleared.
5
Slave digital outputs are in local control. This bit is not used in this application.
6
Not used.
7
Device restart. This bit is set when the slave either warm or cold boots. It is cleared after a
master writes a 0 to the bit.
Second Byte
Bit
Description
0
Bad function code. The function code contained in the master request is not supported for
the specified object/variation.
1
Requested object(s) unknown. Object requested by master is not supported by the
application.
2
Parameters in the qualifier, range or data fields are not valid or out of range for the slave.
3
Event buffer(s) or other application buffers have overflowed. This bit is also set if the slave
receives a multi-frame message from the master.
4
Request understood but requested operation is already executing. The slave will never set
this bit.
5
Bad configuration. The slave configuration is invalid and should be re-configured. If the
configuration is invalid, the slave will set the invalid parameters to default values and
continue to run. Check error log using debug port.
6
Reserved, always 0.
7
Reserved, always 0.