[time-nuts] 5061B Service Manual, Page 8-57 (BEAM I, if LOW)

2016-07-16 Thread Christopher Hoover
My 5061B (with FTS tube) has a low beam current. Maybe 7 on the meter when adjusted onto the primary peak. I bought the Ops and Service manual, but my copy is missing page 8-57 (and 8-56 if that exists). I'll send a complaint/request to Manuals Plus, but in the meantime can anyone share a scan

Re: [time-nuts] FW: GPS Antenna

2016-07-16 Thread Oz-in-DFW
I do not recognize the part number. All I can offer is that Micropulse has been acquired by PCTEL. Their GPS antenna line is here: http://www.antenna.com/apg_product_lines.cgi?id_num=150 It may be that the antenna you have was labelled for an OEM and is identical or very similar to one of

Re: [time-nuts] 5061B Service Manual, Page 8-57 (BEAM I, if LOW)

2016-07-16 Thread Dan Rae
On 7/16/2016 8:11 PM, Christopher Hoover wrote: My 5061B (with FTS tube) has a low beam current. Maybe 7 on the meter when adjusted onto the primary peak. I bought the Ops and Service manual, but my copy is missing page 8-57 (and 8-56 if that exists). Christopher, Given that Foldout Page

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread John Swenson
Yes, I was planning on using a high speed photo diode to actually measure the turn on time of the digits. I hadn't thought of the turn OFF time, do I want the old digit to be turned off before the new one lights up or for them to be overlapping? I have been thinking about what threshold to

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread Chris Albertson
Seriously, it does not matter how long it takes to turn a nixie tube on or off. You measure it and then compensate. Likely would need to continuously measure and adjust the compensation.This is doable and is the only hard part of the problem as it is new while the rest has been done 1000

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread David J Taylor
I, for one, will be following your progress... I think it would be cool as heck having an ultra-accurate clock with a Nixie display... It'd be cool to make it flexible enough to output the time sync to other equipment... __ Clay Autery, KY5G

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread David J Taylor
From: Bob Camp To get a time resolution of 10 ms (yes 10X 1 ms), you don’t really need the pps. The timing of the serial string is probably “good enough”. That assumes you don’t have all sorts of other messages turned on as well. In the case of a wall clock, it’s not clear why anything other

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread Tom Van Baak
> Yes, I was planning on using a high speed photo diode to actually > measure the turn on time of the digits. I hadn't thought of the turn OFF Or just measure the anode/cathode current of the tube. The plots are non-linear and wonderful. At this point, consider moving over to the excellent

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread Clay Autery
I would run a test and track turn ON/OFF times against varying intensities to get enough data to chart/graph. THEN, you can make informed decisions about intensity level, whether you want to consider turn off time, etc. This could become quite voluminous... data acquisition-wise and just the

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread jimlux
On 7/15/16 6:23 PM, Chris Albertson wrote: I did write that it's useless to have a visual display that is three orders of magnitude better than the human perceptional system and was corrected that such a display could be used for film based photography. That is true. But that just adds even

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread Tommy Phone
How about monitoring the Nixie tube current instead of light output. I have a strong suspicion that there's a good correlation between the two. >From Tom Holmes, N8ZM > On Jul 15, 2016, at 11:40 PM, jimlux wrote: > >> On 7/15/16 5:25 PM, Bob Camp wrote: >> Hi >> >> You

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread David
The point of measuring the actual ignition point is to predictably remove delay by driving the element earlier. CRT grid structures support transition times in the 5 to 20 nanosecond range; the smaller distances involved with a nixie tube should support faster operation. Something which just

Re: [time-nuts] FW: GPS Antenna

2016-07-16 Thread Sanjeev Gupta
On Sat, Jul 16, 2016 at 9:56 PM, Lester Veenstra wrote: > Can anyone help Hal? > Data on: GPS Antenna Micropulse Z1001 > Is there a part number, or an year of manufacture? -- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane

Re: [time-nuts] GPS Antenna

2016-07-16 Thread Gregory Beat
MicroPulse™ has been a leading brand of GPS and satellite communications antennas for over 15 years. Their antennas are used by many U.S. GPS receiver companies, as well as most branches of the U.S. Armed Forces and NATO allies. MicroPulse 409 Calle San Pablo Camrillo, CA 93012 US -- The

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread Bob Camp
Hi The gotcha is that it’s the sum of the radiation arriving in the vicinity of the gas. Supplying a bit can flood small variations, but they still are present. You are trying to get what is essentially a neon bulb to trigger accurately to a very tight budget. There is a lot of prior art on

[time-nuts] Getting ntpd to work with Garmin LVC-18x and Ubuntu 16.04..

2016-07-16 Thread Howard Leadmon
I have been running my Garmin under FreeBSD for a few years, and it's been working great. So I recently had to shift to Ubuntu Linux 16.04, and honestly thought it would be easy to plug everything in and just make it happy. Reading the various docs for Ubuntu 16.04 LTS, it says all of the

[time-nuts] FW: GPS Antenna

2016-07-16 Thread Lester Veenstra
Can anyone help Hal? Data on: GPS Antenna Micropulse Z1001 Lester B Veenstra  MØYCM K1YCM W8YCM les...@veenstras.com Physical and US Postal Addresses 5 Shrine Club Drive (Physical) 452 Stable Ln (RFD USPS Mail) Keyser WV 26726 GPS: 39.336826 N  78.982287 W (Google) GPS: 39.33682 N  78.9823741 W

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread jimlux
On 7/16/16 12:08 AM, John Swenson wrote: Yes, I was planning on using a high speed photo diode to actually measure the turn on time of the digits. I hadn't thought of the turn OFF time, do I want the old digit to be turned off before the new one lights up or for them to be overlapping? I have

[time-nuts] GPS for Nixie Clock

2016-07-16 Thread Mark Sims
A company that I founded, at one time shipped about half the world's supply of PC graphics cards. We got several requests from the film and TV industry for display devices that produced images that could be filmed. Our cheap-ass solution was a card that output 24 Hz video and the camera was

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread Bob Camp
Hi > On Jul 15, 2016, at 11:40 PM, jimlux wrote: > > On 7/15/16 5:25 PM, Bob Camp wrote: >> Hi >> >> You can do a pretty good job with a high speed photo diode. They are not >> cheap, but >> you can get fast ones if your Visa card is up to it. >> >> The next layer will

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread jimlux
On 7/15/16 10:04 PM, Chris Albertson wrote: Seriously, it does not matter how long it takes to turn a nixie tube on or off. You measure it and then compensate. Likely would need to continuously measure and adjust the compensation.This is doable and is the only hard part of the problem as

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread David
Use AC coupling to each digit to measure the ignition waveform and detect the breakdown point like with a tunnel diode trigger. Use a higher compliance voltage and greater negative resistance (constant current drive?) to lower breakdown jitter. On Sat, 16 Jul 2016 00:08:45 -0700, you wrote:

Re: [time-nuts] Getting ntpd to work with Garmin LVC-18x and Ubuntu 16.04..

2016-07-16 Thread albertson . chris
A common error is to have pps flipped. The leading edge should fall on the second. Fix it with a NOT gate or in a configure file > On Jul 16, 2016, at 1:58 PM, Hal Murray wrote: > > > how...@leadmon.net said: >> I have also run ppstest, and show a pps stream, granted

Re: [time-nuts] Getting ntpd to work with Garmin LVC-18x and Ubuntu 16.04..

2016-07-16 Thread Gary E. Miller
Yo albertson.ch...@gmail.com! On Sat, 16 Jul 2016 14:48:30 -0700 albertson.ch...@gmail.com wrote: > A common error is to have pps flipped. The leading edge should fall > on the second. Fix it with a NOT gate or in a configure file No need to add inverter latency. ppstest says the 'assert is

