How to Resolve Errors

Device is not found

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)

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 11-6: PNIO status error codes on connect and the related settings in the configuration

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).

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.

Start Wireshark and select Capture\Options from the menu.
Choose the network interface used for the PNIO communication and enter the Capture filter below:
```
ether proto 0x8892 or (ether proto 0x8100 and ether[16:2]=0x8892) or udp port 0x8894
```
Then click start.
Start the runtimeIn computer science, runtime (or run-time) describes the operation of a computer program, the duration of its execution, from beginning to termination (compare compile time). Within KAS, runtime also refers to the virtual machine that manage the program written in a computer language while it is running with your application several times and then stop the Wireshark capturing by selecting Capture\Stop from the menu. You can save your recorded traffic by selecting File\Save from the menu.

Stay Connected with Kollmorgen