Go to start pageConfiguration and programmingConfiguration in Automation Builder...General settingsFirmware identification and updateCommunication interface modulesTroubleshooting for IP configuration tool
Troubleshooting for IP configuration toolPermalink

Firewall exceptions:

On a standard Windows 7 installation without third-party firewall or security tools, the IP configuration tool works correctly.

The Automation Builder setup installs rules or exceptions for the built-in Windows firewall. These rules allow IPConfig to receive responses for the IPConfig scan.

To verify that the Windows firewall is configured correctly, check the firewall settings.

Windows 7/ Windows 10:

For the network used for communication with the PLC, set “Incoming connections” to “Block all connections to programs that are not on the list of allowed programs”.

IPConfig_0050

If a third-party firewall is used, the required exceptions must be configured manually.

Either application-based exceptions can be defined. In this case, Automation Builder and the IP configuration tool must be added as application.

Alternatively, the protocol and the port number can be specified. For IPConfig, use the UDP protocol and port number 24576.

Fault description

Cause

Remedy

Error - general

 ›

 

 🔧

Ensure that all requirements have been considered before and during the update procedure.

The “FW Version” field is empty after the network scan or the firmware version has not been updated after the update procedure (only for Modbus devices and PROFINET devices).

 ›

A connection error exists between the device and the executing PC.

 🔧

  1. Ping the device from the executing PC. If no connection can be established, verify whether the device and the PC are in the same subnet.

    Example: Result OK

    • PC: 192.168.14.71 / 255.255.255.0

    • Device: 192.168.14.10 / 255.255.255.0

    Example: Result OK

    • PC: 192.168.10.71 / 255.255.0.0

    • Device: 192.168.14.10 / 255.255.0.0

    Example: Result ERROR

    • PC: 192.168.10.71 / 255.255.255.0

    • Device: 192.168.14.10 / 255.255.255.0

  2. Select [Scan] again to restart the network scan. If the connection is successful, a newer firmware version is displayed in the “FW Version” column.

Signature check failed

 ›

During the firmware update of CI50x, CI51x and CI52x devices, a signature check is started. The update procedure requires a firmware update file (*.bin) and a signature file (*.bin.sig) in the same directory. If the signature file is missing, the signature check fails.

 🔧

Example:

Firmware update file: C:\AC500\AC500_CI52x_Firmware_V3.2.13.bin

Signature file:C:\AC500\AC500_CI52x_Firmware_V3.2.13.bin.sig

Error: Package timeout

 ›

A timeout error may occure due to an unstable network.

 🔧

Keep the executing PC as close as possible to the devices to be updated. Avoid network switches.

Error: Unable to read device status

 ›

A read error may occur due to limitations in the firmware update protocol. After the firmware update, the IP configuration tool reads the status to verify whether the update was successful.

 🔧

Perform the firmware update again.

Error: IP is not unique

 ›

More than one device uses the same IP address. A firmware update is not possible.

 🔧

Change the IP addresses.

Error: Error State

 ›

An internal device error occurred during the firmware update.

 🔧

  1. Scan again and repeat the firmware update.

  2. If this does not work, power cycle the device, scan again and repeat the firmware update.

Error: Can’t connect to device

 ›

The TCP communication is not sufficient.

 🔧

Increase the connection quality. Keep the executing PC as close as possible to the devices to be updated. Avoid network switches.