EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  <19961997  1998  1999  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  <19961997  1998  1999  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: Should dfanout be called dLoFanout?
From: [email protected] (Rozelle Wright)
To: [email protected]
Cc: [email protected]
Date: Wed, 18 Dec 96 18:40:45 MST
> From [email protected] Mon Dec 16 08:23:48 1996
> Return-Path: <[email protected]>
> Date: Mon, 16 Dec 1996 16:21:46 +0100 (MET)
> Reply-To: Marian Zurek <[email protected]>
> To: Rozelle Wright <[email protected]>
> Cc: [email protected]
> Subject: Re: VME: Cannot find record type dfan
> In-Reply-To: <[email protected]>
> Mime-Version: 1.0
> Content-Type> : > TEXT/PLAIN> ; > charset=US-ASCII> 
> Content-Length: 434
> X-Lines: 24
> 
> 
> 
> I updated files you suggested (with the stuff from the mail), but then I
> don't have consistency with the Record Reference Manual (Release 3.12,
> Issue 1a). Field types are different for (HOPR - int/float in Manual,
> LOPR, HIHI, etc.) So I got an error message at initialisation time (for
> example) 
> 
> "
> Cannot set field HOPR to 0.5
> "
> 
> Does it mean that I should recompile some modules ?
> 
> 
> Regards,
> Marian Zurek
> 
> 
> --
> Marian Zurek
> CERN
> 
> 
> 
Hi Marian,
I finally looked closely at the dfanout which is in the EPICS
distribution.  All of the values (including of course HOPR and LOPR)
are defined as long integers.  This explains why you get an error
when you try to set HOPR to .5 from the opi. 

It is definitely inconsistent with the documentation, and as far as
I can tell, because I went back and looked at old distributions it
has been inconsistent since early R3.12. 

We are using dfanout to set the N fields in several compression
records, so we had never tried using it for floating point numbers.

It will take analog values from an AO and put them out to several
 AI records, but it truncates them first.

If you need floating point data fanout, this won't do it.  You could
probably take the code and all the definitions for the dfanout record
and modify them to be double call the record something else and get
what you need fairly quickly, or there may be a better way to
do this.  

Does any one else have a copy of a floating point data fanout already?

Good Luck,
Rozelle

---------------------------------------------------------
|                                                       |
|Rozelle Wright              Phone (505) 667-4804       |
|Los Alamos Natl Labs AOT-8  FAX (505) 665-5107         |
|PO Box 1663 MS-H820         Group Office (505) 667-6087|
|Los Alamos, NM 87545        email : [email protected]   |
|                                                       |
---------------------------------------------------------
  






Navigate by Date:
Prev: Re: Standard IOC Benchmarks? Noboru Yamamoto
Next: RE: User's Guide on EPICS Build System W. Stephen Syrett
Index: 1994  1995  <19961997  1998  1999  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: soft device support for aai and aao records? William Lupton
Next: Re: Should dfanout be called dLoFanout? Ned Arnold
Index: 1994  1995  <19961997  1998  1999  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 ·