On Thursday 17 November 2005 22:06, Andrew Johnson wrote:
> Benjamin Franksen wrote:
> > On the IOC (example app) this gives me:
> >
> > epics> franksenHost:aiExample.TIME dbNameToAddr failed
> > franksenHost:aiExample.TIME dbNameToAddr failed
> > franksenHost:aiExample.TIME dbNameToAddr failed
> > franksenHost:aiExample.TIME dbNameToAddr failed
> > franksenHost:aiExample.TIME dbNameToAddr failed
>
> dbCommon.dbd defines
> field(TIME,DBF_NOACCESS) {
> prompt("Time")
> special(SPC_NOMOD)
> interest(4)
> extra("epicsTimeStamp time")
> }
>
> Thus the TIME field is not directly accessible outside the
> record/device support code; you can only read timestamps using the
> appropriate DBR_ request types on the VAL field of a record. This is
> because a timestamp is not one of the fundamental value types that CA
> V3 supports.
Dear Andrew,
please re-read my message. I explicitly said I did this to provoke an
error message on the IOC console. I merely wondered if this is such a
severe error that the IOC must report this five times, when (IMHO) once
would have been enough ;-)
Cheers,
Ben
- Replies:
- Re: multiple error messages Andrew Johnson
- References:
- RE: dbEvent.c line 665 Jeff Hill
- multiple error messages Benjamin Franksen
- Re: multiple error messages Andrew Johnson
- Navigate by Date:
- Prev:
Re: multiple error messages Andrew Johnson
- Next:
Re: multiple error messages Andrew Johnson
- Index:
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: multiple error messages Andrew Johnson
- Next:
Re: multiple error messages Andrew Johnson
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|