Sorry for the incredibly late reply. The issues we have had are;
- Used Turck PLCs originally but they were not fast/large enough for our programs (this is second hand information. Our equipment is usually 200 I/O points almost exclusively digital.
- We did not have any support from Turck for CodeSys questions and could not locate a good knowledge base.
- Switched to Wago and suffered thru many firmware upgrades until our programs finally stopped locking up. We had this problem for over a year while we were rolling out equipment.
- Having the same issue with CodeSys support on Wago. A lot of back and forth about if the program is"wrong" or the platform can't support it. Some of our guys like pushing Wago to improve but I would rather focus our efforts on improving our product.
- Many man-hours lost working on ModBus communications. We have found them too slow for many real-time situations. We have nearly turned ModBus communications into cottage industry.
- We use an older version of CodeSys, v2.3, but my understanding is that Wago cannot support the newer version.
- Just not used to such a steep learning curve and having to search so hard for information. I have programmed in many other platforms but have not had to spend nearly as much time as I do now.
Hey DrewE, I do understand what you'r feeling, rolling out machines with an unjustified proper functioning of the program loaded in it. Which might result to techs going back in the field to update program, firmware or fix something.
What I am understanding from your second post is that, you've got multiple problem to be dealt with.
- First! like previous comments explained, Modbus is a sloppy, lazy protocol. If you'r looking for response time, Modbus won't give you, especially if you have couple of drives daisy-chained in you architecture (Not quite sure what your system entails). Best option is EtherNet IP or Modbus TCP/IP can come close.
Secondly! CodeSys is a fantastic platform, if you know how to program it. Spend a little time get up to speed if you firm cannot move to AB or other in-house names. Programming over different protocols could be tactical. I had used CodeSys 2.3 on Wago PLC 7 years ago on water ballast system, worked just fine.
Thirdly! consider reviewing your code. Are you using FBs (R/W, single or double),
(not quite sure such FB in your ladder program). Years back I had come across someone using single-r/w FB to execute multiple r/w command.
Fourthly!, Touch base with your distributor, and/or Wago field application engineer for help, if phone support couldn't help. They should have one in your territory.