First I setup the docking station at one location and after that I created areas and passages.
Later I moved the docking station to another location.
Since then, yarbo was still able to enter the previously created areas.
Then I deleted the first position of the docking station from yarbos databse, because it was obsolete.
Now yarbo is unable to enter the areas I’ve created while the first docking station was active (Areas created with the new position of the docking station active - are fine). At the end of a passway before entering the area to mow, yarbo is driving forth and back a half a meter. But there is no error in the app.
When I drive yarbo into the area manually and the start the job, I get the error: yarbo is out of bound by 1,5 meters and i should drive it back.
Is it possible to fix this is the software, do I have to delete and recreate that unworking areas.
Everything else should stay – Areas, Settings, etc.
You will need to re-create the things have been removed. Start with your Pathways from the Docking Station to the Areas where you had them before, then get your Work Plans created and going again.
I asked the Developers why Work Plans are deleted if they contain an Area that you delete. I was told it’s to keep things tidy, why would you keep all this around? Delete a Work Plan with 10 items because one is no longer there? Not sure that’s a “feature,” but that’s the way it was done.
Thank you for reaching out. Are you able to successfully run the work plan now?
Since we could not locate your SN (Serial Number) information using your email address to review your map, we can only provide some general suggestions based on your current description.
You can try adjusting the “Exterior Area Shrink” setting to a higher value and see if the issue persists.
If the problem remains, we recommend submitting a support ticket with the serial number of your rover, a description of the issue, and the estimated timestamp when the problem occurred.
We appreciate your patience and understanding, and we are here to assist you!
@Ken I have the same problem as @lars Mine would go to the end of the pathway and just keep moving back and forth. I fixed it by moving the setting for boundary to +4 which I had at zero…is there anyway that you know of to get it back to 0? Thanks
Look on your map for small hooks or overlapped boundaries where you may have backed up during mapping or overlapped too small of an area for it to calculate a plan properly. Also look for pinched areas between no go zones and the boundary. If the river cannot navigate these areas due to restricted space, you may need to extend the NGZ and use dead ends to cut these areas
Ahhh…you are wise @bryan.wheeler Yes I do have " heart beat EKG" blip right where I started the area to map and where it finished the connection at the end. Couldn’t I redraw that little piece so it connects smoothly?
My experience says that when you restore your backup not all settings associated with the map are restored. Restore and verify settings. this bit me more than once.