Da Sid Mon (Customer) asked a question.
About once every 15-20 uploads to the controller results in the progress meter getting stuck on 99% and then I get a pop-up message that states "The connection is LOST". The controller then appears to go into STOP mode and no longer can be reached and is completely unresponsive.
The display on the controller shows "BOOT UP" (See attached photos) The only way to get the controller to come back to life is to cycle power.
I am connected to the controller via Ethernet using a Windows 11 computer which is in the same enclosure as the PAC2K. There is a STRIDE 5 port switch and the computer, controller and 2 C-More HMIs are all connected to the switch. After this error occurs, the C-More HMIs are still operating normally (i.e. reachable via ethernet connection-without a connected/working controller it is hard to determine their level of function but they appear to be normal).
I've talked to 2 different AD Tech Support Dudes (who are fabulous BTW) and so far nobody has been able to determine a resolution to this issue. Having worked with the Productivity series of controllers for over 10 years now and never seeing this before is not only quite puzzling but terribly stressful. If I am on-site programming, it's not that big of a deal as I have become quite proficient at flicking the breaker powering the e PAC. However, this situation makes remote programming the ultimate "At your own risk" scenario. Having to call the Client and ask them to cycle power is not only embarrassing but doesn't inspire confidence in the AD Productivity series of controllers. I think that everyone will agree that uploading to a controller should NOT be like rolling the dice in Vegas!
I thank Y'all in advance if anyone has any insight, ideas, suggestions - hell- I'll even take y'alls prayers at this point LOL.
-Sid
P.S. I am using P-Suite Ver 4.2.1 (8) with all the latest firmware updates to the controller (1.7.2.8) just in case y'all wanna know. THX!
Good morning, I am sorry to hear that Tech Support wasn't able to help you resolve this problem.
You mention that you're using P-Suite 4.2.1.8 and firmware 1.7.2.8; however, the latest firmware is 1.7.2.11 and in the Release Notes for P-Suite indicate the following:
Firmware Version History:
P2-622 Version: 1.7.2.11 Release Date: May 22, 2024
Note: P2-622: The steps below are required prior to downloading a project in version 4.2 or higher to prevent the CPU from showing a 'spinner' on the LCD and requiring a power cycle.
Could you verify that either 1.7.2.8 firmware is still currently installed or that indeed the P2-622 has been updated to use 1.7.2.11?
Thanks for the QUICK reply! You are correct, the firmware I'm running is not the latest. I will update and circle back. I do not mean to be a "Debbie "Downer" but I do not think the Firmware update is going to solve the issue. I previously forgot to mention thaT about 4 days ago, I had replaced the existing fully updated 622 Controller unit. I suspected that the 622 I was using was defective and purchased a new unit to exchange. Unfortunately that did not resolve the issue (BUT then again, I had not updated the firmware so, I suppose there is still hope??) . Nonetheless, I will update the current unit and report back. Thanks,
Thank you for the information, and we'll keep a look out for your update. Given the description of the symptoms you're seeing and the security updates between firmware 1.7.2.8 and 1.7.2.11 this update should hopefully resolve the issue.
If not then we'd certainly like to pursue this further by getting a System Report when you're connected to the P2-622 currently installed on-site and possibly getting the original P2-622 returned for investigation.
Please accept our apologies for the stressful situation as you point out that it can undermine the confidence in our products and should not feel like a gamble.
ALRIGHTY! After updating firmware on the new/replaced P2-622 everything seems to be functioning normally. I have completed another 10 or so uploads and have not experienced the previously mentioned issue. Fingers crossed that this has solved it! Thanks again for the assistance! 💪 🙏
:-( NAW.... I spoke too soon. Happened again. I had to call my Customer and ask them to cycle power. THIS BITES! I'm gonna send in a Sys Report and see if Tech Support can help cause this is NOT IT! Grrrr