| 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: 5500 temp monitor Re: mvme6100 HW issues? |
| From: | Kate Feng <[email protected]> |
| To: | "Kasemir, Kay" <[email protected]> |
| Cc: | "[email protected]" <[email protected]> |
| Date: | Fri, 02 Mar 2012 15:52:35 -0500 |
On 02/01/2012 12:18 PM, Kasemir, Kay wrote:
Hi: At SNS, we updated from the MVME2100 to the MVME5500. The 2100 runs forever without added cooling on extender boards in open crates in laboratory setups. The 5500 needs forced cooling right across its heat sinks; it will otherwise soon overheat.
I am surprised that the mvme5500 overheated. Did you use a regular VME crate or a VME64x crate with the mvme5500 board ? So far, we do not have the overheating problem on our mvme5500 boards. Regards, Kate
Richard Dickson found a way to read a Maxim DS1621 temperature sensor that's on the 5500 CPU board, which Xihui Chen turned into an EPICS device driver that we now use on many 5500 CPUs to monitor their temperature, alarming on some limit. We could share that if you want to check possible adaption to the 6100, or see if it's generic enough for use at your site with 5500 boards. Thanks, Kay