A quick read of the documentation for the M9N seems to tell me that if I supply a source of RTCM data to the Rx port on the M9N that it will produce the cm level precision results. I’m guessing that I might have to do some Ucenter tweaking to get things to work, but give me some advice. Workable? I am just setting up a base station with a new ZED-F9P to generate the correction data, and I have several M9N units already in place. It would be great to just add telemetry radios to them and be able to see the results. Plus I save some money.
The NEO-M9N does not support RTK or high precision GNSS. Can you link to the source docs that state it is?
Here’s the datasheet I’m looking at: https://content.u-blox.com/sites/defaul … 014285.pdf
Hi,
The NEO-M9N does support RTCM input, but can’t generate RTCM. It is a single band GNSS, so you won’t get to cm accuracy with RTCM. But it should still give you a significant improvement over normal GNSS + SBAS.
I’ll try and find time to run a quick test.
Best wishes,
Paul
Humm… Pretty inconclusive I’m afraid…
Like Sparky says, the M9N is not RTK-capable. So all you can hope to do is improve on the normal DGNSS accuracy.
With four constellations GNSS + SBAS, I’m seeing horizontal accuracy of around 0.6m.
When I enable RTCM (NTRIP Client from Skylark, through u-center), I can see the RTCM message count increasing but the horizontal accuracy is still around 0.6m…
No magic wand… Sorry!
The NEO-M8P is RTK-capable, and is available (today) at 32%-off:
https://portal.u-blox.com/s/question/0D … -ublox-m9n
Tightened, but a bit contrived, DGNSS not RTK. CEP99 sub metre.
On the other hand I’d generate raw measurements and …