Hi Kay!
Your GUI looks very tidy. Your users must be very happy with that.
Regarding architecture, our system is in fact quite similar:
- Our use case is not end users at beamlines, though, but rather supporting our IOC developers.
- We have one configuration file on the host that controls, which IOCs should be running, and their parameters.
- There is a command line interface that works with this config file to start or stop the configured IOCs (also after the host rebooted) and display some status information.
- The web GUI will edit the config file appropriately and issue the commands to start or stop the IOCs, and also display the status information (e.g. PID).
- Because we only exchange the changed bits of configuration between web client and web server, we can work around stepping on each other's toes a lot better than with multiple text editor sessions.
Cheers,
DJ
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Kasemir, Kay
Sent: Montag, 16. März 2015 17:42
To: [email protected]
Subject: Re: Making EPICS IOC admin tasks easier for end-users?
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
- References:
- Re: Making EPICS IOC admin tasks easier for end-users? Kasemir, Kay
- Navigate by Date:
- Prev:
related to PLC driver priya tiwari
- Next:
RE: Making EPICS IOC admin tasks easier for end-users? tom.cobb
- 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:
Re: Making EPICS IOC admin tasks easier for end-users? Kasemir, Kay
- Next:
Asyn record proccessing( read functions) during PINI=YES Patel Jignesh
- 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
|