Patrick Garner
Active Member
Thanks, Darren. This is a daily learning experience. Great explanation.
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.Adam and John, when using profiles such as this, would you recommend, as John states above, doing a reset RTK and immediately hitting start again, then use distance to last to hopefully gain additional confidence? With these somewhat "soft" settings hopefully it would give me another couple of clicks quickly.
Again, dist to last is the greatest button there is here. As long as you are certain on you're first shot, then keep up with the approx. horizontal and especially vertical and you can most times tell very quickly what's good and what's not. We also do exactly as John describes with "estimating" the next shot. I did a massively deep dark creek meander last week this way. I actually spent more time than I probably had to by having my settings a bit too high for that type of shot and was glad to see Pat start this thread to read what others were doing on these areas.
when using profiles such as this, would you recommend, as John states above, doing a reset RTK and immediately hitting start again, then use distance to last to hopefully gain additional confidence? With these somewhat "soft" settings hopefully it would give me another couple of clicks quickly.
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.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.
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.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.