You also have OUT where it must be INP even for output records.
Sent from my iPhone
> On May 31, 2018, at 8:57 AM, Mark Rivers <[email protected]> wrote:
>
> You have a typo in your DTYP.
>
> Sent from my iPhone
>
>> On May 31, 2018, at 8:28 AM, Jörn Dreyer <[email protected]> wrote:
>>
>> Hi Mark and Michael,
>>
>> her is how I configured the waveform record:
>>
>> record(waveform, $(P)$(R)$(I):DelayTimeA) {
>> field (DESC, "Delay of channel A")
>> field (DTYP, "asnyInt32ArrayOut")
>> field (OUT, "@asyn($(PORT), 0, 100) DELAYTIMEA")
>> field (FTVL, "LONG")
>> field (NELM, "256")
>> }
>>
>> At IOC startup I get the following error message:
>>
>>> Can't set "XXX:Test1:DelayTimeA.DTYP" to "asnyInt32ArrayOut"
>>> Error at or before ")" in file "db/Delay.db" line 355
>>> Record "XXX:Test1:DelayTimeA" does not have a field "OUT"
>>
>> This somehow contradicts the information. And the record reference manual
>> defines also onle the INP field for the waveform record.
>>
>> Regards,
>>
>> Jörn
>>
>> Am Donnerstag, 31. Mai 2018, 15:01:35 CEST schrieb Mark Rivers:
>>> Hi Jörn
>>>
>>>> The waveform record supports only INP direction.
>>>
>>> The devAsynInt32Array.dbd file defines both input and output.
>>>
>>>
>>> corvette:asyn/asyn/devEpics>more devAsynInt32Array.dbd
>>> device(waveform,INST_IO,asynInt32ArrayWfIn,"asynInt32ArrayIn")
>>> device(waveform,INST_IO,asynInt32ArrayWfOut,"asynInt32ArrayOut")
>>>
>>> Your waveform record would use DTYP="asynInt32ArrayOut".
>>>
>>>
>>> Mark
>>>
>>>
>>>
>>> ________________________________
>>> From: [email protected] <[email protected]> on
>>> behalf of [email protected] <[email protected]> Sent:
>>> Thursday, May 31, 2018 7:54 AM
>>> To: 'Jörn Dreyer'; [email protected]
>>> Subject: RE: Transfering array of 256 elements to driver
>>>
>>> From: [email protected] [mailto:[email protected]]
>>>
>>>> I'm working on a driver that needs to set 256 values into one hardware
>>>> register. What type of database record should I use for this purpose?
>>>>
>>>> The waveform record supports only INP direction.
>>>
>>> In fact this is not so: you can write in either direction when processing
>>> the record, it's up to the device driver to decide whether to push or pull
>>> waveform data, so the waveform record will be what you need.
>>>
>>> --
>>> This e-mail and any attachments may contain confidential, copyright and or
>>> privileged material, and are for the use of the intended addressee only. If
>>> you are not the intended addressee or an authorised recipient of the
>>> addressee please notify us of receipt by returning the e-mail and do not
>>> use, copy, retain, distribute or disclose the information in or attached to
>>> the e-mail. Any opinions expressed within this e-mail are those of the
>>> individual and not necessarily of Diamond Light Source Ltd. Diamond Light
>>> Source Ltd. cannot guarantee that this e-mail or any attachments are free
>>> from viruses and we cannot accept liability for any damage which you may
>>> sustain as a result of software viruses which may be transmitted in or with
>>> the message. Diamond Light Source Limited (company no. 4375679). Registered
>>> in England and Wales with its registered office at Diamond House, Harwell
>>> Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United
>>> Kingdom
>>
>>
>> --
>> Dr. Joern Dreyer
>> HIBEF DAQ + Controls
>> Institut für Strahlenphysik
>> Helmholtz-Zentrum Dresden - Rossendorf e.V
>> Abt. FWKX Tel: +49 351 260 3263
>> FAX: +49 351 260 3700
>> 01314 Dresden eMail: [email protected]
>>
>> Helmholtz-Zentrum Dresden - Rossendorf e.V (HZDR)
>> Bautzner Landstraße 400, 01328 Dresden
>> Vorstand: Prof. Dr. Dr. h. c. Roland Sauerbrey, Dr. Ulrich Breuer
>> Vereinsregister: VR 1693 beim Amtsgericht Dresden
>>
>>
- References:
- Transfering array of 256 elements to driver Jörn Dreyer
- RE: Transfering array of 256 elements to driver [email protected]
- Re: Transfering array of 256 elements to driver Mark Rivers
- Re: Transfering array of 256 elements to driver Jörn Dreyer
- Re: Transfering array of 256 elements to driver Mark Rivers
- Navigate by Date:
- Prev:
Re: Transfering array of 256 elements to driver Mark Rivers
- Next:
RE: Transfering array of 256 elements to driver [email protected]
- 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: Transfering array of 256 elements to driver Mark Rivers
- Next:
RE: Transfering array of 256 elements to driver [email protected]
- 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
|