6. HX3040 Redundancy
294
Example:
ReqDiagnostics
VAR_GLOBAL
MODBUS_Device_REQDG_0001
: T_DIAG_MODBUS_RTU_MAPPING_1;
MODBUS_Device_REQDG_0002
: T_DIAG_MODBUS_RTU_MAPPING_1;
MODBUS_Device_REQDG_0003
: T_DIAG_MODBUS_RTU_MAPPING_1;
MODBUS_Device_1_REQDG_0001
: T_DIAG_MODBUS_ETH_MAPPING_1;
MODBUS_Device_1_REQDG_0002
: T_DIAG_MODBUS_ETH_MAPPING_1;
Outstation_REQDG_0001
: T_DIAG_DNP_CLIENT_REQUEST_1;
END_VAR
The "ReqDiagnostics" GVL is editable, so the diagnostic variables of the requests can be created
manually and do not need to follow the model created by the automatic declaration. Actually, you
can use both ways at once, but make sure to use variables related to the device, and ensure not to
delete or change the variables automatically declared, as they might be in use by a MODBUS device.
If you delete or change some variable, the system generates an error during the project compilation.
To correct the name of a variable declared automatically, follow the model exemplified above
according to the device and requests to which it belongs.
By sending an application to the HX3040 CPU and putting it in "Execution", through GVL
"ReqDiagnostics" you can monitor the diagnostics variable values of the MODBUS Mater/Client and
DNP3 Client devices mappings (Figure 6-14).
Figure 6-14. GVL ReqDiagnostics in Online Mode
System_Diagnostics GVL
The "System_Diagnostics" GVL declares the diagnostic variables of the CPU and communication
drivers. This GVL is not editable, so the variables are automatically declared with the type specified
by the device to which it belongs, when it is added to the project.
