EL
ErrorLib
Brands
||
  1. Home
  2. Kuka
  3. ProfiNet Controller/Device 3.1
  4. 13038
About·Privacy·Terms

ErrorLib — Industrial Fault Code Library

Disclaimer: ErrorLib is an independent technical reference tool. While we aim for accuracy, always verify with the manufacturer’s official service manuals before performing maintenance on industrial equipment. ErrorLib is not affiliated with the brands listed.

13038

Profinet device stack cannot be started

Kuka · ProfiNet Controller/Device 3.1

What does 13038 mean?

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.

Common Causes

  • Profinet device software stack failed to initialize on the slave device.
  • Incorrect network configuration on the device.
  • Device firmware corrupted or not loaded correctly.
  • Hardware fault on the device's Profinet interface.

Repair Steps & Checklist

Click steps to track your progress.

  1. 1

    Inspect the 'pndev1.xml' file for any syntax errors, missing data, or signs of corruption.

  2. 2

    Replace the 'pndev1.xml' file with a known good version from a backup or regenerate it using the PROFINET configuration tool.

  3. 3

    Verify that the 'pndev1.xml' file's permissions allow the PROFINET device stack to access it.

Browse all codes in this manual (13)
Verified technical data. Last updated: April 2026

Related Faults

11000Device could not be started within timeout11001Connection to device terminated11006Connection between PLC and device could not be established
Source: Kuka ProfiNet Controller/Device 3.1
Open Manual (Page 70)Search more codes in this manual