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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: OMS VS4 "omsPut: card 0 send ring full!" |
From: | Ron Sluiter <[email protected]> |
To: | [email protected] |
Cc: | [email protected] |
Date: | Thu, 27 Jan 2011 12:44:39 -0600 |
Hello Nerses, If the drvOms driver is configured to use VMEbus interrupts (i.e., omsSetup() interrupt vector argument is nonzero), then the driver puts messages going to the controller into an EPICS ring buffer and enables the controller's transmit IRQ. One guess (I have never seen this error message before, so this guess is in the category of 'wild') is that the omsSetup() interrupt level argument does not match the jumper on the board. Another guess, if you are upgrading from a very old version of the motor record to a recent version, could be this (from the "Motor Record: Known problems with Release 5-9" An undocumented change was made in R5-4 to two OMS setup functions. Namely, the unused 2nd argument ("axes per card") was eliminated from omsSetup() and oms58Setup(). If I missed on both the above guesses, let me know. Ron On 1/27/2011 11:22 AM, Nerses Gevorgyan wrote: Does anyone have a clue why I'm getting this error? |