Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019 
<== Date ==> <== Thread ==>

Subject: Re: waveform ENUM FTVL or BOOL FTVL
From: Hinko Kocevar <hinko.kocevar@i-tech.si>
To: Tim Mooney <mooney@aps.anl.gov>
Cc: tech-talk@aps.anl.gov
Date: Wed, 21 Mar 2012 08:15:12 +0100
Hi Tim,

Thanks for clarifying this matter.

Regards,
Hinko

On 03/15/2012 07:05 PM, Tim Mooney wrote:
Hi Hinko,

The waveform record doesn't actually support ENUM, it just doesn't bother to define its own recordtype-specific list of data types, but instead uses a generic list from base.  I think your best move is to use char or uchar and adopt the standard zero-is-false-nonzero-is-true.

Tim

----- Original Message -----
From: "Hinko Kocevar"<hinko.kocevar@i-tech.si>
To: tech-talk@aps.anl.gov
Sent: Thursday, March 15, 2012 8:22:27 AM
Subject: waveform ENUM FTVL or BOOL FTVL

Hi,

Our Linux OS based instrument will be running soft IOC. The instrument
supports various data types. One of the data types that I have trouble
supporting in EPICS is array of bool values. My intention was to use
ENUM FTVL for waveform but the problem I'm seeing in the IOC shell is:

missing record support entry table Record Support Routine (get_enum_str)
Record Type waveform PV h:b::adllr4:adc_module:dc_rej_bypass-I.VAL  dbGet


I just wanted to confirm that for waveform record FTVL ENUM is indeed
supported. What am I doing wrong?

Here is the PV definition:
record(waveform, "$(H)$(B):adllr4:adc_module:dc_rej_bypass-I")
{
          field(DESC, "TBD")
          field(INP, "boards.adllr4.adc_module.dc_rej_bypass")
          field(DTYP, "liberaGet")
          field(NELM, "9")
          field(FTVL, "ENUM")
}

Note that using other FTVL values works, but they are not "restrictive"
enough to allow only '0'/'1' or 'false'/'true' values.


Best regards,
Hinko



--
Hinko Kocevar
Software development engineer
Instrumentation Technologies d.d.
Velika pot 22, SI-5250 Solkan - Slovenia
T:+386 5 3352600, F:+386 5 3352601
mailto: hinko.kocevar@i-tech.si

http://www.i-tech.si - When your users demand stability

The information transmitted is intended solely for the
addressee and may contain confidential and/or privileged
information. Any review, retention, disclosure or other use
by persons other than the intended recipient is prohibited.
If you received this in error, please notify the sender and
delete all copies.

References:
Re: waveform ENUM FTVL or BOOL FTVL Tim Mooney

Navigate by Date:
Prev: RE: 32-bit TIFFs and PIL Mark Rivers
Next: RE: Build problem with db dependencies Gougnaud Françoise
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019 
Navigate by Thread:
Prev: Re: waveform ENUM FTVL or BOOL FTVL Tim Mooney
Next: RTEMS RPCIO errors Bruce Hill
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·