Hello Emlid Community!
I’m new here. We’ve just ordered our first Reach RTK Kit. Our application is autonomous vehicle testing & development. We need a low-cost system for car speed over ground and heading measurement. We need ideally all data in NMEA as we connect Reach to a data acquisition system (kind of logger).
Please share your up to date experience on the following topics:
Is the speed over ground in Reach output taken from Odometer, specified in ublox NEO M8T Datasheet (see page 14)?
ublox: “The odometer provides information on traveled ground distance (in meters) using solely the position and Doppler-based velocity of the navigation solution.”
We plan to use 2 Reach receivers in Moving base mode with a baseline of ca. 2m on the car’s roof. This system should be able to perform quite a precise relative heading measurement. In addition we would also I saw several forum topics with similar issues, but no up-to-date answers from Emlid Team. A flicker of hope are the improvements to the Dec/2017 release in ground speed.
Reach contains an IMU. How is its data used in the algorithm? Can we expect a True Inertial Heading from Reach? It is normally used in Kalman Filter in RTKLib for Pitch and Roll correction of position, right?
When I connect in moving base mode my rover via NMEA to an external logger, all the data in NMEA will be the result of moving base RTK correction, right?
What delays are typical for Reach system in terms of latency and permanent delay to real world events on UART/Serial output?