Sorry but I disagree. Having done extensive work with the M7 and M6 in
connection with the with GPSDO work we are doing we have characterized the
units extensively. First from what we can see the difference between a SSR-6T
and a $ 16 M6 is that one has a TCXO and outputs sawtooth
Said,
On 20/08/2014 15:42, saidj...@aol.com wrote:
Hi Tony,
that's consistent with what I remember. Do you have the capability to count
the number of 10MHz pulses per second to see if it is phase-coherent with
the UTC 1PPS pulse?
I don't have any means to do that at the moment - when I
From: Tony
As I said, I measured the pulses at either 104ns (9.6MHz), with some
being shorter at 84ns. I've just repeated the measurements on a Reyax
RYN25AI (UBLOX MAX-7C) with the same results. Actually the scope
measures the longer pulses at either 104.3ns or 105.2ns and the shorter
pulses at
FYI. It is still available. Don't have it in hand yet, but one was
ordered just a few days ago...
Dan
On 8/21/2014 6:34 AM, time-nuts-requ...@febo.com wrote:
One example
is Synergy Systems' SSR-6Tr if it's still available. It was announced,
and discussed on this list, in 2012 but it still
Hi Bert,
I don't think we have any fundamental disagreement here. Maybe just a
difference in emphasis.
On 8/21/2014 4:34 AM, ewkeh...@aol.com wrote:
Sorry but I disagree. Having done extensive work with the M7 and M6 in
connection with the with GPSDO work we are doing we have characterized
David,
No problem, its still set-up. As you'd expect its rock solid at 8MHz
with no visible jitter.
Can you point me to the datasheet you're referring to? The MAX-7 and
NEO-7 datasheets don't provide any information on clocking.
In the 'u-blox 7 Receiver Description Including Protocol
On 21/08/2014 08:13, Ed Palmer wrote:
But, timing receivers do have features that can improve performance
over navigation receivers. Some that come to mind are position hold
mode, TRAIM, maintaining performance with only one satellite locked,
sawtooth correction, and precision survey. I
On Thu, Aug 21, 2014 at 9:45 PM, Tony tn...@toneh.demon.co.uk wrote:
I just tried sending various TMODE and TMODE2 configuration messages to the
NEO-7M. These allow you to select 'Disabled' 'Survey In' and 'Fixed Mode'
where you can specify the receiver's lattitude and longitude. Not
Have not tried myself, but there are instructions around describing how to load
T-firmware into non T ublox models. There also seem to be possible to patch the
program ram to enable looked features on models without flash reprogramming
capability.
/Björn
div Originalmeddelande
Paul,
How far from the equator are you? The farther you are, the more trouble
GPS has measuring your latitude due to worsening geometry.
By the way, does anyone know what the timing effects of that will be?
Is it documented anywhere? I noticed that the GLONASS satellites have a
higher
On 21 Aug, 2014, at 16:27 , Tony tn...@toneh.demon.co.uk wrote:
David,
No problem, its still set-up. As you'd expect its rock solid at 8MHz with no
visible jitter.
Can you point me to the datasheet you're referring to? The MAX-7 and NEO-7
datasheets don't provide any information on
tn...@toneh.demon.co.uk said:
Tony, any chance you could do a quick measurement at 8 MHz -
I think that should be a more constant period. ...
No problem, its still set-up. As you'd expect its rock solid at 8MHz with
no visible jitter.
I don't think you have fixed the problem, just made
Hal,
Except for a few magic target frequencies, the output will have
occasional (or frequent) missing or extra
cycles. The output will be clean if you are dividing by a power of 2.
(By switching from 10 MHz to 8
MHz, you have changed from frequent to occasional.)
Not true that
Quoting Tony tn...@toneh.demon.co.uk:
I don't have any means to do that at the moment - when I get time
I'll try programming my STM32F4 discovery board (168MHz ARM Cortex
M4) to take some measurements. However as I haven't used the timers
on that yet it'll take a bit of time to get it
On Thu, Aug 21, 2014 at 4:03 PM, Ed Palmer ed_pal...@sasktel.net wrote:
How far from the equator are you?
I believe 43.235262699 N (my median position) is about 4,809,051
meters from the equator.
___
time-nuts mailing list -- time-nuts@febo.com
To
Ed
We may be talking past each other I had problems with the statement that
the basic M6 and M7 are not suitable for GPSDO's. They are not GPSDO's in
them self but great GPS engines even without saw tooth correction which is an
impossibility since the data is not available. But as you
Hi
I would bet that they drop / add a cycle whenever the output gets ahead or
behind GPS by the appropriate (TCXO period) amount. The output stays “in phase”
with GPS (sort of). The output spectrum looks messy ….
Why would I guess this - it’s the cheap / low computation way to do it. Playing
I'm at about 50 N. I used a Navsync CW-12 connected to a VIC-100
antenna to do a long site survey and got the following results:
Latitude: 1.32 meters Std Dev., -1 to +4 meters total range
Longitude: 1.18 meters Std Dev., -3 to +1 meters total range
Height:3.90 meters Std Dev., +6.6 to
On Thu, Aug 21, 2014 at 11:09 PM, Ed Palmer ed_pal...@sasktel.net wrote:
Since you're closer to the equator your results should be somewhat better
than mine. You could use these numbers to help decide if you've got a
problem or not.
I was unclear. My point was (since I'm really an absolute
David,
No problem, its still set-up. As you'd expect its rock solid at 8MHz
with no visible jitter.
Can you point me to the datasheet you're referring to? The MAX-7 and
NEO-7 datasheets don't provide any information on clocking.
In the 'u-blox 7 Receiver Description Including Protocol
20 matches
Mail list logo
