Yo Gary

My bad. I didn't think the M8F did Timemark as I missed it in the M8F docs and didn't see EXTINT0 nor EXTINT1 pins in the pin list for the M8F. Apparently it uses the FREQ_PHASE_IN as EXTINT for Timemark.

The first email you sent out had text that quoted "EXTINT0", which makes me think EXTINT0 of an M8T and not the EXTINT of an M8F.

I'm not getting anything out of the thesis pdf that suggests an M8F. On page 35, it does mention using an u-blox NEO-M8T.

The M8T can produce Timemarks upon interrupt, 0 + 1, through pins EXTINT0 and EXTINT1, output as UBX-TIM-TM2 messages. If all we're after for this is Timemarks, then the M8T is a lot less expensive than an M8F.

Have I missed something along the way and that we're not looking to do what the thesis did and are on to something else?

Michael

On 13/08/2018 1:23 PM, Gary E. Miller via devel wrote:
Yo MLewis!

On Mon, 13 Aug 2018 13:16:44 -0400
MLewis via devel <devel@ntpsec.org> wrote:

If I understand what was used, it was the EXTINT0 and EXTINT1 inputs 
that cause the GPS module to take a Timemark (timestamp), which is 
output as UBX-Tim-TM2 messages. See page 69 of the M8T manual.
The part in question is a NEO-M8F, not a NEO-M8T

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	g...@rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can�t measure it, you can�t improve it." - Lord Kelvin


_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel

_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel

Reply via email to