arm089 (Customer) asked a question.
P2CDS-622 bricked?
Hello,
After 1 moth or so working with the P2CDS-622 plc, since yesterday the PLC is no longer reachable in IDE. Ping works using the static IP address of the network interface.
This condition raised after receiving "Not enough memory" alerts while trying to download the application.
I have tried the factory reset method using the FW utility tool and the USB port on the PLC but still the device is not shown in the tool (clicked Refresh button many times).
Any hints? How can I factory reset the PLC if the device is not even shown in the FW utility tool?
Thanks,
Is your gateway running? Did you try to set up a manual connection via "Add Favorite Device"? (All of this Codesys, I don't know anything about the Productivity specific implementation or their firmware tools)
Yes it's running, actually I'm working on a another app using the Windows runtime on the same laptop, all working.
Another thing you can try is power up the cpu in stop mode and give it a couple minutes or so to try to connect to it. Also check the cpu lights are functioning correctly (usb, eth, pwr, ect).
It's a good sign you can ping it, so might not be bricked. I've seen the cpu can take a bit to come up on projects that use a lot of the cpu's resources.
Thanks for the reply, all lights are functioning correctly usb, eth and pwr) and the PLC has been sitting on my desk powered and in stop mode for more than 2 hours today but still codesys IDE nor P2CDS-622 Firmware Updater tool can't see it with both ethernet or usb cable.
Also, I have power cycled the PLC and my laptop many times, tried several usb and ethernet cables but still no luck.
Sent a private message to you with recommended next steps.
First situation like this we have seen. We will update publicly here any resolution we do.
Regards
Update on this, we have contacted the customer to offer a replacement unit if their unit still in fail state.
In addition, we will request the failure unit from them to do testing in-house to determine possble cause of failure. Will advise on any progress.
Resolution not made. Sending a replacement unit and they will send the failed unit to us for analysis.
The customer is another country so this may take few weeks to get some useful data. Will advise.
So what was the outcome of the analysis? I've exactly the same issue just that it basically started the moment I opened the box. I sporadically managed to connect with the Firmware update tool and one time I was even able to download the latest firmware file and it said that the installation was successful. And then I setup the two ethernet ports. Ever since it' is just getting worse. If I manage to connect (via USB or Ethernet), latest when I try to download the firmware or simply hit 'refresh' the tool just times out after a few seconds with 'connection lost' (or no response of refresh). Tried many different cables, various computer, even a blank windows install with full admin rights and firewall/virus disabled, all to no avail. That is all via the USB port, over the Ethernet ports I couldn't connect ever since setting the port addresses. Which interestingly enough still respond to a ping command.
Regarding- "So what was the outcome of the analysis?"- we sent out replacement unit 6/11/24 to "am089".
Failure unit requested multiple times but never received.
Tech Support log notes from 7/17/24 "multiple requests for unit. no reply. closing out (they had severe hurricane) ".
For yourself, not sure if a Factory Reset was attempted- (https://docs.codesys-p2cds622.com/en/latest/Additional%20Topics/fwupdate.html)
Scroll to bottom and note the toggling of the Run/Stop switch.
The problem with Factory Reset is, I've to successfully connect with the Firmware tool first to get to this 'Reset' button. And it's not connecting anymore. I tried by just toggling the switch and then cycle power but that doesn't seem to do anything. Or at least it didn't change anything to the fact that I can't establish communication with the firmware tool anymore.