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 2022 2023 <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 2022 2023 <2024> |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: EPICS PLC5 Support |
| From: | Ralph Lange via Tech-talk <tech-talk at aps.anl.gov> |
| To: | EPICS Tech Talk <tech-talk at aps.anl.gov> |
| Date: | Fri, 23 Feb 2024 10:05:31 +0100 |
This Message Is From an External Sender
This message came from outside your organization.
Hi Joshua,
Let me try a partial answer...
On Thu, 22 Feb 2024 at 15:44, Josh West via Tech-talk <tech-talk at aps.anl.gov> wrote:
1. Is the current build stable enough to run indefinitely with no EPICS-caused outages?
Tough question for a system that only has been around for 40 years. :-)
Most systems in EPICS installations undergo regular electrical maintenance procedures (typically once a year). But there may be a few systems (think telescopes, cryo plants) with long runners.
@all: Does anyone have outstanding long-runner IOCs?
Personally, I have a lot of trust in the core parts of the IOC software. Resource leaks and instabilities usually turn up and get fixed pretty quickly.
It's locally developed drivers and Device Supports that often get a lot less used and tested. Since they run in the same process as the core parts, a bug in a driver can degrade or crash your IOC process.
There are ways to run the IOC processes that would restart them immediately in the unlikely case of a crash, so that clients would just see a disconnect/reconnect flicker.
Also, system architecture can help. E.g., handling the long upstream connection and health monitoring in one IOC and the local controller connection in a separate one wouldn't leave the remote end blind if the controller IOC is in trouble.
The EPICS network protocols (Channel Access, PV Access) are scalable and robustly handling disconnect/reconnect situations. If you have outages in your network, the EPICS layer will not significantly add to it.
5. Are there any plans/projects to implement more stringent information security mechanisms into the system (e.g., something consistent with NIST, IEC, etc. for critical infrastructure)?
There is a current project to add TLS (that would be IEC 62351) to the newer PV Access protocol. Prototype stage. Certificate handling is the hard part that's still ahead. (See the last talk during the last EPICS Collaboration Meeting [1] for more details.)
The older Channel Access protocol can be run through SSH tunnels to achieve a comparable level of security.
Cheers,
~Ralph
~Ralph
- Replies:
- Re: [EXTERNAL] EPICS PLC5 Support Hartman, Steven via Tech-talk
- References:
- EPICS PLC5 Support Josh West via Tech-talk
- Navigate by Date:
- Prev: Re: [EXTERNAL] Epics support for DIGITEL MPCQ Ion Pump Controller and Televac MX 200 Vacuum Controller Mrinal Bera via Tech-talk
- Next: Re: [EXTERNAL] Epics support for DIGITEL MPCQ Ion Pump Controller and Televac MX 200 Vacuum Controller Smith, Martin 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 2022 2023 <2024>
- Navigate by Thread:
- Prev: EPICS PLC5 Support Josh West via Tech-talk
- Next: Re: [EXTERNAL] EPICS PLC5 Support Hartman, Steven 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 2022 2023 <2024>
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·