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  2021  <20222023  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  <20222023  2024 
<== Date ==> <== Thread ==>

Subject: mbbo & calcout for drive position management
From: "Crisp, Daniel via Tech-talk" <tech-talk at aps.anl.gov>
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Mon, 3 Oct 2022 21:20:30 +0000

Hello,


I'm just curious how to make this work better.


We have some variable drives with multiple 'things' on it. Since both the names of any 'thing' and the position of them can change, it's helpful to expose these fields to expert users and autosave them. Currently we're doing this with a combination of mbbo and calcout records.


Example: a variable drive with stripping foils at various positions

  record(mbbo, "REA_BTS41:STRIP_D1391:POS_SEL"){
      field(ZRST, "N/A")
      field(ONST, "DLC 500 nm")
      field(TWST, "DLC 2750 nm")
      field(THST, "DLC 3500 nm")
      field(FRST, "DLC 4000 nm")
      info(autosaveFields, "ZRST ONST TWST THST FRST")
      info(autosaveFields_pass0, "VAL")
  }
  record(calcout, "_REA_BTS41:STRIP_D1391:POS_calc"){
      field(INPA, "REA_BTS41:STRIP_D1391:POS_SEL CP NMS")
      field(INPB, "90")
      field(INPC, "-11")
      field(INPD, "-44")
      field(INPE, "-77")
      field(INPF, "-110")
      field(CALC, "A==1?C:A==2?D:A==3?E:A==4?F:B")
      field(OUT,  "REA_BTS41:STRIP_D1391:POS_CSET PP")
      info(autosaveFields, "B C D E F")
  }

I'm open to any suggestions people may have, if they think there's a better way to handle it, but my two main questions are:

    1. How can I keep these PVs and their fields from loading up as [INVALID - LINK_ALARM] on ioc reboot? I tried PINI, "YES", but that didn't seem to do the trick.

    2. The calcout input fields don't appear to be autosaving, I've tried editing the db code to just the letter--i.e. field(B, "90")--and I've tried listing autosave values like "INPB INPC" etc..


I'm sure I'm missing something simple.


Thanks!

-Dan


Replies:
Re: mbbo & calcout for drive position management Ralph Lange via Tech-talk

Navigate by Date:
Prev: Re: Understanding EPICS DSET-based driver Michael Davidsaver via Tech-talk
Next: Read and Write errors with VME-EVR-300 Hong, Ran 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  <20222023  2024 
Navigate by Thread:
Prev: Re: Understanding EPICS DSET-based driver Michael Davidsaver via Tech-talk
Next: Re: mbbo & calcout for drive position management Ralph Lange 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  <20222023  2024 
ANJ, 04 Oct 2022 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·