Hi Sameer,
if the PICS says that 240W is the maximum power then this is the power the
components in the probe will tolerate. The fact that the acceptance power for
the 15N power is only 100W means that this is the power that was needed to
reach the specified pulse length. For example if the probe specification says
25 usec for the 15N 90 degree pulse then the during testing and installation
of the probe the power will be adjusted to meet this specification.
With best regards
Clemens
On 2/28/2025 2:27 PM, Sameer Al-Abdul-Wahid via groups.io wrote:
Thanks to everyone who replied, both on AMMRL and privately.
The “why” is me being (over)protective of an older probe in
a multi-user environment. For example, our 15N channel has a PICS limit of
240 W whereas our acceptance p90 power is 100 W, so I’d prefer that
to be the software limit. But, as Clemens noted, POWCHK won’t protect
against long durations at 100 W, so this is still not
My concern here is simply being (over)protective of an older probe in a multi-user
environment. For example, our 15N channel has a PICS limit of 240 W, but our
acceptance p90 power is 100 W, so I’d prefer that to be the software limit.
However, as Clemens noted, this still won’t prevent a user from mis-setting
a long pulse at 100 W.
It seems the options are to request a new PICS file or to disconnect the PI=
CS cable—losing ATMM/ATMA capability in the process—and def=
ine the probe and power settings manually.
Thanks again,
Sameer
P.S. I explored adding an if statement to Avance.incl to check the power level
and abort the experiment if was too high, but could not find a way to make
that work.
--
Sameer Al-Abdul-Wahid, Ph.D. | Manager
Nuclear Magnetic Resonance Centre | University of Guelph
519-824-4120 ext. 58914 | s.wahid_at_uoguelph.ca
http://nmr.uoguelph.ca/
> From: main_at_ammrl.groups.io on behalf of Anklin, Clemens via groups.io
> Date: Thursday, February 27, 2025 at 19:25
> To: main_at_ammrl.groups.io
> Subject: Re: [AMMRL] Limiting pulse power on Bruker AV III with PICS probe
Sameer
my first question would be, why do you want to limit the power to below what
PICS allows. The PICS power levels are safe for the probe. These entries
define the highest power the probe can tolerate. Of course there are durations
that might be unsafe to your samples. Setting a pulse to several seconds at
maximum power will also not be healthy for the system.
I would not recommend to put an attenuator between frequency source and amplifier.
This would no longer guarantee a linear behavior over the power range.
Best regards
Clemens
On 2/27/2025 2:41 PM, Sameer Al-Abdul-Wahid via groups.io wrote:
Hi everyone,
For a Bruker AV III console and TopSpin 3.6.5, and using a PICS probe, does
anyone know a way to limit the pulse power for a specific nucleus and/or channel?
I know some specific solutions exist (add code to the pulprog, or edit edprobe
for non-PICS probes) but I’m searching for a method that would work
on a PICS probe and across all experiments.
Thanks,
Sameer
--
Sameer Al-Abdul-Wahid, Ph.D. | Manager
Nuclear Magnetic Resonance Centre | University of Guelph
519-824-4120 ext. 58914 | s.wahid_at_uoguelph.ca
http://nmr.uoguelph.ca/
--
==========================
==========================
====================
Clemens Anklin Ph.D. Vice President
Bruker BioSpin NMR Applications & Training
15 Fortune Drive NEW Phone: 978-313-5NMR(5667)
Billerica MA 01821 bluesky: _at_canklin.bsky.social
web: http://www.bruker.com
e-mail: clemens.anklin_at_bruker.com
==========================
==========================
====================
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#2093): https://urldefense.com/v3/__https://ammrl.groups=
.io/g/main/message/2093__;!!PvDODwlR4mBZyAb0!RF7epAz3L6_i_e8abNkAh6RkB7I0wO=
kfDiXfZIZXvqpaXN4jOKjo5d5BdKWTBD6muM6UfK1uwScKhQcmFklvnt6uj7-W$
Mute This Topic: https://urldefense.com/v3/__https://groups.io/mt/111424251=
/7559972__;!!PvDODwlR4mBZyAb0!RF7epAz3L6_i_e8abNkAh6RkB7I0wOkfDiXfZIZXvqpaX=
N4jOKjo5d5BdKWTBD6muM6UfK1uwScKhQcmFklvnqVzt9qO$
Group Owner: main+owner_at_ammrl.groups.io
-=-=-=-=-=-=-=-=-=-=-=-
Received on Fri Feb 28 2025 - 14:36:21 MST