Orion HE (Customer) asked a question.
Yesterday, startup of a new facility expansion. Small P2000 rack with 3 I/O cards. Suite 4.1.1.10 with equivalent firmware. And the thorn in my side, the P2-622.
This is the second attempt at using the 622 in a new project. The first actually died after 2 weeks of use, and those 2 weeks were plagued with the CPU forgetting every single retentive value in the controller every third program change. Even minor changes would awaken some latent rage in the 622 and it would say that it was unable to transfer the project, kick the program into stop mode, and lose every value we had entered. (Pictures are your friend)
This 622, along with the same errors that hindered my previous startup, also decided to throw this ridiculous error message.
Normally, highly-specific error messages are a good thing. In this case, the 622 just lost its mind for a moment. No, the IP didn't change in the project and after this failed transfer, it went without a hitch. It even remembered my retentive values that time. Amazing!
Anyway, if you have a 622 and it hasn't given you a hard time, and you are using User Data Structures, you have been very lucky. Either that or AD pulls a lemon specifically for me every time I order one. Long live the 550!
Have some 622s on the shelf but haven't done much with them. Have had extensive issues with project transfers on P1-540,P1-550,P2-550 since V4. Including one on the latest firmware losing all retentive values and setting them all to zeros after a failed runtime transfer and subsequent stop-mode transfer. Haven't been able to sort out any reasoning yet. I no longer make runtime transfers with productivity CPUs when running, too many issues.
Dang. That's unfortunate. I have extensive Do-more experience and a load of P2-550, and some P3000 experience and Run-mode edits are solid. That you have problems with the P2-550 means there is something we are doing to break these things.
I typically use ethernet to connect to my PLCs, I use UDS quite a bit (something the 622 seems to hate). I use Modbus reads/writes to VFDs and compressor panels. Somehow, some combination of things is crashing something. I know that's obvious and not very helpful, but it was fun to type.
I havent done a project with the 622 yet, though I plan on it being my new main CPU going forward with future projects. Mainly due to whatever special features it is supposed to get in the coming years that the old CPUs wont be getting. Not sure what those are, but AD support said it is capable of getting some new things.
Hopefully I dont run into problems with it. I use Ethernet communication as well, as USB on all CPUs has been far too buggy for me
I almost exclusively use ethernet communication. Since my post, I have been in communication with someone from AD who seems interested in solving the issues I've been seeing. In the two applications I've used the 622, the first 3 IO modules have been the same. That is possibly a coincidence, but it may be causative. I'm trying to think of anything that could cause the dismal performance I've seen with the 622.
It's possible that I have extraordinarily bad luck. If there is a lurking bug (that I keep stumbling onto), I'd like to help AD sort it out.