Coarse event timestamps. What am I missing? RINEX and POS file

My event.pos file appears to me to be suspect. I have tried outputting in GPST and UTC and I get timestamps that look fictitious after the first or second decimal. Here are the 5 decimal places from 10 consecutive timestamps from my latest flight:

99091
39093
79095
27098
71098
23100
39110
79111
23114
71113

Last 3 digits are:

091
093
095
098
098
100
110
111
114
113

What is the actual timekeeping accuracy of the u-blox chip or the emlid interface to it?

Or am I not doing it rite? I’ve gone through some of my other files and I’d be surprised if the timekeeping of the M+ is much better than 0.05 seconds. Unless the problem is with the conversion to rinex?

EDIT: for anyone that was interested, I now think the emlid timing is accurate. Accurate enough, I think, to measure that the Phantom 4 LED lights operate on a duty cycle that is very regular. I think the LED switches on when the correct pulse width is produced from it’s driver, which means the lights cannot switch on and off at anything other than well defined, regular moments in time. I think this is what I’m seeing in the timestamps.

Hi @wsurvey,

Thank you for the review.
Hope it will be helpful for other users :slightly_smiling_face:

This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.