[time-nuts] Source for DC-blocking 50-ohm terminators? (Spectracom 8140)

2018-06-03 Thread Julien Goodwin
I'm looking at using a Spectracom 8140 for 10Mhz distribution, and they specify using a DC-blocking 50-ohm terminator on each run. These seem to be odd enough that none of my usual sources have them (75-ohm DC-blocking terminators yes, 50-ohm, no). While it's easy enough to chain a DC block and a

Re: [time-nuts] nuts about position

2018-06-03 Thread Bob kb8tq
Hi > On Jun 3, 2018, at 7:35 PM, Mark Sims wrote: > > As far as I'm concerned anything that you can do to improve the position > accuracy, environmental changes, noise environment, etc is a good thing. > Minimizing errors and disturbances can't hurt and may even improve things. > How mu

[time-nuts] nuts about position

2018-06-03 Thread Mark Sims
As far as I'm concerned anything that you can do to improve the position accuracy, environmental changes, noise environment, etc is a good thing. Minimizing errors and disturbances can't hurt and may even improve things. How much any improvement provides ... ??? But time nuts tend to be

[time-nuts] HP 53131A Power Off Mod

2018-06-03 Thread Arthur Dent
I had also modified my HP 53132A but kept it extra simple and the modification allows me to use the counter normally.. On my HP 53132A I just mounted a toggle switch in one of the unused holes for the back panel BNC input connectors and wired the switch in series with the power connector. The fron

Re: [time-nuts] Fwd: HP 53131A Power Off Mod

2018-06-03 Thread Wayne Holder
*Important Update:* due to a mistake in my thinking, I had to upgrade the fuse I added to a 220V, 3A model to match the fuses on the internal switching power supply. My original plans were to mount the fuse on the power supply PCB and use it only to fuse the small power adapter used to power the r

Re: [time-nuts] nuts about position

2018-06-03 Thread Bob kb8tq
Hi Location will always impact things a bit. At some point it does become a minor contributor. What point that is varies with a lot of things. One of them is indeed the propagation path to the satellites. How much the ionosphere and troposphere mess things up is very much a “that depends” sor

Re: [time-nuts] nuts about position

2018-06-03 Thread Magnus Danielson
Hi, On 06/03/2018 10:07 PM, Chris Caudle wrote: > On Sun, June 3, 2018 12:57 am, Mark Sims wrote: >> Well, with a little prodding and help from Magnus, I now have the >> Trimble devices outputting RINEX files. > > Is this applicable to a Thunderbolt, and would this improved position > accuracy

Re: [time-nuts] nuts about position

2018-06-03 Thread Chris Caudle
On Sun, June 3, 2018 12:57 am, Mark Sims wrote: > Well, with a little prodding and help from Magnus, I now have the > Trimble devices outputting RINEX files. Is this applicable to a Thunderbolt, and would this improved position accuracy be expected to improve the time accuracy from a Thunderbolt

Re: [time-nuts] HP 5372A TIA Question

2018-06-03 Thread Magnus Danielson
Hi Adam, OK, good to hear about the progress. Let us know about what you learn and if you need additional input. I'm curious what is the cause of this error. Cheers, Magnus On 06/03/2018 04:09 AM, Adam MacDonald wrote: > Thanks Gents, > I ran the additional tests recommended by Poul and Magnus a

[time-nuts] nuts about position

2018-06-03 Thread Mark Sims
I did a test on a 1 second vs a stripped out 10 second rate from the same 24 hour run. The differences were down in the noise. Some people have actually reported slightly better results with 30 second vs 1 second data... but I doubt that... I suspect they used different data sets and the dif

Re: [time-nuts] nuts about position

2018-06-03 Thread Bob kb8tq
Hi If you are doing a longer run into one of the data analysis services - it does not seem to matter much what the spacing on the readings is. One second data does not seem to produce any better result than 30 second data. I don’t think that the 3 second rate on the Trimble will have much impa

[time-nuts] nuts about position

2018-06-03 Thread Mark Sims
I haven't done any extensive testing of how accurate the results are, but comparing them to the position produced by a L1/L2 (error ellipses < 50mm) they seem to be correct. One issue to be aware of is that some receivers want altitude in othometric height (MSL) and others use geoid (GPS) hei