dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorConfiguration in Automation Builderdl-breadcrumb-item__separatorPLC devices and componentsdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorPLC start-updl-breadcrumb-item__separatorIP settingsdl-breadcrumb-item__separatorConfiguration of the IP settings with the IP configuration tooldl-breadcrumb-item__separatorTroubleshooting for IP configuration tool
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Troubleshooting for IP configuration tooldl-permalink__symbolPermalink

Firewall exceptions:

On a standard Windows 7 installation without third party firewall or security tools installed the IP configuration tool should work properly.

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

To check the Windows firewall is set correctly check the firewall settings.

Windows 7/ Windows 10:

On the network that is 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 these exceptions must be configured manually.

Either exceptions for applications can be entered: Automation Builder and IP configuration tool must be added as application.

Or the protocol and the port number must be given (for IPConfig: 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)

Connection error between the device and the executing PC.

  1. Ping the device from the executing PC. If no connection can be established, check 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. Click [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 expects a firmware update file (*.bin) and a signature file (*.bin.sig) in the same directory. Without a signature file the signature check will fail.

Example:

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

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

Error: Package timeout

A timeout error may occure due to an instable network.

Keep the executing PC as near as possible to the devices that shall be updated. Avoid network switches.

Error: Unable to read device status

A read error may occure due to errors in the firmware update protocol. After the firmware update the IP configuration tool reads out the status of the updated device in order to check if the update was successful.

Perform the update again.

Error: IP is not unique

If an IP address is obtained by more than one device an error occures. A firmware update is not possible.

Change the IP addresses.

Error: Error State

Internal device error 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 near as possible to the devices that shall be updated. Avoid network switches.