Tape ordered…
1 Like
Update on the temp. It eventually showed the icon, but still charged to %80 and returned mowing. It has been mowing/charging all day. It did hit 50 right before it left the dock. I will finally be caught up with mowing (after I manually fix the large stripes)
1 Like
While mowing it actually cooled to 46, I think this simple hack may make a small, but meaningful difference. Will continue to investigate other methods.
Thanks for all the tips on the stripes. I look forward to seeing if going to contact helps. Not keen on moving to an 8in overlap.
2 Likes
Note that after the mow grass was much shorter. I did not turn off vision…as much as I hate to admit maybe it would have made a difference. With the shorter grass I seemed to have no issue and the mow looked good. Still baffled on why it would keep the path for so long. Maybe the vision on the side? Too good? IMHO while this did work out in the end, turning off a good feature seems like a poor resolution. For anyone reading this you can also set a no vision area, which is pretty sweet.
1 Like
After receiving my new core and running it with latest firmware available today 3.9.29 and with Android latest application 3.15.6 I have the mower leaving 1-2 lines not cut. I have it running everywhere on gentle contact and 20cm (8 inches) overlap. It clearly indicates it’s intention already on the map view before it heads out doing so. Pictures attached. Arrogant bastard!
I didn’t had this before. I have 7 different mowing areas and noticed this at least on 5 of them. 2 zones where I haven’t had this issue are tiny so maybe that difference here.
I have notified Yarbo about this issue. Tried to open new ticket but on application on the support center menu I have only knowledge base… Remember now that someone had the same problem and wrote it here on the forum. Anyway I just wrote Yarbo an email on the last ticket I still have opened as I’m waiting new replacement caster wheels to arrive.
Have others noticed this behaviour after the last update?
You can get to the support tickets online here.
I have seen this as well. I didn’t get a very good screenshot. Or I would have opened a ticket.
It seems intermittent to me. Same work area different cut angle doesn’t miss any lines.
I’ll check again when It gets back around to this cut angle.
1 Like
It’s a known issue they are working on. The support center will load in app but it takes a long time. I’ve heard up to 20-30 seconds.
2 Likes
Happens to me too on/off. When I notice it early in the plan I cancel and do it again. If it does the same thing I move the angle a bit and it fixes it…
I think it all relates to the routing optimization problem we report quite often…
1 Like
I just set checkerboard and send it back out the next day. The 90 degree rotation gets it all
2 Likes
I have been critical of Yarbo in the past and there is still quite a bit that needs work. With that said something recently changed that made the mowing pattern work as expected for me. This has never happened before. In the past it would leave little nooks all over and then go back and clean them up. This time it did the perimeter then the NGZ around my shed and then started in the corner and worked its way across the lawn, kind of the way I would manually do it. I was very impressed with the improvement.
3 Likes
They keep tweaking it with each update. I keep noticing improvements. Definitely good to see.
2 Likes
Poor GPS area? Looks like it had a false good GPS lock and ended up in the NGZ and then plotted a path out.
1 Like
I have not seen it recalculate the intended path after the job has started. Is that a thing? I’ve seen algorithm bugs that miss stripes, but this looks different.
1 Like
Looks different to me too. Looks like it planned on doing that. But I’m no expert and didn’t stay at a holiday express last night either.
1 Like
Yes, this is a thing. It snags the current path line to get out of the boundary if it’s slightly over.
Ok, I’ll take your word for it. It sure doesn’t update the map to the new path when it avoids something or gets unstuck.
Well, I stand corrected. It just did it for me. I think it might have something to do with recovery once leaving the boundary or entering a NGZ. In my case, there a pretty good downhill slope where it likely couldn’t stop and ended up outside the boundary a little. Just a guess of course.
Probably had a false status 4 and recovered. I see a cloud point further down. Was that expected there?
The lower red was track slippage due to the slope. Not unusual in that area.
1 Like