Hi everyone,
This is resolved, I believe. I received some suggestions from Neil Donovan
and later Aaron Gulledge at Bruker that the voltage to the BSMS might be
dropping below 210 V. The voltage going into the console was in fact fine
(~215 V phase-to-phase), so I'd initially not considered this very much.
Eventually though I discovered that the power cable to the VTCB in the back
of the BSMS had been unplugged! We never regulate temperature so apparently
this went unnoticed. I would guess that leaving it unpowered led to transient
voltage drops, which would cause the observed behavior.
Neil's comments:
--------------------------
Check the input voltage to the BSMS. It should be > 200 VAC. There was a
system where the voltage dropped as low as 187 VAC which would cause these
problems. Then, when the voltage would increase again, a reset would make
them go away. If you are using a UPS, make sure that it is in good condition,
and not in maintenance bypass mode.
Aaron's comments:
--------------------------
I've been reviewing all of the communications regarding this issue, and the
thing that pops to mind is to ask is if this system is on a UPS, and if the
BSMS rack is selected to the correct voltage. I've seen weird, intermittent
errors occur when the voltage selector doesn't match input voltage.
Look on the back of the BSMS rack for a round voltage selector switch. Turn
off the BSMS , unplug the input plug, and measure the voltage going into the
BSMS. Then compare it to what range the switch is set for. If this looks
good and you have a UPS for the system, then we can explore other options.
Thanks to all that gave suggestions!
Alex
> From: Greenwood, Alexander (greenwa2)
> Sent: Thursday, May 20, 2021 11:28 AM
> To: ammrl_at_ammrl.org
> Subject: AMMRL: ICON-NMR segmentation violation/BSMS error
Hi everyone,
Another IconNMR issue -- we are in Topspin 2.1pl8 with Diskless from 3.2
running an AVANCE I. What is happening is every once in a while (generally
about once a week), the shimming on one sample fails, then the BSMS becomes
unresponsive with a red light on the LCB, the sample won't eject, and
automation can't proceed until the BSMS is power cycled.
First, we get a shim failure with the error:
"topshim: ILLEGAL TERMINATION of process 1076 due to signal 11 (segmentation
violation), Shim failed, Lock anomaly during acquisition"
Then the following sample fails with either the error "Failsafe detected hangup,
procedure: lock" or "Sample Changer Error: Empty answer from BacsCommand"
In the BSMS service tool, I find the errors:
"ERROR: B154 from BSMS: Protocol violation by LCB
A slave device signaled an error with the mode bits but it did not give an
error message when the CPU asked for it."
And:
"ERROR: B077 from BSMS: VME Timeout"
And:
"ERROR: 0012 from TOOL: without additional error description"
At the instrument, the BSMS becomes unresponsive--LCB error light comes on
and the last sample to run won't eject. The fix seems to be to switch the
BSMS off and on and restart Topspin, and things are back to normal for a
while.
I've been talking with Bruker about this for *many* months, but haven't really
gotten anywhere. Cooling fans and power supplies are working and voltages are
normal. I have some notion that I need to upgrade the firmware for the SCB-M,
but I'm not sure this makes sense. At any rate I'm not able to because I get a
"communication error" early in the process. The other boards (except SLCB)
download firmware fine.
So, I thought I'd ask if anybody has ever experienced this before?
Alex
Alex Greenwood (he/him)
Manager, NMR Facility
University of Cincinnati
123C Crosley Hall
(513) 556-9211 (office)
(412) 952-8044 (cell)
Received on Wed Dec 01 2021 - 11:40:09 MST