Mowing Against Retaining wall

So I am mapping my mower perfectly against my retaining wall that is only one two blocks high, actually use it as a border around my septic and flowerbed areas. I map it within 4 inches of the all itself never hit the wall once. when i go to mow it always hits the wall and knocks out the brick on the top. mostly where it makes its turn an the end or the start. Then I have a no go zone around the retaining wall area also by the septic and it hits that one also. is there some guidelines how far to map the mower against the object?

From what I’ve read (and observed), Yarbo will twerk itself when turning to exceed the border and get into No-go Zones, my guess is its mapped border applies to where the antennae are, not the physical body. I have also seen Yarbo trying to get itself unstuck and drifting into a No-go Zone while snowblowing (and almost take out its antennae on my car’s tow hitch). I’ve seen Yarbo get too close to the GF’s camper with the snowblower, so I wound up making a bigger No-go Zone around it than what I had. Oh, right – I’ve had this happen myself with the snowblower – I mapped an Area, and during running it turned so the very rear of the tracks hit a cement stair. So I re-mapped a little smaller, and it’s been fine since.

So what do you do? Yeah, tough one. I guess we all have to stay aware of the turns. If mowing, keep your perimeters as straight as possible and free of turns, and have it do several perimeter passes. There’s the new feature to shrink (increase the “setback”) the Area a little to keep Yarbo away from the border you mapped, which is great if you’ve got plants there that like to spread and want the mower to stay back more and more over the season. And “expand” the area if you discover your border isn’t wide enough. I don’t know if any of that will help.

Have you been able to try the updated object detection yet as well? I don’t have the latest firmware yet – still waiting. I don’t know if that will begin to address the errant twerking you’ve seen.

2 Likes

I just got my updates yesterday. Will try that out soon, and I will also try to shrink the area like 4 inches and see if that helps.. Once i get the trimmer hopefully I can stay a little farther away and let it trim with its spring loaded arm and not let the main mower come that close. Luckily I dont have too many objects to get close to. I will test it out and get back to you all. who knows might help yet someone else out.. Thanks for the quick reply.

2 Likes

The reference point for mapping is the center of the core right between the two antennas. The path planning algorithm doesn’t seem to account for the module size and it seems to have very little regard for exceeding the bounds when backing and when avoiding. It’s unclear why. It should never drive over a mapped area line. Ever. This is a basic function that should be expected to work flawlessly with a few exceptions and that is poor GPS signal when in float mode. This is where the “safety buffers” they built in should help prevent this and where vision will ultimately help as well. But whenever I see it do it, perfect GPS, HDOP, everything and you can watch it do it in the app. It knows it’s doing it. So, like you, I’ve had to work around it and make sure I leave even more buffer. It’s not ideal and I really hope they get this figured out soon. I see improvements in each release. It’s really, really trying not to exceed the area lines now. It’s still not perfect though.

2 Likes

@bryan.wheeler - Breaks me 'eart seeing the videos and aftermath of an errant Yarbo. It’s not funny, given the damage caused, even if it’s just a $7 light or something. Spot on with your comments here, Bryan.

I’ve finally messed about a little with vision with my mower the latest FW (my first real tries with the mower), leaving it at the default setting of Moderate Bypass. It will map out obstacles and draw them with red splotches on the map, but it seems to get a little too cautious and goes way out around these obstacles. It avoids narrow gaps where I drew the map. It also seems to get confused by different soil/grass/shadow colors. A straight white fence I mapped in parallel had it get close, then go waaayyyy far away from it and then back in an arc. I set it to Gentle Contact, and it went straight by the fence as it really should.

So I may keep Moderate Bypass in Areas where I’m confident it’ll “find” its own no-go zones with vision and not veer away too much, but it’ll be mostly Gentle Contact for now until more improvements come to vision.

Seeing the red blotches appear on the map with the vision was kinda cool, though.

1 Like

It’s got a lot of potential but yeah I am gentle contact for most of my areas for now. I got one that has a few trees, a sewer clean out and a coax pedestal. The old avoidance handled that really well. The new one is missing a lot on my perimeter and when it’s avoiding. Looking forward to Yarbo getting that dialed in.

We suggest leaving a 30cm buffer zone around the retaining wall. Additionally, in the recent update, we’ve added an option to choose whether to mow the perimeter of no-go zones. You can now select not to mow in those areas. We hope this helps resolve your issue. Feel free to reach out if you have any more questions!

1 Like