Can you be more specific about what you mean by "the axis configuration settings don't always seem to stick for every axis"?
Do you mean they are not restored correctly after a reboot? Or do they get lost while the IOC is running?
Mark
________________________________________
From: [email protected] [[email protected]] on behalf of Luchini, Kristi L. [[email protected]]
Sent: Thursday, March 06, 2014 6:48 PM
To: [email protected]
Subject: MAXv model-3 driver - omsMAXvConfig problem
Hello,
We have seen a problem with the MAXv omsAsyn support, where the axis configuration settings don't always seem to
Stick for every axis. We have a temporary workaround, where to use the MAXv command "APP" which saves the configuration
settings as the Power-up default.
Has anyone implemented a solution to this problem?
Details:
EPICS R4.13.12
RTEMS-R4.9.4
MVME6100
MAXv-8000 FW 1.44
- Regard,
Kristi
- Replies:
- RE: MAXv model-3 driver - omsMAXvConfig problem austen.rose
- RE: MAXv model-3 driver - omsMAXvConfig problem Luchini, Kristi L.
- References:
- MAXv model-3 driver - omsMAXvConfig problem Luchini, Kristi L.
- Navigate by Date:
- Prev:
RE: Store long strings in EPICS record. Mark Rivers
- Next:
Re: Sequencer is not monitoring Pvs from another IOC Benjamin Franksen
- 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:
MAXv model-3 driver - omsMAXvConfig problem Luchini, Kristi L.
- Next:
RE: MAXv model-3 driver - omsMAXvConfig problem austen.rose
- 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
|