Re: [time-nuts] Looking for GPS module (Exactime ET6000/Datum 9390-6000)

2017-01-18 Thread ziggy9+time-nuts
I considered that. Unfortunately the Heol Designs units don’t emulate the SV6-CM3 and the Ace receivers were not a direct replacement. So it seems they have nothing to offer at this time. > On Jan 18, 2017, at 1:24 AM, Gregory Beat wrote: > > Heol Designs offers replacement

Re: [time-nuts] Looking for GPS module (Exactime ET6000/Datum 9390-6000)

2017-01-18 Thread Gregory Beat
Heol Designs offers replacement boards for Trimble GPS receivers. http://www.heoldesign.com/N01x-Trimble-Lassen-SK2-iQ-sQ-LP-ACE-replacements-boards Heol Design's GPS receivers are based on the Copernicus II high performance GPS chip set and mimic the legacy Trimble GPS receivers. These OEM

[time-nuts] Looking for GPS module (Exactime ET6000/Datum 9390-6000)

2017-01-17 Thread Mark Sims
The TSIP protocol is the same one we all know and love. But some of the values in the commands are different, particularly the set_io_options command that sets which commands that the receiver sends automatically and in what format it sends them. I suspect that, alone, would make dropping in

[time-nuts] Looking for GPS module (Exactime ET6000/Datum 9390-6000)

2017-01-17 Thread Mark Sims
The protocol gets saved in a serial EEPROM. The firmware is apparently in masked rom and cannot be upgraded. Trimble has some ancient utilities that let you change the protocol between GPS (only does GGA and VTG sentences unless you paid for custom firmware), TAIP (which Lady Heather now

Re: [time-nuts] Looking for GPS module (Exactime ET6000/Datum 9390-6000)

2017-01-17 Thread Hal Murray
hol...@hotmail.com said: > On the chip with the "MX" marking on it, what f/w version does it show > (usually v5.02 or v5.10)? I have a couple of CM3's configured for TAIP > output, but I have the programs for switching them to TSIP or NMEA. Does the which-protocol get saved away someplace or

Re: [time-nuts] Looking for GPS module (Exactime ET6000/Datum 9390-6000)

2017-01-16 Thread ziggy9+time-nuts
Due to the stickers, I don’t see anything with MX on it, but I presume you mean the ROM. It has 28655-01 and V5.00 on it. The other model number is 26889-81, the -x1 kind of implies that it’s TSIP, and from sniffing the GPS traffic in a prior exercise, I can confirm that it is. > On Jan 16,

[time-nuts] Looking for GPS module (Exactime ET6000/Datum 9390-6000)

2017-01-16 Thread Mark Sims
On the chip with the "MX" marking on it, what f/w version does it show (usually v5.02 or v5.10)? I have a couple of CM3's configured for TAIP output, but I have the programs for switching them to TSIP or NMEA. --- > The module is basically a Trimble SveeSix-CM3 and is

[time-nuts] Looking for GPS module (Exactime ET6000/Datum 9390-6000

2017-01-16 Thread Mark Sims
I recently added code to Lady Heather to support up to 10 external com links (serial or TCPI/IP). One is the receiver port, one will be a TICC, and two are "echo" ports. One echo port echoes all the raw data sent by the receiver and the other does the same thing except the data is formatted

Re: [time-nuts] Looking for GPS module (Exactime ET6000/Datum 9390-6000)

2017-01-16 Thread ziggy9+time-nuts
I did see that one, but I am hoping I can procure something that isn't from an overseas surplus scrapper. If I can't find anything else, then I guess it's my only choice. Unfortunately, the Heol folks don't have anything to offer here either. It's not a WNRO problem, as the week and date are

Re: [time-nuts] Looking for GPS module (Exactime ET6000/Datum 9390-6000)

2017-01-15 Thread Mike Cook
If your friends don’t have a CM3 spare, there is one on eBay item 141712522709. It might be worth pulling the GPS part and testing it stand alone as there have been numerous week number roll over problems surfacing. If that is the case for yours then a replacement gets you nowhere. > Le 16

[time-nuts] Looking for GPS module (Exactime ET6000/Datum 9390-6000)

2017-01-15 Thread ziggy9+time-nuts
I’ve had an intermittent problem with my ET6000/9390-6000 GPSDO where the reported error (the FRQ: display on the LCD) initially is OK (low E-12’s) and then creeps up to the limit (~500), and the tracking and locked LEDs go out. I’ve spent some time troubleshooting this and it seems confirmed