Ernest, Autosave doesn't (currently) permit a request file to be used
more than once in a create_*_set() call, because I neglected to code for
this possibility when I added macro substitution. You can, nevertheless,
have nearly the effect you want, in the following way:
Make files I'll call all_motor_positions.req, and all_motor_settings.req,
with the following content:
all_motor_positions.req:
-----------------------
file motor_positions.req M=CM1:motor
file motor_positions.req M=CM2:motor
...
all_motor_settings.req:
----------------------
file motor_settings.req M=CM1:motor
file motor_settings.req M=CM2:motor
...
Include the following function calls in place of the ones in your email:
create_monitor_set("all_motor_positions.req", 5, "P=U01:")
create_monitor_set("all_motor_settings.req", 5, "P=U01:")
The include files, motor_positions.req and motor_settings.req, must occur in
a directory included in autosave's requestfile path to be found. (See
set_requestfile_path(), in autosave's docs.)
I'll look into what would be required for autosave to work as your first try
expects. It probably won't be pretty, because (IIRC) autosave has the notion
of a file name directly representing a save set buried pretty deeply into its
structure. Also, it won't happen until after synApps 5.4.
Tim
Ernest L. Williams Jr. wrote:
Hi,
I am getting the following error from autosave version 4-4:
==========================================================
create_monitor_set("motor_positions.req", 5, "P=U01:, M=CM1:motor")
0x00000000 (0)
create_monitor_set("motor_settings.req", 30, "P=U01:, M=CM1:motor")
0x00000000 (0)
create_monitor_set("motor_positions.req", 5, "P=U01:, M=CM2:motor")
save_restore:create_data_set: 'motor_positions.req' already in c
mode0xffffffff (-1)
create_monitor_set("motor_settings.req", 30, "P=U01:, M=CM2:motor")
save_restore:create_data_set: 'motor_settings.req' already in c
mode0xffffffff (-1)
create_monitor_set("motor_positions.req", 5, "P=U01:, M=CM3:motor")
save_restore:create_data_set: 'motor_positions.req' already in c
mode0xffffffff (-1)
create_monitor_set("motor_settings.req", 30, "P=U01:, M=CM3:motor")
save_restore:create_data_set: 'motor_settings.req' already in c
mode0xffffffff (-1)
================================================================
I guess this means that it is not reentrant like the sequencer?
In any case, we will do the request file like this:
========= motor_positions.req =================
$(P):CM1:motor.DVAL
$(P):CM1:motor.OFF
$(P):CM2:motor.DVAL
$(P):CM2:motor.OFF
$(P):CM3:motor.DVAL
$(P):CM3:motor.OFF
==========================================
Thanks,
Ernest
--
Tim Mooney ([email protected]) (630)252-5417
Beamline Controls & Data Acquisition Group
Advanced Photon Source, Argonne National Lab.
- References:
- Error from Autosave version 4-4 Ernest L. Williams Jr.
- Navigate by Date:
- Prev:
Error from Autosave version 4-4 Ernest L. Williams Jr.
- Next:
RE: solaris-x86 build error on 3.14.10 Mark Rivers
- 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:
Error from Autosave version 4-4 Ernest L. Williams Jr.
- Next:
sscan compile error on base 3.14.10 on linux John M. Skinner
- 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
|