ddrown
Member

Ok, updated the code with the *dop data: GPS pdop=1.8, hdop=1.5, vdop=0.9

Wow, you have a very strong signal there. It should be easy to pull HDOP out of GSA, it's already parsing that message.

Building on the JSON data, I added a webpage that will poll /state.json and build graphs. You can reach the web page by putting your teensy's IP address in your web browser. As well as general stats: PPS...

I've added a webserver to the code to make it easier to get data from the NTP server. /state.json from the teensy returns the following structure: { "ppsToGPS": 396, // milliseconds between PPS timestamp and...

That's interesting, the teensy should be more than able to keep up with an iburst. PPS would be able to tell you a lot at a glance Some other ideas for LED indication: * offset between local clock and GPS...

Excellent, glad to hear it is working for you. Those are low delay and jitter numbers, I like to see that.