Troubleshooting

This chapter lists common problems when integrating a BNI IO-Link master via PROFINET in an engineering tool such as the Siemens TIA Portal, their causes, and how to solve them. The table gives a quick overview. The sections below the table describe each problem in more detail.

Common PROFINET problems

Problem

Explanation

Solution

References

BNI device does not communicate in the PLC program (bus error, no connection, no process data).

  • PROFINET device relationship is not established.

  • Device name in the project differs from the device name in the field.

  • Check that both device names are identical.

  • Assign the device name again.

BNI device is not found (not listed, not reachable, offline).

  • Device is not reachable in the network.

  • PROFINET protocol is not active.

  • Check power supply and Ethernet connection.

  • Check the configured protocol.

BNI device is not available in the hardware catalog, or the GSDML does not fit the device (device not listed, firmware incompatible).

  • GSDML file is not installed.

  • GSDML version is outdated and not compatible with the firmware.

  • Install the GSDML file in the engineering tool.

  • Use a GSDML version that matches the device firmware.

Pin 2/4 signals of a port show no data (no input or output bytes).

  • Module on slot 1 is a variant without IO data (w/o IO).

  • Digital Input/Output submodules provide no process data on this module.

  • Plug the Pin 2/4 submodules in slot 2.

  • Or use the slot 1 module with IO data.

ISDU parameters are not written to the IO-Link device.

  • Parameter entry has length 0.

  • ISDU submodule has too few entries.

  • ISDU subslot does not match the port.

  • Enter index, subindex, length and data for each parameter.

  • Select an ISDU submodule with enough entries.

  • Plug the ISDU submodule into the subslot with the port number.

Safety Hub safe channel submodule cannot be plugged or used.

  • Wrong module on slot 1.

  • Safe submodules fit only the Safety Hub module with 16 subslots.

  • Plug the IO-Link I/O Ports (w/o IO) with Safety Hub and ISDU module on slot 1.

  • Assign the secure and standard I/O submodule to the port.

  • Restart the master.

BNI device does not communicate in the PLC program

Symptom

  • After going online in TIA Portal, the PROFINET device does not show a green checkmark.

  • The PROFINET device reports a bus error.

  • The PLC does not exchange process data with the BNI IO-Link master.

Cause

The PROFINET device relationship is not established. The PLC addresses the BNI device via its PROFINET device name. If the name configured in the project does not match the name stored in the device, the connection cannot be established.

Instructions

BNI device is not found

Symptom

  • The BNI device is not listed after clicking Update list in the Assign PROFINET device name dialog.

  • The BNI device is not found when scanning the network.

  • The BNI device is not reachable (offline).

Cause

The BNI device is not reachable in the network, or it is not operating with the PROFINET protocol.

Instructions

BNI device is not available in the hardware catalog

Symptom

  • The BNI device is not listed in the hardware catalog under Other field devices > PROFINET IO > IO.

  • Modules or submodules expected for the firmware version are missing.

Cause

The GSDML file of the BNI device is not installed. Outdated GSDML versions may not be compatible with the latest firmware version.

Instructions

Pin 2/4 signals of a port show no data

Symptom

  • The Digital Input or Digital Output submodule of a port provides no input or output bytes.

  • Pin 2 and Pin 4 states cannot be read or written in the PLC program.

Cause

The module on slot 1 is a variant without IO data (IO-Link I/O Ports (w/o IO)). Neither the module nor the Digital Input and Digital Output submodules provide process data. Pin 2 and Pin 4 must be read or written via the Pin 2/4 submodules in slot 2.

Instructions

Symptom

  • IO-Link device parameters are not changed after the connection is established.

  • The IO-Link device keeps its previous parameter values.

Cause

Only ISDU parameter entries with a length greater than 0 are written to the IO-Link device. The ISDU submodule must provide enough entries for all parameters. The subslots of the ISDU Parameter Configuration module (slot 3) map directly to the ports, without the offset that slot 1 has.

Instructions

Safety Hub safe channel submodule cannot be plugged or used

Symptom

  • The Safety I/O submodules (PROFIsafe 2.4 or 2.6) from the Safety Hub folder cannot be assigned to the port subslot.

Cause

The safe submodules of the Safety Hub are only available for the IO-Link I/O Ports (w/o IO) with Safety Hub and ISDU module on slot 1. This module provides 16 port subslots: a secure and a standard subslot per port. With any other module on slot 1, the submodules cannot be assigned.

Instructions