The Nortel devices can talk either as a Thunderbolt or as a SCPI device.  Use it as a Thunderbolt (/rxt).  In SCPI mode the satellite positions are polled for once a minute (at xx:xx:33).  Thunderbolt mode provides much more and better control of the receiver.

However I don't see any satellite data as I do with my Resolution T.  I
am using

I tried /rxt but that won't communicate.  Must I put the unit in
Thunderbolt mode?    Is there
a jumper or a command that will do it?  The manual that I have does not
mention different
modes.  It only talks about SCPI.

Thanks,
Pete.

On 1/5/2017 12:41 PM, Mark Sims wrote:

I have a '50AA here.  But I don't use any command line options relating to
box ID.  Just start up LH - LH talks to the box, determines it's a Trimble
variant, and off to the races it goes.

73/jeff/ac0c
www.ac0c.com
alpha-charlie-zero-charlie

-----Original Message-----
From: Peter Reilley
Sent: Thursday, January 05, 2017 12:11 PM
To: Discussion of precise time and frequency measurement
Subject: Re: [time-nuts] No sat positions in LH with Trimble NTBW50AA?

I tried /rxt but that won't communicate.  Must I put the unit in
Thunderbolt mode?    Is there
a jumper or a command that will do it?  The manual that I have does not
mention different
modes.  It only talks about SCPI.

Thanks,
Pete.

On 1/5/2017 12:41 PM, Mark Sims wrote:

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.

I'm using /rxt for my NTBW50AA and after reading your message I changed
it to /rxy.
I got the same problems as Pete described, so I returned to Thunderbolt
mode.

Regards,
Ignacio, EB4APL

El 05/01/2017 a las 18:41, Mark Sims escribió:

Originally I set the BAUD rate to 19200 with 7 bits and ODD parity
because that
is what the manual said.  I confirmed these settings using an
oscilloscope.  With
that, LH mostly worked.

After some of the suggestions here I tried this;
"C:\Program Files (x86)\Heather\heather.exe" /3 /br=9600:8::1 /rxt /gb
/tz=-5EST/-4DST /vx
This worked perfectly.

It is the BAUD rate that threw me.  I have a lot of experience with
ASYNC going back to the days
of the ASR33 and ASR35.  I know that some systems were auto-BAUD but
the manual does not
mention that, I assumed that it was fixed at 19200 which actually did work.

One curious thing that I noticed; previously the clocks differed by
about 18 seconds between my Resolution T
and my NTBW50AA.  The NTBW50AA agreed with my Win10 machine setup as
Microsoft installed it.
With the NTBW50AA in Thunderbolt mode, the Res T and the NTBW50AA both
agree.  Now, only Win10 is
out by about 18 seconds.

Anyway, thanks for all the help,
Pete.

On 1/5/2017 12:41 PM, Mark Sims wrote: