Experimental Physics and
Industrial Control System

I would put it into the device support initialization area -

	Would you worry that one cannot guess what the options might
be from an inspection of the .db file? Do you think it might be prudent
to put default values in the .db file, or would that just cause more
confusion if/when the defaults are overwritten by the device support
record initialization?

A problem would be if the assignment of these values can change. Channel access clients monitor the value as a short and only send the string assignments at connection time. So that is a possible problem. If they can change - you may want to map them from a static assigment to the dynamic values in the device support only - and not export the fact that the strings are assigned different values at different times.

	Good point! For the H/W I had in mind, the configuration could
only take place with the H/W off-line. If bringing the H/W back online
requires an IOC re-initialization, then I infer that problem is moot.

	If, however, the H/W is expected to be reconfigured online
(e.g. if it is connected via ethernet or a "field bus"), then it
requires the special care you mention.

References:

Re: initialize of mbbi state labels Bob Dalesio

Navigate by Date:

Prev: RE: initialize of mbbi state labels Mark Rivers

Next: converting from R3.13.0Beta12 to R3.13.8 Kevin Tsubota

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: initialize of mbbi state labels Bob Dalesio

Next: RE: initialize of mbbi state labels 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