Failed Jump
- Thread starter Jim Frame
- Start date
From one epochs cluster to another. It could be that RTK epochs create new cluster which is not currently selected cluster. And there are criteria when we should re-select current cluster.
Jim Frame
Well-Known Member
At my "problem child" today I had 15 groups and on the first try wasn't able to complete the shot per the profile parameters. I observed for probably half an hour, but never got the DPOS notification. Is the DPOS timer tired to the current group rather than the time observed?
DPOS timer should be tired to GNSS file recording time.
Nate The Surveyor
Well-Known Member
Jim, I've got my DPOS set for maximum time. So that it's always recording, parallel with rtk. Boundary Profile. I can't remember the settings, but that's what it does.
Duane Frymire
Active Member
In the profile, under "what to record", you can check "raw data" and change from internal memory to sd card. It will then have a dpos file on every shot for the entire time on point. But, make sure you still have the timer set to some number (I use 5 minutes) rather than "never". If you check never it seems to override the other setting and not record data.
I've had failed jumps on long sessions and it usually eventually returns to the group that was good for 20-30 minutes and finally solves. Particularly bad area due to some sort of interference, it kept going back to brown and kept failing so I eventually manually accepted:
the red and brown seem to be near but not within the 0.13' I have set. Would be useful if I could tell how far apart these solutions really are. Anyone know how to do that while still collecting on the point?
Nate The Surveyor
Well-Known Member
I don't know the answer to your question....
But, I have a solution.
Open it up to 0.25' horiz and 0.3 vert.
What is, is both brown, and green are one group, maybe 0.35' ida. Your 0.13 is dividing it into 2 groups. The real coord may be on the border between the 2 group's. Opening it up, would allow it to treat this high rms shot, as one point.
I know that's not what you asked. But, it could help. Also, going back through the screenshots, will tell you a bit about the 2 group's, (this is more in keeping with your question). You may see that the ppk coord agrees with this average of the 2 groups.
I did open mine up a little, and it did solve the "jumping back and forth between 2 close group's, that are in fact one group.
Nate
But, I have a solution.
Open it up to 0.25' horiz and 0.3 vert.
What is, is both brown, and green are one group, maybe 0.35' ida. Your 0.13 is dividing it into 2 groups. The real coord may be on the border between the 2 group's. Opening it up, would allow it to treat this high rms shot, as one point.
I know that's not what you asked. But, it could help. Also, going back through the screenshots, will tell you a bit about the 2 group's, (this is more in keeping with your question). You may see that the ppk coord agrees with this average of the 2 groups.
I did open mine up a little, and it did solve the "jumping back and forth between 2 close group's, that are in fact one group.
Nate
Duane Frymire
Active Member
Not a bad idea to open it up. But I do like longer occupation for a ppk on these type of shots. 25 minute ppk was 0.10'N, 0.03'E, 0.05'up. Opening it up on rtk I might not have gone past the 20 minute mark ppk, which I think is kind of the sweet spot for ppk.
In this case I'm going to go back and check with tape between some found rebar. I'm finding half foot error in 40' from others work (or mine). Conventional requires measuring up almost a sheer cliff and gnss requires dealing with the interference (i think from communications towers). I'm confident the JAVAD is correct as usual, but haven't run into this magnitude of interference before (maybe some spoofing going on?).
This is not true. I have mine set to never, but have recording of raw GNSS set explicitly, so I do not get the DPOS timer or notification. It's always recording raw data whether 12 seconds or 12 minutes.
Duane Frymire
Active Member
I had a customer who wasn't getting raw data, so I changed that setting and it worked.
This setting is specific to the action profile, so if the action profile is changed, then the behavior may change as well if the subsequent profile isn't set the same.