Hello Spinlanders,
Thank you one and all for your useful suggestions and valuable insights
based upon your collective years of real world experience with Bruker NMR
systems.
The problems that we experienced turned out to have been caused by excessive
heat in our lab due to extended electrical power failures. The heat caused
the Aspect 3000 disk interface board and process controller board to cease
functioning properly. The two boards were replaced and our AC-200 NMR
system was revived.
We now have the two original disk interface and process controller boards
that need to be checked out and restored to normal function. We have asked
Arnold Itkin of NMR Associates and Peter Ziegler of Bruker if they know of a
shop that is capable of performing required repairs. We are still hoping to
get a lead from Arnold or Peter. Meanwhile, if any kind sole in the group
has any suggestion, please send it along.
Again, thanks one and all and kind regards,
Lawrence
Lawrence Byrnes
Laboratory Manager, Numare Spectralab Incorporated
Research Director, The Schoenenberg Institute of Molecular Spectroscopy
Hidden Meadow Farm, 3551 Winding Road
Kintnersville, PA, 18930-9543
610-346-8660 (voice)
610-346-7571 (fax)
numare_at_eclipse.net
www.eclipse.net/~numare/
Important notice! Please read!
This electronic mail (email), and any files transmitted with it, are
confidential and intended solely for the use of the individual or entity to
whom they are addressed. If you are not the intended recipient, you are not
permitted to distribute or use this message, or any of its attachments, in
any way. We also request that you advise the sender of the incorrect
addressing. This notice also confirms that this email message has been virus
scanned and that, although no computer viruses were detected, Numare
Spectralab Incorporated and The Schoenenberg Institute of Molecular
Spectroscopy accept no liability for any consequential damage resulting from
email containing any computer viruses. This email message may contain
legally privileged and/or confidential information. If you are not the
intended recipient(s), or the employee or agent responsible for the delivery
of this message to the intended recipient(s), you are hereby notified that
any disclosure, copying, distribution, or use of this email message is
prohibited. If you have received this message in error, please notify the
sender immediately by email and delete this email message from your
computer.
Thank you.
----- Original Message -----
From: Lawrence Byrnes
To: AMMRL
Cc: Lawrence Byrnes
Sent: Sunday, July 02, 2006 7:56 PM
Subject: AMMRL: Bruker AC-200 NMR, DISR94 problem
Hello Spinlanders,
Having problems with our Bruker AC-200 NMR system DISNMR software.
System is Bruker AC-200. Has Aspect 3000 computer with Hitachi DK 512S 17
170 MB hard drive, array processor and process controller running DISR94 NMR
data acquisition and processing software under ADAKOS operating system. Had
several system hang ups while working last week. Thought the hard disk
drive that was replaced last November was at fault. Seems to have turned
out to have been disk interface board in Aspect computer instead. Replaced
disk interface board, loaded ADAKOS on alternate hard disk drive and copied
files from PC computer hard drive to get DISR94 up and running.
Can now read/write files, process NMR data files, copy files between Aspect
3000 and PC computers via NMRLINK. Can not run NMR experiments. Get
'ILLEGAL INTERRUPT, ' message and data in job where we try to run NMR
experiment gets changed as if real component of data is removed leaving only
imaginary component of data. Also scale of data is changed so that
remaining component of data is blown up by several orders of magnitude. Can
set and examine data acquisition parameters and issue 'II' Initialize
Interface command. Everything appears to be normal with exception of not
being able to run simple proton or X-nucleus NMR experiments.
Is there a file or files that did not get copied to PC computer hard drive
from working Aspect 3000 hard drive when backup was made that is responsible
for above problem? What do we need to do to get our system functioning
normally once again?
Will post solution to group in the event that some other kind sole runs into
same problem.
Thank you and kind regards,
Lawrence
Received on Fri Jul 28 2006 - 10:12:00 MST