Fine timestamp lose accuracy in some packets

Hi there,
I’m using a RAK831 concentrator over a raspberry pi 3. After some code changes which I found in this forum, I achived to improve the accuracy of the field “time” into the gateway ( I have an accuracy of nanoseconds). So far, so good.
The problem that I’ve found out in some packets ( around 20% of them) is that packets lose 3 digits of accuracy. These packets have 000 in the last 3 digits. I know that it could be a possibility, but it happens often, so I’m sure there is another problem there.

Packet with 9 digits accuracy:
{“rxpk”:[{“tmst”:2661074596,“time”:“2020-01-17T12:41:13.757927757Z”,“chan”:6,“rfch”:1,“freq”:918.000000,“stat”:1,“modu”:“LORA”,“datr”:“SF7BW125”,“codr”:“4/5”,“lsnr”:9.2,“rssi”:-48,“size”:23,“data”:“QEQYAyaABQAB15NgexkO+nRB9I20tn4=”}]}

Packet with 6 digits accuracy:

[{“tmst”:2723351956,“time”:“2020-01-17T12:42:16.035314000Z”,“chan”:7,“rfch”:1,“freq”:918.200000,“stat”:1,“modu”:“LORA”,“datr”:“SF7BW125”,“codr”:“4/5”,“lsnr”:10.2,“rssi”:-73,“size”:23,“data”:“QEQYAyaABgABb8G1UbonwA86LDJ1tD8=”}]}

Thanks for any hint!

Hello,rak831 uses sx1301 chip, which supports microseconds.

Hi!
So why do I have some packets with nanosecond? I have the GPS module enabled, I believe that GPS increase the time accuracy to nanoseconds, right?

Does RAK7243 support fine timestamps for geolocation?, I read this post, about RAK7243, and a time accuracy of nanoseconds is achieved, and that gateway uses sx1301 chip too.

Sorry, that was my mistake.

The time accuracy obtained by modifying the code is not accurate at the nanosecond level.