SivaDev1038
commented
1 year ago Internal Comment
not able to understand what does the ftime counter actually represents
Open SivaDev1038 opened 1 year ago
SivaDev1038
commented
1 year ago Internal Comment
not able to understand what does the ftime counter actually represents
SivaDev1038
commented
1 year ago Update from the Customer Sounds like a 1 second count to me and if anything different would not be PPS = Pulse Per Second right?! Each GPS PPS input resets the counter to zero, which then steadily counts up to 999…999 nano seconds at which point next pulse arrives and resets the counter to zero, which then steadily… I’m sure I see a pattern here!
!wink.png_v=12|width=72,height=72,alt=":wink:"!
Not rocket science even though it uses a Satellite (or 3)
!slight_smile.png_v=12|width=72,height=72,alt=":slight_smile:"!
Atlassian Ticket Link
https://r161038.atlassian.net/browse/CSE-68
Issue Description
Hello everyone,
I have enabled the optional feature for fine time stamping (‘ftime’) in rxpk on the gateway. I am not able to understand what does the ftime counter actually represents.
It says on hal documentation that it is number of nanoseconds since last PPS [0…999999999]. But the values received is observed to increase with time upto 999999999 and then start over. Should the ftime more or less same, since it counts the nanoseconds past the last PPS pulse ?.., which by nature happens every second.
If there is any reference or ideas available to understand it then please do share.
Many Thanks !
What did we understand from the customer issue?
...
What doubts do we have?
...
Clarifications needed from the customer
...
Insights:
...
Supporting Internal Logs/Metrics
...
Approach/Next Steps
...
Environment
...
Checklist
labelshave been assigned.