I am writing as I own a ZED-F9R ArduSimple kit, with NTRIP RTK corrections via 4G.
I would need to use it with an update rate of ideally 20 Hz. However, I am currently struggling to get such a high update rate.
I tried setting an update rate of up to 40 Hz with u-center, and a baud rate of 921600, but that did not help.
Indeed, I tried recording a localization trace with gpspipe, and post-processed it to get a .wkt file, reporting for each GNSS receiver update a timestamp and the position, together with other information.
I also developed a Python program which reports an estimate of the actual update rate, by parsing the .wkt file and analyzing the timestamps for each update from the GNSS receiver.
Even if I set 40 Hz and increase the baud rate, I always get as a result an effective rate of 10 Hz or less (more than 4 times less than expected).
Do you know why we are observing this behaviour? Is there some setting we can tweak to try to improve the performance of the receiver?
Thank you very much in advance.
>Do you know why we are observing this behaviour?
Probably because you are configuring it incorrectly, you don’t describe exactly what you set.
As I understand it, you need to decouple the rates, such that (CFG-RATE-MEAS × CFG-RATE-NAV) >= 500 milliseconds (<= 2 Hz). This is the rate at which it will solve for an RTK position.
CFG-RATE-NAV_PRIO is the synthetic high rate you want position reporting, a subset of messages will report at this rate.
Please login or Register to submit your answer