Re: [time-nuts] Lady Heather and Lucent RFTGm-II-XO / RFTGm-II-Rb

[Rodger Adams via time-nuts]

> Hey Mark,
>  
> Thanks for the reply.  
>  
> It was relatively straightforward getting the Lucent RFTG software to work.  
> No special cable or PCMCIA card was needed.  Here’s what I’ve learned in the 
> few days that I’ve had my modules. 
>  
> First, the RFTG software runs under Windows XP with no problem.  I gave up on 
> trying with Windows 10 and compatibility modes.  I downloaded virtualbox 
> (free) which lets me run a Windows XP virtual machine on Windows 10.  (you’ll 
> still need to have an XP install disk)   I gave the VM just enough memory and 
> disk space for it to run RFTG so it runs without wasting a lot of resources 
> on the host, Windows 10 pc.
>  
> For the physical interface I use standard, cheap RS-232 to USB serial 
> adapters.  Virtualbox allows you to select which USB devices get passed 
> through from the host to the XP VM so I simply pass the serial port usb 
> device through to the VM and run the USB serial port drivers in the XP VM.  
>  
> Now that I have a working XP PC with a serial port the rest is easy.  The 
> RS-232 port can be connected to the RS-422/485 port with a simple 3 wire 
> connection, as follows.  On the RS-232 interface, connect pins 2,3 and 5 to 
> pins 9,8, and 7 (in that order) of the RS-422 port on the RFTGm-II-XO module. 
>  This is the port on the far right end of the XO module that is labeled 
> RS-422/1 PPS.  As soon as I made this connection, I was able to see serial 
> data flowing from the module at 9600N81 using a terminal program.  After 
> running RFTG.exe and selecting the right serial port, RFTG came to life 
> showing the GPS status, etc.   By moving the RS-232 interface over to the 
> RS-422 port on the Rb module, (same pin configuration) you can monitor the 
> status of the Rb module instead. 
>  
> The RFTG software is designed to use 2 serial ports, 1 for the XO and 1 for 
> the Rb.  I think this is where the Lucent proprietary “Y” cable comes into 
> play.  Although I haven’t proven this yet, I believe that the 2 RS-422 
> connections (1 from the XO and 1 from the Rb) are simply combined in the 
> module on the upper left side of the frame. (above the Rb module, connectors 
> labeled J7 through J11)  I’m guessing that the Lucent “Y” cable plugs into 
> J7, J8 or J9 and splits the “combined” RS-422 signals back into 2 separate 
> RS-422 ports.  I have some USB to RS-422 ports (although I could just use 
> RS-232 ports)  and some DB-15 connectors on order.  As soon as I prove this 
> to be the case, I’ll post the cable schematic here.  Once I have this working 
> it will allow for monitoring and control of both the XO and the Rb 
> simultaneously using RFTG.exe. (right now, I can only look at either one at a 
> time)
>  
> If I can help you in any way with getting this set up for Lady Heather please 
> let me know.  I’m not a programmer, but will be glad to capture data, test, 
> or assist in any way I can.
>  
> Thanks,
>  
> Rodger


> On May 23, 2017, at 1:43 PM, Mark Sims  wrote:
> 
> I also got one in.   Unfortunately it talks some proprietary, undocumented 
> command set.   I was hoping to be able to sniff what the Lucent code is doing 
> and eventually add support to Lady Heather.
> 
> How did you connect up to the device to use the Lucent code?  The 
> documentation talks about using some PCMCIA RS-485 card and seems to use a 
> "Y" cable that has a toggle switch that switches between the two boxes... 
> that cable is undocumented.
> 
> ___
> 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.

[time-nuts] HP-53132A standard oscillator performance

[Mark Sims]

I recently got in a 53132A with the standard oscillator.   I now have Lady 
Heather working with it (along with any counter that can stream readings out a 
serial port).  Attached is a plot of the performance over a 15 hour period.  
Counter set to time interval mode,  start=HP-5071A 1PPS,  stop=53132A reference 
output.  There was around 10 ns of coax delay on the reference output to 
minimize possible effects of the counter using its own reference as the stop 
signal. 

The frequency span was around 1Hz over the 15 hours... with some rather funky 
frequency excursions.

Speaking of 53132A oscillators,  I want to get one of the aftermarket boards 
off of Ebay.  Does anybody have any experience with them?  I leaning towards 
the board by Gerry Sweeny since it has multiple oscillator footprints on it and 
I have some rather nice Oscilloquartz 8663's that will go on it.

I also want to add one of the 3 GHz option boards.  Again, any experience with 
those?  The Chinese ones claim better sensitivity than the one from Poland...  
but you know buyer beware about Chinese specs...   There is also an $80 8 GHz 
(usable to 10 GHz) board,  but its sensitivity specs are rather poor.___
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.

Re: [time-nuts] Looking for info on Trimble 16634-10

[Scott Armstrong]

Hi Guys,

Found a little info..

The main board/receiver used in this unit is also used in the Trimble
Placer 100 and RefTek 73A.
Hopefully, these two leads may develop into some useful info.

Thanks,
Scott AA5AM

On Tue, May 23, 2017 at 6:59 AM, Bob kb8tq  wrote:

