Six fixed engines in bad locations is difficult to achieve. Using the default Boundary Action profile is what I would recommend. You can increase the minimum duration for more protection from bad fixes.
New Guy dumb question #1
- Thread starter jahalnon
- Start date
Six fixed engines in bad locations is difficult to achieve. Using the default Boundary Action profile is what I would recommend. You can increase the minimum duration for more protection from bad fixes.
Many places I work 1 engine is about all your going to get. I stay on point 240 seconds and repeat the observation and rely on PPK sometimes completely on PPK. I spent 5 - 10 minutes on every shot I took today and a good number of them wouldn't finish phase 1. Part of what I worked on was a creek with steep mountains rising up from it covered in mountain laurel. Traversing alone would have been hell so I wait for the LS to do it's thing. Time is it's friend.
Darren Clemons
Well-Known Member
I agree with both Matt and Adam here. The default boundary action profile is very good for most locations. That being said, in places like what Adam describes, where one is all you can get, the LS can and very often will get a good solution. The PPK will, if given enough time and with probably at least 2 different PPK session will then "validate" to you, the user that you have a good coordinate.
The LS and it's many, many adjustable settings is all about the user getting a "feel" for what it's doing and setting up your own personal profile accordingly. Matt is correct in that when in canopy the LS will almost never attain a full 6 engine fix, but that's not necessarily needed to get good tight reliable data. From our 2 years of use, the engines are, for the most part, weighted from #1 (the quickest and usually first to fix) to #6 (the last and most difficult to fix). Now, most times in the woods and under canopy, when we are collecting a point, we see between 2 and 4 engines fixed. It will most always include engine #1, but the other one to three that it will be using will be a mixture of engines 2 through 6.
Bottom line is, if your profile is set to collect for a minimum of 180 to 240 seconds and the LS completes all three phases of the RTK process, you can almost bet your last dollar you will have a good coordinate.
Again, that being said, we've had a ton of points, as Adam describes, that just won't finish either phase 2, or most likely the phase 3 validation. Still there's a very good chance you have a good coordinate here, it just depends on the data stored up to the point where you "stop" and store the point. If there's more than 240 seconds of separation between the epochs in the group it's an extremely high probability the shot is good.
I've stopped and stored these many times. After I do, I always "reset engines" while still on the point, hit start again and watch the "distance to last" white box and as soon as I get a few epochs that give me 0.03'/0.05' kind of numbers, I know the last shot was good. Then, usually having a PPK point collected, process that back at the office and most likely will get another good check.
The LS and it's many, many adjustable settings is all about the user getting a "feel" for what it's doing and setting up your own personal profile accordingly. Matt is correct in that when in canopy the LS will almost never attain a full 6 engine fix, but that's not necessarily needed to get good tight reliable data. From our 2 years of use, the engines are, for the most part, weighted from #1 (the quickest and usually first to fix) to #6 (the last and most difficult to fix). Now, most times in the woods and under canopy, when we are collecting a point, we see between 2 and 4 engines fixed. It will most always include engine #1, but the other one to three that it will be using will be a mixture of engines 2 through 6.
Bottom line is, if your profile is set to collect for a minimum of 180 to 240 seconds and the LS completes all three phases of the RTK process, you can almost bet your last dollar you will have a good coordinate.
Again, that being said, we've had a ton of points, as Adam describes, that just won't finish either phase 2, or most likely the phase 3 validation. Still there's a very good chance you have a good coordinate here, it just depends on the data stored up to the point where you "stop" and store the point. If there's more than 240 seconds of separation between the epochs in the group it's an extremely high probability the shot is good.
I've stopped and stored these many times. After I do, I always "reset engines" while still on the point, hit start again and watch the "distance to last" white box and as soon as I get a few epochs that give me 0.03'/0.05' kind of numbers, I know the last shot was good. Then, usually having a PPK point collected, process that back at the office and most likely will get another good check.
I'm beginning to understand the min duration being set higher and the Boundary Action Profile setup. I used the BAP on 2 very difficult points today and repeated same twice with good results for the RTK solution. The dpos sent for both of these were not long enough in time to get an agreeable solution.
I now understand the only benefit of my 6/6:6 set up was not for the RTK solution, but that it "forced" a long duration of collecting for dpos. Which did get me agreeable solutions for the 2 points today.
So if I understand this a little better now, the BAP as Matt highlighted, if allowed to get a thumbs up "Accept" should be a good RTK shot with all 3 phases completed as Darren mentions?
I now understand the only benefit of my 6/6:6 set up was not for the RTK solution, but that it "forced" a long duration of collecting for dpos. Which did get me agreeable solutions for the 2 points today.
So if I understand this a little better now, the BAP as Matt highlighted, if allowed to get a thumbs up "Accept" should be a good RTK shot with all 3 phases completed as Darren mentions?
You can also stop with stop button and take full control of duration. You lose validate at the end, but you can do it manually by resetting engines and waiting for a new fix that adds epochs to the overall average (which tells you that the new fix agrees with the average). Then stop and accept.
Nate The Surveyor
Well-Known Member
I set my U1 button to reset, as Shawn said above.... This makes it fast.
Patrick Garner
Active Member
Great thread.