Calling Up The Diagnostics Function Block; Performing Bus Diagnostics Using Diaggetbusstate(); Figure 166: Entity For The Function Block Diaggetbusstate() In Fup; Figure 167: Function Block Diaggetstate() In Fup - WAGO I/O SYSTEM 750 Manual

364 PROFIBUS DP-V1 Master
6. Create an entity of the function block DiagGetBusState(). Enter a name
above the function block. In this example it is "GeneralBusInformation".
Enter the value "3" for the DEVICENUMBER for controller "PFC200 CS
2ETH RS CAN DPM" (750-8208/xxx-xxx).

Figure 166: Entity for the function block DiagGetBusState() in FUP

7. Call the function block DiagGetBusState() for diagnosis of the slave from
the library BusDiag.lib.
8. Create an entity of the function block DiagGetState(). In this example it is
"DiagnosticsNode." Enter the value "3" for the DEVICENUMBER for
Controller "PFC200 CS 2ETH RS CAN DPM" (750-8208/xxx-xxx).

Figure 167: Function block DiagGetState() in FUP

In this example, both function blocks are called up during the program sequence.
To prevent prolonging the cycle times during the program sequence, set the input
"ENABLE" for DiagGetState() to "TRUE" only when performing diagnostic
operations.
11.3.4

Calling Up the Diagnostics Function Block

Call up the function block as shown in the following figure.

Figure 168: Off-line view of variable window in CODESYS

11.3.5

Performing Bus Diagnostics using DiagGetBusState()

To perform bus diagnostics, proceed as follows:
750-8208 PFC200 CS 2ETH RS CAN DPM
Version 1.1.0, valid from FW Version 02.06.20(09)
WAGO-I/O-SYSTEM 750
Manual