LS not using Galileo in RTN solution on CORS?

[Jack M]

Is is possible for our older model LS to receive corrections using Galileo and GPS L5 on the network? All GNSS constellations are visible on the LS screen but don't appear to be utilized.
I don't see an option in J-Field to select\change the message type or mount point to RTCM 3.2 MSM4 IMAX. Any help would be greatly appreciated. Thanks.
Jack M

 

[Adam]

Yes, the setting for that should be under Mountpoint in the RTN APN setup screen. You will need to also change to the 6 or 2 engine multi constellation firmware under the advanced settings.

 

[Jack M]

Yes, the setting for that should be under Mountpoint in the RTN APN setup screen. You will need to also change to the 6 or 2 engine multi constellation firmware under the advanced settings.

Thanks for the support, Adam! Much appreciated. I will give that a try today.

 

[Jack M]

I changed the mount point and firmware type to 6 engine multi constellation but I don't see an option to change the "Receive Format" from RTCM 3 to RTCM 3.2.
Does this option exist in there somewhere? I'm running Linux 4.4.190.9 & J Field 3.0.8.94 & GNSS 3.7.7.200427. Thanks

 

[Jack M]

RTCM 3.2 option?

 

[Adam]

It looks like you did correctly Jack.

 

[Duane Frymire]

RTCM 3.2 option?

My screen looks same (no mention of msm) using NY RTN. If I understand correctly, the base controls the correction stream. If I set my LS as base there is a spot to choose msm type. But with RTN, the mountpoint you choose determines the type. I think that screen looks the same when using LS as base with msm selected; I'll have to look at it next time. At any rate, I'm still having better luck with fixes with RTN using the GPS/GLO, rather than either of the others (nearest cors is 26 miles).

 

[Matt Johnson]

@Vladimir Zhukov does a new "Receive Format" option need to be added for RTNs?

 

[Vladimir Zhukov]

Hello Matt, RTCM 3 should be selected while configuring of the TRIUMPH-LS rover profile. it would distinguish automatically between RTCM 3.x Min, RTCM 3.x MSM3, RTCM 3.x MSM4, or other RTCM 3 types of corrections.

The correct Mount Point, which sends MSM messages, should be selected as well.
it makes a sense start first with RTCM3MSM_NEAR.
And yes, you will need to also change to the 6 or 2 engine multi-constellation firmware.

 

[Matt Johnson]

His screenshot is showing a connection but no Received/Lost count.

Jack do you have NMEA GGA enabled?

 

[Vladimir Zhukov]

Select RTCM3MSM_NEAR first, not RTCM3MSM_IMAX

 

[Jack M]

Select RTCM3MSM_NEAR first, not RTCM3MSM_IMAX

Thank you Vladimir. This seemed to work. I also changed to the 6 engine firmware.

 

[Jack M]

His screenshot is showing a connection but no Received/Lost count.

View attachment 9906

Jack do you have NMEA GGA enabled?

Yes, but I was indoors at the time and as soon as I went out it was receiving correction data as normal. I also did as Vladimir suggested using the RTCM3MSM_NEAR mountpoint which seemed to work. I attached a couple screenshots for you to have a look at. Are the values under Sats: (highlighted in RED) GPS \ GLON \ GAL \ BEI \ QZSS?
Both point #3 & #10 were in similar open sky about 9 minutes and 500 ft apart from one another. In point 10, does it look like GLONASS is being used in this solution?
Thanks guys for your help.
Jack M