[time-nuts] GPS message jitter (was GPS for Nixie Clock)

2016-07-16 Thread Mark Sims
I just added some code to Lady Heather to record and plot the time that the timing message arrived from the receiver (well, actually the time that the screen update routine was called, maybe a few microseconds difference).I am using my existing GetMsec() routine which on Windoze actually

Re: [time-nuts] Getting ntpd to work with Garmin LVC-18x and Ubuntu 16.04..

2016-07-16 Thread Hal Murray
how...@leadmon.net said: > Does anyone have any ideas, or have this all working under Ubuntu 16.04 LTS? > I would sure love to get my time server back online, as I pretty much have > everything on the network sync with it.. The PPS stuff on Linux needs some magic setup. You need to run

Re: [time-nuts] GPS Antenna

2016-07-16 Thread Lester Veenstra
The GPS Antenna Micropulse Z1001 appears to be what is now designated GPS-TMG-26N Lester B Veenstra MØYCM K1YCM W8YCM les...@veenstras.com Physical and US Postal Addresses 5 Shrine Club Drive (Physical) 452 Stable Ln (RFD USPS Mail) Keyser WV 26726 GPS: 39.336826 N 78.982287 W (Google) GPS:

Re: [time-nuts] Getting ntpd to work with Garmin LVC-18x and Ubuntu 16.04..

2016-07-16 Thread Howard Leadmon
I made sure that even by hand I had run the ldattach, and that /dev/pps0 existed and was also linked to /dev/gpspps0 which is the case. I have also run ppstest, and show a pps stream, granted the weird thing is it seems like I get two lines of the same output ever second so not sure what is

Re: [time-nuts] Getting ntpd to work with Garmin LVC-18x and Ubuntu 16.04..

2016-07-16 Thread Gary E. Miller
Yo Howard! On Sat, 16 Jul 2016 16:32:20 -0400 "Howard Leadmon" wrote: > I have also run ppstest, and show a pps stream, granted the weird > thing is it seems like I get two lines of the same output ever second > so not sure what is up there. One is the assert edge of the

Re: [time-nuts] Getting ntpd to work with Garmin LVC-18x and Ubuntu 16.04..

2016-07-16 Thread Hal Murray
how...@leadmon.net said: > I have also run ppstest, and show a pps stream, granted the weird thing is > it seems like I get two lines of the same output ever second so not sure > what is up there. One is clear changing, the other is assert changing. There should be info in syslog or whereever

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread Clay Autery
Holy crap there's a lot of information there... I'll be on that site for a while! Thanks! __ Clay Autery, KY5G MONTAC Enterprises (318) 518-1389 On 7/16/2016 2:06 AM, David J Taylor wrote: > > If you don't mind an LCD display instead of Nixies . > >

Re: [time-nuts] GPS for Nixie Clock

2016-07-16 Thread Bob Camp
Hi Since we have moved into synchronizing this stuff at the nanosecond level (maybe we are even lower than that by now ..), simply getting a wide band enough signal off of a Nixe socket is going to be “interesting”. An array of picosecond photo diodes on each tube may be the only way to go. How

Re: [time-nuts] Getting ntpd to work with Garmin LVC-18x and Ubuntu 16.04..

2016-07-16 Thread Gary E. Miller
Yo Hal! On Sat, 16 Jul 2016 12:14:44 -0700 Hal Murray wrote: > how...@leadmon.net said: > > Does anyone have any ideas, or have this all working under Ubuntu > > 16.04 LTS? I would sure love to get my time server back online, as > > I pretty much have everything on the

Re: [time-nuts] GPS message jitter (was GPS for Nixie Clock)

2016-07-16 Thread Tom Van Baak
Hi Mark, As one example of what you'll see, scroll down to the NMEA Latency/Jitter plot at: http://leapsecond.com/pages/MG1613S/ In that 900 sample (15 minutes) run, the mean latency was 350.2 ms with a standard deviation (jitter) of 10.7 ms. I'll dig out some other data I may have. It will