UW CHEMISTRY NMR
Announcments & Equipment Logs
GG500 Log Book
Welcome to the Chemistry NMR Online Log Book – your One Stop portal to communicate about the spectrometer to the Facility Staff in a timely manner.
Please record your comments and relevant observations about DRX499 instrument by submitting an entry using the “Post Log Entry” box found below.
Subscribe to DRX499 logs
304 Responses to “GG500 Log Book”
« Previous 1 2 3 4 … 31 Next »
DRX499 functionality has been restored. Use as normal.
Could not tune/match, or run any experiments. Appears to be some sort of connectivity error. It doesn’t get past “acbbsms: initializing ACB…”
Here’s the error chain:
“ProcessTable: Timeout occurred when starting child processes: Interrupted system call”
then “Error in copmem: – cannot send command to coprocessor (timeout: flag=1). Check for bad RCU/TCU or crashed startd on CCU” then a third error message “wobb error (stderr) Error in childprint: – cannot send message to parent (timeout: flag=69). Check for bad hardware or crashed startd on CCU” then the fourth error message in the chain: “stop coproc: not all children have terminated!”
I’ve had this issue multiple times over the past year; can we have instructions for troubleshooting this if it comes up again?
Locking and setting the temperature worked fine.
The machine would not get the receiver gain. Wouldn’t lock either. Logging out and signing back in didn’t help, nor did reloading the proton parameters or switching samples.
Tried to lock and tune but software was unable to execute “wobb.” I logged-off the computer again and received same error messages:
1 ProcessTable: Timeout occured when starting child processes: Interrupted system call
2 Error in copmem:
– cannot send command to coprocessor (timeout: flag =1).
Check for bad RCU/TCU or crashed startd on CCU
3 Error in childprint:
– cannot send message to parent (timeout: flag=69).
Check for bad hardware or crashed startd on CCU
4 stop_coproc: not all children have terminated!
How can we fix these problems and run experiments in the future?
Got an “internal error” when tried xaua. Had to acquire data via rga/zg.
This is a general comment. Whenever I am on the spectrometer, I cannot shorten my reservation by changing the end time on the reservations page. I always get the “Request exceeds maximum time allowed during walk on time” error.
Used instrument this afternoon for a VT experiment with Jon. The evaporator hose was quite frozen on to the glass Dewar piece at the end of the experiment (magnet had been cold for roughly 2 hours total: 30 minutes between 250 and 200 K, 45 min between 230 and 260 K, 20 min at 260, 20 min at 280, and then frozen to the instrument when we got back to room temperature). We patiently let the piece thaw by turning off the evaporator and then taking the hose out of the Dewar (while frozen, with a few people assisting so as not to put any torque on the glass piece). Within 20 minutes, the piece freely came off the glass piece and the instrument returned to 298 K. Nothing strange so far.
Right before we went to remove the sample (after roughly 5 minutes at 298 K), instrument temperature spiked to 340 K (The edte window was set to 298 K, the heater appeared off in that window, nothing had changed at the instrument). Sample was warmer than room temp, but not 340 K warm? The “ejection” air flow then proceeded to drop the temperature back to 298 K and without changing anything, the instrument maintained that temperature? This seems like a really weird thing?
I’ve sat and monitored the temperature now for 45 minutes or so to make sure that it’s stable at 298 without any weird spikes. The only thing that’s weird now is that the lock signal is incredibly jumpy (way more so than usual on the 498).
It sounds like the vibration damper is leaking air out of the foot closest to the refrigeration unit. I put my hand next to it and felt air squirting out of the top part (looks like some kind of nut/bolt type assembly?)
Difficulties logging on. my username was added to a “control list?” Other users couldn’t log on either (Wilson Bailey), so I gave the computer a hard restart and it worked again.
Wobb center way off and not clearly defined