How to resolve errors

Device is not found

  • Check if device is switched on
  • Check the network connection
  • Ensure the correct name was set on the device

Error setting the IP configuration

CL-RPC Lookup

Timeout error

  • Ensure that the IP configuration is valid and appropriate for your network
  • Increase the IP configuration delay

Other errors

  • Ensure you use the correct device name
  • Ensure you have chosen the correct GSDML file (also check if the GSDML file version is appropriate for the firmware version of the device)

Connect response error

Timeout error

  • Ensure that the IP configuration is valid and appropriate for your network
  • Increase the IP configuration delay

Connect response error

Depending on the PNIO status error check, if the settings listed in the table below are set appropriate for your device.

PNIO Status Check the specified setting
1C010003 Slave\ObjectUUID (correct GDML file)
DB81010A Master\Activity timeout factor
DB81010B Master\Controller name
DB81010C Master\Controller name
DB810207 Master\RT-Class
DB81020A Master\Send clock factor
DB81020B Slave\Reduction ratio
DB81020C Slave\Phase
DB81020F Master\Watchdog factor
DB810210 Master\Watchdog factor
DB8103,* Slave\Module IDs,IOs
DB810407 Master\Alarm timeout
DB810408 Master\Alarm retries

Table 7-18: PNIO status error codes on connect and the related settings in the configuration

Module configuration is different

  • Ensure you have configured the modules present on the device (If you have read the module configuration from the device, ensure you have selected the correct modules in the resolve ambiguous modules dialog displayed after selecting the GSDML file).
  • Ensure you have chosen the correct GSDML file (also check if the GSDML file version is appropriate for the firmware version of the device).

Writing parameterization error (with status 0XDF80*)

  • Ensure you have configured the modules present on the device (If you have read the module configuration from the device, ensure you have selected the correct modules in the resolve ambiguous modules dialog displayed after selecting the GSDML file).
  • Ensure you have chosen the correct GSDML file (also check if the GSDML file version is appropriate for the firmware version of the device).

If your error could not be resolved using the hints above, update the firmware of your device and the GSDML file to the latest version and try again.

For further analyses record the PNIO communication using Wireshark.