time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

View all threads

HP 5335a opt 40 addendum

NJ
Norman J McSweyn
Tue, Oct 21, 2008 6:10 AM

Hi all!
I'm having some trouble programming my 5335a. The manual that Agilent
has doesn't cover opt 40. Have psyched out several of the codes that
aren't in the manual.
Using Labview 8, string that is sent is this: in,az1,bz1,ap0,bp0,fn2,trg
(initialize)
(chA impedance 50 ohms)
(chB """"""""""""""""")
(chA preset off)
(chB""""""""""")
(time interval)
(trigger measurement)

CHANNEL A AND B IMPEDANCE COMMANDS ARE GUESSES!!!!

The result is a hang with no measurement.
If I forgo the impedance settings via gbib (doing it manually), I will
get an error (front panel 1.0). Manual says this is an invalid HPIB
alpha command sent. I will get a measurement. It takes 1.5 sec or so.

I'm on vacation for the next two weeks. This am will be busy. Will be
free 16Z give or take.
Thanks,
Norm n3ykf

Hi all! I'm having some trouble programming my 5335a. The manual that Agilent has doesn't cover opt 40. Have psyched out several of the codes that aren't in the manual. Using Labview 8, string that is sent is this: in,az1,bz1,ap0,bp0,fn2,trg (initialize) (chA impedance 50 ohms) (chB """"""""""""""""") (chA preset off) (chB""""""""""") (time interval) (trigger measurement) CHANNEL A AND B IMPEDANCE COMMANDS ARE GUESSES!!!! The result is a hang with no measurement. If I forgo the impedance settings via gbib (doing it manually), I will get an error (front panel 1.0). Manual says this is an invalid HPIB alpha command sent. I will get a measurement. It takes 1.5 sec or so. I'm on vacation for the next two weeks. This am will be busy. Will be free 16Z give or take. Thanks, Norm n3ykf
MD
Magnus Danielson
Tue, Oct 21, 2008 11:19 PM

Norman J McSweyn wrote:

Hi all!
I'm having some trouble programming my 5335a. The manual that Agilent
has doesn't cover opt 40. Have psyched out several of the codes that
aren't in the manual.
Using Labview 8, string that is sent is this: in,az1,bz1,ap0,bp0,fn2,trg
(initialize)
(chA impedance 50 ohms)
(chB """"""""""""""""")
(chA preset off)
(chB""""""""""")
(time interval)
(trigger measurement)

CHANNEL A AND B IMPEDANCE COMMANDS ARE GUESSES!!!!

They are correct.

You do not say anything on trigger levels and other 040 settings
thought. The programming example 13 indicates that you should do
something like this:

in,fu2,co1,bs1,tr1,at+2.71,bt+3.14

This becomes

in  - Initialize
fu2 - Time Interval
co1 - Set COMA on
bs1 - Set SLOPE B to NEGATIVE
tr1 - Set TRIGGER LEVELS to REMOTE
at+2,71 - Set TRIGGER LEVEL A to +2,71 V
bt+3.14 - Set TRIGGER LEVEL B to +3,14 V

The programming example does not use the trg command!

The result is a hang with no measurement.
If I forgo the impedance settings via gbib (doing it manually), I will
get an error (front panel 1.0). Manual says this is an invalid HPIB
alpha command sent. I will get a measurement. It takes 1.5 sec or so.

I'm on vacation for the next two weeks. This am will be busy. Will be
free 16Z give or take.

I hope the above hints helps. I haven't tested them against my HP5335A
(with option 040) but I could do the effort if you need additional
assistance.

Cheers,
Magnus

