On 10/05/2014 04:19, Chris Albertson wrote:
On Fri, May 9, 2014 at 10:46 AM, Tony tn...@toneh.demon.co.uk wrote:
But isn't that only supported by 'timing' GPS modules that allow you to
specify the location? But they are rather more expensive than the common
navigation type modules - are there
On 10/05/2014 15:15, Attila Kinali wrote:
On Fri, 09 May 2014 18:46:05 +0100
Tony tn...@toneh.demon.co.uk wrote:
Quite a remarkable datasheet for a low cost part - I've not found any
other low cost oscillator with either of those specifications, and even
some (most?) of the OXCO don't specify
On Mon, May 12, 2014 at 3:03 AM, Tony tn...@toneh.demon.co.uk wrote:
Unfortunately they use way too much power - 800mW maximum compared to
50mW
for a UBLOX MAX-7c which are around $15. It also is specified at 50ns
rms,
99% 100ns. It appears that most, if not all, the timing type modules
Unfortunately they use way too much power - 800mW maximum compared to
50mW for a UBLOX MAX-7c which are around $15. It also is specified at
50ns rms, 99% 100ns. It appears that most, if not all, the timing
type modules are higher power as well as more expensive; unless anyone
has any
On Fri, May 9, 2014 at 10:46 AM, Tony tn...@toneh.demon.co.uk wrote:
But isn't that only supported by 'timing' GPS modules that allow you to
specify the location? But they are rather more expensive than the common
navigation type modules - are there sub $15 modules that support that
On Fri, 09 May 2014 18:46:05 +0100
Tony tn...@toneh.demon.co.uk wrote:
Quite a remarkable datasheet for a low cost part - I've not found any
other low cost oscillator with either of those specifications, and even
some (most?) of the OXCO don't specify the freq/temp slope.
I'm quite sure the
On 06/05/2014 02:24, Chris Albertson wrote:
On Mon, May 5, 2014 at 6:55 AM, Tony tn...@toneh.demon.co.uk wrote:
Yes - that is exactly what I intended. The problem though is maintaining
sufficient accuracy during periods when the GPS clock is unavailable or
unreliable (perhaps due to local
On 03/05/2014 18:41, Tom Van Baak (lab) wrote:
Tony, Chris, Bert,
Since all you want is a 10 ns time stamp / data logger you do not need a GPSDO,
or OCXO, or VCXO.
The solution is cheap and very simple.
Your GPS receiver provides a 1PPS to the microprocessor. Use a plain XO or
TCXO; the
The data loggers will be continuously powered, in fixed locations
and should have reasonably good views of the sky so the use of a low
cost GPS module should be feasible.
Hi Tony,
Ah, now you are asking a completely different question. When you started this
thread you didn't mention
On Mon, 05 May 2014 14:55:20 +0100
Tony tn...@toneh.demon.co.uk wrote:
On 03/05/2014 18:41, Tom Van Baak (lab) wrote:
Tony, Chris, Bert,
Since all you want is a 10 ns time stamp / data logger you do not
need a GPSDO, or OCXO, or VCXO.
The solution is cheap and very simple.
Your
On Mon, May 5, 2014 at 6:55 AM, Tony tn...@toneh.demon.co.uk wrote:
Yes - that is exactly what I intended. The problem though is maintaining
sufficient accuracy during periods when the GPS clock is unavailable or
unreliable (perhaps due to local interference), but I don't have any handle
on
On 03/05/2014 02:07, Edesio Costa e Silva wrote:
Welcome!
Take a look at NavSpark from SkyTraq (http://www.skytraq.com.tw/). They had
an Indiegogo
(https://www.indiegogo.com/projects/navspark-arduino-compatible-with-gps-gnss-receiver)
campaign recently and should deliver real soon now. The
On 5/2/14, 7:07 PM, Tony wrote:
On 03/05/2014 02:07, Edesio Costa e Silva wrote:
Welcome!
Take a look at NavSpark from SkyTraq (http://www.skytraq.com.tw/).
They had
an Indiegogo
(https://www.indiegogo.com/projects/navspark-arduino-compatible-with-gps-gnss-receiver)
campaign recently and
Looks like this is all you'd need for most timing projects. Just add your
favorite OCXO and some wire.
The SPARC (not Spark) is actually a step up from ARM. It was developed by
Sun Microsystems (now Oracle) it is optimized for things like fast context
switching, multi tasking and so on, all the
On 5/4/14, 8:40 AM, Chris Albertson wrote:
Looks like this is all you'd need for most timing projects. Just add your
favorite OCXO and some wire.
The SPARC (not Spark) is actually a step up from ARM. It was developed by
Sun Microsystems (now Oracle) it is optimized for things like fast
Moin,
On Fri, 02 May 2014 23:54:25 +0100
Tony tn...@toneh.demon.co.uk wrote:
I'm considering designing and building some dataloggers, probably ARM
Cortex based (eg. STM32F4xx), which record the time of infrequent
events, preferably to better than 100ns and if possible better than
50nS.
Hi
Well some of us still have RSX-11M (and RSTS/E) code floating around …..
Bob
On May 4, 2014, at 12:30 PM, Jim Lux jim...@earthlink.net wrote:
On 5/4/14, 8:40 AM, Chris Albertson wrote:
Looks like this is all you'd need for most timing projects. Just add your
favorite OCXO and some
On 5/4/14, 10:07 AM, Bob Camp wrote:
Hi
Well some of us still have RSX-11M (and RSTS/E) code floating around …..
B
As do I, but the stuff I'd actually reuse is pretty OS independent
(signal processing code in FORTRAN, and in reality, I'd most likely
rewrite it anyway.)
I suspect you'll
On Sun, May 4, 2014 at 5:40 PM, Chris Albertson
albertson.ch...@gmail.com wrote:
Looks like this is all you'd need for most timing projects. Just add your
favorite OCXO and some wire.
The SPARC (not Spark) is actually a step up from ARM. It was developed by
Sun Microsystems (now Oracle) it
These guys claim IEEE-754 FPU. But this is not the board to use for a
Posix-like OS. For that you'd want disk controller, networking and so on.
The big advantage of this thing is that it has an Arduino compatible boot
loader and pinout so it drops into that environment which is VERY easy
Hi
Well I do have those Sparc machines sitting over in the shed ….. I suspect
hauling over the CRT monitor to go with it would be a bit of a pain. I doubt I
would win the “low power GPSDO of the year” award with it.
Like it or not, once you get to 64 bit math, the “this versus that”
On 5/4/14, 11:38 AM, Chris Albertson wrote:
These guys claim IEEE-754 FPU. But this is not the board to use for a
Posix-like OS. For that you'd want disk controller, networking and so on.
Ah, so they did include the FPU: that's handy.
Actually, an in-ram file system, along with a decent
On 5/4/14, 11:44 AM, Bob Camp wrote:
Hi
Well I do have those Sparc machines sitting over in the shed ….. I
suspect hauling over the CRT monitor to go with it would be a bit of
a pain. I doubt I would win the “low power GPSDO of the year” award
with it.
Like it or not, once you get to 64
I am not advertising for DX but I have bought 4 with good results and their
units have a 5 V regulator on it. Some have even a TTL to RS converter on
board.
Bert Kehren
In a message dated 5/2/2014 11:40:47 P.M. Eastern Daylight Time,
tn...@toneh.demon.co.uk writes:
On 03/05/2014 00:59,
Tony
There seem to be many variables. Cost, power, how many, overall stability
etc. Most likely you will find that the GPS module is not the most expensive
part but the VCXO. It also makes a large difference if it is one off or a
larger volume is needed. You can always find a bargain, and
Tony, Chris, Bert,
Since all you want is a 10 ns time stamp / data logger you do not need a GPSDO,
or OCXO, or VCXO.
The solution is cheap and very simple.
Your GPS receiver provides a 1PPS to the microprocessor. Use a plain XO or
TCXO; the frequency does not need to be accurate, just stable
On Sat, 03 May 2014 02:38:07 +0100
Tony tn...@toneh.demon.co.uk wrote:
On 03/05/2014 00:59, ewkeh...@aol.com wrote:
Welcome to the nuts Tony
Thanks, Bert.
You are not specifying exactly how accurate time has to be but in
my book and based on tests the most reasonable priced GPS with 1
Hi, I'm new here so please be gentle!
I'm considering designing and building some dataloggers, probably ARM
Cortex based (eg. STM32F4xx), which record the time of infrequent
events, preferably to better than 100ns and if possible better than
50nS. The data loggers will be continuously
tn...@toneh.demon.co.uk said:
Can anyone point to figures for a typical non-TXCO low cost oscillator, 10
or 16MHz?
In general, low cost oscillators make pretty good thermometers.
I think you have a much better chance of getting good results if you are
willing to post-process the data.
I
Welcome to the nuts Tony
You are not specifying exactly how accurate time has to be but in my book
and based on tests the most reasonable priced GPS with 1 pps is a Ublox 6M
that you can get with antenna for less than $ 22 antenna included from
_www.DX.com_ (http://www.DX.com) . They have
Welcome!
Take a look at NavSpark from SkyTraq (http://www.skytraq.com.tw/). They had
an Indiegogo
(https://www.indiegogo.com/projects/navspark-arduino-compatible-with-gps-gnss-receiver)
campaign recently and should deliver real soon now. The NavSpark chip has an
trigger pin for time capture, a
On 03/05/2014 00:48, Hal Murray wrote:
tn...@toneh.demon.co.uk said:
Can anyone point to figures for a typical non-TXCO low cost
oscillator, 10
or 16MHz?
In general, low cost oscillators make pretty good thermometers.
True, but it's short term stability that matters here - over 10s of
On 03/05/2014 00:59, ewkeh...@aol.com wrote:
Welcome to the nuts Tony
Thanks, Bert.
You are not specifying exactly how accurate time has to be but in my book
and based on tests the most reasonable priced GPS with 1 pps is a
Ublox 6M
that you can get with antenna for less than $ 22 antenna
The Neo-6M based module (Crius CN-06) is available from HobbyKing for $20
(sometimes on sale for $16). You do have to add the wire to access the 1PPS
signal.
In my testing, I prefer it over the Adafruit Ultimate GPS. The Neo-6M seemed
to a a little more sensitive (could get reliable lock
here is what I'd do
Get a decent OCXO (ovenized crystal oscillator and control it with your
GPS. Don't worry if the GPS's PPS is 50ns or 5ns. You are going to be
averaging these for a while.Basically you build a GPSDO.These have
become very easy to make. I have one I made for
tn...@toneh.demon.co.uk said:
In general, low cost oscillators make pretty good thermometers.
True, but it's short term stability that matters here - over 10s of seconds
the temperature shouldn't change much - especially if a bit of insulation
is used around the oscillator.
Ballpark is 1
-Original Message-
From: Tony
[]
I'm considering designing and building some dataloggers, probably ARM
Cortex based (eg. STM32F4xx), which record the time of infrequent
events, preferably to better than 100ns and if possible better than
50nS. The data loggers will be continuously
37 matches
Mail list logo
