The controller is started and it is green (after about 3 sec.), but...
Effect |
Cause / Background |
||
---|---|---|---|
...all configured PROFINET Slaves remain red. |
No connection to the network. Issues with firewall. Check that the device scan functions correctly. |
||
...a PROFINET Slave remains red. |
Device not in network. Check that the station name is correct. Slave terminates the connection with errors. Performance problems; the communication watchdog starts when establishing the connection. For more information, see: |
||
…PROFINET Slaves switch between green, red, and orange. |
When establishing the connection, the symbol of the slave is an orange triangle. The
station status is If the In the red/error state, the station status shows the causes. Typical errors are the causes are: |
||
Status: |
Cause |
||
81813F02 |
DNS unknown RealStationName |
Incorrect station name or the device is not reachable over the network |
|
CF81FD05 |
Connection aborted: AR consumer DHT expired |
Send clock cannot be maintained (see 1.4, 1.3.3) |
|
CF81FD06 |
AR cmi timeout |
Send clock cannot be maintained. The firewall blocks the messages from the slave (UDP/RPC). |
|
… PROFINET Slave is green, but it has a red exclamation mark, or individual modules are red. |
The controller has an active connection, and therefore everything is okay. The PROFINET Device reports PROFINET diagnostic messages only for individual modules. |