5. Initial Programming
261
Figure 5-26. ReqDiagnostics GVL in Online Mode
GVL System_Diagnostics
In “System_Diagnostics” GVL, are declared the diagnostic variables of the CPU, of the
communication interface (Ethernet and PROFIBUS) and of all communication drivers. This GVL
isn’t editable and the variables are declared automatically with type specified by the device to which
it belongs whne it is added to the project.
ATTENTION:
In “System_Diagnostics” GVL, are also declared the diagnostic variables of the direct representation
MODBUS Client/Master requisitions.
Example:
Device.Application.System_Diagnostics
VAR_GLOBAL
DG_MODBUS_Symbol_Client : T_DIAG_MODBUS_ETH_CLIENT_1;
DG_MODBUS_Symbol_RTU_Master : T_DIAG_MODBUS_RTU_MASTER_1;
DG_NX3030 AT %QB66229 : T_DIAG_NX3030_1;
DG_NX5001 AT %QB66922 : T_DIAG_NX5001_1;
DG_MODBUS_Client AT %QB67191 : T_DIAG_MODBUS_ETH_CLIENT_1;
DG_MBUS_Direct_1_Mapping_000 AT %QB67211 : T_DIAG_MODBUS_ETH_MAPPING_1;
END_VAR
As can be observed in the previous example, the symbolic mapping MODBUS communication driver
don’t have its diagnostics allocated at %Q variables with the AT directive. The same occurs with
newest communication drivers, as Server IEC 60870-5-104.
Sending an application to the CPU and changing it to “RUN”. Through “System_Diagnostics” GVL,
it is possible to watch diagnostics variable values of MODBUS Clientt/Server device mappings, as
shown at Figure 5-27.
To Next Page
Loading...
General