ProSoft Technology MVI46-DNP - Manual (Page 70)

MVI46-DNP ♦ SLC Platform Reference
Master/Slave Communication Module
Page 70 of 143 ProSoft Technology, Inc.
August 23, 2007
Trip/Close
The MVI46-DNP module supports Trip/Close functionality for Binary Output
points.
This allows Trip/Close commands to be sent to the MVI46-DNP module, for dual
point control. Each DNP Trip/Close command will occupy 2 bits within the
module memory.
This does overlap the regular pulse on/off and latch on/off Binary Output
database, therefore special consideration must be used to make sure that points
are not used twice.
The following table describes the address mapping for the module using Latch
and Pulse commands, and Trip/Close functionality.
DNP BO Database Point BO Latch/Pulse Point BO Trip/Close Point
0 BO 0 Close BO 0
1 BO 1 Trip BO 0
2 BO 2 Close BO 1
3 BO 3 Trip BO 1
4 BO 4 Close BO 2
5 BO 5 Trip BO 2
100 BO 100 Close BO 50
101 BO 101 Trip BO 50
1000 BO 1000 Close BO 500
1001 BO 1001 Trip BO 500
2046 BO 2046 Close BO 1023
2047 BO 2047 Trip BO 1023
As you can see from the above chart, trip/close requires 2 points within the
module's DNP database. A trip is represented by the value of 2#10 for those 2
points, and a close is represented by the value of 2#01 for those same 2 points.
The module can only process 1024 trip/close points, as the database for the DNP
BO is limited to 2048 bits total.
DNP Counter Data
This data type stores accumulated count data. These data are stored in the
module in a double word value and have a data range of 0 to 4,294,967,296. The
size of this data area is determined from the configuration parameter Number of
Counter Points. The data area is partitioned into two separate areas. The first is
the DNP counter data acquired from the SLC, and the second is the counter data
from the IED units. The configuration parameter, Number of Counter Points for
SLC, determines the size of the SLC's data area. The remaining portion is
defined as the IED counter data area.