There is no need to have the device support distributing the values.
It is simpler to do this via database processing
and have the other records extract the values for
themselves from the original input record.
Pete
> -----Original Message-----
> From: Jens Rekow [mailto:[email protected]]
> Sent: 17 November 2005 15:38
> To: [email protected]
> Subject: record/device support general style question
>
>
> My way so far is another: There is one AsynDriver-powered record
> (stringin) which retrieves and holds the status string. That
> value is read
> by a longin record via dbGetField() in a standard device
> support, which
> extracts the information and distributes to all the other
> relevant records
> via dbPutField(). Thus these other records don't need any
> device/record
> support implementation themselves but are set remotely.
> Unfortunately this
> complicates handling the alarm/invalid states of these records.
>
> So the question is:
> Would it be better to have already my AsynDriver-powered record, which
> reads the status bytes, distributing the values to the
> different records
> via dbPutField()?
> Alternatively I like the idea of only one device support
> implementation
> for several records which is flexible using the INP field as a
> parameter...
>
>
> Any suggestions?
> What could be more 'stylish'?
>
> Thanks in advance,
> Jens
>
>
- Replies:
- Re: record/device support general style question Rok Sabjan
- Navigate by Date:
- Prev:
Getting CA data with VC Xu HuiJuan
- Next:
RE: Getting CA data with VC Jeff Hill
- Index:
1994
1995
1996
1997
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: record/device support general style question Liyu, Andrei
- Next:
Re: record/device support general style question Rok Sabjan
- Index:
1994
1995
1996
1997
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
|