Of course “do what you want”, but was curious if there’s any “benefit” to doing the outer edge first vs last? Trying to think if it’s faster, or if it is better for turns etc
If you do them last, it may traverse over the freshly striped area on it’s way to start the perimeter. It not always smart enough to start at the closest point.
I do it first because of what @cobradunn said. It really is personal preference.
I do at least 2 laps of perimeter pass first as a sanity check to make sure he makes it all the way around properly. Then I go inside and let him work.
I definitely watch it on the first perimeter lap too.
I have received the firmware update on one of my Yarbos. But how do I switch between area first or perimeter first?
Area settings and tap and hold the 3 lines on the one you want to move up to be first in the order list.
thanks. hadn’t tried that ![]()
and drag farther than you think you need to.. ![]()
I do perimeter last, because that’s usually the most likely thing to screw up. At least the area is completed before the core treks off on walkabout. Or in areas that don’t need a perimeter done, I can simply end the task once the area is complete instead of mucking about with “% done → preview” 500000 times.
But it does come down to preference, when done.
I like it, except if you’re doing any automatic pathing rotation it won’t happen unless the plan completes.
I run two perimater laps last which I think gives a clean border to the area.
I do 2 perimeters first. I can usually pay attention long enough to make sure Yarbo completes that part. My attention span fades after that and Yarbo can usually handle the rest.
This was new. Anyone seen this before? Should I be concerned?
Wow, haven’t seen someone with that error in a really long time. Congratulations! You win the prize. I’d get a ticket in for them to double check it, even if the reboot fixes it. I think it’s probably just a calibration thing. Hopefully something they can fix remotely if needed.
If you can’t say anything nice… just dont say anything. ![]()
![]()
Ticket# 189078.
Never seen that one. I usually win the prizes for issues no ones’s seen before ![]()
