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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: Vacuum GUI: Vac. Status and Pumping Procedural Aid |
From: | Mark Rivers <[email protected]> |
To: | "'Crisp, Daniel'" <[email protected]>, "[email protected]" <[email protected]> |
Date: | Tue, 24 Feb 2015 18:23:00 +0000 |
Hi Daniel, Sorry for the delay in replying. I don’t know if you’ve received any replies to your post. I have attached screen shots of the Equipment Protection System on our beamlines at the APS. Our vacuum systems are protected by PLCs. The attached screen shots are from medm. You will see where requests can be made to open or close gate valves, etc. The vacuum is displayed in analog readings from the Pirani and cold-cathode
gauges, by binary setpoints on the gauges, and by the values read from the ion pumps. These screens also include water-flow, x-ray safety shutters and other non-vacuum related components. Mark From: [email protected] [mailto:[email protected]]
On Behalf Of Crisp, Daniel Hello, I’m curious if anyone has any examples of how their lab implements EPICS based Vacuum Screens. Any and all examples or ideas would be appreciated, but I’m particularly interested in screens detailing sections separated by beamline gate
valves. My intent is to develop these screen(s) in cs-studio. Besides controlling and monitoring pumps, valves, and gauges, my target user will: -likely be doing maintenance or upgrades to a section of beamline (replacing diagnostic drives, a variety of pumps, seals, or hoses; performing leak checks.. etc.). ----likely be focusing on this screen specifically to do the task at hand, conserving screen space isn’t as necessary as when considering controls for typical operations. -Not always remember all of the underlying PLC logic for interlock conditions. (# of seconds given to perform an action, which valves up or down stream need to be open, etc.) -Have to decide on an efficient pumping procedure that could vary by section and could also change depending on how the last user left the system. The resulting goal is to have an intuitive screen which additionally serves as a procedural aid.
I very much appreciate any and all input. Thanks! |
Attachment:
13BM_EPS.png
Description: 13BM_EPS.png
Attachment:
13ID_EPS.png
Description: 13ID_EPS.png