<html><body><div style="font-family: tahoma,new york,times,serif; font-size: 14pt; color: #009900"><div><br></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Wesley Moore" <wmoore@jlab.org><br><b>To: </b>"Nathan Baltzell" <baltzell@jlab.org><br><b>Cc: </b>"Peter Bonneau" <bonneau@jlab.org>, "Amrit Yegneswaran" <yeg@jlab.org>, "Brian Eng" <beng@jlab.org><br><b>Sent: </b>Wednesday, April 26, 2017 11:41:06 AM<br><b>Subject: </b>Re: CSS GUI for Hall B FT Interlock System<br></div><div><br></div><div data-marker="__QUOTED_TEXT__">Gateway is now updated to pick up 129.57.86.160. The GUI now resolves fine on my end. <br><br>Peter,<br><br>On the 'Thresholds and Enable Control Settings' tab, is disabled supposed to be green? Just making sure this isn't some artifact of the a different cs-studio version.<br><br>Wesley<br><br>----- Original Message -----<br>> From: "Nathan Baltzell" <baltzell@jlab.org><br>> To: "Peter Bonneau" <bonneau@jlab.org><br>> Cc: "Wesley Moore" <wmoore@jlab.org>, "Amrit Yegneswaran" <yeg@jlab.org>, "Brian Eng" <beng@jlab.org><br>> Sent: Wednesday, April 26, 2017 11:10:26 AM<br>> Subject: Re: CSS GUI for Hall B FT Interlock System<br><br>> Hi Peter,<br>> <br>> Thanks a lot for the info. Sure, if there’s some new big issues with client<br>> mode, then we certainly should try the alternative, and will be good to know<br>> how these issues will affect the existing gas system in the future.<br>> <br>> Off hand I don’t remember all the details, but I think there were previously at<br>> least some missing alarm fields (but your list looks complete). It may be that<br>> newer versions are better, and/or that the EPICS side of the interlock system<br>> is simple enough regardless. Anyway, I’m not opposed to running in server mode<br>> if we confirm it all works ok. One thing that we usually want is to make sure<br>> autosave/restore of alarm limits and severities upon ioc (crio) reboot works;<br>> maybe you already have that.<br>> <br>> I’ll take a look at the PV list and get back to you next week (I’m out for the<br>> rest of the week). A channel access gateway should be pointing to your crio<br>> shortly, and your screen is linked from the FT main menu (which I need to clean<br>> up one day, along with some of the other growing menus ...).<br>> <br>> Thanks,<br>> Nathan<br>> <br>> <br>> <br>> On Apr 26, 2017, at 8:38, Peter Bonneau <bonneau@jlab.org> wrote:<br>> <br>>> Hi Nathan,<br>>> <br>>> The Excel file named FT Hardware Interlock System Design Documentation.xlsx on<br>>> the website listed below has a tab with the EPICS PV's.<br>>> <br>>> https://userweb.jlab.org/~bonneau/FT%20Hardware%20Interlock%20System/System%20Documentation/<br>>> <br>>> The IP address for the FT cRio is 129.57.86.160.<br>>> Regarding the cRio as an EPICS server or client, Brian has found a problem while<br>>> using the client configuration on the gas system. He's discovered it doesn't<br>>> always work on the newer cRio processors like the one used on the FT. He's been<br>>> looking into this problem and has submitted a service ticket to National<br>>> Instruments requesting a fix for this bug. So far, NI has not resolved<br>>> this issue.<br>>> <br>>> The FT cRio was configured as an EPICS server to see if we can duplicate this<br>>> problem in this configuration. We use the EPICS server configuration in other<br>>> critical cRio applications such as the Torus and Solenoid FastDaq. I've been<br>>> working on the FT cRio as an EPICS server for a week and haven't been able to<br>>> duplicate this problem yet.<br>>> Do we know which fields are missing from the NI EPICS implementation? I'd like<br>>> to submit a service ticket request to NI to implement any missing fields. At<br>>> the most, the interlock systems will have ~ 7 Boolean signals each in the<br>>> alarm handler to indicate the operating status of the system.<br>>> The NI EPICS fields implemented for a Boolean are: OSV, SEVR, STAT, VAL, ZSV.<br>>> <br>>> The NI EPICS fields implemented for a double are: HHSV, HIGH, HIHI, HSV, LLSV,<br>>> LOLO, LOW, LSV, SEVR, STAT, VAL.<br>>> <br>>> Thanks,<br>>> <br>>> Peter<br>>> <br>>> On 4/25/2017 10:08 AM, Nathan Baltzell wrote:<br>>>> Thanks Peter,<br>>>> <br>>>> Yes, it is definitely important to have all DSG's Hall B hardware interlocks in<br>>>> EPICS. We weren't aware you were also working on cs-studio user interfaces,<br>>>> but that is certainly welcome!<br>>>> <br>>>> <br>>>>> A softIOC is not needed since the FT Interlock cRio is configured as an EPICS<br>>>>> server (IOC).<br>>>>> <br>>>> I’m not so sure about this. On cRios, one thing we've found necessary in the<br>>>> past, in order to get full EPICS functionality, is to have them read/write<br>>>> (e.g. at 1 Hz) to duplicate soft channels (with different names) on a real<br>>>> EPICS ioc. This is due to incomplete EPICS implementation on the cRio/labview,<br>>>> e.g. alarm fields. Brian has helped with this previously for all the gas cRios<br>>>> in Hall B.<br>>>> <br>>>> It would be nice if we can modify and shorten the PV names on this softioc from<br>>>> what you have in your pdf, in order to fit the existing conventions in the rest<br>>>> of Hall B EPICS. Can you provide the PV list in a format that is easily<br>>>> modifiable (e.g. excel, ascii)? Then we can converge on the names and<br>>>> generate the softioc.<br>>>> <br>>>> Also, we'll need to know this cRio’s ip address.<br>>>> <br>>>> And later we can discuss what needs to go in the alarm handler ...<br>>>> <br>>>> Thanks,<br>>>> Nathan<br>>>> <br>>>> <br>>>> <br>>>> <br>>>> On Apr 25, 2017, at 6:54 AM, Peter Bonneau<br>>>> <bonneau@jlab.org><br>>>> wrote:<br>>>> <br>>>> <br>>>>> Wesley,<br>>>>> <br>>>>> Under the Detector/FT menu in the clas12_menu.opi file, there needs to be GUI's<br>>>>> for the FT Interlock system.<br>>>>> The CSS test GUI we made to test the FT EPICS interface could be used, however<br>>>>> it does not look like the other existing CLAS12 GUI's (compact, dark colored<br>>>>> background, etc.).<br>>>>> In the new SVT svtOverview.opi, a section for hard interlocks has been added.<br>>>>> GUI's similar to this is needed for the FT.<br>>>>> A softIOC is not needed since the FT Interlock cRio is configured as an EPICS<br>>>>> server (IOC).<br>>>>> Regarding the alarm handler, there will be a few signals for the handler to<br>>>>> report the status of the system. We'll list them later after talking to the FT<br>>>>> group that is coming in May.<br>>>>> DSG will be implementing a similar new Hardware Interlock System for the RICH in<br>>>>> the upcoming few months. We'll also be upgrading the existing SVT Hardware<br>>>>> Interlock System to include the EPICS interface that will use the GUI's that<br>>>>> have been started already. I'll mention these projects in the next slow<br>>>>> controls meeting.<br>>>>> Peter<br>>>>> <br>>>>> On 4/24/2017 11:01 AM, Wesley Moore wrote:<br>>>>> <br>>>>>> Peter,<br>>>>>> <br>>>>>> It's not clear what you are asking. It looks like you are pretty far along.<br>>>>>> The older version of cs-studio you are using may have compatibility issues<br>>>>>> with the latest version we are testing. But that's easy to try.<br>>>>>> <br>>>>>> The documentation and block diagram you doesn't really answer these things:<br>>>>>> <br>>>>>> Do you need a softIOC to write these PVs too or did you make one?<br>>>>>> Do you need the alarm handler setup?<br>>>>>> <br>>>>>> You still have a standing invitation to the slow controls meetings. But as<br>>>>>> Brian/George did for gas systems, you can keep us in the loop without<br>>>>>> attending.<br>>>>>> <br>>>>>> Wesley<br>>>>>> <br>>>>>> From: "Peter Bonneau"<br>>>>>> <bonneau@jlab.org><br>>>>>> <br>>>>>> To: "Wesley Moore"<br>>>>>> <wmoore@jlab.org><br>>>>>> <br>>>>>> Cc:<br>>>>>> dsg-ft@jlab.org<br>>>>>> <br>>>>>> Sent: Monday, April 24, 2017 9:08:21 AM<br>>>>>> Subject: CSS GUI for Hall B FT Interlock System<br>>>>>> Hello Wesley,<br>>>>>> <br>>>>>> The Hall B FT group needs a CSS GUI for the FT Hardware Interlock System. This<br>>>>>> GUI would be integrated into the other FT EPICS screens.<br>>>>>> <br>>>>>> The FT Hardware Interlock System is an independent backup system which can<br>>>>>> disable the LV, HV, and FT chiller. The system can be monitored and trip<br>>>>>> thresholds adjusted via Labview and/or an EPICS GUI.<br>>>>>> DSG has completed the initial programming on the cRio for the EPICS interface.<br>>>>>> Located in the EEL building and configured as an EPICS server, the PV signals<br>>>>>> are now available via the Hall B .86 subnet. The EPICS interface has been<br>>>>>> tested via a CSS test GUI.<br>>>>>> Detailed information on the system configuration, hardware, EPICS PV signal<br>>>>>> names, CSS test screen .OPI file, and LabVIEW interface can be found on the FT<br>>>>>> Hardware Interlock System website here:<br>>>>>> <br>>>>>> https://userweb.jlab.org/~bonneau/FT%20Hardware%20Interlock%20System/<br>>>>>> <br>>>>>> Peter<br>>>>>> <br>>>>>><br></div></div></body></html>