Todd Dice (Customer) asked a question.
Click Ver 3.21 IP issue when updating firmware.
When we download a project via the Ethernet port to a C2-01CPU using Click Ver 3.21, we change the default IP address to 10.10.10.15 before firmware upgrade as our laptops normally communicate with a Productivity PLC. Anyhow, for some reason in V3.21, we must change the IP address twice. We change it first to get online to update firmware, an then we must change it again to download PLC project. I note after firmware upgrade, the blue wheel of death cursor remains on the computer for close to a minute before communication timeout, and then when reconnecting, we note the CLICK has reverted to old IP address so we must reassign 10.10.10.15 a second time.
Is this a new out-of-box CPU? Or is it an existing CPU with a project loaded?
A default out-of-box C2 will be set for DHCP. When powered up it will be discoverable but report an IP of 0.0.0.0 for about 30 seconds while waiting for an assignment from a DHCP server. If a DHCP server does not respond, then the CLICK will self-assign an APIPA address in the 169.254.x.x range. You can of course change the configuration from DHCP to a Static IP matching the network of your computer in order to get connected. You stated “…after firmware upgrade…” you should have received a popup, “Firmware was updated successfully.” Did you receive that message? What were the versions displayed?
I’m also curious if you are directly connected to the CLICKs Ethernet from the PCs NIC? Or is there a network switch between them? Is there a DHCP server on this network?
Is it possible for you to use the USB connection until we can resolve your issue?
It seems like the firmware update was successful, but that the process did not complete correctly. I'm sorry that I don't have an answer for you yet, can we complete this Q&A?
4) When you "must reenter IP address", what address is displayed? "0.0.0.0" or "169.254.x.x" or ???
5) After "Firmware was updated successfully", what are the two versions displayed?
6) I’m also curious if you are directly connected to the CLICKs Ethernet from the PCs NIC?
7) Or, is there a network hub/switch between them?
8) Which type of Ethernet connection from the PC? Wired, WiFi, USB-Wired?
9) Is there a DHCP server on this network?
10) Is it possible for you to use the USB connection until we can reproduce and resolve your issue?
I'll attempt to answer these as best I can as it's our assembler whose experiencing this.
Thank you for reporting this issue and providing the detailed information. We have reproduced it and have reported it to the vendor. It seems limited to when using a USB Ethernet Adapter with a direct wired connection to the CLICK Port1, and only occurs during the firmware update process. It works correctly when connecting through a Network Switch, or using a non-USB Ethernet Port.