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:
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.
---------------
I just got my Trimble NTBW50AA GPSDO up and running with Lady Heather 5.0.
However I don't see any satellite data as I do with my Resolution T. I
am using
_______________________________________________
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.
_______________________________________________
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.
