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  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: PVManager Re: importing "org.csstudio.utility.pv" in BOY Jython scripts
From: "Kasemir, Kay" <[email protected]>
To: Hovanes Egiyan <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Tue, 15 Apr 2014 12:15:18 -0400
Hi:

Creating PVs inside BOY scripts is problematic.

The intended use case for BOY, being a display tool, is:
Select widget, enter PV name, done.
-> BOY connects to the PVs, widget handles received values.

Maybe change the widget defaults to not be alarm sensitive etc.

In rare cases, you can use scripts to do things which would have been impossible with for example MEDM, EDM:
Select widget, enter PV name, add script, configure input/output PVs for the script, done.
-> BOY connects to the PVs, sends received values to script, you handle the values in the script, maybe updating widget properties in response.

If you _create_ PVs within the script, you run into many pitfalls related to the connection handling, the PV cleanup, or what you experience now, which is the complete update of how PVs are handled inside CSS between versions 3.1 and 3.2.
 From 3.2 on, org.csstudio.utility.pv has been replaced with the PVManager, http://pvmanager.sourceforge.net

So now you would have to start your script like this:

use  "org.epics.pvmanager.."
… and then read the PVManager examples of how to use it.

Sorry,
Kay


On Apr 15, 2014, at 11:40 AM, Hovanes Egiyan <[email protected]> wrote:

> Hi,
> 
> we have a quite large number of BOY OPI-s that use Jython scripts. These 
> Jython scripts
> use  "org.csstudio.utility.pv", namely PVFactory,  so they contain the 
> following line:
> 
> from org.csstudio.utility.pv import PVFactory
> 
> Until now we have been using basic EPICS CSS 3.1.7 build from SNS , and 
> now we would
> like to use the recent version 3.2.16. But what happens now with that 
> version is that Jython fails
> to find the "org.csstudio.utility.pv" on the line shown above. That 
> plugin is incuded in the plugin
> directory, and when I explicitly append the jar-file  to the sys.path, 
> then the scripts work.
> At this time I do not want to go into each script file and add a line to 
> append the jar
> file. Instead, I was wandering if I can recompile EPICS CSS from SNS 
> source in such a way that I do
> not need to specify the "org.csstudio.utility.pv" path myself in the 
> scripts. Just getting the source for 3.2.26
> and making the "org.csstudio.basic.epics.product" produces the same 
> result. Is there something
> simple that I need to change in Eclipse when building the product to 
> have that jar-file included in the list
> when Jython loads?
> 
> Thanks,
>    Hovanes Egiyan.
> 



References:
importing "org.csstudio.utility.pv" in BOY Jython scripts Hovanes Egiyan

Navigate by Date:
Prev: importing "org.csstudio.utility.pv" in BOY Jython scripts Hovanes Egiyan
Next: extending of visa application Yuan He
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: importing "org.csstudio.utility.pv" in BOY Jython scripts Hovanes Egiyan
Next: extending of visa application Yuan He
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 17 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·