4. Configuration
124
Notes:
Value Variable:
Name of the symbolic variable to be mapped. When a reading command is sent, the
return sent in response will be stored in this variable. In case of a writing command, the written value
is also stored in this variable. The variable may be simple, array or array element and may be in
structures.
Static Group:
It chooses which DNP3 group creates the mapping.
Index:
The field is used to set the index of the first mapping point of the DNP3 protocol.
Size:
It is a read-only field that reports how many points are being used by this mapping. The value
of this field varies according the variable type set in the mapping.
Range:
It is a read-only field that reports the range of addresses which is being used by this mapping.
It is formed by the sum of “Index” and “Size”. It is not allowed overlapping ranges with other
mappings of the same type.
Quality Variable:
Name of the symbolic variable that stores the quality of the mapping. It is always
of QUALITY type, and it is available from LibDataTypes library. The variable may be simple, array
or array element and may be in structures.
ATTENTION:
There are situations in which the variables of the groups 30 (Analog Inputs) and Group 40 (Analog
Outputs) receive Outstation values that cannot be stored, due to the difference between the variations
of the received data and the storage variable mapped on the DNP3 client. In such cases, the quality
of this point will be INVALID and the point value will be the last valid value read by the DNP3
Client. This will occur only if the DNP3 Server responds in a wider range than the mapped on the
DNP3 Client. On the other hand, if it responds in the same or a lower variation range, the value and
quality of the point will be stored as the DNP3 Server response.
For example: A variable INT (16-bit) mapped on the DNP3 Client and Server responds in the 32-bit
variation. In this case, the value contained in the response of DNP3 Server is not updated and the
quality will be INVALID.
ATTENTION:
The DNP3 Client driver does not generate events based on its mappings values. The events should
be generated by the respective IED. Therefore, if the IED does not support events generation, the
DNP3 driver will not be able to generate them either.
Configuration of the DNP3 Client Link Layer
The configuration of the DNP3 Client Link Layer (Figure 4-31), follow the parameters shown below
(Table 4-76):
