I apologize for the confusion caused by the earlier answer. You can refill the spools! I’ve updated the information now to reflect this, and I appreciate you bringing it to our attention. Thank you for your interest in the Yarbo mower + trimmer—it’s designed to be a great lawn helper, and we hope it meets your expectations!
2 Likes
Currently, as Bryan mentioned, the safety buffer is in place to ensure safe operation. For more precise trimming, we’re developing a dedicated software system that will allow the trimmer to handle tasks smoothly and efficiently.
1 Like
@Yarbo-Forum - If you are artificially enforcing buffers, as was done with No-go Zones several FW releases back, people are just going to re-map. What will happen when Yarbo removes those setbacks/buffers?
I expect Yarbo to follow the map I set – period. No buffers. No going into No-go Zones. No exceeding Area boundaries. That needs to be the baseline expectation for this machine. From there we can have documented cautions, recommendations, and best practices, and we can create tutorials. Any other behavior of an automated machine of this size and power is not acceptable.
I understand that these cautionary buffers are likely done to prevent phone calls, but actually correcting the problems is the right way to go. If I make a mistake mapping or with a No-go Zone (and I do!), I’ll own it. If Yarbo backs up into my Arborvitae…again…that’s on Yarbo, as that type of thing should NEVER happen with a production release in customer hands.
5 Likes
For NG zones I can’t get closer than 8" no matter how I map. I tired CW and CCW mapping with treads tight to edge of the obstruction. The resulting cut is always 8-12" way. I’d be thrilled with 4".
1 Like
NGZ’s are at 30cm
1 Like
Completely agree Ken! People are going to work around these limitations and when things change from a firmware update, bad things can happen.
2 Likes
30cm, well that explains a lot. Was this documented somewhere that I missed? Although that wouldn’t be a great selling point.
I fully agree with @bryan.wheeler. People are playing games by mapping into NG zones and dropping smaller templates in. If and when they fix the excessive setback, it’ll be trampling over all sorts of the things with existing maps.
2 Likes
I think it was alluded to in some of the release notes. I don’t know that it is specifically documented anywhere.
1 Like
I’d have to look that up. Expand the boundary by 4 inches. Then when the next update comes, Yarbo will be trying to mow my fences. Good luck with that.
1 Like
No if you artificially remap your map boundary larger and then they allow zero vs the forced 4 inch offset, you will have issues. If you just map and deal with the 4 inch safety buffer, you shouldn’t have an issue. Same with NGZ’s. Templates have a 30cm buffer but I think drawn gets a little closer.
Two things.
Regardless of what Yarbo does I have issues. Just ask my wife.
Second. If you have me drive Yarbo to draw a map I will get as close as I can to the immoveable objects in my yard to cut down on weed whacking. I think that’s what everyone would do. And if I can drive Yarbo there, then it should be able to go there own its own.
I drove Yarbo to create the permitter. So Yarbo can traverse the areas I drove him would you agree?
Yarbo’s “safety buffer” should be that they do their turns inside the perimeter where they have room.
Then perimeter mowing, which is how the boundary was created should be fine.
Throwing in a 4 inch safety buffer is just hiding the root cause of the issue.
I guess I could be missing something…
5 Likes
I agree with you 100%. My other robot mowers behave exactly as you describe, and their RTK accuracy is “spot on”.
Basically my expectation is that the robot will “playback” the parameter lines that I manually drove when performing the original mapping. There shouldn’t be any deviation from what I programmed.
3 Likes
How many of you have Template No-go Zones around your trees and posts and have been refining them smaller and smaller to do away with the weed whacking, as is the motivation behind what @ken.w.gregory is doing?
As I mentioned elsewhere, folks are just going to map differently (or keep resizing Template No-go Zones) to get around limitations. Lift the limitations, and there go your Prized Petunias.
4 Likes
I completely agree with you and in your case I don’t think you’d have an issue when they remove any safety buffers. But those that mapped on the other side of their fence or something to get around 4 inch or 30cm buffers are going to be surprised.
1 Like
That’s needs to be in bold capital letters at the top of the release notes appearing before you can update. “BREAKING CHANGES in this release!” I’ve done some cheating with a couple round tree NGZ templates myself.
4 Likes
Ken, thank you for your sincere feedback. I totally understand your points about the buffer at the boundary as well as near the No-go Zones.
You’re right — the ultimate solution to issues like going out of bounds or entering No-go Zones is to improve the navigation system itself.
I’ll pass your feedback to our product team. Thanks again!
1 Like