Lately, during the work program, after completing the first counterclockwise lap of the perimeter, instead of turning left and continuing counterclockwise three times, it tries to turn right, colliding with the rubber edge of the lawnmower against the perimeter wall all three times, and quite forcefully before changing its settings. Currently, I’m set to stay 10 cm further inland, but even if I set it to 20 cm, I wouldn’t avoid these collisions. I hope the new update comes out soon and fixes these problems as well.
This sounds abnormal. I would definitely log a ticket. Grab video and enable issue record at the bottom of the app. Note the times/date in your ticket and let them know you snagged a recording from the app. Don’t forget to turn it off when done reproducing the issue.
In the interim, have you tried setting the perimeter laps to the default of 2 or changing it up some to see if the issue persists?
I use the spiral cut because I have a slope that at the moment I can only do this way.
Thank you for sharing these details. I’d also suggest submitting a support ticket for this issue so our team can look into the logs and investigate the root cause more thoroughly.
I remembered what might have caused the problem… while testing, I had remapped the area clockwise. However, it still doesn’t recognize boundary walls accurately. I’ve already reported this issue several times. Let’s hope the next update works miracles.
I don’t recall ever seeing that we should map in a certain direction. Should mapping always be done counter clockwise?
I think so, and it would be logical since he works that way. I had asked if he could also work clockwise, especially when there are slopes, so he could do them uphill with a spiral cut.
It’s not a requirement but highly recommended. It will always run the plan with the right antenna on the boundary line regardless of how you mapped it. Best to map CCW for areas and CW for NGZ’s
OK, but in my case, the problem started after I remapped the area clockwise. However, the main problem to solve, in my opinion, is still the wrong approach when working near the fenced perimeter boundaries.
My understanding is that they are working on adding this ability soon. I think it will require DR and VO to be in place first though.
If you remap clockwise, you will (currently) end up with a slightly larger area than one mapped counter clockwise, I guess 1 Yarbo width wider. You can use this to your advantage if you want it slightly larger go CW or the NGZ slightly smaller by going CCW.
That sounds like they aren’t really using the center of Yarbo to mark the perimeter…
I have no reason to doubt what you are saying but I have to ask, highly recommended by who? There is no documentation that I can find that says or even implies this. The only thing I could find was that the core uses the center of the unit for reference. If I have solid GPS while mapping what difference would it make? The GPS coordinates would be the same no matter which direction it gets mapped. I get the whole right vs left antenna thing but I don’t see how that applies here. If that is truly the case they should document that, explain why and maybe it would cut down on support incidents.
From what I’ve read in the forums, it uses the left antenna only to draw the boundary. Then of course it follows the boundary CCW with the left antenna too.
This is only an issue because they include a hefty unmowed buffer zone that some of us would prefer they wouldn’t.
If this is correct, this is how you can get a slightly larger or slightly smaller perimeter or NGZ.
Yes, I followed what the Yarbo team said. Let’s hope they arrive soon.
I searched the wiki and it is documented in the @Ken big read me. Haven’t seen it anywhere else. I can tell you I’ve seen Yarbo sometimes recommend this. I think it made a newsletter. But mostly it’s been the user community stating this. I can tell you personally that when I mapped my back yard with the SAM I went CW vs CCW. I didn’t know it mattered. When I got the mower it ran the opposite way. In a corner where I went right mapping, it now approaches and goes left. Problem is, it routinely bumped my fence with the corner of the bumper in that exact spot. That was November of last year. When they added forced buffers, it obviously stopped. This is why I say it matters. Maybe it was GPS issues being up against the fence and up against the porch in that corner, but it did it so reliably every time that it seemed like a path planning issue. I also feel like the SAM could get much closer to objects VS the mower which would map the center of the core would be further along and closer to whatever you are turning away from. Then if you attach the mower and it doesn’t calculate the size of the core + mower and turning angle, well, collision.
Anyways, I agree, it should be documented. Maybe @marco can assist here.