EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

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

Subject: Re: MAXv problem
From: Ron Sluiter <[email protected]>
To: "Davidsaver, Michael" <[email protected]>
Cc: "Keister, Jeffrey" <[email protected]>, [email protected]
Date: Thu, 22 Apr 2010 10:32:04 -0500
Hello Michael,

This is a known, ill defined, problem.  It appears to be a rare,
intermittent, hardware issue.

At least one MAXv board, with the same symptoms you describe,
has been returned to OMS that I know of.  I believe OMS is
beginning to understand what is causing this problem.

I would RMA the board back to OMS and tell them you are
having watchdog problems.  Have them contact me if they
have any further questions.

Ron

Davidsaver, Michael wrote:
All,

We are seeing a problem with one MAXv motor controller in a crate with 6
controllers running the version 6.4.3 of the motor support with Base
3.14.10 on RTEMS 4.9.3.  The symptoms I see are that the IOC becomes
unresponsive.  After a soft reboot of the CPU I see the following on the
console

MAXv card #3 is NOT running; status = 0x2

This message is printing the firmware state register, which is
indicating that the processor on the maxv card is still
(re)initializing.

The IOC then hangs waiting for a reply from the card in motor_init.  I
can attach with a remote debugger and see that it is stuck in a loop
waiting for the card to update a register.  A full power cycle seems to
bring the card back to life, but the problem has recurred several times
in recent weeks.

Is this a known issue with a fix?  We do have a spare, so I am inclined
just to return this one to the manufacturer.


Michael Davidsaver NSLSII Controls Group Brookhaven National Lab (631)344-3698




References:
MAXv problem Davidsaver, Michael

Navigate by Date:
Prev: Re: Striptool crashes for Fedora 11 64 bit version... Robert Soliday
Next: gateway won't set "busy" PV type properly Dennis Nicklaus
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: MAXv problem Davidsaver, Michael
Next: Re: EPICS Installation Mauro Giacchini
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·