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: "Redman, Russell O." <[email protected]>
To: "'Benjamin Franksen'" <[email protected]>, EPICS Techtalk <[email protected]>
Date: Thu, 19 Jul 2001 08:21:37 -0700
Dear Benjamin,
I too would like to be able to configure the maximum and minimum raw values
for Raw Soft Support in ai/ao records.  I deal with all of my hardware
remotely, over CAN bus and serial connections, so I must do the conversions
into raw values without the benefit of device support.  At the moment I am
using AOFF and ASLO, but it would be much cleaner if I could specify the
ranges [EGUL, EGUF] and [RAWL, RAWF], letting the Raw Soft Support calculate
EOFF and ESLO.
Cheers,
Russell O. Redman

-----Original Message-----
From: Benjamin Franksen [mailto:[email protected]]
Sent: Wednesday, July 18, 2001 3:43 PM
To: EPICS Techtalk
Subject: Apropos making fields configurable


Benjamin Franksen wrote:
> 
> Definitely not. Anyway you'll have to have two ways if you want to be
> backward compatible. Remember the solution for the linear conversion?

...thinking about which: I am still not quite happy with the analog
conversion.

Main problem is that raw soft support does not (and cannot) set EOFF and
ESLO. Cannot, because maximum and minimum raw values are not known.

So while we're at it, I propose to make these fields configurable, too,
so that analog records with raw soft support can use the linear
conversion feature.

Another issue is breakpoint conversion. The behavior is now so that if
the value to be converted is grater than the largest value in the table
or smaller than the smallest, the resulting value is cut off, and the
record goes into a SOFT state with severity INVALID.

This doesn't make much sense. If I want to have values restricted
between some minimum and maximum, I use the DRVH / DRVL fields. If I
want INVALID severity, I can set LOLO / HIHI and LLSV / HHSV
appropriately.

At least, it would be nice to have this configurable on the record
level. It is often desired to implicitly extend the table linearly
beyond the highest or lowest values, using the first resp. last slope.

If there is consent that these featues would be nice, I can try to hack
that into the ax record support resp. cvtBpt code.

Ben
-- 
Berliner Elektronenspeicherring-Gesellschaft für Synchrotronstrahlung
(BESSY) GmbH, Control System Group
Albert-Einstein-Straße 15, 12489 Berlin, +4930 6392 8462, www.bessy.de


Replies:
Re: Apropos making fields configurable Benjamin Franksen

Navigate by Date:
Prev: Announcement:EPICS seminar in IHEP Beijing. Noboru Yamamoto
Next: Sequencer question: programs vs. state sets Brian McAllister
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: Announcement:EPICS seminar in IHEP Beijing. Noboru Yamamoto
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 ·