Here is my set up process for uhf on topcon hiper vr base.
If I click configuration I get this
Just got the uhf antenna for my rs3. If anyone knows the best settings for my topcon hiper vr uhf id love to know. Thanks
1 Like
Hi Conner,
Thanks for sharing the screenshots! I looked through them, and let me suggest some modifications that can help establish the connection.
-
The UHF radio of Reach RS3 uses the TrimTalk protocol, so let’s change the Protocol to TrimTalk Tx.
-
Let’s set the Modulation to GMSK.
-
Please also double-check that the selected frequency is the same on the receivers.
Can you please try these and check whether you can receive corrections with Reach? Thanks!
3 Likes
I made sure I was broadcasting msm4 and changed the kHz to 25 in the topcon vr and I it worked for a minute and I got a fix than I stoped receiving corrections and I could never get it back. I also changed to 25kHz in Emlid uhf settings. I also made sure I could get a fix with my topcon vr rover.
1 Like
I played with a bunch of settings but nothing worked.
I’ve only gotten it to work once and it was like how @Wombo described. There issues was different from mine because they were trying to get trimmark 3 protocol to work with an RS3 without a adl but you need a adl for that.
I wonder what style of protocol trimtalk topcon vr uses like
- TRIMTALK 450S
- TRIMMARK II/IIe
- TT450(HW)
- TRIMMARK 3
All I got from the owners manual is it supports Trimble protocol. I would assume 450s and not trimmark 3 since this is a pdl not adl
1 Like
Your Topcon settings nomenclature is not exactly consistent with Trimble but it’s possible the “TrimTalk” option is actually referring to the later “TrimTalk v1” which incorporates, and should be compatible with, all the earlier protocols that you have listed…including the TT450S that you need. So you could also try that setting.
However, I would first try throttling back the bandwidth in the RTCM3 corrections stream. FYI I was using TT450S protocol with the TM3 but ultimately gave up and abandoned the idea. But even with newer PDL & ADL radios my RS3’s still have problems coping if the stream is greater than 780 bytes/second or roughly equivalent to 28 SV’s. The fix disappears as the RS3’s get bogged down dealing with internal TT450 parser crashing.
Does the Topcon allow you to disable correction constellations back to say minimal GPS only, or configure legacy RTCM3 and see what happens? If that works, it will take longer to obtain a fix, but you could at least establish some confidence and build back out from there.
1 Like
Thanks for the reply. Yes I did try disabling QZSS and beiDou on the hiper vr broadcast. I will try taking off Galileo then maybe glonass. And probably run 12.5kHz for less data to bog down the rs3. I can only broadcast msm4 ,3 or rtcm3.x as seen from the picture above. I don’t think I can switch to legacy rtcm on hiper vr.
When you fix disappeared did your status say waiting for corrections or were you still receiving corrections but lost fix?
I’ve only received corrections for about a minute then it said waiting for corrections. So I’m more worried about the radios talking to each other. But maybe that’s why it talk because I’m sending to much data to the rs3
Also I don’t think I need to change any settings on my rs3 rover like disabling qzss and etc. right?
Thanks
Same behavior as here but bear in mind it still could be something else.
I would first see “Receiving corrections” and then the fix - with all looking good.
Then after about 20 to 30 seconds the fix would drop, and from then on only display “Waiting for corrections”. It would remain in that inconsistent state until rebooted.
Without making any other changes to anything, try simply rebooting the RS3 and see what that does.
If you are experiencing what I am describing, then changing the basic GNSS settings is not going to have an effect.
1 Like
Okay I was able to turn all constellations off except gps and broadcast over 12.5mHz but I could not receive corrections. If I switch to 25mHz I can receive but only like once every 10 sec. I turned on glonass and was able to get a quick fix. I think if I was able to receive 12.5mHz I would have a more reliable connection because of the less data transfer at 4800baud. I’ve tried restarting and changing settings but still couldn’t receive at 12.5mhz. I found that msm3 doesn’t work well for the rs3 I was not able to get a fix and it was 100ft off. Msm4 Or rtcm3.x options works good though.
I can try to dm @geo.henry on Emlid forums. I would need a subscription to dm him on linkedin.
Are you getting the 10 seconds from the Flow Status Overview “Age of corrections”?
One of the key problem indications I get is that this number will start to blow out as the number of SV’s approaches critical mass. In my case with less than 28 SV’s it happily updates around 1 sec, but with more SV’s the age starts to increase until things grind to a halt.
This is my base only broadcasting gps to my rs3 and it’s struggling to keep a connection. About every 10 sec the age resets
Best I got with that setup was a float
Can I ask what mHz you use? 12.5 or 25?
Seems @bernardo.barraza was able to get his topcon gr5 working with an rs3 via UHF to.
1 Like
I use 25kHz, it’s actually a better option to fit in more if you are using an older uncompressed protocol like TT450S.
With what you have happening with only 6 SV’s there is definitely something not right. The RS3 does initially receive some corrections so the basics must be in the ball park. But there is more going on, for example extra data that maybe the Topcon is sending and/or not being understood in the RS3 that then stops it in its tracks.
Did you try the “TrimTalk” setting?
Either way at this stage I would be sending a system report to Emlid so they can have a peek at what’s being reported internally. The logs are very extensive so provide some UTC times of example occurrences so they can zero in. You can see an example in my post that you linked above.
Reach_20250105201441.zip (530.9 KB)
I did record a log on the Emlid flow app while doing that test. Is that how you got your log info?
I did try the trimtalk and It performed the same as trimtalk tx. I’ll try Msm4 then rtcm 3.x option on trimtalk and trimtalk tx protocol and see what works best, but my results with msm4 and rtcm3.x has been the same so far. When I chose rtcm3.x I get an option to set a station iD, but I leave it unchecked, not sure if that helps.
Details here:
How to download Full system report | Reach RS2/RS2+
Hi conner2806,
I Used 25, bandwith in the Base Trimble R8 and Topcon.
In my base configuration I used 25kHz at 9600b. Also transmitting in RTCM3, not 3.2 nor 3.1, in your case it could be 3.x. By changing the configuration you could also use 12.5kHz at 4800b.
I use GPS and GLONASS because it is the only thing my base allows and I also activate the legacy messages in the RS3. For both brands I have used the same
1 Like