EPICS Controls Argonne National Laboratory

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  <20212022  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  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: CS-Studio (Phoebus) Dynamic Population of PVs in GUI
From: "Pearson, Matthew R. via Tech-talk" <tech-talk at aps.anl.gov>
To: "Manoussakis, Adamandios" <manoussakis1 at llnl.gov>
Cc: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Fri, 15 Jan 2021 16:44:35 +0000

Hi,

 

If you’re talking about N*M*Z waveforms, it can depend on how big N, M and Z are. If there’s not too many then you can put multiple waveforms on one screen (depending on waveform size and update rate). Or, you could have a common screen having a single waveform on it, and you can open that via buttons which pass macros in to define the PV name.

 

If you really need a menu to select N, then M, then Z, then one option would be to construct the PV name on the IOC database side, then set an INP link in a subarray (which can point to any of the waveforms defined by N, M and Z). Then the screen only has to contain a single high level PV for the subarray record. That would avoid CS-Studio scripts, although it would be possible in a client script I think that would be the least preferable solution long term (for example, you may have to update the script periodically, or re-write it for new clients).

 

Cheers,

Matt

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of Manoussakis, Adamandios via Tech-talk
Sent: Thursday, January 14, 2021 5:29 PM
To: EPICS tech-talk <tech-talk at aps.anl.gov>
Subject: [EXTERNAL] CS-Studio (Phoebus) Dynamic Population of PVs in GUI

 

Hello All,

 

I was curious what the best way to go about populating our GUIs in CS Studio when we are dealing with multiple PVs that share a common attributes.  Such as

 

Device1:Subdevice1:Signal1

Device1:Subdevice1:Signal2

 

Device1:Subdevice2:Signal1

Device1:Subdevice2:Signal2

 

And so forth for N devices M Subdevices Z Signals

 

I was thinking to use macros that pull from drop down menus which would then populate the correct PVs for say specific waveforms.

 

Dropdown menu to select Device #, Dropdown menu to select subdevice # and then populate the PV waveforms for the correct subset I selected.

 

I only just started to use CS Studio and I think this seems possible but wasn’t completely sure.  I also saw that I could write some python scripting and have it run in CS Studio to parse out and place the correct PVs depending on drop down selections but wanted to check in first and see how people have been using it.

 

Thanks

 

 


References:
CS-Studio (Phoebus) Dynamic Population of PVs in GUI Manoussakis, Adamandios via Tech-talk

Navigate by Date:
Prev: CS-Studio (Phoebus) Dynamic Population of PVs in GUI Manoussakis, Adamandios via Tech-talk
Next: PVXS release 0.1.1 Michael Davidsaver 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  <20212022  2023  2024 
Navigate by Thread:
Prev: CS-Studio (Phoebus) Dynamic Population of PVs in GUI Manoussakis, Adamandios via Tech-talk
Next: Re: CS-Studio (Phoebus) Dynamic Population of PVs in GUI Michael Davidsaver 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  <20212022  2023  2024 
ANJ, 15 Jan 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·