I am using ArduRover 4.6 with a CUAV V5+ flight controller and CUAV C-RTK 9P modules for both the base station and rover. RTK was working perfectly yesterday in the same environment and with the same configuration. Today, despite no changes to the setup, RTK is no longer working.
Current Observations:
GPS Status: 3D GPS only (no RTK Fix).
HDOP: Below 1.0 with 24+ satellites visible.
RTCM3 Corrections: Sent from the base station, shown as received in Mission Planner, but RTK Fix is not achieved.
Error Message: “Configuration of fixed position on Septentrio receiver failed” when trying to reconfigure the base station.
Steps Taken:
Verified all cables and connections (no damage).
Restarted both base station and rover modules.
Checked baud rate (460800) and GNSS mode (GPS+GLONASS+Galileo).
Repeated Survey-In process for the base station.
Tested in the same location as yesterday (indoors, near windows).
Unexpected Behavior:
RTK worked yesterday under identical settings and conditions.
RTCM corrections appear to be transmitted and received but are not processed for RTK Fix.
What could cause RTK to stop working under the same conditions? Are there specific logs or diagnostics I should check for the CUAV V5+ or C-RTK 9P? Any insights or suggestions are appreciated.
@cuav_le could you help me about this problem?
Thank you.
marblecreek
(Rover; AP 4.6.0-BETA, Pixhawk 6X CM4)
3
Move outdoors with clear view of the sky. I tried testing things indoors when working on getting GPS yaw to work - super flaky results, until, moving outside…
@baltazar119@marblecreek Hi, I just got back from vacation. Narrow sky viewing angles can affect RTK measurements and positioning. It may enter RTK floating point solution or fail to enter RTK fixed solution state. You need to move the rover and base station to a location with a good aerial view; especially GPS for yaw requires more accurate position estimates.
We are encountering an unexpected issue with our CUAV C-RTK F9P Base and Rover units paired with **Pixhawk V6X. Last week, the system operated flawlessly in the exact same location with stable RTK Fix throughout the day. However, a few days later, the RTK functionality ceased entirely—the Rover cannot achieve RTK Fix, even when forcing corrections from a nearby third-party NTRIP/CORS station. Critically, the base station’s positioning cannot be the issue, as it previously worked without adjustment. Environmental factors and hardware placement remain unchanged. The sudden failure suggests potential firmware, configuration, or hardware faults. Please advise on diagnostics or updates that might resolve this abrupt loss of functionality.