Troubleshooting
H172203_1_001 213 / 234
22 Troubleshooting
The following chapter describes the possible causes of faults, and the work required to rectify
them.
In the event of repeated faults, shorten the maintenance intervals in accordance with the
actual load.
If a failure occurs during operation, the system interrupts the current procedure.
On the TopSpin screen an error message is displayed. Take down the complete error
message. Furthermore, have ready the following information:
• Part number and ECL (Engineering change level) of the units.
• Spectrometer type and order number.
• Magnet Type.
With this information contact the customer service. See Contact [}221] for contact details. In
many service cases a copy of the logfile is very helpful, see below.
Contact the manufacturer in the event of faults which cannot be rectified in accordance with
the instructions below.
22.1 Diagnostic and Troubleshooting
In case of a problem regarding the BSMS, check the following points:
• Are all power voltages ok? Check the LED‘s on each subsystem including power supplies
indicating if it is correctly powered.
• Are all firmware components up to date? It may be necessary to load the current
BsmsCheckDownload.txt file from the Bruker FTP server and do the checks as described
before.
For further investigations, the BSMS provides a detailed logging service. The latest
information can be retrieved under the menu point Main | Service | Display logged
messages. On the same Web Page, there is a button for resetting the buffer before running
a specific command sequence. How to access the Service Web pages is described in
chapter Service Web [}34].
Additionally, it is possible to activate periodical transfer of that logging information to the hard
disk of the EPU. This feature is available in TopSpin by typing the command bsmsdisp and
selecting the Service Tab. There is a check box for enabling this transfer and a button for
viewing the stored long term information. These files will be saved with savelogs.
It may be necessary to configure the logging (how detailed some events are logged), which is
provided under the menu point Main | Service | Log Configuration.
There is a watchdog task running on the ELCB. If the application is blocked for a long time
then the BSMS is rebooted. The watchdog function, which is normally active, can be disabled
on the service main page (service access is necessary).
After a restart, the logging of the session before - the post mortem log - is still available
In this manual you can find separate chapters on troubleshooting in the description of the
individual units e.g. ELCB, SPB, etc.