-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pairing tcpvel and tcpfix #11
Comments
You could try checking the timestamps, but the velocity publishing is normally a different data packet from the positional. You could sync outside of this package in your subscriber or try to change the logic here: |
Did you notice that emlid GPS data has an latency issue? |
I would assume there would be if you are using RTK since that has a motino profile, but I am not sure about normal GPS. |
I am using RTK. Do you know how much the latency is? |
I do not have any estimate or a guess.
…On Tue, May 5, 2020 at 1:04 PM Artly ***@***.***> wrote:
I am using RTK. Do you know how much the latency is?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAQ6TYXOJHIIVSIE2ZXE6CTRQBBJLANCNFSM4MYHRUHQ>
.
|
I found it was about 150ms https://twitter.com/SmallpixelCar/status/1258825869281222657 |
I noticed that the repo publish tcpvel and tcpfix separately. How can I pair the tcpvel and tcpfix message to make sure they come from the same emlid data packet?
Also, the tcpvel linear has a Nan when the object is not moving. Could you fix it?
The text was updated successfully, but these errors were encountered: