Greetings,
Having some severe communcation problems with my Mercury Plus
400MHz with ATB probe on Linux (RHEL WS 4 running VnmrJ 1.1D). I
recently lost communication with the console, and no amount of 'su
acqproc', 'su acqproc' followed by console reset, and /vnmr/bin/setacq
has brought it back. I am also unable to 'ping inova', I always get a
'destination host unreachable' error when I try to 'ping inova' (inova
is listed in /etc/hosts). Here is what I have tried so far:
Using the configuration I had before (console connected to standard
ethernet port, network connected to second ethernet port):
su acqproc
su acqproc + console reset
/vnmr/bin/setacq
Tried this with both 'console connected to standard ethernet port',
and 'console connected to second ethernet port'.
None of these worked
Using a different configuration (console connected to second ethernet
port, network connected to standard ethernet port)
su acqproc
su acproc + console reset
/vnmr/bin/setacq
Tried this with both 'console connected to standard ethernet port',
and 'console connected to second ethernet port'.
These haven't worked either. Neither has a power cycle of the console
I then switched the cards, so that eth0 is now eth1 and vice versa, and
also no luck on that, using the same methods as above.
I am using 172.16.0.1 for the console IP, which is reflected in the
/vnmr/acq/bootptab
I also tried a different crossover cable, and that doesn't seem to be
the issue. I'm going to swap out the comm board with a mercury 300
tomorrow to see if it's the board, does anyone have any other
suggestions? At this point I'm willing to try anything. I checked the
comm board that I have, it's not the one that has communication problems
(some of the mercury communicstion boards had repeated problems with
'inactive Status' messages because of a bug with the chip, but this comm
board should be okay).
This may be unrelated, but just in case, I was tuning for 31P a couple
of days ago. I tuned, acquired, got the spectrum and then tuned back to
13C. For some reason I lost lock after that, and got it back for just a
little while before I lost it again and could not get a signal on D2O.
The next day I still didn't have a lock, and that was when the 'inactive
Status' occurred, which has so far been unrecoverable.
ANY suggestions would be greatly appreciated, as I'm out of ideas on
this one. Of course, this all happens the week before I'm due to go on
vacation......
Thanks for any assistance,
Chris
Received on Fri Sep 29 2006 - 12:07:11 MST