EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  <19981999  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  <19981999  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: MBBI, SHFT, and GDCT
From: [email protected] (Ralph Lange)
To: [email protected] (Marty Kraimer)
Cc: [email protected] (EPICS Tech-Talk)
Date: Tue, 18 Aug 1998 11:15:56 +0200 (METDST)
> I am not sure what is being asked. Is this it?
> 
> The change will be made to mbbiRecord, mbbiDirectRecord, mbboRecord, and
> mbboDirectRecord.
> 
> For each, SPC_NOMOD will no longer be specified for SHFT.

This will enable Raw Soft Supported records pointing to arbitrary bit
subsets of other records.

> For all existing mbbi, mbbo, mbbiDirect, mbboDirect device support in
> base statements like the following
> 
>  pmbbo->shft = pvmeio->signal;
> 
> will be changed to
> 
>   if(pmbbo->shft==0) pmbbo->shft = pvmeio->signal;
> 
> 1) Do we really want to do the later?

I suggest not doing this change:

If SHFT depends on the INP/OUT address field, Device Support should set
it. Not setting it when SHIFT <> 0 will allow rubbish in the database and
lead to errors that are hard to track down. Setting SHFT for Raw Soft
Support will be allowed anyway, since Raw Soft Support won't override it.

I guess overwriting SHFT unconditionally will minimize the change in the
system's behaviour.

> 2) What about all the support not in base?

Doesn't have to be changed, then. (I like that aspect...)

> 3) Where will this be documented?

Release Notes plus Record Reference Manual. Since this only affects Raw
Soft Support, I would regard it a minor change.
 
> This also does not seem to address Bob Dalesio's concern about what
> happens when links are modified dynamically.

Bob wants to modify hardware links dynamically. This is an entirely new
feature, which is strongly device (and Device Support) dependent and will
most likely only be available with certain Device Supports for a long, long
time.

The proper way to do this would be having the INP/OUT/NOBT fields SPC_MOD
(for hardware related records) and the Device Support recalculate SHFT and
MASK whenever these fields are changed. This would imply major changes to
Record and Device Support. Bob's approach of recalculating SHFT and MASK on
each process() may be sub-optimal in terms of performance, but ... well,
sounds reasonable until this feature is to be implemented generally.

> For bi, bo records signal is used to select bit in register. For
> mbbi,mbbi it was used to select low order bit in register. Do we really
> want to change this convention?

Not really!

Ralph

References:
Re: MBBI, SHFT, and GDCT Marty Kraimer

Navigate by Date:
Prev: Re: ADL file formats Peregrine McGehee
Next: Re: MBBI, SHFT, and GDCT Marty Kraimer
Index: 1994  1995  1996  1997  <19981999  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: MBBI, SHFT, and GDCT Marty Kraimer
Next: Re: MBBI, SHFT, and GDCT Marty Kraimer
Index: 1994  1995  1996  1997  <19981999  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, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·