Controller Diagnostics out of the Cockpit
| Note
This topic only applies to the standard (non-safety-related) controller. The steps for the Safety PLC are described in the help chapter "Safety PLC Commissioning: From Compiling to Debugging  ‣ Safety PLC Commissioning: From Compiling to Debugging
×‣ Connecting vs. Monitoring Mode vs. Debug Mode ×‣ Controlling the Safety Application from the Safety Cockpit ×‣ Safety PLC Diagnostics out of the Safety Cockpit ×‣ Monitoring/Debugging the Safety PLC ×‣ Monitoring Mode: Displaying Online Values ×‣ Debugging Safety-Related Code: Forcing/Overwriting ×‣ WATCHES: Monitoring/Debugging the Safety-Related Application ×‣ Safety PLC Simulation ×". |
- Display of the essential diagnostic information on the controller.
- Main control functions to start, stop, and reset the controller. If supported by the controller, project sources can be read from the controller.
| Note
Poor internet connection? Performance problems due to VPN connection? You can adapt the TCP communication settings by increasing the handshake timeout value and the polling interval. See topic "TCP Communication Connection". |
How to open the controller 'Cockpit'
- Make sure that the controller is set as target system. For that purpose, TCP/IP must be selected in the drop-down list as shown below.
Note
If you have configured a redundant control system built up with, for example, two RFC 4072R controllers, the drop-down list provides all TCP/IP LAN ports of the controllers for selection. This allows you to access both controllers in the redundant system in order to gather, for example, status information for the purpose of diagnostics of the redundant control system.
For detailed information, see the topic "Configuring a Redundant Control System". - Click the 'Connect to controller' button on the 'Cockpit' toolbar to establish a communication connection between PLCnext Engineer and the controller:
The 'Connect' command is also available in the context menu of the controller in the PLANT and in the ONLINE STATE window (Cross Function Area).It is not necessary to be attached to the controller application (no
debug mode required).
The information is divided into several sections which can be selected via the list on the left. The shown information depends on the controller type involved. Example:
The LEDs on the overview page correspond to the LEDs on the controller device. Like the hardware LEDs, these virtual LEDs light up according to the device status.
| Further Info
For detailed information on the LED indicators of your controller, refer to the user manual of the device. |
Notifications log (PLCnext Technology targets only)
Diagnostic messages sent from the PLCnext Technology target (i.e., from firmware components) are loaded, logged and displayed in the 'Notification' category of the PLCnext Cockpit. Each entry shows a 'Severity' identified by a particular icon, the origin of the message ('Sender') and the name.
| Note
If you have configured a redundant control system built up with, for example, two RFC 4072R controllers, the 'Notifications' log also displays information on the redundancy role (PRIMARY/BACKUP) and redundancy type (FIRST/SECOND) of the controller that initially created the notification. For detailed information, see the topic "Configuring a Redundant Control System". |
| Further Info
For a detailed description of possible messages refer to the controller manual. |
| Icon | Severity |
|---|---|
 | Internal |
 | Information |
 | Warning |
 | Error |
 | Critical error |
 | Fatal error |
While the PLCnext Technology controller is connected, the list of notifications is updated each second. New notifications are appended at the end of the list. The total number of entries appears in the tooltip of the filter icon in the upper left corner of the list header.