ProSoft Technology MVI46-DNP - Manual (Page 111)

Reference MVI46-DNP ♦ SLC Platform
Master/Slave Communication Module
ProSoft Technology, Inc. Page 111 of 143
August 23, 2007
5.10 SLC File Usage
SLC File # of
Elements Max.
Elements M1:
Elements M1: Range DNP Data
N: 128 0- 0 to 127 DNP Binary Inputs
N: 256 128- 128 to 383 DNP Analog Inputs
N: 128 384- 384 to 511 DNP Counters
N: 128 512- 512 to 639 DNP Binary Outputs
N: 128 640- 640 to 767 DNP Analog Outputs
N: 128 768- 768 to 895 IED Binary Inputs
N: 256 896- 896 to 1151 IED Analog Inputs
N: 128 1152- 1152 to 1279 IED Counters
N: 128 1280- 1280 to 1407 IED Binary Outputs
N: 128 1408- 1408 to 1535 IED Analog Outputs
N: 60 60 1536 to 1595 1536 to 1595 Error/Status Data
N: 60 60 1596 to 1655 1596 to 1655 Error List Data
N: 40 40 1656 to 1695 1656 to 1695 Additional Status
N: 128 1696- 1696 to 1823 DNP Float Inputs
N: 128 1824- 1824 to 1951 Reserved
N: 128 1952- 1952 to 2079 DNP Float Outputs
N: 128 2080- 2080 to 2207 Reserved
Use this form to define the files set up in the SLC for data transfer to and from
the M1: file from the module. This form will aid in the construction of the ladder
logic required to transfer the data.
Each data type should be placed in a separate data file. This will make
debugging and expansion of the ladder logic easier. The values placed in the
table can be used to define the variables required in the COP command in the
ladder logic. For example, if the DNP Binary Input data has the following values:
N:20:0, 10 (0 to 9), the COP command would have the following parameters:
Source #N20:0
Dest #M1:1.0
Length 10
This assumes the module is placed in slot one of the rack. This will copy the first
10 elements of N20 starting at offset 0 to the M1: file elements 0 to 9
representing binary input data.