It would be good if you could tell Yarbo not to back up at dead ends and not to turn around when it is in dead ends. It would also be good if you could use the remote control and drive Yarbo away when it says Yarbo lifted.
Thank you for your suggestion. Regarding deadends, are you suggesting that Yarbo should use an alternative pathway connected to the end of a deadend to exit, instead of reversing along the same path?
As for the lift-related suggestion, I’ll pass it along to our product team for consideration, especially if more users express interest in this feature.
Hi. No. If yarbo stops its work in the middle of a deadend because lost gps or lift detected and you continue the work plan sometimes yarbo turns 180° to drive forward out of the deadend.
It could be good that yarbo didn’t do that. So it backed out again.
And sometimes yarbo backs up from the start of a deadend but then it needs to mow grass under the rover when it reaches the end of the deadend.
Thanks.
There is a request to bring snowblower Sidewalks to the mower. I heard from a little birdie that it is in plan. It sounds like you’d want the “one-way” version for the mower, as do others.
Deadends: Out, reverse, back.
Sidewalks: “Super Pathways.”
- Out, 180 degree turn, back (default behavior)
- Out, reverse, back (same as Deadend, added late season, haven’t tested)
- One way (start at Mapped Item X, go through, end at Mapped Item Y, continue on – does this most of the time – not “supposed to work”, does, is awesome, DON’T “FIX” THIS ONE-WAY BEHAVIOR, YARBO! Pretty please?
)
Both can be added to Work Plans. I think the one-way Sidewalk is used as a Pathway, but don’t quote me on it – it’s been a while, and I just add them to my Work Plans anyway.
In talking with an engineer months ago, he pointed out that Sidewalks – which I’d not tried at that time – are Pathways with more features and should simply replace Pathways. Gets my vote.
Thank you for your clarification. For the first issue you mentioned, I’ll forward it to our product team for consideration. Regarding the second issue, we have received similar feedback before and have already passed it along to the product team for evaluation.
Thanks again for your valuable input!