Hi folks...

I know I should be watching the list discussions more as this one MAY have already come up, even possibly indirectly...

Has anyone given ANY thoughts to the idea(s) of interoperability between whatever program we end up with and say, a Modicon Quantum or like the AB PLC5 or ControlLogix? Is this something that we WANT to approach (provided we get blessings from the appropriate manufacturers). FWIW, this should not be a problem with Modicon since they have their ethernet (and modbus) protocol freely documented (and available) on their web site. There are, of course, others to consider as well (Omron, Siemens, etc).

Any thoughs, ideas, comments (but please, no flames - this was NOT a troll).

Ron Gage - Saginaw, MI
([email protected])
_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc

 

Ron,

In an earlier post I proposed that we adopt a modular design where individual RLD, SFC, etc. programs and I/O drivers would be loaded at run time. In such a design you would only be a simple device driver away from interpretability.

I believe that provisions for interpretability are a must! Thanks for your comments.

rickj

_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo

 

I have given this quite a lot of thought although I have not posted anything regarding such.

It is likely that the first thing I code will be a "driver" to communicate with Mitsi A series PLC's. There protocol is freely documented, at least for serial links (RS232 and RS485).

Dave West E-Mail: [email protected]
Semiras Projects Ltd. PGP public key available on request.


_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc