Topcon correction setup

Soon_60

Member
1) Maybe it is not a good thing that the correction stream has both ..5 and ..7 messages. I think that it is not recommended...

2) The NTRIP caster (base) might be set up so that it requires a periodical update of your position as a NMEA message -> NTRIP client settings.

I have a neighbor using my base with Topcon AGI-4 on NTRIP with no problems at all.
But he can not type in the base URL, has to use IP number...
If my base dynamic IP has changed and he does not get a NTRIP client connection, then he must SMS "STATUS" to base LTE router phone number and gets the IP in a reply SMS...
 

Soon_60

Member
And
3) Without knowing exactly how everything is set up in your system:
In NTRIP correction data stream hardware flow control must be OFF. This a a common problem when using a Lefebure Android NTRIP client and bluetooth serial dongle to get the corrections to the receiver. Occasionally lost data in NTRIP stream is not a problem but old data is...
 
Location
North
1) Maybe it is not a good thing that the correction stream has both ..5 and ..7 messages. I think that it is not recommended...

2) The NTRIP caster (base) might be set up so that it requires a periodical update of your position as a NMEA message -> NTRIP client settings.

I have a neighbor using my base with Topcon AGI-4 on NTRIP with no problems at all.
But he can not type in the base URL, has to use IP number...
If my base dynamic IP has changed and he does not get a NTRIP client connection, then he must SMS "STATUS" to base LTE router phone number and gets the IP in a reply SMS...
You forgot to tell details about your base (for reference). It is quite obvious that Topcon AGI-4 receivers run well from "a" base but not from another one.

I did not understand your comment about ..5 and ..7 messages, are you suggesting to remove 1005 or all xxx7 messages? I guess not.
 

Soon_60

Member
OK. I have a Trimble receiver at my base. I use a SNIP-Lite (free) caster.
It streams: RTCM3.x messages (and rates) were: 1004(1), 1006(10), 1008(10), 1012(1), 1013(10), 1033(10)
So those are the older type "Legacy" messages.

Streams also CMR+ on a separate Mountpoint for my old EZ-Guide 500 receivers...

For MSM (Multiple System Messages) maybe it is OK to stream both type MSM 4 and MSM 7 (my 5 was a missprint - false news...). As a default U-Center caster does it so for F9P and a lot of the Mountpoints on rtk2go.com:2101 seem to configured so...

But the more messages you stream the more the rover system has to digest. Maybe not all that smart to steam out stuff that really is not needed?

I was maybe more thinking about:
"Sending legacy (1001-1004 and 1009-1012) and MSM messages in the same stream can cause problems for remote RTK users and is not recommended."
 
Last edited:
Location
North
The above sounds like some solid advice. The RTCM 1013 was interesting.

A pity that it is so difficult to find information about supported messages and the minimum set for many OEM receivers.
 

Badshot

Member
Location
Kent
You saw autonomous. Do not use that as it will favour gps signal . So basically non corrected gps .
ALWAYS use Egnos with the correct sat numbers selected as a minimum

yoir method is fine as it will then connect to the strongest of those 5! Autonomous is pass to pass accuracy of about 1.5m so please don’t use it!
Ah ha.
You may have just answered my question on another thread.
Autonomous is pants then.
I'll stick it on sbas.
 
Location
North
RTCM 1013 is a list of messages sent and the time intervals and maybe also info about leap seconds used.
It is not needed for RTK.

www.use-snip.com have very good listings of all the different messages.
They do but so do many other web sites. Not difficult to figure out what each message serves for. Much more difficult to find which messages each receiver needs and which are a bonus. Like who is able to make use of RTCM 1013? More importantly who needs RTCM 1008/1007 or 1033. Who accepts legacy messages only. Probably many more important details that my memory has lost at the moment.
 

Charles Quick

Member
BASE UK Member
Location
Somerset
I think I have something working, although impossible to say until it gets used in anger.
minimal message set:
Code:
1004(1), 1006(10), 1008(10), 1012(1), 1033(10)
Antenna descriptor in 1008 and 1033 is
Code:
LEIAR25.R3   NONE, 10250003
Which is pretending to be a Leica AR25 (same as the EUREF receiver I tried which also just about worked, RTK dropped in and out a lot, but it is 250km away!)
Also included a bogus serial number but I'm not sure if it's checked.
 

Carbon Week - 1 to 5 March.

  • 83
  • 0
Carbon Week

Carbon Week is a series of AHDB events, taking place from 1 to 5 March.
The webinars and panel discussions will feature a range of speakers and are for farmers and growers interested in understanding more about the carbon cycle, carbon auditing, reducing emissions and the opportunities around this.
More information about each session can be found from these links:
Top