LS as a network rover?

Shawn Billings

Shawn Billings
5PLS
Create a General Profile for RTN. Create an RTN profile inside the General profile with the IP address and password for the corrections.
 

Matt Johnson

Well-Known Member
5PLS
See Appendix A in the Quick Start Guide.

1543417568389.png




1543417603538.png
 

Duane Frymire

Active Member
On related note, is there any reason I would need to use a different coordinate conversion to state plane in the collect screen when using rtn v base/rover? I set up to use VT rtn (trimble version) and picked NAD83(2011) for reference frame (same as when using base). Using base/rover I hit known points in VT state plane, but switching to rtn I get 3.5 feet difference.
The coordinate system I have the page set to is HTDP WGS84(ITRF2008) to NAD83(2011)/NAVD 88/SPCS83. Seems like a double correction, but why does it give me double correction on one and not the other when both base reference frames are the same?
 

Matt Johnson

Well-Known Member
5PLS
It sounds like you have the wrong reference frame selected for the RTN profile. This RTN may be broadcasting WGS84 coordinates instead of NAD83.
 

Duane Frymire

Active Member
It sounds like you have the wrong reference frame selected for the RTN profile. This RTN may be broadcasting WGS84 coordinates instead of NAD83.
that's what I'm thinking. Yet VT rtn specifically says it's reference frame is NAD83. I looked at my MN profile and I've set that to WGS84 a few years back (also a trimble network). Are all the Trimble rtn's broadcasting WGS84 while stating their reference frame is NAD83? The Leica rtn in NY states NAD83 and that's what I set the profile reference frame to. Seems to be different definitions of reference frame going on that could cause problems.
 

Mark O'Hara

New Member
On related note, is there any reason I would need to use a different coordinate conversion to state plane in the collect screen when using rtn v base/rover? I set up to use VT rtn (trimble version) and picked NAD83(2011) for reference frame (same as when using base). Using base/rover I hit known points in VT state plane, but switching to rtn I get 3.5 feet difference.
The coordinate system I have the page set to is HTDP WGS84(ITRF2008) to NAD83(2011)/NAVD 88/SPCS83. Seems like a double correction, but why does it give me double correction on one and not the other when both base reference frames are the same?
Could it be one is US foot, the other is International foot?

I have the latest software update on this LS+ I just bought off someone. It doesn't have this screen circled. Is network RTK an option I need to pay extra for?
 

Attachments

  • RTK don't have.jpg
    RTK don't have.jpg
    315.2 KB · Views: 123

Mark O'Hara

New Member
Setup for corrections is under the RTCM icon on the Home Screen now.
Thank you! I didn't have the RTCM icon b/c it was set as default to radio corrections. Now that I changed it to Wireless LAN, I think I should be all set. Spent 4 or 5 hours trying to find that setting. No instructions in the manual, and nothing online through either videos or online manuals. With more and more people going to RTN correction streams, it might be something Javad may want to address for other future users.

I appreciate your help tremendously!
 

Mark O'Hara

New Member
Thanks Matt. Got it working, but not getting the results I was expecting (barely fixed position). Got to be something not maximizing my settings. I've tried faster sampling rates. I'm using RTCM3MSM_IMAX under 50% open sky cover and the nearest CORS station is only 1.3 miles away.
 

Attachments

  • Javad-rtk results.jpg
    Javad-rtk results.jpg
    456.7 KB · Views: 151

Duane Frymire

Active Member
Thanks Matt. Got it working, but not getting the results I was expecting (barely fixed position). Got to be something not maximizing my settings. I've tried faster sampling rates. I'm using RTCM3MSM_IMAX under 50% open sky cover and the nearest CORS station is only 1.3 miles away.
Lots of variables to good performance, but one thing to try is using single base when within 5 miles of CORS. There's a "nearest" option or you can pick individual stations.
 

nusouthsc

Active Member
Maybe just a bad day? Or possibly try a different mount point? Despair not, it will perform as your are expecting. Possibly have someone look through your settings on RAMS.
 

Mark O'Hara

New Member
Quick update. I was in my backyard which has about a 30% opening, but usually I can get a quick fix 90% of the time with my other rover. But it wasn't set up in the same location(closer to a fence on top of a 4' retaining wall. Once I moved it to my regular spot, I got a couple fixes. My other rover also likes to exaggerate the accuracy while the precision is usually off. I think the LS doesn't play that game. Which I appreciate. I also took both rover heads on a field trip out to a site and along the drive observed the rate of a time to fix/hold and noticed they both did pretty well. It was only about a mile drive, but I plan on doing some more testing. Just haven't had the chance.

Quick question. My state (Massachusetts) has it's own public CORS network. The nearest station is 1.3 miles away, the other nearest CORS stations are about 20 miles away (I'm within the green triangle on the MATB station. 90% of my work is within 3 miles of it. I've always gone with network corrections, but was wondering if a single baseline might produce better results? I think I'm splitting hairs, but figured I'd ask.

Thanks for the help guys!
 

Attachments

  • MaCORS_RTN_2023_Map.jpg
    MaCORS_RTN_2023_Map.jpg
    1 MB · Views: 118

TonyC

Member
My experience so far is that the LS+ works a lot better using UHF corrections from a base than cellular from a RTN.
When running side by side with my Hiper VR. The Hiper VR outperforms the LS+ using the same cellular correction, but the LS+ outperforms the Hiper VR when using UHF from the same base.
 
Last edited:

giulio

Member
Maybe you're right, I too have difficulty connecting to cors RTN, in the video I am attaching you can see how to go from 24 +6 satellites to 6+12, and in the "statusbar-satellites" screen the satellite navigation status codes jump from ( 51-55) at 20 edi the fixing despite having galileo and beidou does not occur, although showing an RTN-Rover connection without apparent problems (LQ: 100%, delay: 1 sec) (Rate: 1.Hz, Latency: 0.1sec) (Received: 100%, Lost:0) I can only get good solutions with the T3s as a basis, but now I'll have to return them and therefore I too would like to solve the RTN connection problem.
 
Top