Base Station Components:
Trimble Zephyr 3 Antenna
Trimble Alloy Receiver
Trimble TDL 450H
Settings:
TDL450H is set to broadcast at 35W
Serial Baud - 38400
Radio Link Rate - 9600
Data Protocol - TRIMTALK 450S
Frequency - 440.5 MHz
Radio Mode - Base/Rover (should work both TX and RX)
The RS3 is just stuck on waiting for corrections. I am using the correct antenna, I’ve set the correction source as via UHF at 440.5 MHz. Firmware is 32.2.
I am working with Emlid for suggestions, however we haven’t come to a solution yet. Anyone use a TDL450H to broadcast corrections and receive the corrections on their RS3?
Before creating a new thread, please refer to the docs for Reach RS3 or Support tips category of this forum.
In case you are creating a thread about an issue, please specify the appropriate sub-category first!
I’m using two very similar configs with my RS3’s that work - not ideally - but they do work:
NetR9 + Zephyr 3 and an ADL Vantage which is the smaller brother of the TDL450H (TDL450H is a Trimble rebadge of the Pacific Crest ADL Vantage 35)
NetR5 + Zephyr 2 and PDL4535 (Trimble rebadge this as the HPB450)
To give you some confidence on this the code and settings between the ADL Vantage & TDL450H are identical, for example I can use the Trimble PDL450 PDLCONF software to also configure the ADL Vantage fine.
Have you confirmed the TDL450 is actually transmitting? Apart from the superficial LED indications, best check is with a cheap configurable UHF radio like a Baofeng UV-5R or similar.
Do you get any initial indications in the RS3 that you received corrections? Or at any point intermittently afterwards?
In the absence of more information at this stage my guess would be the issue is most likely your Alloy settings. How have you configured the I/O port? My optimized settings from the NetR9 that work for me are below.
Now the caveat: this next bit may not be your immediate problem, but you are likely to eventually encounter this and need to throttle the data from the Alloy. The RS3 can choke up with internal TT450S parser crashes.
Emlid may be able to provide a progress update here?
The quick and dirty workaround is to simply limit constellations, but with your Alloy a much better option is to configure a bandwidth limit bytes/second. It should behave the same as the NetR9 in this regard and intelligently select the optimum SV’s to squeeze in. On the Alloy you may not see the bandwith limit configuration option until you select RTCM3.
Thank you so much for the write-up, this is awesome information.
I have confirmed the TDL450 is transmitting, I use that base station with a Trimble R10 rover. Which was working correctly at the time of testing.
No initial indications in the RS3 that any corrections were received. I’ve let it run for extended periods and still have yet to receive corrections.
I have updated the COM port settings on the Alloy to match what I have set on the TDL450. I will take a look at the settings through the web interface and compare them with yours next time I’m on site. I am hesitant as I don’t want to end up in a situation where I optimize for Emlid equipment and compromise the use of my Trimble equipment, which is more predominantly used on-site.
Thanks for the clearer picture, given the stream is completely broken it’s looking more likely the I/O port settings. Look carefully at the MSM selection.
And in this case don’t set the bandwidth limit first up. Only do this as a second step if you experience problems later. You just want to have both devices receiving first, fingers crossed they coexist.
If you do need to throttle later for the RS3, you may still be ok with the R10 if you are in good open conditions. If you are in a difficult environment where every SV counts you may not be so lucky. I struggle in places where the bandwidth of Lora & NTRIP will work fine (but are often out of range).
Also don’t overlook that you have a second serial port that you could set up as a separate parallel stream for the RS3 if you were really keen…and had another radio and frequency/license etc.
Before experimenting with I/O port settings take a screen shot and/or save your currently working settings into an “application file” via Receiver Configuration - Application Files. Save it into the receiver and also your laptop as a backup. It’s easy to quickly recover if you dig yourself into a hole.
Just an update on this thread: we’re in touch with @manpreet.gill via email and are still looking into the issue. I’d encourage you to continue the discussion with users who have experience with this setup. Hopefully, we’ll find a solution soon!
