EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  <20012002  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  <20012002  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: Apropos making fields configurable
From: Marty Kraimer <[email protected]>
To: Benjamin Franksen <[email protected]>
Cc: EPICS Techtalk <[email protected]>
Date: Fri, 20 Jul 2001 13:53:20 -0500
Benjamin Franksen wrote:
> 
> Hello everyone,
> 
> good news: the changes needed to implement what was proposed for
> breakpoint conversion are very simple.
> .......



I think the following is the current status of the discussion.

RESOLVED PROBLEMS

I think we all agree to the following:

Making VAL configurable

The VAL field of the following files will include promptgroup(GUI_INPUTS)

aiRecord.dbd
biRecord.dbd
eventRecord.dbd
longinRecord.dbd
mbbiDirectRecord.dbd
mbbiRecord.dbd
stringinRecord.dbd

The VAL field of the following files will include promptgroup(GUI_OUTPUT)

aoRecord.dbd
boRecord.dbd
calcoutRecord.dbd
longoutRecord.dbd
mbboDirectRecord.dbd
mbboRecord.dbd
stringoutRecord.dbd

NOTES: 1) the string records already have this. 2)I will also make the changes
that allow hex values to be assigned to constant link fields.




Breakpoint tables when reaching end of table (Solution by Benjamin Franksen)

Make following change to dbLexRoutines.c

diff -r1.22 dbLexRoutines.c
812a813,816
>     if(number>1) {
>         pnewbrkTable->papBrkInt[number-1]->slope =
>             pnewbrkTable->papBrkInt[number-2]->slope;
>     }



UNRESOLVED Problems

Breakpoint table alarm problem when reaching end of table.
Benjamin suggested adding a field BRSV.
Instead of adding yet another field why not just change
     recGblSetSevr(pai,SOFT_ALARM,INVALID_ALARM)
to
     recGblSetSevr(pai,SOFT_ALARM,MAJOR_ALARM)
when cvtRawToEngBpt or cvtEngToRawBpt returns an error.


EOFF and ESLO cant be computed by softRaw support

Russell Redman suggests that we add fields RAWL and RAWF.
Instead of this why dont we just allow the user to assign values
to ESLO and EOFF, i.e. just add promptgroup definitions to the dbd files.


Allow a subroutine to do conversions (Suggestion by Rolf Keitel)

I think this is messy. When Andrew Johnson adds the extensible link support
(3.15) then I think this can be solved in a nice way.



Marty Kraimer


Replies:
Re: Apropos making fields configurable Benjamin Franksen
References:
RE: Apropos making fields configurable Redman, Russell O.
Re: Apropos making fields configurable Benjamin Franksen

Navigate by Date:
Prev: scaler record: int -> float Tim Mooney
Next: RE: Apropos making fields configurable Redman, Russell O.
Index: 1994  1995  1996  1997  1998  1999  2000  <20012002  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: Apropos making fields configurable Benjamin Franksen
Next: Re: Apropos making fields configurable Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  <20012002  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 ·