Norman J McSweyn wrote: > Hi all! > I'm having some trouble programming my 5335a. The manual that Agilent > has doesn't cover opt 40. Have psyched out several of the codes that > aren't in the manual. > Using Labview 8, string that is sent is this: in,az1,bz1,ap0,bp0,fn2,trg > (initialize) > (chA impedance 50 ohms) > (chB """"""""""""""""") > (chA preset off) > (chB""""""""""") > (time interval) > (trigger measurement) > > CHANNEL A AND B IMPEDANCE COMMANDS ARE GUESSES!!!! They are correct. You do not say anything on trigger levels and other 040 settings thought. The programming example 13 indicates that you should do something like this: in,fu2,co1,bs1,tr1,at+2.71,bt+3.14 This becomes in - Initialize fu2 - Time Interval co1 - Set COMA on bs1 - Set SLOPE B to NEGATIVE tr1 - Set TRIGGER LEVELS to REMOTE at+2,71 - Set TRIGGER LEVEL A to +2,71 V bt+3.14 - Set TRIGGER LEVEL B to +3,14 V The programming example does not use the trg command! > The result is a hang with no measurement. > If I forgo the impedance settings via gbib (doing it manually), I will > get an error (front panel 1.0). Manual says this is an invalid HPIB > alpha command sent. I will get a measurement. It takes 1.5 sec or so. > > I'm on vacation for the next two weeks. This am will be busy. Will be > free 16Z give or take. I hope the above hints helps. I haven't tested them against my HP5335A (with option 040) but I could do the effort if you need additional assistance. Cheers, Magnus
NJ
Norman J McSweyn
Wed, Oct 22, 2008 4:32 AM

Magnus,
Thanks for the enlightenment!
I modified the driver that NI has on their site. Works. Have been
manually setting the trigger levels on the front panel. Now know how to
use the -40 to do it.

I'll further modify the driver in the AM.

The manual I have doesn't have programming example 13.

I take it that the instrument will trigger automatically when the
conditions are met?

I'm comparing the 1pps output from an M12+t to the divided down 10MHz
out from a Thunderbolt.

Next hurdle is to do something with the collected data.

Thanks,
Norm

Magnus, Thanks for the enlightenment! I modified the driver that NI has on their site. Works. Have been manually setting the trigger levels on the front panel. Now know how to use the -40 to do it. I'll further modify the driver in the AM. The manual I have doesn't have programming example 13. I take it that the instrument will trigger automatically when the conditions are met? I'm comparing the 1pps output from an M12+t to the divided down 10MHz out from a Thunderbolt. Next hurdle is to do something with the collected data. Thanks, Norm
MD
Magnus Danielson
Wed, Oct 22, 2008 7:56 AM

Dear Norm,

Norman J McSweyn wrote:

Magnus,
Thanks for the enlightenment!
I modified the driver that NI has on their site. Works. Have been
manually setting the trigger levels on the front panel. Now know how to
use the -40 to do it.

Great! Happy to help!

I'll further modify the driver in the AM.

The manual I have doesn't have programming example 13.

I haven't looked in detail, but I think the HP5335A manual on the HP
site is the same as I have, and then you should have all the details you
need.

I take it that the instrument will trigger automatically when the
conditions are met?

Indeed it does.

I'm comparing the 1pps output from an M12+t to the divided down 10MHz
out from a Thunderbolt.

Next hurdle is to do something with the collected data.

Way to go!

You should learn to calculate Allan deviation and friends. Not to hard.
You should learn to estimate drift rate and subtract that from
measurements, since that is often ignored and the drift rate will form a
lower floor for longer measurement runs. This is an error which is
either canceled by locking or by software.

Cheers,
Magnus

Dear Norm, Norman J McSweyn wrote: > Magnus, > Thanks for the enlightenment! > I modified the driver that NI has on their site. Works. Have been > manually setting the trigger levels on the front panel. Now know how to > use the -40 to do it. Great! Happy to help! > I'll further modify the driver in the AM. > > The manual I have doesn't have programming example 13. I haven't looked in detail, but I *think* the HP5335A manual on the HP site is the same as I have, and then you should have all the details you need. > I take it that the instrument will trigger automatically when the > conditions are met? Indeed it does. > I'm comparing the 1pps output from an M12+t to the divided down 10MHz > out from a Thunderbolt. > > Next hurdle is to do something with the collected data. Way to go! You should learn to calculate Allan deviation and friends. Not to hard. You should learn to estimate drift rate and subtract that from measurements, since that is often ignored and the drift rate will form a lower floor for longer measurement runs. This is an error which is either canceled by locking or by software. Cheers, Magnus
NJ
Norman J McSweyn
Wed, Oct 22, 2008 3:01 PM

