Ill try it out.
I got it up and running. My novatel smart 7 rover connects to it and obtains a rtk fix in seconds and stays connected and when i restart it it gets rtk again very soon . Ill update when i have more hours of testing but looks promising .
How can i enable msm7 message in the reach rs2? Im sure theres a way if you could provide detailed instruction of how to?
The Ublox F9P chip in the RS2 is capable of outputting msm7 messages, but it’s not something that Emlid has currently implemented as it’s heavy on the communication bandwidth (especially for Lora). I saw this mentioned on a separate thread where someone was asking about it. But they tend to be very open to feature Request suggestions, so write in your use case and how it would be helpful and if there are enough people interested they may put it on their development roadmap.
That is what is recommended to these newest agricultural receivers like novatel etc. It should work without but it should be there as an option to use i think .
MSM7 is roughly the same data as MSM5, but higher resolution. In turn, MSM5 includes one more set of information (doppler info) over MSM4. Considering even with MSM4 we’re already achieving centimetric accuracy, I really fail to see how sending more data, using more bandwidth, will have any added benefit for precision AG. For geodesy and surveying I can see the point, but for AG, not so much.
Then again, I’m not an engineer so maybe you can ask your reps if they have a justification for this.
I’m thinking that most of the gains that could be had in the future would come from other fields like machine learning and image processing, but I’m getting off topic now.
You can never drive too accurately. Also implement steering is starting to appear. The tractor is driven by gps as straight as possible, then the implement also has a gps guidance system to steer itself to ensure it does not drift.
I indeed see how useful it may be. However, if you work with our Caster, then we have a step-by-step guide explaining how to connect a base and a rover via NTRIP for passing and receiving corrections. It doesn’t contain the instructions for the configuration of the 3d-party receivers, but it shows how to connect them together.
The Reach Panel doesn’t have a screen for surveying, so the satellite map view isn’t provided. But this is something that may be considered for the Web interface!
That’s interesting. Was the receiver placed outdoors at that time? I assume that this might have happened because the receiver couldn’t receive a good-quality signal indoors, so the bars were always low. But please let me know if I’m wrong with my assumption.
Reach RS2 indeed doesn’t output MSM7 messages by default. Usually, MSM4 messages are enough for 3d-party receivers. But I’ve added your notes as a feature request!
Reach Panel interface doesn’t have a function for surveying. That’s why there’s no option for checking the different map layers. But our beta Web Interface allows you to access survey project data! So, supporting the images from WMS servers is something we could consider for Web Interface.
Hi David, my guess is the satellites page is programmed to show you all satellites visible to the RS2, even those below the SNR threshold. But only those above the threshold are actually used in computing the position. In terms of the base transmitting RTCM corrections, I’m unsure if the base uses the SNR mask to limit which to transmit, or if it transmits all of them and let’s the rover use it’s own SNR mask to limit them.