Known Issues

This section describes bugs and issues that have been reported and that the development team is currently working on. For further questions, see Frequently Asked Questions (FAQ).

Scan

• Some IO-Link devices take longer to be recognized by the IO-Link network module (UDP devices only). #55747

  Workaround

  Rescanning IO-Link devices can remedy the situation.

General information

• During the BET installation, all network drivers and network adapters are restarted. This can have a particular impact on real-time applications such as soft PLC programs that rely on uninterrupted network connectivity or where there is an active VPN connection. #135670

  Workaround

  your system and pose security risks, including accidents or data loss. We recommend that you close all critical applications, especially real-time or mission-critical software, before proceeding with the installation. Save your work and make sure you are aware of all possible consequences.

Topology

• If a device requires a “login”, starting a login process in the detail view will not revert to the login data for the device that already exists in the database. #94602

  Workaround

  Log in by entering your username and password.

• In large topologies with many network modules, it can happen that authentication takes a little longer and results are displayed late. This is particularly common in topologies with network modules that do not support REST API. This problem will be solved in the next releases. #344929

• In the planning phase with offline devices, it can happen in some cases that EIP network modules do not receive the assigned IP addresses. This can mean that the network module cannot be accessed after a topology import. However, this error does not affect operation with online devices that were integrated via Scan. #345203

Parameterization of IO-Link devices

• Diagnosis menu/observation is displayed without entries: The IODD for this device contains process data mapped as ISDU parameters. However, the process data is only displayed at BET within the “Process data” tab. Since the interface for the device is automatically built from the IODD, there may be no data in the “Diagnostics” tab.

• BNI IOL sensor/actuator hubs: Extension port cannot be switched on via IODD. The settings for the extension port are not included in the IODD. Therefore, they cannot be changed via the normal parameters. If a PLC is connected, the correct setting of the hubs is generated by the validation of the devices. #132591

  Workaround

  • If a PLC is connected, the correct setting of the hubs is generated via the validation of the devices.

  • If you do not have a PLC connected at the moment but want to switch the hubs, you can use the option to change the index and subindex via the web interface of the Balluff-IO-Link network MOdul or via the “ISDU parameters” tab. As a rule, the index 0x55 must be changed. More detailed information can be found in the instructions of the hubs.

• If a parameter of type TimeSpanT is entered, inaccuracies may occur in the value entered. For example, 30 days can be written one millisecond higher or lower than entered. #173446

• GSDML/ESI configurator: For data lengths with bit lengths over 4 bytes, the parameters may be translated incorrectly into the ESI format. A tool such as CODESYS, which supports this format, can display these values incorrectly. The order of the data parameter values is usually reversed.

Firmware update

• Since March 2024, you have received encrypted firmware for the following network modules:

  • BNI00HL

  • BNI00K4

  • BNI006A

  • BNI008M

  • BNI00HM

  • BNI00HW

  • BNI00H4

  • BNI00K5

  The new firmwares offer an increased security standard. These encrypted firmwares can no longer be replaced by the previously unencrypted firmwares. Upgrading to encrypted firmware is only possible if the firmware used on the network module has been prepared for such an upgrade.

  If an attempt is made to update from an unencrypted firmware that is not designed for an upgrade to an encrypted firmware to an encrypted firmware, this will result in a failed update.

  If an attempt is made to set an encrypted firmware from an unencrypted firmware, this will result in a failed update.

• For BNI00HL firmware version 1.1.4 and BNI00HM firmware version 4.8.4 is not supported:

  • Correct visualization of the port status in the master view

  • Visualization of the process data of all connected devices in the master view

• When updating the firmware of a BNI00HL with FW 1.0.x to FW 1.1.4, BET displays an error at the end of the update because the device is reset to the factory settings and BET cannot find the device after the reset (no IP address in Profinet and default Profinet name). The firmware is saved on the device despite the error message.

  Workaround

  • Resetting the settings indicates a successful update

  • After the update, perform a new network configuration for the devices and change the IP address.

• When updating the firmware of a BNI00HM with FW 1.1.x to FW 4.8.4, BET displays an error at the end of the update, as the device is reset to IP 192.168.1.1 and BET cannot find the device after the reset, unless the update has already been carried out with this IP. The firmware is saved on the device despite the error message.

  Workaround

  • Resetting the settings indicates a successful update

  • After the update, perform a new network configuration for the devices and change the IP address.