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: Re: mbboDirect vs. autosave
From: Andrew Johnson <[email protected]>
To: <[email protected]>
Date: Tue, 2 Dec 2014 11:57:57 -0600
Hi Eric,

The mbboDirect record was a bit of a mess in 3.14, it didn't always
behave as it should when you try using it in a way that the original
author didn't think about. I cleaned up both mbb*Direct record types for
the 3.15 release but that did change their behaviour somewhat in places.
The Release Notes describe what changed including fixing some of the
things you describe below.

I realize that this information doesn't help you immediately, I'm just
letting you know that the new release should be better when you get the
chance to upgrade to it.

- Andrew


On 12/01/2014 05:17 PM, Eric Norum wrote:
> A while back there were some threads discussing problems with mbboDirect
> record initialization.  Those problems appear to extend to
> autosave/restore, too.
> 
> I have an R3.14.12.3 IOC with an mbboDirect record of which I use four
> individual bits (4 through 7).  I originally had
> record(mbboDirect, "$(P)$(R)EVR:event122trig") {
>     field(DESC, "Heartbeat")
>     field(DTYP, "asynUInt32Digital")
>     field(OUT,  "@asynMask($(PORT) 0x37A 0xFF 0)")
>     field(NOBT, "8")
>     field(MASK, "0xFF")
>    info(autosaveFields_pass0, "VAL")
> }
> in the database, but that didn’t seem to work.  Everything got set back
> to 0 on IOC startup even though the autosave life contains a non zero
> value (e.g. 128 or 192).
> It appears that
>     info(autosaveFields_pass0, "B4 B5 B6 B7 VAL”)
>  works, but feels like a bit of a hack to me.
> Is there any better way of handling this?
> 
> Also, a client doing a caput to an mbboDirect record .VAL field doesn’t
> update the .Bx fields.  I think that was discussed previously, though.
> 
> Perhaps I should just replace the mbboDirect with a longout and make
> clients deal with all the bit testing/setting/clearing themselves.
> -- 
> Eric Norum
> [email protected] <mailto:[email protected]>
> 

-- 
People everywhere confuse what they read in newspapers with news.
-- A. J. Liebling

References:
mbboDirect vs. autosave Eric Norum

Navigate by Date:
Prev: RE: edm questions Mark Rivers
Next: Using EPICS with Attocube stepper motor Ana Malagon
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: mbboDirect vs. autosave Eric Norum
Next: mbboDirect vs. autosave Eric Norum
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 ·