You might want to check the temperature of the SGU boards. If you do not know
how, let me know and I will email you. I don't have my notebook with me right
now and do not remember the command.
I hope that helps.
Jay
________________________________
> From: main_at_ammrl.groups.io on behalf of Frank Holger Foersterling via groups.io
> Sent: Tuesday, February 18, 2025 4:58 PM
> To: main_at_ammrl.groups.io <main_at_ammrl.groups.io>
> Subject: [AMMRL] Intermittent SGU errors on Avance500 III HD NMR
Dear colleagues,
I have been trying to troubleshoot an intermittent acquisition problem on
our 500MHz Bruker Avance III HD system. Any acquisition command like ii, zg,
atma will hang and throw a "Error 97 in SGU1" message, which can only be
cleared by resetting and re-scanning the AQS rack from the web tools.
The problem sometimes occurs several times a week, then is dormant for several
weeks (lately at least a couple of times a week). I am currently in touch with
Bruker on narrowing down the problem, but am wondering whether anybody has come
across something similar and found a solution.
From the few times I was personally present, the order of events usually is:
Sudden loss of lock, with a error message:
GAB/2 [Z] Parity Error on GCON Interface! Possibly due to reset on IPSO.
04-09:44:46.379 BSMS Error: GAB/2 [Z] Parity Error on GCON Interface!
Possibly due to reset on IPSO.
Blue status light on the SGU/3 board.
At this point, the sample can be re-locked without problem. But any subsequent
acquisition command (ii, zz, atma,etc) will fail with multiple errors (like 8
of them)
Error 97 in SGU1: -- CH1 SLOT 4 RACK 1: 80MHZ clock error. Check if REF IN
(J5) is connected to a Reference Board and restart the system.
All LEDs on the SGU/3 will turn red.
The problem can be rectified by typing "ha", and thelect the DRU to call up
the corresponding service web and Reset/rescan the AQS rack. Then the instrument
will work normal until the next occurence.
I also tried power cycling the entire AQS rack or the whole console, that would
also clear the problem, but not any better than the procedure above.
I a few cases, I would see a similar eerrors and lost lock, instead of the SGU
errors just give me a simple communications error (Error in communication with
ipsoserver (COMM_FAILURE_WaitingForReply), and "ha" would show the DRU unit as
missing. In that case just a hard power cycle of the AQS rack will clear the
problem, but I believe that these symptoms are just a variation of the problem
above.
I checked the LEDs on the power supply on the back of the console, the main
is yellow, the +50V and -5V green, and the +/- 20V off. Bruker thinks that
is normal and should not be the cause of the problem.
The issue also predates our move into our new building, and we now have a Bruker
supplied UPS connected to the console, so I don't believe that a bad incoming
power is the problem.
On advice of Bruker I tried swapping the reference board, but that did not
solve the problem.
We are running Topspin 3.7 under CentOs7, and as far as I can tell all firmware
is up to date. If those sympoms look familiar to anybody and you found a
solution, I would be very eager to hear from you, as this has haunted me now
for a while.
Thanks
Frank-Holger Foersterling
University of Wisconsin-Milwaukee
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#2046): https://urldefense.com/v3/__https://ammrl.groups=
.io/g/main/message/2046__;!!PvDODwlR4mBZyAb0!TjGZS7ivUd0YteT6OKfH8YCfhD6QK2=
6BkxguqOZ9xxJC-6--KAv9rlc8fA-mMhopdtcfm5qZNR4weEh2GAEUUb6digpp$
Mute This Topic: https://urldefense.com/v3/__https://groups.io/mt/111262639=
/7559972__;!!PvDODwlR4mBZyAb0!TjGZS7ivUd0YteT6OKfH8YCfhD6QK26BkxguqOZ9xxJC-=
6--KAv9rlc8fA-mMhopdtcfm5qZNR4weEh2GAEUUf5IAb-F$
Group Owner: main+owner_at_ammrl.groups.io
Unsubscribe: https://urldefense.com/v3/__https://ammrl.groups.io/g/main/lea=
ve/12177410/7559972/1125599165/xyzzy__;!!PvDODwlR4mBZyAb0!TjGZS7ivUd0YteT6O=
Received on Tue Feb 18 2025 - 17:48:59 MST