Is there a limit to the survey in time ? - mine as been sat at 259200 for a couple of days - I’ve been away so set the accuracy to .01 and left it running for what was probably a couple of weeks … it’s currently showing accuracy achieved of 0.0102 but the
duration and observations number hasn’t changed for a few days.
0.0102 is perfectly acceptable but I’m curious as to why the process hasn’t completed.
Any pointers would be great.
So I’ve now hit the “save current position” button but no coordinates have been populated in the lat/long fields. I’ve done this process previously with much reduced accuracy and the fields do get populated, so I’m confident the hardware is fine - and I’ve had a RTK fixed rover running around the fields, within the limits of a previous quick 0.5m survey that completed successfully.
I’ve now restarted the survey in process with a 0.02m accuracy target but it’s looking like it’ll take weeks to complete.
Am I expecting too much by aiming to achieve 0.01m survey results from a Here4 ?
After a couple of hours, it’s as good as it’s gonna get, and a self-survey it’s really only globally accurate to ~1.5m anyway despite the reported std dev. I’d say 24 hours is the most you should bother suffering.
But as long as you use the same coordinates each time you power the base station (easily done by saving the configuration to flash), you get repeatable accuracy and precision to the centimeter level.
Stopping the survey should’ve started fixed mode at the last surveyed spot (despite not completing on its own), but that’s all lost now…
Thank you Yuri, I really appreciate your input.
Having lost the previous weeks of surveying in I’ve since restarted it with SurveyIn Acc set to 0.04 thinking that might complete fairly quickly, but it hasn’t stopped surveying and is now showing Current Acc = 0.03xyz and still showing as invalid, so i’m now curious when it’ll decide to end the survey and show a valid position - I’ve a feeling if I hit the use current position option I’ll not get the lat/long boxes populated as before.
I’ll likely just set SurveyIn Acc to 0.5 which will hopefully result in a valid position within a reasonable period if the current survey doesn’t finalise.
I’ve noted your comments elsewhere about Here4s not being ideal for implementing GPS yaw, but I’ve not seen your reasoning behind your comments. I’m now pondering adding another Here4 so I’m pondering if I should be looking at an alternative to the Here4 ?
Thanks for inspiring my current mower project, I’ve lost count of how many times I’ve watched your excellent videos, I appreciate your knowledge and your willingness to share.
This is outdated advice. They are fine for that application after CubePilot made some improvements.
Thank you, I appreciate your reply.