Magnus Danielson wrote:

Dear Norm,

Norman J McSweyn wrote:

Magnus,
Thanks for the enlightenment!
I modified the driver that NI has on their site. Works. Have been
manually setting the trigger levels on the front panel. Now know how to
use the -40 to do it.

Great! Happy to help!

I'll further modify the driver in the AM.

The manual I have doesn't have programming example 13.

I haven't looked in detail, but I think the HP5335A manual on the HP
site is the same as I have, and then you should have all the details you
need.

Magnus,
Unfortunatly, the manual on Agilent's site is the one that I have,
without the -40 addendum.

I take it that the instrument will trigger automatically when the
conditions are met?

Indeed it does.

I'm comparing the 1pps output from an M12+t to the divided down 10MHz
out from a Thunderbolt.

Next hurdle is to do something with the collected data.

Way to go!

You should learn to calculate Allan deviation and friends. Not to hard.
You should learn to estimate drift rate and subtract that from
measurements, since that is often ignored and the drift rate will form a
lower floor for longer measurement runs. This is an error which is
either canceled by locking or by software.

Data is time stamped and in a text file. One file is the TI data from
the 5335a, the other is part of the @@Hn (with the sawtooth correction)
message from the M12+T. In the interest of ensuring that I have a useful
data set, I need to find a way to use Excel to check that no seconds
have been skipped. Then post process the TI measurement to reflect the
1pps sawtooth.

The next steps are a mystery. I drive locomotives for a living. This is
a hobby!! Have been playing with math for a while now, so it's not a
black art! Didier has a few pages on measurements and one with tvb's
explanation of Allan deviation. This will be today's reading!!!

Translating this into an Excel spreadsheet is the next hurdle.

Comparing the two devices (Thunderbolt to M12+T) is rather banal. It's
like comparing two types of apples together. Not much difference.
However, it's a steep learning curve to get to this point.

Any pointers are welcome!

Thanks,
Norm n3ykf

Cheers,
Magnus


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Magnus Danielson wrote: > Dear Norm, > > Norman J McSweyn wrote: >> Magnus, >> Thanks for the enlightenment! >> I modified the driver that NI has on their site. Works. Have been >> manually setting the trigger levels on the front panel. Now know how to >> use the -40 to do it. > > Great! Happy to help! > >> I'll further modify the driver in the AM. >> >> The manual I have doesn't have programming example 13. > > I haven't looked in detail, but I *think* the HP5335A manual on the HP > site is the same as I have, and then you should have all the details you > need. Magnus, Unfortunatly, the manual on Agilent's site is the one that I have, without the -40 addendum. > >> I take it that the instrument will trigger automatically when the >> conditions are met? > > Indeed it does. > >> I'm comparing the 1pps output from an M12+t to the divided down 10MHz >> out from a Thunderbolt. >> >> Next hurdle is to do something with the collected data. > > Way to go! > > You should learn to calculate Allan deviation and friends. Not to hard. > You should learn to estimate drift rate and subtract that from > measurements, since that is often ignored and the drift rate will form a > lower floor for longer measurement runs. This is an error which is > either canceled by locking or by software. > Data is time stamped and in a text file. One file is the TI data from the 5335a, the other is part of the @@Hn (with the sawtooth correction) message from the M12+T. In the interest of ensuring that I have a useful data set, I need to find a way to use Excel to check that no seconds have been skipped. Then post process the TI measurement to reflect the 1pps sawtooth. The next steps are a mystery. I drive locomotives for a living. This is a hobby!! Have been playing with math for a while now, so it's not a black art! Didier has a few pages on measurements and one with tvb's explanation of Allan deviation. This will be today's reading!!! Translating this into an Excel spreadsheet is the next hurdle. Comparing the two devices (Thunderbolt to M12+T) is rather banal. It's like comparing two types of apples together. Not much difference. However, it's a steep learning curve to get to this point. Any pointers are welcome! Thanks, Norm n3ykf > Cheers, > Magnus > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. >