EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Communication between EPICS and PLCs at your facility?
From: "Kasemir, Kay via Tech-talk" <tech-talk at aps.anl.gov>
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>, "Samadli, Ayaz" <ayaz.samadli at xfel.eu>
Date: Wed, 6 Jul 2022 12:57:42 +0000
Hi Ayaz,

I'd say there are at least two aspects to EPICS PLC integration.

First is of course the basic protocol, which depends on the PLC that you're using.
In the US, Allen Bradley is quite common, and there's an EPICS device driver for that.
In Europe, Siemens is prevalent, and there's an EPICS device driver for that.
There are many more, just look for "PLC" on https://epics.anl.gov/modules/manufacturer.php
Those device drivers allow you to read some number from a PLC into an EPICS analog input record, or a bit from the PLC into a binary input record, or to write a number from an EPICS analog output record to the PLC and so on. Each PLC model and the corresponding EPICS support have some details of how you may have to place the data on the PLC for efficient communication.

The second aspect of PLC integration is deciding who's in charge. Do you want to read a number from the PLC into an analog input record, and then add alarms to that record, with interlock logic on the IOC, so the PLC is just I/O and all the rest is handled in EPICS? Or do you handle the I/O, the alarming, the interlocks all on the PLC, so the IOC reads the current value into an analog input, the OK/trouble indication into a binary input, the alarm threshold into another analog input? Do you allow changing the alarm threshold on the PLC via an analog output record on the IOC? Can both the EPICS IOC and some PLC touch screen write the alarm threshold?
Putting logic into the IOC means it's more accessible. At least people who know EPICS can inspect the alarm thresholds of an analog input record at runtime. If you move them into the PLC, you can't see any of it unless you have the source code for the PLC, and/or make each piece of information available via additional records.
One approach is to place interlock logic onto the PLC, where you might argue that it's more 'secure'. Alarm logic on the other hand is meant to help operators do their job, but alarms don't perform any safety critical function, so they're better handled on the IOC where they are more accessible and easier to implement/modify.

Cheers,
Kay


From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Samadli, Ayaz via Tech-talk <tech-talk at aps.anl.gov>
Sent: Wednesday, July 6, 2022 5:46 AM
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: [EXTERNAL] Communication between EPICS and PLCs at your facility?
 
Dear All,

At the European XFEL, we have an R&D project to replace the current custom communication protocol between our in-house SCADA system, Karabo, and PLCs (Beckhoff). I would be interested in your recommendations and current implementations for communications between EPICS (or other SCADA systems) and PLCs at your facility. Can you please share your experiences and suggestions with us?

If you want to get more details, please feel free to reach out to me.

Best Regards,
Ayaz


Ayaz Samadli

Controls - Control Software Engineer


European XFEL GmbH

ayaz.samadli at xfel.eu

www.xfel.eu


Headquarters: Holzkoppel 4, 22869 Schenefeld, Germany


Managing Directors: Prof. Dr. Robert Feidenhans’l, Dr. Nicole Elleuche

Registered as European X-Ray Free-Electron Laser Facility GmbH at

Amtsgericht Hamburg, HRB 111165

References:
Communication between EPICS and PLCs at your facility? Samadli, Ayaz via Tech-talk

Navigate by Date:
Prev: Re: Communication between EPICS and PLCs at your facility? Torsten Bögershausen via Tech-talk
Next: C++ Software Engineer opportunity at ITER Gunion Robert via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024 
Navigate by Thread:
Prev: Re: Communication between EPICS and PLCs at your facility? Timo Korhonen via Tech-talk
Next: C++ Software Engineer opportunity at ITER Gunion Robert via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  <20222023  2024 
ANJ, 14 Sep 2022 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·