Hi,
This protocol looks familiar, we have written a driver for the N1470 series of NIM HV power supplies here:
http://controls.diamond.ac.uk/downloads/support/caenN1470/
Streamdevice definitely supports more that one parameter as we use it like that:
record(ao, "$(P)$(Q):VSET$(CHAN)") {
field(DESC, "HV Setpoint")
field(DTYP, "stream")
field(FLNK, "$(P)$(Q):VSET$(CHAN):RBV")
field(OUT, "@caenN1470.proto writechan($(ADDR),$(CHAN),VSET,$(P)$(Q)) $(PORT)")
field(PREC, "1")
field(EGU, "V")
field(DRVH, "8000")
field(DRVL, "0")
field(PINI, "YES")
field(SDIS, "$(P)$(Q):DISABLE")
}
And in the protocol file:
readchan { out "$BD:\$1,CMD:MON,CH:\$2,PAR:\$3"; in "#BD:%*d,CMD:OK,VAL:%f"; }
Do you have all your macros defined when you instantiate the template file?
Thanks,
Tom Cobb
> -----Original Message-----
> From: [email protected] [mailto:tech-talk-
> [email protected]] On Behalf Of Jörn Wüstenfeld
> Sent: 24 March 2015 10:25
> To: [email protected]
> Subject: Strange StreamDev behaviour
>
> Hello,
> I currently have a problem with Streamdev version 2.6 and asyn 2.26
> using base
> 3.14.12.4 on an arm linux.
>
> I have a protocol that needs two parameters:
>
> monIMdec {
> out "$BD:\$1,CMD:MON,CH:\$2,PAR:IMDEC";
> in "#BD:%*i,CMD:OK,VAL:%i";
> }
>
> The corresponding database file contains the following record using
> this
> protocol:
>
> record (ai, "xxx:monIMdec")
> {
> field (DESC, "readback of current resolution")
> field (DTYP, "stream")
> field (INP, "@CaenHVNimUsb.proto monIMdec($(ps), $(channel))
> $(interface)")
> field (PREC, "2")
> }
>
> Running the IOC I get the following error message during the
> initializaion
> phase:
>
> _main_ Businterface '0)' not found for 'xxx:monIMdec'
> _main_ xxx:monIMdec: Can't attach to bus 0) -1
> _main_ xxx:monIMdec: Record initialization failed
>
> If I do a "dbpr xxx:monIMdec", the value in the record is undefined.
> If I do a "dbtr xxx:monIMdec" and then a "dbpr xxx:monIMdec" the
> expected
> value is set. and no further messages are printed.
>
> It looks to me that during initialization the parser of StreamDev does
> not
> handle more than one protocol parameter.
> What can I do to get rid of this error messages?
>
> With kind regards,
>
> Jörn Wüstenfeld
>
--
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
- Replies:
- Re: Strange StreamDev behaviour Jörn Wüstenfeld
- References:
- Strange StreamDev behaviour Jörn Wüstenfeld
- Navigate by Date:
- Prev:
Strange StreamDev behaviour Jörn Wüstenfeld
- Next:
Re: Strange StreamDev behaviour Jörn Wüstenfeld
- 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:
Strange StreamDev behaviour Jörn Wüstenfeld
- Next:
Re: Strange StreamDev behaviour Jörn Wüstenfeld
- 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
|