RS2+ as Ntrip base for Trimble

Hi, I am trying to use and RS2+ as a RTK base station for some Trimble Receivers (R2,R10). I have got this working well except for the Galileo system. RTCM Messages I am sending from the RS2+ are 1006,1074,1084,1094,1124,1230,1008 and 1033.

Message 1094 is the Galileo message, and I have used snip to understand what is different about the Emlid 1094 message and other services I have access to. The only difference is that the codes L1C and L7Q for Emlid and L1x and L5x for others

Is it possible for Emlid output the 1094 message with the L1x and L5x code?

Attached are some screenshots


Hi! I also have the same problem that I wrote about in this forum thread. Look at this information, maybe it will help you.

Emlid promised to study this problem, but so far there is no answer.

1 Like

Hi, yes I have had a read of your thread as well.

Can you confirm your CORS is sending the 1094 message with the L1X (E1) and L7X (E5b) codes and this is working with your trimble gear?

If this is the case then it might be the missing L5x (E5a) that Trimble require for a solution.

Our cors broadcasts these Ntrip messages, see the screenshot. Trimble works without problems from it.

1 Like

Hi guys,

The L5X code refers to the Galileo signal in the E5a frequency band, while L7Q corresponds to E5b. Our Reach receivers can only track the E5b signal (L7Q). This is why, if Trimble indeed requires the E5a signal for the calculation, Galileo satellites from Reach RS2+ would not be considered. Due to hardware limitations, we can’t update the existing devices to support E5a. However, I’ve shared your use case with our development team for future reference.

1 Like

RTCM SC-104 has evolved, and here is a brief history.

With Version 3.2 came Multiple Signal Messages, which combined “messages together with associated data instead of sending separate messages to accomplish the same task.”

Here is the fine print:

"GLONASS Bias Information Message

Message 1230 communicates the GLONASS Code-Phase Bias (CPB) information. This information allows RTK rovers to compensate for differences in biases between themselves and the base station, enabling or improving the resolution of GLONASS ambiguities.

CPB values for all GLONASS FDMA signals available in the data stream of both MSM and Legacy (1081-1088 and 1009-1012) are mandatory for full GLONASS interoperability."

Emlid’s REACH M2 is using RTCM-3.2, and if MSM4 is being used, then 1230 would not be needed, if the above cite is true ( available in the data stream of both MSM).

Via REACH M2 with a GNSS antenna that is capable of receiving them.