![]() ![]() > But there is still an offset of around 10.3ms, which I think is induced by USB as explained in this article about other chipsets ( August/016078.html) > The offset induced by the "pulse length" has disappeared. > To do the inversion, I just changed the "Pulse Mode" parameter to "Falling edge" from "Rising edge". The offset "-62.580ms" for the GPS seems normal to me, i guess it's the processing time of the NMEA frames by the U-Blox NEO-6M.īut, I don't understand why my PPS clock has an offset of "+110ms" compared to Internet NTP servers? Remote refid st t when poll reach delay offset jitter I let it run for a while, and this is what I get: Server 127.127.20.14 minpoll 4 maxpoll 4 mode 16 prefer I am using ntp 4.2.8p15 on windows with loopback-ppsapi-provider.dll drivers I soldered pin 3 of the u-blox chip to have the PPS on the DCD/CLK pin of the CH341A. I use a USBTTL adapter (CH341A) connected to a NEO-6M in +5V, RX, TX, GND. I post this message because I have a huge offset (+110ms) on a PPS source compared to NTP internet servers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |