<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>Dmitry, I am doubtful the “dope slap” (my term) will resolve your problems, but it can’t hurt. What this does is to force the main CPU board back to a normal state when it gets hopelessly confused and won’t obey normal commands (i.e. it thinks the instrument is running when it is not), confusion which persists even after powering off. To do the “dope slap” you can either (1) tell the instrument to run (from its panel) when the door is open (triggering a high-priority error condition that seems to reset the CPU), or (2) you can temporarily pull the white connector that has about a 3 cm loop of white wire located on the back panel (next to the serial cable), which similarly triggers an error condition. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>One thing that can get the CPU overloaded is trying to collect both absorbance and interference scans at high rotor speeds (typically above 45-50K, but it depends on the firmware version). Is that what you were doing when these error messages started? I haven’t seen that particular set of symptoms arise from CPU overload, but I don’t run the newest versions of the firmware (the code in the EPROMS that Ronald mentioned), so that might make a difference in symptoms. In my experience though CPU overload is cured by simply turning the power off and back on.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>FYI it’s generally a good idea to turn the power off and back on between successive runs to be sure the CPU clears out any backed-up tasks and messages.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'>John<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:blue'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> RASMB [mailto:rasmb-bounces@list.rasmb.org] <b>On Behalf Of </b>Toth IV, Ronald T<br><b>Sent:</b> Tuesday, July 01, 2014 2:13 PM<br><b>To:</b> dmitry.veprintsev@psi.ch; rasmb@list.rasmb.org<br><b>Subject:</b> Re: [RASMB] Fwd: endless error messages<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Hi Dr. Veprintsev, <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>We had a drive malfunction error on our machine not too long ago. It was accompanied by looping error messages as you describe, and also would lock the door out, requiring us to take off the panels and loosen the vacuum manually to retrieve samples.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>There are several things you could try, but in our case we needed our tech to visit to fully resolve the issue. There's a component called the "Eproms" that could be the culprit, so they wouldn't necessarily need to replace the whole board. I've heard the error can happen if the oil level is low as well. I was also directed to search the archives for a post with the phrase "dope slap," it involves unplugging some wires in the back to clear the error messages, but I can't seem to locate the post at the moment. <o:p></o:p></span></p></div><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'><o:p> </o:p></span></p><div><div><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>- Ronald Toth</span><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> </span><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Post Doctoral Researcher</span><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>Macromolecule and Vaccine Stabilization Center</span><span style='color:black'><o:p></o:p></span></p></div></div><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>University of Kansas</span><span style='color:black'><o:p></o:p></span></p></div></div></div></div></div><div><div class=MsoNormal align=center style='text-align:center'><span style='color:black'><hr size=3 width="100%" align=center></span></div><div id=divRpF373235><p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'> RASMB [rasmb-bounces@list.rasmb.org] on behalf of Dmitry Veprintsev [dmitry.veprintsev@psi.ch]<br><b>Sent:</b> Tuesday, July 01, 2014 3:52 PM<br><b>To:</b> <a href="mailto:rasmb@list.rasmb.org">rasmb@list.rasmb.org</a><br><b>Subject:</b> [RASMB] Fwd: endless error messages</span><span style='color:black'><o:p></o:p></span></p></div><div><div><div><div><p class=MsoNormal><span style='color:black'>Dear All, <o:p></o:p></span></p><div><p class=MsoNormal><span style='color:black'>I was wondering if some of you have already experienced the endless error messages and hopefully found a cure to the problem. Our instrument functions for several runs after the repair which involves computer boards replacement or reset. After that it comes up with an error message (drive malfunction is the most common, but several others are also present), and shuts itself off, possible as a consequence of too many error messages in the log. <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>Is it a buggy firmware version or something more serious? <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>Nearly every board has been replaced, and the power supply has also been looked into. <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>Any suggestions are welcome as the level of desperation is raising exponentially :)<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:black'>best regards, Dmitry<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='color:#888888'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='color:#888888'><o:p> </o:p></span></p></div></div></div><p class=MsoNormal><span style='color:black'>-- <br>Dr. Dmitry Veprintsev<br>Group Leader<br>Conformational Dynamics of GPCRs<br>Laboratory of Biomolecular Research, OFLC/103<br>Paul Scherrer Institut<br>5232 Villigen PSI<br>Switzerland<br><a href="mailto:dmitry.veprintsev@psi.ch" target="_blank">dmitry.veprintsev@psi.ch</a><br>Tel +41 (0) 56 310 5246; Fax +41 (0)56 310 5288<br>Secretary Mrs. Stefanie Whale +41 (0)56 310 4252 <a href="mailto:stefanie.whale@psi.ch" target="_blank">stefanie.whale@psi.ch</a><br><a href="http://www.psi.ch/~veprintsev_d" target="_blank">http://www.psi.ch/~veprintsev_d</a> <o:p></o:p></span></p></div></div></div></div></div></div></body></html>