TboltMon isn't the only program that can read TSIP, but it is mostly aimed at Thunderbolt owners. A better piece of software would be Trimble Studio and/or TSIP talker. You can get them from here...
ftp://ftp.trimble.com/pub/sct/embedded/bin/
regards
Tim
Ok, TrimbleStudio does not appear to work with this device, despite it being labelled as "Trimble". The docs mention a protocol called UCCM. If I connect to the device with a serial terminal, at 57600/8/N/1, I get a UCCM-P prompt, and if I type help it lists the commands below. This appears similar, but not identical to the Lucent command set. For example, you do not enter a ":" character before running a command like "SYST:STAT?". Entering that command gives the following response (GPS coordinates removed):
UCCM-P >SYSTEM:STATUS?
-------------------------------------------------------------------------------
57964-80 serial number 60498671 firmware ver 2.0.1.6-01 LINK mode
-------------------------------------------------------------------------------
Reference Status __________________________ Reference Outputs _______________
XX Ref 8KHz 0: [LOS]
XX Ref 8KHz 1: [LOS] TFOM 2 FFOM 0
XX Ref 8KHz 2: [LOS] UCCM A Status[ACTIVE]
XX Ref 8KHz 3: [LOS]
>> GPS: [phase:-8.6E-08]
ACQUISITION ...................................................[GPS 1PPS Valid]
Tracking: 5 ____ Not Tracking: 6 ________ Time ____________________________
PRN El Az C/N PRN El Az GPS 00:13:33 08 Aug 2015
2 14 73 35 5 45 62
26 31 307 33 25 31 195 ANT DLY 10 ns
29 85 88 47 16 10 327 Position ________________________
20 61 162 43 18 10 205 MODE Hold
13 11 108 36 15 7 141
21 44 261 LAT N xx:xx:xx.xxx
LON W xxx:xx:x.xxx
HGT +xxx.xx m (MSL)
Commands*IDN?
ALARm:HARDware?
ALARm:OPERation?
DIAGnostic:OUTPut ON|OFF
OUTPut:REFerence?
OUTPut:ACTive:ENABle
OUTPut:ACTive:DISable
OUTPut:ACTive:HOLDover:DURation:THReshold <seconds>
OUTPut:ACTive:HOLDover:DURation:THReshold?
OUTPut:INACTive
OUTPut:INACTive?
OUTPut:STATe?
SYNChronization:HOLDover:DURation:STATus:THReshold <seconds>
SYSTem:PRESet
SYNChronization:TFOMerit?
LED:GPSLock?
SYNChronization:FFOMerit?
GPS:POSition N or S,<deg>,<min>,<sec>,E or W,<deg>,<min>,<sec>,<height>
GPS:POSition?
GPS:POSition:HOLD:LAST?
GPS:REFerence:ADELay <numeric value>
GPS:REFerence:ADELay?
GPS:SATellite:TRACking:COUNt?
GPS:SATellite:TRACking?
DIAGnostic:ROSCillator:EFControl:RELative?
SYNChronization:TINTerval?
DIAGnostic:LOG:READ:ALL?
DIAGnostic:LOG:CLEar
SYSTem:PON
OUTPut:MODE?
SYSTem:STATus?
SYSTem:COMMunication:SERial1:BAUD 9600|19200|38400|57600
SYSTem:COMMunication:SERial1:BAUD?
SYSTem:COMMunication:SERial1:PRESet
SYSTem:COMMunication:SERial2:BAUD 9600|19200|38400|57600
SYSTem:COMMunication:SERial2:BAUD?
SYSTem:COMMunication:SERial2:PRESet
OUTPut:STANby:THReshold <seconds>
changeSN
SYNChronization:REFerence:ENABLE LINK|GPS
SYNChronization:REFerence:DISABLE LINK|GPS
SYNChronization:REFerence:ENABLE?
STATus
POSSTATus
TOD EN|DI
TIME:STRing?
REFerence:TYPE GPS|LINK
REFerence:TYPE?
PULLINRANGE 0|1|2|...|254|255
PULLINRNAGE?
DIAGnostic:LOOP?
DIAGnostic:ROSCillator:EFControl:DATA GPS|<value>
DIAGnostic:ROSCillator:EFControl:DATA?
OUTut:TP:SELection PP1S|PP2S
OUTut:TP:SELection?
GPSystem:SATellite:TRACking:EMANgle <degrees>
GPSystem:SATellite:TRACking:EMANgle?
DIAGnostic:TCODe:STATus:AMASk
DIAGnostic:TCODe:STATus:OMASk
DIAGnostic:TCODe:ERRor:AMASk
DIAGnostic:TCODe:ERRor:OMASk
DIAGnostic:HOLDover:DELay
DIAGnostic:HOLDover:DELay?
GPS:SATellite:TRACking:IGNore <PRN>, ...,<PRN>
GPS:SATellite:TRACking:IGNore?
GPS:SATellite:TRACking:INCLude <PRN>, ...,<PRN>
GPS:SATellite:TRACking:INCLude?
GPS:SATellite:TRACking:<select>:ALL
? or HELP
I was using an HP 5370B (resolution of < 50 ps - yes picoseconds) referenced to my Efratom FRT Rb standard.
Very nice, wish I had one of those in my lab
Commands
*IDN?
This is SCPI the *IDN? is a dead giveaway!
http://www.ivifoundation.org/scpi/default.aspx
http://www.ivifoundation.org/docs/scpi-99.pdf
Nope, it's someone's half-ass copy of SCPI. If it was SCPI, you'd commands with either a ':' or a "*".
I think this thing can return all the same sort of useful information you can get with the other units, but it just seems to be some proprietary command set that isn't going to be compatible with any software out there. That's really ashame, as it otherwise seems like a decent unit. Many of the commands are the same, but without the ':" prefix on them, the software isn't going to work.
Nope, it's someone's half-ass copy of SCPI. If it was SCPI, you'd commands with either a ':' or a "*".
I think this thing can return all the same sort of useful information you can get with the other units, but it just seems to be some proprietary command set that isn't going to be compatible with any software out there. That's really ashame, as it otherwise seems like a decent unit. Many of the commands are the same, but without the ':" prefix on them, the software isn't going to work.
You're right! - I should have looked closer, didn't even notice the : was missing.
And that's bloody annoying -
why only go 99% of the way ?
I was using an HP 5370B (resolution of < 50 ps - yes picoseconds) referenced to my Efratom FRT Rb standard.
Very nice, wish I had one of those in my lab
Actually, that's not my best time interval measurement tool.
https://www.eevblog.com/forum/testgear/wavecrest-dts-2077-teardown/msg279391/#msg279391
Ed
I assume that you figured out how to use it, can you show us what it does.
It's a Time Interval Counter. It measures frequency, time from A to B, rise time, fall time, period, pulse width, etc. But it does it *really* well!
I've been struggling to extract its full potential because it needs an input with very sharp rise and fall times. Forget 10 MHz, even 100 MHz isn't really enough, 1 GHz is okay! I built a circuit to square up a 5 or 10 MHz signal so that it can be properly measured, but it needs a little more work.
One of the particularly neat features is called a "strobing voltmeter". It allows you to sample the input at time intervals as small as 10 ps and report the results. In other words, it's digitizing the signal at 100 Gs/s.
I threw together a proof-of-concept program to test this. The attached picture is the output from my squaring circuit. Due to limitations in the strobing voltmeter, it took me quite a while to figure out how to get this picture. Initially I didn't think I would be able to do it. The horizontal scale is in units of 100 ps. The vertical scale is in volts. The voltage is small because the maximum voltage on the input is only 1.7 volts. I
really don't want to blow the input on this thing!
Ed
So for the display, what can you get out if it(resolution/digits). Yes, i read the manual, i replied in your orig thread.
One of the particularly neat features is called a "strobing voltmeter". It allows you to sample the input at time intervals as small as 10 ps and report the results. In other words, it's digitizing the signal at 100 Gs/s. I threw together a proof-of-concept program to test this. The attached picture is the output from my squaring circuit. Due to limitations in the strobing voltmeter, it took me quite a while to figure out how to get this picture. Initially I didn't think I would be able to do it. The horizontal scale is in units of 100 ps. The vertical scale is in volts. The voltage is small because the maximum voltage on the input is only 1.7 volts. I really don't want to blow the input on this thing!
Ed
Hi Ed
I have a 2079 , any chance of a copy of your proof program ?
The strobo graph seems really usefull
/Bingo
So for the display, what can you get out if it(resolution/digits). Yes, i read the manual, i replied in your orig thread.
I just measured a time interval from A to B. The reported result was 753,191,898.407 ps as the average of 1000 results. It also displays Std. Dev. (113.2 ps) and pk (+- 199.9 ps). The measurement took a couple of seconds because the input frequency was only 500 Hz.
Ed
Some more info on the Trimble/Wun-Hung-Lo hybrid. I powered it down to drill some ventilation holes in the case. Upon powering it back up, I see that the elevation mask setting has been reset.
So apparently they don't write settings to non-volatile RAM.
Some more info on the Trimble/Wun-Hung-Lo hybrid. I powered it down to drill some ventilation holes in the case. Upon powering it back up, I see that the elevation mask setting has been reset.
So apparently they don't write settings to non-volatile RAM.
Maybe there is no non-volatile RAM in these units. It appears that they came from a telco environment where they would be powered off of continuously float-charged lead-acid batteries. They would never be powered down so, no need for non-volatile storage. With a bit of reverse-engineering you should be able to add a battery backup to the GPS receiver itself. It's designed to support that.
FYI, I have a similar Trimble GPSDO that I obtained from a source other than our favorite auction site. It's command prompt is UCCM> rather than UCCM-P>. The OCXO is a Trimble 65256 with a 2006 date code instead of a 73090 unit with 2009 or 2010 date code. The performance seems similar to the RFTG. In other words, not as good as the Trimble Thunderbolt or other members of the Z38 family. I unsoldered the OCXO and found that, by itself, the performance (other than aging) is better than when it's in the circuit.
Ed
Some more info on the Trimble/Wun-Hung-Lo hybrid. I powered it down to drill some ventilation holes in the case. Upon powering it back up, I see that the elevation mask setting has been reset.
So apparently they don't write settings to non-volatile RAM.
Maybe there is no non-volatile RAM in these units. It appears that they came from a telco environment where they would be powered off of continuously float-charged lead-acid batteries. They would never be powered down so, no need for non-volatile storage. With a bit of reverse-engineering you should be able to add a battery backup to the GPS receiver itself. It's designed to support that.
FYI, I have a similar Trimble GPSDO that I obtained from a source other than our favorite auction site. It's command prompt is UCCM> rather than UCCM-P>. The OCXO is a Trimble 65256 with a 2006 date code instead of a 73090 unit with 2009 or 2010 date code. The performance seems similar to the RFTG. In other words, not as good as the Trimble Thunderbolt or other members of the Z38 family. I unsoldered the OCXO and found that, by itself, the performance (other than aging) is better than when it's in the circuit.
Ed
Well, it does provide a command to set the serial number, and if you set that, it does persist past a power cycle. So there must be some non-volatile storage there.
And even if their wasn't, that's shoddy design IMHO. Even if you expect it to be battery backed up indefinitely, if you ever have to do maintenance on the equipment, or if there is some AOG that removes power for an extended period of time, when the power is restored your technician will need to re-configure everything. It's hard to find a microcontroller these days without some built-in EEPROM, so I think most engineers would back up the settings in EEPROM.
But drawing some conclusions from the firmware and the non-functional software they provided with this unit, I think this is classic Wun-Hung-Lo engineering, so I am not surprised that they didn't bother to add the few extra lines of code to store the GPS settings in non-volatile RAM and restore them on power-up.
By the way, Ed - the Lucent seems to be almost an order of magnitude more stable than this thing so far. It's interesting to watch the Lucent OCXO age. The EFC voltage has been following a general upward trend since I powered it on. I guess at some point, this will level off, and at that point the OCXO will be considered broken in?
By the way, Ed - the Lucent seems to be almost an order of magnitude more stable than this thing so far. It's interesting to watch the Lucent OCXO age. The EFC voltage has been following a general upward trend since I powered it on. I guess at some point, this will level off, and at that point the OCXO will be considered broken in?
Not really. OCXOs age - period. That's why you need a GPSDO - to lock the OCXO to a stable reference and keep the frequency constant. What will happen is that the rate of aging will slow down to the specified value for the OCXO or lower. If you had 100 OCXOs of the same type you'd find that aging could be high or low, positive or negative depending on the individual unit. Aging could be positive one day and negative the next, even after you've accounted for changes in temperature, supply voltage, humidity (yes!), air pressure (yes!) etc. Whether the levels are significant depends on the user and the application.
Ed
By the way, Ed - the Lucent seems to be almost an order of magnitude more stable than this thing so far. It's interesting to watch the Lucent OCXO age. The EFC voltage has been following a general upward trend since I powered it on. I guess at some point, this will level off, and at that point the OCXO will be considered broken in?
Not really. OCXOs age - period. That's why you need a GPSDO - to lock the OCXO to a stable reference and keep the frequency constant. What will happen is that the rate of aging will slow down to the specified value for the OCXO or lower. If you had 100 OCXOs of the same type you'd find that aging could be high or low, positive or negative depending on the individual unit. Aging could be positive one day and negative the next, even after you've accounted for changes in temperature, supply voltage, humidity (yes!), air pressure (yes!) etc. Whether the levels are significant depends on the user and the application.
Ed
I see. Well, the PPS excursions reported by Z38XX have definitely settle down since initial power-on. Now it is maybe 50% of the time within +/-10ns, 70% of the time within +/-20 ns, and it does not ever seem to go above about 60ns, whereas when it was first powered on, it was bouncing between +/- 90ns pretty much constantly.
For those who have the rftg-ii-rb, what is the power input pin.
I bought the Lucent set and it arrived yesterday. I added a Garmin external antenna and powered the units using a laptop 19.5v brick until I build a better supply. They came up in about 15 minutes and after locating the antenna optimally I am getting 6 and sometimes 7 satellites. I thought they only tracked 5 at a time? Satstat works well and the unit finished the survey. Tfom and ffom are as low as they go. Overall very pleased with how smoothly it all went.
I bought them to sync my counters and spectrum analyzer. The killer is they were hardly off much at all after all that.
Jerry
I bought the Lucent set and it arrived yesterday. I added a Garmin external antenna and powered the units using a laptop 19.5v brick until I build a better supply. They came up in about 15 minutes and after locating the antenna optimally I am getting 6 and sometimes 7 satellites. I thought they only tracked 5 at a time? Satstat works well and the unit finished the survey. Tfom and ffom are as low as they go. Overall very pleased with how smoothly it all went.
I bought them to sync my counters and spectrum analyzer. The killer is they were hardly off much at all after all that.
Jerry
They can sync up to 8 satellites at a time.
I bought the Lucent set and it arrived yesterday. I added a Garmin external antenna and powered the units using a laptop 19.5v brick until I build a better supply. They came up in about 15 minutes and after locating the antenna optimally I am getting 6 and sometimes 7 satellites. I thought they only tracked 5 at a time? Satstat works well and the unit finished the survey. Tfom and ffom are as low as they go. Overall very pleased with how smoothly it all went.
I bought them to sync my counters and spectrum analyzer. The killer is they were hardly off much at all after all that.
Jerry
I am very happy with mine as well. It is more than accurate enough to calibrate my frequency counter.
For those who have the rftg-ii-rb, what is the power input pin.
Pin 1 is +24VDC and Pin 2 is GND
Has anyone used the RTFG.exe on WinXP to configure the RFTGm-II-Rb/RFTGm-II-XO pair?
From the look of it, it was written for Win95 or Windows 3.11. I can load up an old PC with Win95 if I have to but if anyones gotten it to work on WinXP that would be great to know.
Just mainly looking to program in my cable length or atleast read out what it is. I've used a FTDI based RS422 interface and can see binary data coming across in teraterm but the RTFG program doesn't seem to connect
I do know using the output of the XO GPD Locked and used on my HP53131A's external ref and then measuring the Rb output I have 10Mhz +/- 200ns