Cyclic diagnostics
The variables PnIoBoxState and PnIoBoxDiag are available for cyclic diagnostics.
These variables are cyclically exchanged with the process image between the PROFINET driver and the System Manager.
PnIoBoxState
Number | Text | Description | Remedial action / reason |
|---|---|---|---|
0 | No error | No error | No error |
1 | PROFINET Device state machine is in boot mode | PROFINET Device State Machine is still in the start-up phase | Not an error, wait |
2 | Device not found | Device does not reply to the Identify Request | Check connection, device connected, was the device called by its correct name? |
3 | The stationname is not unique | The station name is not unique | There are two or more devices in the network with the same PROFINET name. A correct identification cannot take place. |
4 | IP could not set | IP address could not be set. | The PROFINET device has rejected the IP settings for some reason. Check whether the IP settings are correct. |
5 | IP conflict | An IP conflict has occurred in the network. | A possible cause is that several devices have the same IP address. |
6 | DCP set was not successful | There was no reply or an erroneous reply to a DCP Set. | Check connection, device connected, was the device called by its correct name? |
7 | Watchdog error | The connection was broken off with a Watchdog error. | Check the cycle time, check the connection, if necessary increase the Watchdog factor. |
8 | Datahold error | The connection was broken off with a Datahold error. | Frame Data status was invalid for the length of the DataHoldTimer. Restart the device if necessary. |
9 | RTC3: Sync signal could not be started | For IRT only: the Sync signal could not be started. | Is EtherCAT Sync signal correct or has Sync0 started? |
10 | PROFINET Controller has a link error | The PROFINET controller has no link. | Check cable and connection. |
11 | The aliasname is not unique | The alias name is not unique | There are two or more devices in the network with the same alias name. This is made up of the neighborhood information (PortId.ChassisId). A correct identification cannot take place. |
12 | The automatic name assignement isn't possible - wrong device type | The automatic name assignment is not possible. | The expected PROFINET device is not in the projected position (VendorId or DeviceId does not correspond). Hence, no automatic naming and thus no device start is possible. |
31 | only for EtherCAT gateways: WC-State of cyclic EtherCAT frame is 1 | For EL6631 only: EtherCAT WC State is 1 | Check the mode on the EtherCAT master & slave (OP?). |
PnIoBoxDiag
In contrast to the State variable, the variable PnIoBoxDiag can be used to display more than one state at the same time, i.e. the information is bit-coded and up to 16 parameters can be displayed. The following statuses are currently displayed.
Number | Description |
|---|---|
0x0000 | No diagnosis |
0xXXX1 | IOC-AR is not established |
0xXXX2 | IOC-AR is established |
0xXXX4 | IOC-AR is established but no ApplReady |
0xXXX8 | IOC-AR is established but module difference |
0xXX1X | At least one AlarmCR get diagnosis alarm |
0xX1XX | At least one InputCR is invalid |
0xX2XX | At least one InputCR provider is in stop |
0xX4XX | At least one InputCR problem indicator is set |
0x1XXX | At least one OutputCR is invalid |
0x2XXX | At least one OutputCR provider is in stop |
0x4XXX | At least one OutputCR problem indicator is set |
On the one hand information about the status of the IO Controller Single AR is displayed here. In addition, collective statuses are formed from the Frame Data statuses of the individual CRs. The whole thing happens for the input and the output CRs (currently only one is possible; in future the controller will support several CRs). In addition a PROFINET alarm is also displayed in the “PnIoBoxDiag”