System Diagnostics Pages

At runtime it’s always available a system diagnostic tool.It can be displayed in two ways:

• Rotary: setting it to the 0xD value at least for 5 seconds
• Page function: at application level it’s available the function ‘DiagnosticPagesRecall’ to be used, for example, inside a button click event.

The start of the diagnostic tool will close the application pages without stopping the PLC program. The application will not be affected by any modification.Exiting from the diagnostic tool (‘Exit’ button on ‘Home’ page) or restarting the system will restore the original application.Available pages are:

• Home: starting page with exit button to return to the original application
• CANopen: it allows to execute a CAN network diagnostic, if available and configured on target. It uses the standard widget PanelCanStatus.
• GDNet: it allows to execute a GDNet network diagnostic, if available and configured on target. It uses the standard widget PanelGdNetStatus.
• GILOGIK II: it allows to execute a GDNet nodes diagnostic (GILOGIK II), if available and configured on target. It uses the standard widgets BusGdNet and CardGdNet.
• ePCLogic400: it allows to execute a ePCLogic (local bus) diagnostic, and local cards diagnostic, if available and configured on target. It uses the standard widgets Bus400 and CardBus400
• System: displays some information related to firmware versions, disc space and memory status.

Notes:The diagnostic tool works correctly only if the target has been correctly configured with a running PLC.During diagnostic tool execution, the PLC program still run with the original program and the working machine will not be interrupted.