Further to my earlier thread regarding certain RTCM3 message types 1007 and 1008 - I have been doing some more testing trying to use an RS2 base with existing/legacy third party RTK receivers.
Unfortunately the great stumbling block to successfully using an RS2 base in this situation appears to be that the vast majority of these existing receivers from the likes of Topcon, Trimble etc acting as rovers is that they are really only capable of receiving “classic” RTCM3 corrections - that is really RTCM 3.1 only and not the newer RTCM 3.2 (and 3.3) corrections which use the newer multi-constellation MSM message types like the RS2. This is especially true in Precision Ag where the “if it ain’t broke don’t fix it” mindset is prevalent and the refresh lifetime of some of these receiver models is anywhere from 5 to 10 years.
There are development plans from the SNIP caster team to support what they call “Create Classic from MSM Message” using their message translation function. This could be used to create RTCM3 message types 1001~1004 (GPS) and 1009~1012 (GLONASS) from MSM messages. Unfortunately this is a future feature, so again does not work right now. It would also necessitate another “box” or step.
I’d like to ask Emlid if they would consider supporting a “classic” RTCM 3.1 style output in ReachView that uses non-MSM4 correction output so that the existing fleet of legacy RTK rovers will be able to use the RS2 as a base. I know this may be seen as a somewhat retrograde step but it would increase the use, flexibility and appeal of the RS2 massively to the army of users out there with lots of other legacy receivers.
Please, pretty please Emlid with a cherry on top