Maybe your R8s doesn’t have the correct license and only works with GPS and Glonass. You need to check you’re R8s configurations to know what options are activated and contact Trimble to purchase additionnal Galileo and BeiDou licences if needed.
I’m not sure how to check the current options installed in a R8s. The R10 as a web interface we can interact with over Wifi, but I can’t say for the R8s.
all GNSS options of the R8s are activated! → ja = yes → nein = no
In the upper right is the solution, it is from GPS and Glonass with emlid caster and rs2 as base.
Due to GPS and Glonass only, there are only 11 satellites in the solution.
I think it’s important to check whether the messages that Reach sends are supported by your Trimble. I’ve made a small research, but couldn’t find the particular BeiDou and Galileo messages your receiver asks for. Still, I think it should be possible to find it in specs or clarify it with the Trimble support.
Also, I’d check that the firmware of both receivers is updated to the latest versions – just to ensure there are no issues with that.
I’ve discussed the possible reasons with our devs. MSM and legacy messages are not intended to be mixed. Most likely, it’s the reason why your Trimble can’t use base corrections when both MSM and legacy messages are enabled.
You can stick to the setup with only GPS and GLONASS legacy messages or try enabling GPS, GLONASS, Galileo, and BeiDou MSM messages. If your Trimble supports all of them, it can help.
Sorry, but i think you didn’t get what the Problem is.
The R8s dosen’t need legacy messages, the R8s works fine
with the German Ntrip correction service (SAPOS) including
GPS, GLONASS, Galileo and BeiDou. I pointed that out in the
screenshot above (SAPOS NRW). The MSM4 messages from
SAPOS are nerarly the same as from RS2-Base via Emlid Caster.
I am not a MSM specialist, so i can’t figure out in depth wehre
the diffrences are, for me they looking identical, but the R8s
couldn’t handel the Gallileo and BeiDou MSM from RS2-Base
via Emlid Caster.