LS+ w/ T3 Best Practices

avoidthelloyd

Active Member
What are your best practices for using this setup in mature pine during wet conditions where you need to take thousands of topo shots? Asking for a friend. Haha.

I've had poor performance over the past week in canopy (even with moderate sky). What would you do to help topo a 2.8 mile road through the pine woods?

LS+ Settings? Upgrades? Attachments? Custom stuff? Thanks!
 

Adam

Well-Known Member
5PLS
Well, it takes time to get a verified location. It's perfect for most everything except topo in thick heavy woods when there is a lot of terrain and detail. This is one of the only times I will usually set control and make sure the robot batteries are charged up.
 
I would agree with Adam. The math makes sense for 0.01 second verified shots one after another with a good robot is quicker than taking the time to verify each shot in tough situations. Last year I had 10,000 feet of creek topo in a deep ravine in very woolly country and did all of the topo shots with a robot because it was a very bad GNSS environment and I would still be doing it if I were using my beloved LS.
 

APADDEN07

Member
Any best practices in general would be helpful.

I'm still using a profile with 1-engine only fixes because for a long time the software just wouldn't allow a 2 engine fix unless I was in a wide open field and could still see the base.

It's been working, so I haven't changed anything, but with the constant stream of updates its tough to know whether or not I should be changing anything with each new release. The patch notes are nice, but they don't really tell the whole story with each update.

As for work in thick pine canopy, my only limiting factors have been tons, tons, tons, of sky for the base, and radio reception. If you can get those two, you should be in good shape. I recently marked 4 miles of line through dense side sloping wilderness and just kept leapfrogging the base ahead. For sure you could tell when you had quality sky and radio topography (2400+' from the base and still getting good readings with 4 guys pushing blazes and paint behind me) vs 800' with an unlucky move to the wrong rock ledge.
 

Matt Johnson

Well-Known Member
5PLS
In the PreRelease version there are new Variety + RTPK profiles that I have developed and tested. They are designed to always give a good solution any require the user to only press the Start button and then wait for accept to be displayed. I am working on documentation to explain the Variety and RTPK settings that I want to publish when it is moved to the Release branch.

For the Variety + RTPK High Confidence profile my goal was to have it be on the level of reliability so that it gives a bad solution less than 1 in a 1,000,000 times. The Variety + RTPK Topo is designed to be quicker and on a reliability only giving a bad solution of at least 1 in a 100,000.
 
Last edited:

Phillip Lancaster

Active Member
In the PreRelease version there are new Variety + RTPK profiles that I have developed and tested. They are designed to always give a good solution any require the user to only press the Start button and then wait for accept to be displayed. I am working on documentation to explain the Variety and RTPK settings that I want to publish when it is moved to the Release branch.

For the Variety + RTPK High Confidence profile my goal was to have it be on the level of reliability so that it gives a bad solution less than 1 in a 1,000,000 times. The Variety + RTPK Topo is designed to be quicker and on a reliability only giving a bad solution of at least 1 in a 100,000.
What's the Variety set at on HC vs Variety on Topo?
 

APADDEN07

Member
How stable is the current pre-release/ when will this be implemented in a release version? I tried the new pre-release version about a month ago and the performance was so bad I went to the release version, which I haven't had to do since we got the LS+.
 

Matt Johnson

Well-Known Member
5PLS
There haven’t been any stability issues that cause crashes in PreRelease versions for a long time from what I can remember. If a build is found not to be stable then it isn’t moved to PreRelease. There has been some refactoring of the communication settings in the past which required some settings needing to be changed in PreRelease in the past.

The plan is to move it to Release very soon.
 
Top