Hi - Everything below is straightforward – but I’ll mention it just in case.
If this is a VnmrS or DD2 – I always power cycle (power supply under the acquisition controller) before
giving up on the acquisition controllers. To be specific su acqproc, switch power off for 15 seconds – possibly
another press of the button on the master controller (though a power cycle should also reboot) then su acqproc
to reconnect. Sometimes a failure of a sequence can keep the system from reconnecting a few times before
it gets itself right – so repeat the process before giving up. “Inactive” in VnmrJ indicates that acqproc is not running.
You might only be dealing with an internet connectivity problem with acqproc.
Also – whenever I begin fooling with bad acquisitions I disconnect the amplifier inputs on the attenuator board
(or RF boards for DD2). It is not unknown for sequences to fail with the transmitter on.
The above experience is common when writing and testing sequences – I have been through it many times a day –
and often intermittent failures are not necessarily an indication of a serious problem.
If things do not come back after a few tries of the above – you probably have a service problem that will require some
board swapping. There are many ways a controller cage can fail -- Its easy to check voltages – they should all be just
above their stated values, but many other more subtle things can be wrong.
I am currently dealing with an intermittent failure that stops long runs – the Agilent service number was still
a productive way to go – and I am expecting a service call.
Dave Rice
Stanford Chemistry – Formerly Agilent Solids Applications
From: Plant,Daniel
Sent: Wednesday, February 18, 2015 5:12 PM
To: ammrl_at_ammrl.org
Cc: Plant,Daniel
Subject: AMMRL: Dead Agilent console...
Hello Folks,
A colleague has a problem with an Agilent 600 console.
I'll copy his notes below. Any help will be appreciated.
Dan
The first hint of a possible problem came yesterday morning with the spectrometer being unresponsive accompanied by an “ACode Error.” An RF card-cage reset, via its Master Board, appeared to solve that problem, and the instrument worked fine through late this afternoon. However, when I tried to begin with the next sample, I noticed that a “Set Up Parameters” command (“su”) failed, and the system went into an “Inactive” mode. Master Board resets appeared to briefly return the system to “Idle,” but it would suddenly turn back to “Inactive” without issuing any other commands. I then notice that the scrolling LED’s displays on the RF boards were no longer showing their regular displays, and they eventually failed to give any “patterns” together. The card cage’s power supply was indicating that all its DC Voltages were present with green panel lights, but I wasn’t able to check test points with a multimeter. As I mentioned above, none of the other obvious power-cycles proved useful.
Received on Thu Feb 19 2015 - 10:46:19 MST