> Hi
>
> Yet again another quick read mistake :)
>
> Bobb
>
> > On May 23, 2017, at 7:35 AM, Tim Shoppa  wrote:
> >
> > Bob, that was 16.368MHz, an extremely common crystal to find in the first
> > couple generations of GPS receivers. 16.368 MHz is 16 times the 1.023 MHz
> > C/A GPS signal chipping rate; multiplied by 96.25 to get the 1575.42 MHz
> L1
> > frequency and multiplied by 75 to get the 1227.60 MHz L2 frequency.
> >
> > Tim N3QE
> >
> > On Tue, May 23, 2017 at 7:24 AM, Bob kb8tq  wrote:
> >
> >> Hi
> >>
> >> If you guess that the design started in 90 and ran through 93~94 that
> >> is a very early unit for Trimble. 16.384 MHz suggests some sort of
> telecom
> >> or data bus application.
> >>
> >> Bob
> >>
> >>> On May 22, 2017, at 11:48 AM, Scott Armstrong  wrote:
> >>>
> >>> Hi Guys,
> >>>
> >>> I popped open the case.  Not too crowded in side. The case is an
> extruded
> >>> aluminum case that has the back endplate  welded on.
> >>>
> >>> There are 4 board assemblies in the case.
> >>>
> >>> *Interface board that connects the 22 pin connector to the other two
> >> boards.
> >>> * Power supply board. (12016-00). Main component looks to be a DC-DC
> >>> converter made by Computer Products.
> >>> * Main board (14636-)  This board has a 16.368 MHz osc made by NDK.
> >>> * A daughter board (14789E) which is the receiver and is attached to
> the
> >>> main board.
> >>>
> >>> Date codes I see are 89, 91, 92 and 93  so unit was probably assembled
> in
> >>> '93.
> >>>
> >>> Maybe some of the assembly numbers will be recognizable if they are
> used
> >> in
> >>> other units.
> >>>
> >>> Thanks,
> >>> Scott AA5AM
> >>>
> >>>
> >>> On Sat, May 20, 2017 at 12:33 AM, Bill Hawkins 
> >> wrote:
> >>>
>  FWIW, that looks like aviation equipment (gov't or civil), with a
>  locking connector.
> 
>  That stuff is designed for minimum size and weight. You might find the
>  inside of the box quite cramped.
> 
>  Buying aviation parts is even more expensive than buying boat parts.
> 
>  Bill Hawkins
> 
> 
>  -Original Message-
>  From: time-nuts on behalf Of Bob Bownes
>  Sent: Friday, May 19, 2017 10:48 PM
> 
>  Pretty sure that connector is an off the shelf Amphenol part. If you
>  can't find it, however, you can replace it with an off the shelf one
>  that will fit in the same hole. (If your lucky, you can even re-use
> the
>  pins.)
> 
>  The replacement will run you about $30-40 for the pair, chassis and
>  plug. Check Mouser, etc.
> 
> > On May 19, 2017, at 23:21, Bob kb8tq  wrote:
> >
> > The mating side of that 22 pin connector isn't going to be cheap. It
> > looks like something out of their government systems group back in
> the
>  late 90's. If it is, you may have a hard time getting info on it.
> > I'd pop it open and see what's inside. At least that will give you an
> > idea if it's 20 years old or 5 years old. Knowing the era should help
>  in the search for information.
> >
> > Bob
> >
> >> On May 19, 2017, at 10:21 PM, Scott Armstrong 
> wrote:
> >>
> >> I acquired a Trimble 16634-10 receiver. A search of the web has
> >> turned up nothing so far.
> >> The unit is in a steel box built like a tank. SMA connector for
> >> antenna input and a 22 pin circular connector for the I/O and power
> >>
> 
>  ___
>  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.
> >>
> >> ___
> >> 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.
>
> ___
> 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] Lady Heather and Lucent RFTGm-II-XO / RFTGm-II-Rb

[Mark Sims]

I also got one in.   Unfortunately it talks some proprietary, undocumented 
command set.   I was hoping to be able to sniff what the Lucent code is doing 
and eventually add support to Lady Heather.

How did you connect up to the device to use the Lucent code?  The documentation 
talks about using some PCMCIA RS-485 card and seems to use a "Y" cable that has 
a toggle switch that switches between the two boxes... that cable is 
undocumented.

___
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.

Re: [time-nuts] gLAB PPP noisy clock residuals

[Ole Petter Ronningen]

>
> I did a comparison of a few PPP results some years ago, maybe you saw it
> already
> http://www.anderswallin.net/2013/12/comparing-gps-ppp-solutions/


Ah, yes I forgot about that! Nice, I'll revisit RTKlib again.


> For the web-service running NrCAN, there was an URL API that allows running
> the filter/algorithm forward and backward ("filtfilt" in matlab or numpy),
> to get rid of the initial transient in only the forward solution. You could
> ask the maintainers, or I can try to dig in my archives (I should have
> python code that submits RINEX to the service and retrieves the results).
>

 That could be an option, I will contact the maintainers.

if you dig in the ESA gLAB settings, can you set the ZTD-model identically
> and see what happens?
>

I will investigate the  TZD-model, thanks for the tip. I was trying to wrap
my head around differential code biases; It seems NrCAN PPP applies
corrections, but I believe gLAB does not by default (and it crashes when I
give it -model:dcb:p1c1 strict). Not sure if DCB would show up as an issue
at the level I am looking at now, though.

If you post your RINEX:es and other relevant data I can try processing also
> and see what I get.


Appreciate the offer! :) Link to a recent RINEX that gives a reasonable
result from NRcan PPP:
https://www.dropbox.com/s/er9o6lfg4gva486/2017.05.21.zip?dl=0

Thanks!
Ole
___
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.