Re: [time-nuts] Garmin GPS17
Suppose your 17 HVS having flat backup battery, once power up, by default, it goes to Garmin mode. You need to run the setup with: SNSRCFG http://www8.garmin.com/support/collection.jsp?product=010-00242-53 Reconfigure the 17 to NMEA mode Chao, Pascal On 10/31/09, mike cook wrote: > A stab in the dark. I don't have one of these. > > The doc I find says that these are supplied with a rechargable lithium cell > which enables back up of GPS data . It is supposed to last 10yrs, so if > yours is reaching retirement age it may have gone awol and dropped the > serial parameters to a state which your monitor is not set too. > So you could try all the baud rates listed in the specs. Use a terminal > emulator instead of the monitor program, which appears to be a graphic app, > to see if you getting any data output . > > default appears to be 9600,8 bit,no parity > > Serial Interfaces > a.. Port 1: True RS-232 output, asynchronous serial input compatible with > RS-232 or TTL voltage levels, RS-232 polarity > b.. Port 2: Asynchronous serial input only, compatible with RS-232 or TTL > voltage levels, RS-232 polarity > c.. Baud Rates > d.. 300/600/1200/2400/4800/9600/19200 > e.. > Serial Formats > a.. Port 1: Selectable between NMEA 0183 v2.00, NMEA 0183 v3.00, and > Garmin® binary formats; NMEA 0183 v2.0 (ASCII); Approved output sentences: > GPALM, GPGGA, GPGLL, GPGSA, GPGSV, GPRMC, GPVTG; Proprietary sentences: > PGRMB, PGRME, PGRMF, PGRMM, PGRMT, PGRMV > > - Original Message - > From: "Neville Michie" > To: "Discussion of precise time and frequency measurement" > > Sent: Saturday, October 31, 2009 9:15 AM > Subject: [time-nuts] Garmin GPS17 > > >> >> Hello all, >> I have a Garmin GPS17 HVS which is a GPS receiver/antenna in one unit. >> When I first bought it I used it to discipline an HP10811 OCXO. One day >> it stopped >> responding to its monitor program. >> I got a TBOLT which has kept me busy and now I want to compare it to the >> Garmin. >> >> Although I used to be able to run the monitor program and it does not >> respond any more, >> if you put it under the sky and power it up, after a while you get a PPS >> out of it that is >> in phase with the GPS. >> >> So there is somebody home but they have turned out the lights. >> >> The Garmin manuals mention failure to respond if you do the wrong thing, >> Can anyone help me get it going again? >> >> Cheers, >> Neville Michie >> >> >> ___ >> 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.
Re: [time-nuts] Any Time nuts in AU?
Good day all I am a mountaineer in the Blue Mountains, west of Sydney. I don't worry much about any extra digit (up to now), happy with whatever I have, heard and learn from America, Europe and down here Oceania from time nuts mail tunnel, those info are always above my head and very informative. How do I keep time ? I built several GPSDOs from scratch since 2006 with NavSync CW25 - TIM module, with 1PPS and NCO up to 30.000MHz. I have only one clock, an FRK,uncalibrated, as I learn from the group, a man with one clock is a happy man ! I do not have any HP timing related test gear, I use a soundcard stereo input for comparison, still waiting for any instruction from the group "how to clock the PC" up to nuts-standard. Cheers from Pascal VK2IHL / XV2PN On Thu, Oct 8, 2009 at 9:11 AM, arie schellaars wrote: > G'day folks. > I am Latrobe Valley Victoria. > Cheers > Arie > VK3DBF > >> Just a test to see if I can send to >> the mailing list and to find out how many "time nuts" are in >> the land down under >> >> Thanks Ray. >> > > Send instant messages to your online friends http://au.messenger.yahoo.com > > ___ > 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.
Re: [time-nuts] GPS Week 1536 causing problems?
Hi 18X owners I experienced same problem with my fleet of 16HVS (originated from Kit Scally ?). The non functioning GPS is not on Garmin PVT mode, neither NMEA mode !!!. Reconfigured by using SNSRCFG software switch to NMEA or Garmin mode, my 16HVS is back to business. http://www8.garmin.com/support/collection.jsp?product=010-00321-05 Pascal On Tue, Jul 7, 2009 at 1:48 PM, M. Warner Losh wrote: > In message: <4a52bd4f.5020...@rubidium.dyndns.org> >Magnus Danielson writes: > : Hal Murray wrote: > : Anyone else lose an 18x? > : > > : >>> I lost one a while ago. Similar. It just stopped doing anything > : >>> useful. > : > > : >> Battery failure? > : > > : > I don't think it has a battery inside. That seems like a poor design. > Too > : > many reasonable use cases would include sitting in a drawer for > extended > : > periods of time. > : > : Providing an RTC has benefits, especially when considering week-rollover > : issues, since when the receiver wakes up it has no idea of date at all, > : pulling in the RTC time and date is a sufficient hint, and adjusting > : with detailed info from the GPS is a trivial extention. Then adjusting > : the RTC is not a hard thing to do every once in a while. The same > : problem could also be solved using EEPROM space. A byte would suffice. > > Usually, you're right. There's one case that might make it not > suitable. > > Many contracts require spares for all the important gear. Long > storage times makes storing the last known date ineffective. Of > course in this case "long" is on the order of 9-odd years. This may > be good for many applications, but not necessarily ones that have 10 > or 15 year deep spares requirements... > > Warner > > ___ > 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.
Re: [time-nuts] Broken Ovenaire OSC 85-50
Hi Joe Please open the link below http://www.airlab.com.au/nuts/joe_1.htm for an update of a simulated fault from an out of tune of the narrow band pass filter Kind regards Pascal Nguyen ___ 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] Broken Ovenaire OSC 85-50
Hi Joe I am just a radio amateur and I build a lot of oscillators for my need, including a GPSDO "tunable" with CW25-TIM GPS receiver chip set. Please allow me to share my usual trouble shooting when oscillator is not working properly. I see an oscillator is just only a high gain amplifier with positive feed back via "narrow band pass" filtering to sustain an oscillation in a controllable manner. I had a look at your circuit with all Vcbe of all transistors transcribed, it seems to me all transistors are within normal limit (bias # 0v7). Please look at the "narrow filter", my suggestion is to check this circuit. 1) 22pF in parallel with a serial (10uH - 30pF) is a diplexer, high impedance to ground for 10 MHz and low impedance to ground for unwanted spectrum. 2) 80 pF feed back capacitor. 3) 10 MHz Xtal Now I can perform a differential diagnosis: All transistors are correctly biased, can eliminated fault from power supply and transistors. A quick and dirty approach is to do a loose coupling (capacitor or inductor) with the 10 uH inductor, connect to an external 10 MHz variable output source, check gain of all transistor stages to the last output Check high impedance to ground for 10 MHz, disconnect the "diplexer", check magnitude of output signal, signal is increasing, hurray we see the problem. Same signal level, put the diplexer back to the circuit, check the 80 pF cap, all else failed, the last component of the "narrow filter" is the Xtal. Good luck Pascal Nguyen vk2ihl / xv2pn ___ 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] NavSync CW12 and CW25
Hi Ed I build a 432.424MHz and 144.424MHz beacons for radio amateur application based on CW25-TIM modules ($150 ea july-07). I cannot provide any further details than the spec published by Navsync, due to lack of measurement facility, my set up is simply a Rb standard and two RT662 HF receivers driven with 5MHz source from Rb 10MHz/2) . Audio outputs are directed to PC soundcard and water falls are visually compared, an entry level for amateur like myself. I etched the PC board for 3V3 SM power supply, backup battery, RS 232 converter (3v level) and 1PPS, NCO output, NMEA output, status LED indicators. My first board was populated with CW25 NAV, the only module available at that time, max freq 10MHz NCO. My second with CW25 TIM, max freq 30 MHz NCO Control the NCO is quite simple, via simple protocols, ie 10MHz output is such as " $PRTHS,FRQD,10.000.000 ". The CW25 TIM, factory default NCO output is 10 MHz, since startup and will lock to 1pps when status fixed, the module is running warm to touch at, I suppose an ovenised crystal is inside. I do not have the CW12, if the module is CW25TIM, it is worthy to get the CW12 to save the pain of etching a PCB. Pascal Nguyen On 8/7/08, Ed Palmer <[EMAIL PROTECTED]> wrote: > Has anyone worked with the NavSync CW12 GPS board or the CW25 module > that its based on? It's been mentioned a few times on this mailing > list, but not really evaluated or discussed to death. :-) > > I'm looking for a new GPS board and this one looks quite interesting. > It's main feature is a programmable 10 Hz to 10 MHz oscillator that's > phase-locked to the 1 PPS output. They're both available at the same > time (on different pins). > > The user manual isn't online, but I asked them via email and got a copy > with no problem. The datasheets and product briefs are available at: > > Datasheets > http://www.navsync.com/docs/CW12-TIM_DS_V1.pdf > http://www.navsync.com/docs/CW25-TIM_DS_Rev_1.pdf > > Product Briefs > http://www.navsync.com/docs/CW12_TIM.pdf > http://www.navsync.com/docs/CW25_TIM.pdf > > I see that they're not suggesting that this little module is a > full-blown GPSDO. This app note talks about it. > > http://www.navsync.com/docs/AN03_GPS_Timing.pdf > > The prices are CW12 - $89, CW25 - $64 > > I have no relationship to Navsync or any reseller. I'm just a potential > customer. > > Thanks, > Ed > > > ___ > 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.
