Re: [AMMRL] Tuning rods pinned?

From: Baleja, James D via groups.io <jim.baleja=tufts.edu_at_groups.io>
Date: Thu, 2 Oct 2025 17:01:11 +0000

Thank you EdEz, Karel, and Clemens for your comments.

I’m working remotely today, so I’ll try the PICS line removal
and reconnection tomorrow. So far the other software suggestions haven’t worked
(such as alternately between WOBB and ATMM and altering the .bb file).

I also noticed that the TUNEFREQ (which flickers between 590.211 and 590.133)
is almost exactly 10 MHz off from the CENTERFREQ (600.133).

Let’s hope for the PICS!

Jim


--
Jim Baleja
(he/him/his)
Associate Professor
Departments of Medical Education (office: MV525S) and Developmental, Molecular, & Chemical Biology (lab: MV614)
Tufts University School of Medicine
136 Harrison Avenue
Boston, MA 02111
Phone: 617-636-6872 (goes to voice mail)
https://pubmed.ncbi.nlm.nih.gov/?term=baleja&sort=date


> From: main_at_ammrl.groups.io on behalf of Ezell, Ed via groups.io
> Date: Thursday, October 2, 2025 at 12:40 PM
> To: main_at_ammrl.groups.io
> Subject: [External] Re: [AMMRL] Tuning rods pinned?

Hey Jim, this has popped up and Mike Grove of Brukertold me to:" go to
/conf/instr/probeheads and find the .bb file for the probe installed. Open
the text file and find the $atmaposset line for the nucleus and lock solvent
(mine was solvent specific failure) after the solvent name there are a bunch
of commas and numbers etc. that are the Starting Positions for the tuning
motors. Easiest fix is probably just replace numbers in DMSO line (my solvent
was DMSO for the ATMA error) with the ones in the Acetone line and save the
file. Then try the ATMA with DMSO. Correcting motor positions should do
the trick."

The lines I used look like this:

DMSO -001,+000.0235, +00.0024 + 008#
Acetone -001, +000.0021, +00.0026 +008#

so I changed that +000.0235 number for DMSO to be +000.0021 and it did indeed
do the trick! That was in 10/18/24, later in 4/11/25 it happened again this
time for CDCl3. My notes don't say what solvent I compared to but it was a
number 000.0235 changed to 000.024 but also needed a Topspin restart to
take effect.

EdEz
________________________________
> From: main_at_ammrl.groups.io on behalf of Anklin, Clemens via groups.io
> Sent: Thursday, October 2, 2025 7:28 AM
> To: main_at_ammrl.groups.io <main_at_ammrl.groups.io>
> Subject: Re: [AMMRL] Tuning rods pinned?


HI Jim

have you tried unplugging and replugging the PICS cable?

Clemens

On 10/1/2025 5:53 PM, Baleja, James D via groups.io wrote:

Hi all, I'm getting this message, which I think means that the tuning rods
are pinned. I can tune fine on 13C.
atma_ProbeCorba_impl::start exception: Error: channel can't be wobbled with
this probe [Probe: [1H] can't be selected on the [1H] channel
[Nuc-MotorBase:movePreset-Motor-Nr:3 <1H Tune>: can't move to position -244 (current:3)]]

This is on a Bruker 600 Avance Probe TXI 600S3 H-C/N-D-05 Z

I know that a user was trying to tune the 1H channel to 19F, which I don't
think this probe will do.

Any comments would be welcome!

Thanks

Jim


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#2871): https://urldefense.com/v3/__https://ammrl.groups=
.io/g/main/message/2871__;!!PvDODwlR4mBZyAb0!VceZqrOjUhstnfEf24mTrw9KAbxtdh=
r6oA_pSRrPLV5EYo3cravIIEV87WrdEFsFf-GZQoDgZgrDXrJ2lPwicCNElDQB$
Mute This Topic: https://urldefense.com/v3/__https://groups.io/mt/115545023=
/7559972__;!!PvDODwlR4mBZyAb0!VceZqrOjUhstnfEf24mTrw9KAbxtdhr6oA_pSRrPLV5EY=
o3cravIIEV87WrdEFsFf-GZQoDgZgrDXrJ2lPwicBlPVPvo$
Group Owner: main+owner_at_ammrl.groups.io
-=-=-=-=-=-=-=-=-=-=-=-




Received on Thu Oct 02 2025 - 10:33:10 MST