4. INITIAL PROGRAMMING
Where:
Device Name: Name that appear at the Tree View to the device.
Mapping Number: Number of the mapping that was declared on the device mapping table, following the up to down
sequence, starting with 0001.
ATTENTION
It is not possible to associate quality variables to the direct representation MODBUS Mas-
ter/Client drivers’ mappings. Therefore it is recommended the use of symbolic mapping
MODBUS drivers.
Example: Device.Application.Qualities
VAR_GLOBAL
MODBUS_Device_QUALITY_0001: LibDataTypes.QUALITY;
MODBUS_Device_QUALITY_0002: LibDataTypes.QUALITY;
MODBUS_Device_QUALITY_0003: LibDataTypes.QUALITY;
END_VAR
The Qualities GVL is editable, therefore the mapping quality variables can be created manually without need to follow the
automatic declaration model, and can be used both ways at same time. But must always be of LibDataTypes.QUALITY type
and take care to don’t delete or change a variable automatically declared, because they might being used by some device. If the
variable be deleted or changed an error is going to be generated while the project is being compiled. To correct the automatically
declared variable name, it must be followed the model exemplified above according to the device and the requisition to which
they belong.
To the MODBUS communication devices the quality variables behave on the way showed at Table 54.
The following picture shows an example of the presentation of this GVL when in Online mode.
ATTENTION
If a symbolic mapping MODBUS Client/Master driver’s variable be mapped in IEC 60870-
5-104 Server driver, it is necessary that the MODBUS mapping quality variables had been
created to generate valid quality events to such IEC 60870-5-104 Server points. Case op-
posite, aren’t going to be generated “bad” quality events to IEC 60870-5-104 Server clients
in the situations that MODBUS Master/Client can’t communicate with its slaves/servers, by
example.
55
To Next Page
Loading...
Need help?
General
