13037
Profinet controller stack cannot be started
Kuka · ProfiNet Controller/Device 3.1
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.
Repair Steps
- 1
Review the parameterization settings for the PROFINET firmware by examining the contents of the 'bas_cm_api.xml' file.
- 2
Verify that all required parameters within 'bas_cm_api.xml' are correctly configured according to the PROFINET specifications.
- 3
Compare the 'bas_cm_api.xml' file with a known good backup or reference configuration for correct structure and values.
Verified technical data. Last updated: March 2026
Source: Kuka ProfiNet Controller/Device 3.1