NTRIP and Mobile Internet

[Pheasant Surprise]

Considering Reach RS2, I wonder if their deliveries are in schedule. Have not seen owner reports at Ag forums and the Reach website still promotes pre-orders for delivery in mid June.

They are literally shipping pre-orders now. Some folks in the UK have already received theirs.

There's already quite a few positive performance reports on the Emlid Community Forum from the folks that got their hands on pre-production units

 

[Briantee]

I would second the Reach RS2, all built in a good case.

 

[steveR]

EGNOS should give 20 to 30 cm pass-to-pass accuracy and is usually considered accurate enough for spraying and fertiliser spreading. No need for any base and the correction signal is free.

Considering Reach RS2, I wonder if their deliveries are in schedule. Have not seen owner reports at Ag forums and the Reach website still promotes pre-orders for delivery in mid June.

In theory, the Garmin Glo using EGNOS, will deliver such levels of accuracy, but experience suggests otherwise... I do need to do some investigation as to just how accurate in the real world, the Glo is.

Maybe Father Christmas will buy me a Reach2 if the Govt will not subsidise me for one!

 

[Northern farmer]

In theory, the Garmin Glo using EGNOS, will deliver such levels of accuracy, but experience suggests otherwise... I do need to do some investigation as to just how accurate in the real world, the Glo is.

Could you give me a pointer to Gramin GLO techical specs stating EGNOS support? I feel EGNOS support was mentioned at this forum but when I look at the Garmin website they only mention waas and with very small letters.

They do advertise GLONASS support which is very confusing because the receiver gives lower accuracy when using (autonomous) GPS + GLONASS compared to using GPS only but with EGNOS correction.

How do you know the GLO has EGNOS fix? The manual explains LEDs indicating the receiver status, constant green means GPS fix but there is no status indication about SBAS fix. Have you looked at the NMEA data, that should cover the fix type?

I have no experience about GLO but if it does support EGNOS and if that correction is active, I guess GLO should not give much worse position accuracy than the other EGNOS precision Ag devices. Just trying to understand if this Garmin GLO did not provide the accuracy it should or if the EGNOS accuracy is simply not fulfilling your expectations (I could understand that too).

 

[steveR]

Could you give me a pointer to Gramin GLO techical specs stating EGNOS support? I feel EGNOS support was mentioned at this forum but when I look at the Garmin website they only mention waas and with very small letters.

They do advertise GLONASS support which is very confusing because the receiver gives lower accuracy when using (autonomous) GPS + GLONASS compared to using GPS only but with EGNOS correction.

How do you know the GLO has EGNOS fix? The manual explains LEDs indicating the receiver status, constant green means GPS fix but there is no status indication about SBAS fix. Have you looked at the NMEA data, that should cover the fix type?

I have no experience about GLO but if it does support EGNOS and if that correction is active, I guess GLO should not give much worse position accuracy than the other EGNOS precision Ag devices. Just trying to understand if this Garmin GLO did not provide the accuracy it should or if the EGNOS accuracy is simply not fulfilling your expectations (I could understand that too).

I read the EGNOS connection somewhere in the past week on a US site, as they use WAAS there, and the Garmin people said that it (the Glo) used EGNOS over here. No link though... :-( The LED info is practically useless in the real world, and it needs separate software.

One author said that he had identified an Egnos fix using software to identify the individual sat, but although I can do this with my BT software, I have no idea if it is actually using the correction data... Or indeed how to identify an EGNOS sat!! The Glo does seem to pull in a vast number of signals mind... I will have a look when I am using it next.

On your final para. I am really going on my farm fieldnav software stating the accuracy factor. I have noticed that it does vary, and last week when fertilising grass , the accuracy was shown at 1m and on checking track to track I was driving very accurately (for me!). More than good enough even for spraying grassland.

Later!

https://www.gsa.europa.eu/european-gnss/egnos/services/service-access

 

[Bemo]

Hi, I have currently got 4 John Deere receivers (3x sf 3000 and 1x sf6000). 2 of them are on the free signal 1 is on mobile RTK(£700) from a dealers base station and 1 is on sf3(£800), would it be possible for me to install a Reach RS2 on one of my buildings to run all of them if I upgraded them to RTK. Farthest fields are 5 miles away. If so what would be involved in allowing the reach to communicate with the John Deere receivers.
Thanks.

 

[Pheasant Surprise]

Hi, I have currently got 4 John Deere receivers (3x sf 3000 and 1x sf6000). 2 of them are on the free signal 1 is on mobile RTK(£700) from a dealers base station and 1 is on sf3(£800), would it be possible for me to install a Reach RS2 on one of my buildings to run all of them if I upgraded them to RTK. Farthest fields are 5 miles away. If so what would be involved in allowing the reach to communicate with the John Deere receivers.
Thanks.

Funny you should just post that. I’ve just posted this message in another thread....the short answer right now is unfortunately not if the JD receivers will only understand the older RTCM 3.1 correction format.

Currently when in base mode the RS2 blasts out the newer RTCM 3.2 correction format and uses only the newer MSM message type to do so. This precludes a lot of existing/legacy receivers from using it as they “don’t speak MSM”....

Yep unfortunately as of right now the front end interface, ReachView, in the RS2 receivers only allows the newer multi-constellation MSM style message output (RTCM 3.2) and not the “classic” GPS & GLO only message types found in RTCM 3.1 when in base mode. The underlying ublox chip and the software RTK libraries will however support the original/classic MT’s as well as the newer MSM style messages.

Emlid said that they would consider adding the specific MT’s for antenna descriptor etc to support Trimble/Topcon rover receivers, but really the bigger issue is that all these “old” (and I use that term reservedly) receivers that we have won’t speak the new RTCM 3.2 lingo, which is kind of frustrating but understandable given the “if it ain’t broke don’t fix it attitude” in the Precision Ag industry and hey RTCM 3.2 has only been out there since 2013...so give them time to catchup

I just posted a message on the Emlid forum asking if they would consider adding “classic” (or legacy) RTCM 3.1 output in ReachView. Will see what they say.

There is another possible solution on the horizon - that is once SNIP implement the “Create Classic from MSM Message” translation feature in their software it would be possible to use the SNiP caster software to turn “old” from “new”

 

[Bemo]

Ah thank you, it is not quite that simple then. Would it be possible to do it with older tech that blasts out RTCM 3.1 or would that be counter productive For the future, or wait to see if they can add support for the classic receivers.
Also what type of system would my dealer be using as I am sure they wouldn’t be too keen on telling me.
Thanks.

 

[Pheasant Surprise]

Ah thank you, it is not quite that simple then. Would it be possible to do it with older tech that blasts out RTCM 3.1 or would that be counter productive For the future, or wait to see if they can add support for the classic receivers.
Also what type of system would my dealer be using as I am sure they wouldn’t be too keen on telling me.
Thanks.

As the RTCM 3.1 standard has been around since 2006 (with subsequent updates for a few years) - virtually all the current gear on the market supports it as an open standard. Quite certain your dealer’s base would simply be issuing RTCM 3.1 correction.

Some correction service providers will also offer RTCM 3.2 / MSM correction outputs on their NTRIP networks too for the more up to date gear.

The main limitation with 3.1 is that it ‘only’ supports GPS and GLONASS correction, as these were the only two constellations in existence at the time the standard was updated. This is fine but in the future support really is needed for all the newer global satellite constellations such as Galileo and BeiDou, hence RTCM 3.2 standard was developed and this uses more modern message types called MSM....

What Emlid have decided to do is to jump directly to RTCM 3.2 output and just support MSM4 type only message output when in base mode. This supports all the existing and “new” constellations and works really well - but it won’t work (until they perhaps change things) to support the older/legacy rover receivers which can only understand/expect “classic” RTCM 3.1 messages.

I’ve asked Emlid on their forum if they’d consider updating the ReachView interface to support existing/legacy receivers when an RS2 is being used as a base receiver, and use classic message types found in RTCM 3.1 as another option.

I reckon if there’s a big enough call for it, from other users in construction and surveying they could well do it, but that’s only a guess from me.