<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19019"></HEAD>
<BODY>
<DIV dir=ltr align=left>
<DIV dir=ltr align=left><SPAN class=657433420-10032011><FONT color=#0000ff
size=2 face=Arial>Ian, this is a problem <SPAN
class=525024220-10032011>which I believe</SPAN> occurs in all XL-I's. Basically
under some circumstances the CPU on the data acquisition board (DAB) <SPAN
class=525024220-10032011>gets overloaded and </SPAN>just can't keep up with
everything it needs to do. One symptom that this is occurring is indeed that the
XL Monitor window on the computer runs several minutes behind real-time.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=657433420-10032011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=657433420-10032011><FONT face=Arial><FONT
color=#0000ff><FONT size=2>The circumstances that usually create this problem
are running both optical systems together and <SPAN
class=525024220-10032011>using </SPAN>high rotor speeds. I actually don't think
I've <U>ever</U> been able to complete a run at 60K rpm <SPAN
class=525024220-10032011>when </SPAN>collecting both absorbance and interference
data.<SPAN class=525024220-10032011> Increasing the interval between scans will
help avoid crashes.</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=657433420-10032011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=657433420-10032011><FONT color=#0000ff
size=2 face=Arial>Because of this problem between runs you always should cut the
power to the instrument to make the DAB clear itself out. If it starts off
'confused' you may hit trouble under circumstances where otherwise you would
not. Restarting the computer will <U>not</U> help.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=657433420-10032011><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=657433420-10032011><FONT color=#0000ff
size=2 face=Arial>John</FONT></SPAN></DIV><BR>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> rasmb-bounces@rasmb.bbri.org
[mailto:rasmb-bounces@rasmb.bbri.org] <B>On Behalf Of </B>Ian
Berke<BR><B>Sent:</B> Thursday, March 10, 2011 12:23 PM<BR><B>To:</B>
rasmb@rasmb.bbri.org<BR><B>Cc:</B> david.keller@yale.edu; Incarvito,
Christopher<BR><B>Subject:</B> [RASMB] CPU Board Malfunction on
XL-I<BR></FONT><BR></DIV>
<DIV></DIV>Hi all,
<DIV><BR></DIV>
<DIV>We have an XL-I machine (~1.5yr old) which has given a CPU board
malfunction error (code#11) several times now. It happens after several
hours and the centrifuge just shuts down while the computer still thinks it's
scanning. Beckman tells us it's a software problem on the computer and an
upcoming software release should fix it. They suggest that in the meantime
I do a short absorbance scan (r 6.2-6.7) of the counterbalance to allow the
computer's data saving to catch up with the AUC scans of other cells.</DIV>
<DIV><BR></DIV>
<DIV>I don't know if it's related, but a couple of times I also noticed that the
centrifuge and the computer were out of sync as the centrifuge accelerated to
speed. I started the centrifuge from the computer and began calibrating
the laser for IF. That part went as normal, but when I looked at the XL
monitor on the computer, the speed readings were delayed by ~1-2min and the
computer would be waiting for speed and not letting me start scanning until it
had caught up.</DIV>
<DIV><BR></DIV>
<DIV>Has anyone else experienced this problem?</DIV>
<DIV><BR></DIV>
<DIV>Thanks,</DIV>
<DIV>Ian</DIV></BODY></HTML>