RTK Facet_SW Maps NTRIP Client_Mount Points

GPS/GNSS
1

With the recent upgrade to the SW Maps application the NTRIP Client parameters were lost and of course I didn’t realize this until using it for a project. I tried to re-establish connectivity which I did, but I couldn’t obtain RTK-fix accuracy, only float.

The new SW Maps application now includes versioning - V1 and V2. Does anyone know the difference between the two?

Also, mount point options are new. WISCORS has the following available:

  • Advanced mountpoints (corrections can include all satellite constellations)
  • CMRxGNSS (GPS & Glonass & Galileo & BeiDou)
  • RTCM34 (GPS & Glonass & Galileo & BeiDou) **formerly known as RTCM32
  • Legacy mountpoints (correction formats limited to GPS & Glonass constellations)
  • CMRplus (GPS & Glonass) **formerly known as CMRplusGNSS
  • CMRplusGPS (GPS only)
  • RTCM31 (GPS & Glonass)
  • RTCM23 (GPS only)
  • RTCM3Net (GPS & Glonass)
    Anyone know which mount point should be selected in SW Maps that would work well with the RTK Facet and meet the WISCORS options?

I believe the proper selection of the mount point should allow for RTK fixed positioning, but I had randomly tried many of the options and I couldn’t establish a fix. Any other thoughts on why I may not have been able to get a fix?

Thanks much!

1 Like
2

I would definitely prefer the RTCM34 mountpoint.

V1 or V2 depends on the WISCORS Caster. Most that I’ve used seem to be backwards compatible.
I just checked SW Maps and I’m using V1 for my State CORS NTRIP.

3

Okay, so V1 works for you. I’m not sure what WISCORS Caster is, but perhaps its can be used either way. I tried it both ways to get an NTRIP connection that would give me RTK Fix, but there was no change either way.

Regarding the mount points, RTCM34 is listed many times. Here is a short list.

image
image104×233 11.2 KB

I don’t know what the differences are. Is there a recommended or can I choose any of the RTCM 34 mount points?

And are you getting RTK FIX on the latest SW Maps app after updating the NTRIP client info?

4

WISCORS is a network of sites throughout the US State of Wisconsin. Different sites on the network may have subtly different hardware and firmware deployed, and consequentially the exact message mix may differ from site to site / mount point.

The FAA (US Federal Aircraft Administration) which hosts some of the NOAA CORS sites didn’t provide GLONASS, for example.

5

Makes sense, but if there is a list of 20 RTCM34 mountpoints in SW Maps within the list to choose from how do you know which one to choose? The WISCORS email regarding mountpoint options provided back to me this morning was included in the original post, but it simply identifies RTCM34 and no other message mix, as you mention, based on specific towers and their associated equipment.

6

Ah, Those mountpoints are the actual Station names, which is unfortunate.

7

Pick your closest station from the map/link below and give it a try.
As you already know, this isn’t typical.

https://wiscorsweb.dot.wi.gov/TrimblePivotWeb/Map/SensorMap.aspx

1 Like
8

Yes, I have No problems with the recent SW Maps and a similar CORS network:
http://rtn.usm.edu/

1 Like
9

The caster will normally select the appropriate Station (for single baseline) based on your GGA Sentence.
Make sure you selected “Send NMEA GGA to Caster” in SW Maps.

10

Within SW Maps, should I check the NTRIP Client box for “Apply Base Antenna PCO”? I do have the send NMEA GGA to Base Station checked within the Edit NTRIP Client page.

11

Yes, but that wouldn’t be causing your problems.

In the full Mountpoint List, is there anything that resembles “SB” (for SingleBaseline), or “Near”, basically anything that would make you think “Nearest” ?

Or any Mountpoint with VRS ?

12

I will check that out as soon as I am back by the GPS unit later this afternoon. Thank you!

1 Like
13

Okay, so here is the list of mountpoints available when the NTRIP connection is being made.

Screenshot_20250226_182654_SW Maps
Screenshot_20250226_182654_SW Maps1080×2340 175 KB

Screenshot_20250226_182701_SW Maps
Screenshot_20250226_182701_SW Maps1080×2340 179 KB

Screenshot_20250226_182707_SW Maps
Screenshot_20250226_182707_SW Maps1080×2340 178 KB

I’ve tried many of them with quality of only float or worse.

Gnss status varies where some show baseline length, age differential, and ref station and some only show it as N/A.

Screenshot_20250226_182834_SW Maps
Screenshot_20250226_182834_SW Maps1078×1438 261 KB

14

Sorry… I missed this from your Original Post.

Try: RTCM3Net

That might very well be VRS.

Also, whenever you see a baseline length that long, you wont get a RTK fix.
You’re hoping for 20 miles or less :wink:

image
image412×124 34.3 KB

15

Unfortunately RTCM3net is not in the list of mount points available to choose. If it were, it would likely work because that is one directly provided to me by Wiscors as an applicable mountpoint. I just can’t choose that one. Can it be typed in?

16

Some States make you pay for Virtual Reference Station (VRS) service.
My State just recently made VRS free.

It’s worth a phone call or email. They can quickly get you on the right track.

17

Thanks for all the help! Things were working so well before the auto update of the app.

1 Like
18

Did you look at the WISCORS map to find the nearest station to you? They have a pretty dense network, I imagine you should be able to find a station nearer than 118 miles if you’re within the state.

19

I have looked at the map and there are several that are much closer than 118 miles. However, there is no matching name or ID that tells me which of the 30 mount points in the list corresponds to the base stations that are closest to me.

20

I still have to test this, but apparently the config data was pointing to port 2102 and it should be 2101. I am guessing my list of mount points will change with the correct port number. And hopefully this should fix the RTK FIX issue.

1 Like