EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  <19961997  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  Index 1994  1995  <19961997  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 
<== Date ==> <== Thread ==>

Subject: Bug in OMS Driver routines
From: Guy Jennings <[email protected]>
To: [email protected]
Date: Wed, 13 Mar 1996 13:14:14 -0600
Is this a bug ?

In Epics r3.12.2, the file "drvOms.c" contains an intialisation of

char	oms_motor_specifier[MAX_OMS_CHANNELS+1] = {'X','Y','Z','T','U','V'};

(i.e. supports only 6 axes) whereas the rest of the code allows the two 
additional axes 'R' and 'S'.   I assume that this should be

char	oms_motor_specifier[MAX_OMS_CHANNELS+1] = {'X','Y','Z','T','U','V','R','S'};

or even (to be excessively anal!)

const char* const oms_motor_specifier = "XYZTUVRS";

Guy Jennings


Navigate by Date:
Prev: Channel access security Frank Lenkszus
Next: more vxWorks statistics Jim B. Kowalkowski
Index: 1994  1995  <19961997  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: Channel access security Frank Lenkszus
Next: Re: Bug in OMS Driver routines Joseph P. Sullivan
Index: 1994  1995  <19961997  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 
ANJ, 10 Aug 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·