EPICS Home

Experimental Physics and Industrial Control System


 
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Asyn and devices with changing register map
From: <[email protected]>
To: <[email protected]>, <[email protected]>, <[email protected]>
Date: Mon, 9 Jan 2017 09:57:23 +0000
> On 01/06/2017 05:30 PM, Konrad, Martin wrote:
> > Are there any drivers that populate this dynamically on
> > IOC start from a configuration file or even from the EPICS database file?
> 
> The aravisGigE driver lazily creates parameters in drvUserCreate().

An example of a record using this approach:

https://github.com/areaDetector/aravisGigE/blob/master/aravisGigEApp/Db/AVT_Mako_1_52.template#L78

The OUT field is parsed, and the string "ARVI_SensorBit" is then available as drvInfo in drvUserCreate():

https://github.com/areaDetector/aravisGigE/blob/master/aravisGigEApp/src/aravisCamera.cpp#L362
 
This string tells the driver that it is a parameter ("SensorBit") that can be looked up from the camera ("ARV"), with integer format ("I").

I never dug deeper to find out if you can get the requested DTYP of the record. If you could, then you could dispense with the format character ("I" in this case) in the OUT field.

Thanks,
Tom


-- 
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



References:
Asyn and devices with changing register map Konrad, Martin
Re: Asyn and devices with changing register map Michael Davidsaver

Navigate by Date:
Prev: RE: synApps_5_8 build error Abdalla Ahmad
Next: RE: synApps_5_8 build error Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Asyn and devices with changing register map Michael Davidsaver
Next: RE: Asyn and devices with changing register map Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <20172018  2019  2020  2021  2022  2023  2024