Patrick Garner
Active Member
Thanks, Darren. This is a daily learning experience. Great explanation. 
Locating resource areas (top bank of river etc)
- Thread starter Patrick Garner
- Start date
I often reset RTK if I am just tooling around without verification on. Most of the time when using verification I let my LS run thru the paces without much input from me. Every now and then if I get in a hurry and don't want to wait till the end I will use reset RTK instead of waiting for the shot to completely finish. I only do that if I am certain about the fix it's using and that enough time has passed.
Patrick Garner
Active Member
Slowly understanding! Thnx.
In addition t reset RTK, we have a command named Reset Tracking. It is found on the RTK V6 screen. It is automatically triggered whenever the LS has not obtained a fix in a preset value of time.
The setting for this is in General Setup/Advanced/RTK-DGPS...Reset Tracking After. I use a value of 30 seconds. The default is much too long for my taste.
If I am doing topo in the woods, I am manually pressing Reset Tracking about three seconds prior to reaching my destination. The highest likelihood of a fix begins 10 seconds after reset tracking is executed.
One more tip...which would take a bit to explain...but if during phase 2, you see a single engine fix, and 15 or 20 seconds passes, and no other engines fix, press reset RTK. If the first engine that fixes during phase 2 is a bad fix, the following good fixes will not match, and you are kind of stuck until the bad fix is rejected. Just give it a little kick with Reset RTK.
The setting for this is in General Setup/Advanced/RTK-DGPS...Reset Tracking After. I use a value of 30 seconds. The default is much too long for my taste.
If I am doing topo in the woods, I am manually pressing Reset Tracking about three seconds prior to reaching my destination. The highest likelihood of a fix begins 10 seconds after reset tracking is executed.
One more tip...which would take a bit to explain...but if during phase 2, you see a single engine fix, and 15 or 20 seconds passes, and no other engines fix, press reset RTK. If the first engine that fixes during phase 2 is a bad fix, the following good fixes will not match, and you are kind of stuck until the bad fix is rejected. Just give it a little kick with Reset RTK.
Darren,
I like your description of "soft settings". I use "soft settings" on most everything. I am one of the few that sees no problem with rather relaxed settings, repeated enough so that I have the level of confidence required. I often let the LS run unattended while I scour the area. I am not disappointed when I return 5 or 10 minutes later and see that I got 10 shots within a 0.1 foot radius, and one is 6.5 feet away.
I think the LS gives us 23 ways to be sure of a measurement.
In thinking about this thread I tried a new profile today. It's set for a confidence of 2 with a minimum phase 1 duration of 130 seconds. No validate, 1 epoch, no consistency counter. This forces the LS to get at least two fixes that agree with a minimum time between the two fixes of 130 seconds. I've also changed my reset tracking time to 30 seconds per John's advice. I also changed the confidence guard from the defaults to 0.2' and 0.3'. Extra epochs are unimportant when you just want to prove that your fix is good. With this setting you may still get a lot of epochs if the engines can repeat the fix fairly easily.
Darren Clemons
Well-Known Member
Thanks for reminding me about changing the default setting on reset tracking...I do this manually quite a bit and this will (as so, so many thing in the LS will), do it for me if I just set it up correctly.
What you describe about that "one engine fix" in phase 2 if what I was referring to earlier about it "bogging down". Once it does this, it may very well sit in this state for several minutes, but a quick reset RTK may get you back clicking away with epochs matching your phase 1 within seconds (as you say above about 10 seconds).
The LS is an unbelievable machine and will almost always get you your shot going through its three phase protocol and, as you also say, the wonderful thing is you can wander around looking ahead and such while it works. That being said, with all we're discussing here, a shot that sometimes may take 15 to 20 minutes can sometimes be shortened to 3 to 5 minutes with the proper understanding of what the LS is doing and watching, as John also said, the "23 ways" the LS gives us to be sure of a measurement.
Darren Clemons
Well-Known Member
I like this..
. Think I'll give it a try. This will accomplish what we're looking for in some areas, two pops at least 120 seconds apart. What do you have on "how to stop"? Still use minimum duration of 120+ seconds since by setting phase one to last a minimum of 130 it will be past that?
I have is set to Stop After 1 epoch. Minimum duration is off. This setup only requires the LS to get 2 fixes 130 seconds apart. I started with 130 because I have seen bad fixes repeat at 126 seconds. Never longer though. It's really close to that 126 though, so I might recommend upping it. I'd probably go for 180 to be certain. In the open, you'd have a lot of epochs because the engines could repeat the fix quickly, but the shot would not end until a fix is acquired after 130 seconds. I also have recording raw data on for this profile so I can DPOS later. It's likely in canopy that the shot will take longer than 130 seconds unless the LS happens to gets the right fix when the start button is pressed and manages to repeat it fairly quickly after 130 seconds.
Patrick Garner
Active Member
Would it be helpful to have a White Box "Reset Engines" option? Then the user would never have to leave the Collect screen.
Patrick Garner
Active Member
Adam, brilliant. 5 stars, sir.
Just added that feature to U4.
Just added that feature to U4.
Last edited:
Clifton Keith
Active Member
U4 works good for reset RTK.