-
Notifications
You must be signed in to change notification settings - Fork 146
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
"inputting RTK results from the F9P" need two separate C099-F9P boards? #82
Comments
The raw data here should be in any format that can be positioned by rtklib, but map4 uses ubx and spf files, and We have not tested it with rtcm.
|
Yes. |
Thank you for the kindly reply. |
This is because when we did that before, the output of f9p became abnormal. Perhaps there is a setting that can be done with a single f9p, but we have not found it. |
thanks. |
We have not tested it with m8t, but maybe eagleye will work with m8t. Also, m8t is a single-frequency receiver, so I don't recommend it because of its poor rtk performance. |
Are both gnss mounted on the vehicle? How do you get rtk corrections when both are moving? |
Both GNSS are mounted on the vehicle. |
This issue is closed for now. If you have problems again, please reopen this issue. |
"When inputting RTK results from the F9P into the Eagleye, two F9Ps are used as follows.
(1) A receiver that outputs NMEA (RTK results from the F9P internal engine)
(2) A receiver that measures RAW data through RTKLIB and outputs Doppler velocity."
as this said.
by the way, "A receiver that measures RAW data", the RAW data is the RTCM V3 raw data ?
or rtcm v3 data can be used to calc velocity?
Thanks
The text was updated successfully, but these errors were encountered: