Experimental Physics and
Industrial Control System

Hi Jeroen,

 

• Now I would like to do a test to be able to connect to an PLC. We use ABB PLCs via modbus over IP at the moment. So, it would be nice to have a way to use that same setup with EPICS. Does anyone know of an IOC for this type off communication between EPICS and PLCs?

 

There is an EPICS driver for Modbus communications, and many of us use it to communicate with PLCs.

 

https://github.com/epics-modules/modbus

 

It contains an example IOC and example startup scripts that communicate with Koyo PLCs.  For example this one:

https://github.com/epics-modules/modbus/blob/master/iocBoot/iocTest/Koyo1.cmd

 

I am using this driver to talk to Allen Bradley SLC500 PLCs over Modbus for our beamline equipment protection systems.

 

This is the script that configures the Modbus driver for that system:

https://github.com/CARS-UChicago/GSECARS-EPICS/blob/master/iocBoot/ioc13ida_linux/eps_modbus.cmd

 

The EPICS records are defined in the .substitutions files in that same directory.

 

Let me know if you have any questions.

 

Mark

 

 

 

 

Hi,

We at Partrec are investigating if EPICS is useable for us. I have done an EPICS base install on an Ubuntu server following the instructions on docs.epics-controls.org. And did some tests with creating a sample IOC and caput that all seems to work fine.

Now I would like to do a test to be able to connect to an PLC. We use ABB PLCs via modbus over IP at the moment. So, it would be nice to have a way to use that same setup with EPICS. Does anyone know of an IOC for this type off communication between EPICS and PLCs?

 

Hope you can help.

Jeroen Schwab

De inhoud van dit bericht is vertrouwelijk en alleen bestemd voor de geadresseerde(n). Anderen dan de geadresseerde(n) mogen geen gebruik maken van dit bericht, het niet openbaar maken of op enige wijze verspreiden of vermenigvuldigen. Het UMCG kan niet aansprakelijk gesteld worden voor een incomplete aankomst of vertraging van dit verzonden bericht.

The contents of this message are confidential and only intended for the eyes of the addressee(s). Others than the addressee(s) are not allowed to use this message, to make it public or to distribute or multiply this message in any way. The UMCG cannot be held responsible for incomplete reception or delay of this transferred message.