EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
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  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 
<== Date ==> <== Thread ==>
Subject: Re: Sequencer interpretation of PV names with {,} characters
From: "Kasemir, Kay via Tech-talk" <tech-talk at aps.anl.gov>
To: "Ivashkevych, Oksana" <oksana at bnl.gov>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Fri, 3 Nov 2023 15:42:22 +0000

If there’s no way to escape macros, you might have to connect programmatically, see “pvAssign” in sequencer manual:

 

/* Initially, don’t assign */

double pv;

assign pv to “”;

 

 

  /* Then later in some “init” state */

  pvAssign(pv, “XF:BM-ES{Psh_blade1}Pos”);

  pvMonitor(pv);

 

 

From: Kasemir, Kay <kasemirk at ornl.gov>
Date: Friday, November 3, 2023 at 11:38 AM
To: Ivashkevych, Oksana <oksana at bnl.gov>, tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Re: Sequencer interpretation of PV names with {,} characters

SNL uses {macro} for macros, like the shell or database would use $(macro).

Not sure if there’s a way to escape curly brackets like “\{not_a_macro\}” …

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Ivashkevych, Oksana via Tech-talk <tech-talk at aps.anl.gov>
Date: Friday, November 3, 2023 at 11:30 AM
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: [EXTERNAL] Sequencer interpretation of PV names with {,} characters

Hello,

The PV names I would like to link to have {, } inside their names, e.g “XF:BM-ES{Psh_blade1}Pos”.

It appears that the sequencer module does not like the curly brackets.

 

The PV name inside my runTest.st file compiles well, but when I run the sequencer, the PV in question does not connect, with errors:

 

sevr=minor runTest[0](after 0 sec): assigned=1, connected=0, monitored=1, got monitor=0

 

Everything works if a PV does not have  {} in its name.

 

I was wondering if someone could comment on it, where it could be happening, and if it is possible to patch may be.

 

Thank you

Oksana  

Replies:
RE: Sequencer interpretation of PV names with {,} characters Ivashkevych, Oksana via Tech-talk
References:
Sequencer interpretation of PV names with {,} characters Ivashkevych, Oksana via Tech-talk
Re: Sequencer interpretation of PV names with {,} characters Kasemir, Kay via Tech-talk
Navigate by Date:
Prev: Re: Sequencer interpretation of PV names with {,} characters Kasemir, Kay via Tech-talk
Next: Re: Get the type of a PV in C++ API Veseli, Sinisa 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  2021  2022  <2023>  2024 
Navigate by Thread:
Prev: Re: Sequencer interpretation of PV names with {,} characters Kasemir, Kay via Tech-talk
Next: RE: Sequencer interpretation of PV names with {,} characters Ivashkevych, Oksana 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  2021  2022  <2023>  2024 
ANJ, 03 Nov 2023 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·