Profinet controller stack cannot be started

What does 13037 mean?

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.

• The Profinet controller stack failed to start.
• Initialization error within the Profinet communication software.
• Missing or corrupted Profinet configuration files.
• Insufficient system resources to run the Profinet controller.

Click steps to track your progress.

1. 1

   Review the parameterization settings for the PROFINET firmware by examining the contents of the 'bas_cm_api.xml' file.

2. 2

   Verify that all required parameters within 'bas_cm_api.xml' are correctly configured according to the PROFINET specifications.

3. 3

   Compare the 'bas_cm_api.xml' file with a known good backup or reference configuration for correct structure and values.