This is not the first time when Yarbo is scraping walls, fences and branches while maneuvering - basically crossing the No-Go zone or perimeter zone boundaries, which should not happen at all!
Today Yarbo knocked himself out by crashing into water tank and pressing emergency button.
My area settings are set for 3 cm buffer for ngz, but what I expect that yarbo will mimic my ngz drawing perimeter with 3cm extra gap from original perimeter and the zig-zag operations shold respect the ngz / area perimeters and take into account its own dimensions.
As @rgloverii mentioned, please submit a support ticket and include the estimated timestamp of when the issue occurred. Our team will further investigate the matter.
And you all know where are the cutting discs located under the mower head. And the ngz border is right near the rock. So some good 10 - 15 cm inside NGZ with it’s mower head.
My observation/assumption is that yarbo’s position is basically the position of it’s core center - orange flashing light.
When mapping the NGZ, or area border, we usually map them alongside the object, zone, flower bed etc. etc. And then the position in that case will be the distance from orange light to the side of the rover in case I drive yarbo right along the flowerbed.
In case I set for example 0 cm buffer for ngz and yarbo is approaching NGZ not in parallel, but perpendicularly, the distance from orange light to back of yarbo is bigger than to side and to front is even bigger with mower module. So it looks like Yarbo thinks it’s ok as far as yellow flashing light do not cross the mapped ngz border … but forgets that yarbo’s hardware will cross that border if the orientation will not be parallel to the NGZ.
The center between to 2 antennas seems to be the ploting point for yarbo. It isnt until just recently that my unit has been getting close to crossing g NGZs and this morning it happened. Got stranded on my septic tank lid causing damage. Dont know to what extent yet.
This wasnt always the case, it used to respect NGZs. I also started having issues with Yarbo going into NGZs.
The other issue is that it has no idea where its rear end is when the trimmer is attached. The other day it took out two downspouts on my house. There are NGZs around them, which it honored but when it was adjusting itself it backed into them with the trimmer and snapped the mounts and pulled them out from the roofline.
I don’t have a complex yard, and I have scratches to bare metal on my back brace mount. I will not run a mow area with the trimmer on, as I know something is going to go wrong.
I stand by this, yarbo needs to rethink it’s software, and it’s team working on it.
The only time I think this is fine is when it is mowing the NGZ edge AS MAPPED. After that, it should NEVER cross the boundaries. Either NGZ or perimeter. Just too may unknowns as it was mapped from a side profile, not a front or rear one. This is my opinion of course, not what it actually does. But I believe you are correct, it thinks it can go half a core length over the line because that is how it was “mapped”. Not good.
I agree. I felt it was too generous before with NGZ in past iterations of the firmware. Did Yarbo change its dimensions? I’m in the process of mapping a new property with the MP1 (maiden voyage) so I’m interested to see if my YARBO too is infected.
Ngz perimeter lap is not causing any issue as yarbo is basically doing the same route I did when drawing ngz. Issue is when yarbo is doing the area zig-zags and gets too close to ngz.
Previously it was better. A dirty fix could be introducing 2 ngz perimeter laps. That could cover the yarbo length miscalculations.
Btw - i’m wondering where the route calculation logic sits and where the route calculation happens. Is it locally on phone app or it’s done somewhere on Yarbo’s cloud servers?
Technically route calculation should be easy and quick fix.not requiring any firmware updates etc.
Thanks for the update and for sharing your ticket number. I checked your case, and it has already been assigned to one of our specialists for further investigation. I’ll also pass your feedback regarding the NGZ issue along to our team. Thank you for taking the time to share your observations.
