5. Initial Programming
258
[Device Name]_QUALITY_[Mapping Number]: LibDataTypes.QUALITY;
Where:
Device Name: Name that appear at the TreeView 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 Master/Client
drivers mappings. Therefor it is recommended te use of symbolic mapping MODBUS drivers.
Examples:
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 “Quality” GVL, is editable, therefore the mapping quality variables can be criated 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
4-13.
ATTENTION:
If a symbolic mapping MODBUS Client/Master driver’s variable be mapped in Server IEC 60870-5-
104 driver, it is necessary that the MODBUS mapping quality variables had been created to generate
valid quality events to such Server IEC 60870-5-104 points. Case opposite, aren’t going to be
generated “bad” quality events to Server IEC60870-5-104 clients in the situations that MODBUS
Master/Client can’t communicate with its slaves/servers, by example.
Sending an application to the CPU and changing it to “RUN”. Through “Qualities” GVL, it is
possible to watch diagnostics variable values of MODBUS Clientt/Server device mappings, as shown
at Figure 5-25.
To Next Page
Loading...
General