Experimental Physics and
Industrial Control System

"Kasemir, Kay" <[email protected]> · Mon, 16 Mar 2015 16:41:55 +0000

Hi:

On Mar 16, 2015, at 12:04 PM, "Lauk Daniel Johannes (PSI)" <[email protected]<mailto:[email protected]>>
 wrote:
We developed a web-based GUI for this. I attached a screenshot.
If you’re interested, let me know.

Neat!

We have a related setup for beam lines. Our emphasis is on providing a way to start/stop IOCs as the devices on the beam line change, meant for users who add/remove beam line devices and need to enable/disable IOCs, but who don't necessarily work on IOC databases etc.

For a screenshot, see "IOC Control" slide in my presentation at the 2014 EPICS meeting in Lanzhou.
Our IOCs run under procServ. Compared to the PSI web interface, we leave the configuration (name of IOC, procServ port, startup script, ..) out of the web interface.
When we create a new IOC, we need to manually add it to some file on the beam line which lists all IOCs.

The idea of the web interface is to list all the available IOCs, to mark their desired state as active or not, and to update the actually running IOCs to the desired set of running IOCs.
For example, the IOC for a certain sample environment device can be marked as inactive while that piece of hardware is absent from the beam line.

Once somebody puts that device back onto the beam line, they can mark the IOC as "active" and start it.
Or push "update" which will start all IOCs that should be active but aren't, respectively stop all IOCs that are running but shouldn't be.
In case the Linux server gets rebooted, it will automatically start all IOCs that were last marked as 'active'.

Thanks,
Kay

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System