Kuka ProfiNet Controller/Device 3.1
13 fault codes documented
Device could not be started within timeout
The PROFINET communication with the specified device ({Name}) failed to establish within the configured timeout period ({Timeout} ms). This indicates an issue preventing the device from initiating communication with the controller, potentially leading to system downtime.
Connection to device terminated
The PROFINET connection to the specified device ({Name}) has been terminated. This fault indicates an interruption in the device's power supply or a physical break in the network connection, leading to a complete loss of communication.
Connection between PLC and device could not be established
The PROFINET connection between the PLC and the specified device ({Name}) could not be established within the configured timeout period. This can be caused by an excessively low bus timeout setting, a mismatch between the controller and PLC configurations, or a defective PROFINET device, preventing proper operation.
Configured device differs from real device
The PROFINET device configured in the controller's software does not match the actual physical device connected at the specified Slot and Subslot for {Name}. This configuration discrepancy prevents correct communication and operation of the device.
Connection between PLC and device terminated
The PROFINET connection between the PLC and the specified device ({Name}) has been terminated. This issue can stem from interrupted power or network connections, or from performance problems related to the number of devices or incorrect cycle times on the PROFINET network.
PROFIenergy cannot connect to Cabinet Control
The PROFIenergy function is unable to establish a connection with Cabinet Control. This fault typically occurs if Cabinet Control has not been loaded correctly or is malfunctioning, which prevents PROFIenergy functionalities from operating.
PROFIenergy cannot log onto Cabinet Control
PROFIenergy is unable to successfully log onto or authenticate with Cabinet Control. This can be caused by an incompatibility between the KUKA System Software version and PROFIenergy, or if Cabinet Control itself is not loaded or functioning as expected.
Profinet controller stack cannot be started
The PROFINET controller stack failed to start. The root cause is an incorrect parameterization of the PROFINET firmware, specifically an issue within the 'bas_cm_api.xml' configuration file. This prevents the robot controller from acting as a PROFINET controller.
Profinet device stack cannot be started
The PROFINET device stack failed to start. This is caused by a faulty 'pndev1.xml' file, which is critical for the device stack's operation. A corrupted or incorrect 'pndev1.xml' prevents the device from establishing PROFINET communication.
Error initializing Profinet firmware
An error occurred during the initialization of the PROFINET firmware. This indicates that either the PROFINET software stack itself is faulty or the 'bas_cm_api.xml' configuration file contains errors, preventing proper system startup.
Error reading configuration file
The system encountered an error while attempting to read a crucial PROFINET configuration file, specifically 'IPPNIO.xml', 'PNIODriver.xml', or 'bas_cm_api.xml'. A faulty configuration file prevents the loading of essential PROFINET settings and system operation.
Error reading MAC address from KLI
The system failed to read the MAC address from the KLI (KUKA Line Interface). This fault indicates that the KLI configuration is faulty, which is essential for the PROFINET device to properly identify itself and communicate on the network.
Reference Stop - Impermissible Operating Mode
This signal indicates that a reference stop has occurred because the robot is operating in a mode not permitted for referencing. Reference runs are strictly confined to operating modes T1 (Teach mode 1) and CRR (Continuous Run Robot).