Experimental Physics and
Industrial Control System

Tom,

as I didn't see a reply to this: we use pvload for things
that sometimes change (like e.g. filters in filter wheels
in our case). You can load it at startup, and again from
the command line whenever you want to change something.

HTH,
Maren Purves

[email protected] wrote:

Hi all,

I've been writing an areaDetector driver that will support the majority
of generic GigE Vision cameras, and I've run into a problem. A number of
the parameters supported by the driver are enumerations that vary from
camera to camera. For instance, the TriggerSource enum on one camera may
be ["Internal", "External"], or ["Line1", "Line2", "FixedRate",
"Software"] on another. I could create a database for each camera
containing the correct labels for each parameter, but it would be a lot
neater to get the mbbo/mbbi record to query asynPortDriver for a list of
strings at startup.

Does anyone have any ideas on the neatest approach on this, and some
pointers on where to make the modifications?

References:

Writing mbbo/mbbi text labels using asynPortDriver/areaDetector tom.cobb

Navigate by Date:

Prev: Re: GPIB to ethernet converter emmanuel_mayssat

Next: Re: how often do you use Tornado IDE tools for vxworks programming Bruce 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: Writing mbbo/mbbi text labels using asynPortDriver/areaDetector tom.cobb

Next: RE: Writing mbbo/mbbi text labels using asynPortDriver/areaDetector 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  2017  2018  2019  2020  2021  2022  2023  2024