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: Default values and edb.def
From: Andy Foster <[email protected]>
To: Epics Questions <[email protected]>
Date: Tue, 2 Apr 1996 12:29:17 +0100 (BST)
I am totally confused over how default values are used 
from 'edb.def' (if at all).

Example: 

I tried, as a test, adding the ASG field to a binary-in
record. I added ASG to the 'sym' file with no value against it
i.e. ASG:

Running 'sch2edif' gave me an 'edf' with no reference to the ASG
field at all.

Then, running 'e2sr' gives the warning:

Warning: No property, port, or default value for "ASG", using " "

which is fine except that in the 'edb.def' file, I had explicitly
added:

(ASG  (char(default "ENGINEERING")))

It doesn't surprise me that 'e2sr' was unable to find a value for ASG
from the 'edf' file since this contains no reference. But, then how can
you use 'edb.def' to set a default? I would have thought 'sch2edif' would
pick up the ASG field even though no value had been set against it and this
would enable 'e2sr' to use 'edb.def' for default values. 
Have I got the wrong end of the stick? 
It seems to me that in the current system, default values are set 
through the 'sym' files?

I was doing this in an attempt to get rid of the many warnings that are 
generated from 'e2sr'.

Andy

===================================================================================
Andy Foster
Royal Greenwich Observatory	Tel:       44 (0)1223 374899 (direct)
Madingley Road			Fax:       44 (0)1223 374700
Cambridge			E-mail:    [email protected]
CB3 0HA				Home Page: http://www.ast.cam.ac.uk/~ajf
UK


Navigate by Date:
Prev: Re: CA API: Future directions? Peregrine McGehee
Next: S: CapFast Symbols for mbb*Direct Ralph Lange
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: Re: X Window Software for x86 Chris Timossi
Next: S: CapFast Symbols for mbb*Direct Ralph Lange
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 ·