While Yarbo is executing a job, quite often Yarbo will hard-stop (Yarbo will even lift up slightly in the back due to its momentum). The most common scenario is Yarbo crosses (or comes close to) an area/no-go zone boundary. If Yarbo touches an obstacle, it’s expected to hard stop, but virtual boundaries don’t require such rough movements.
This seems to be putting unnecessary wear on the motors and drivetrain. Is this being improved in future updates?
Thank you for bringing this to our attention and sharing your observation.
After consulting with our team, we’d like to clarify that this behavior is part of the intended design. The sudden stop near area or No-Go Zone boundaries is meant to ensure Yarbo stays safely within defined limits, as we’ve seen instances where the unit could otherwise cross into restricted zones.
This behavior does not impact normal operation, and it functions as designed to prioritize boundary safety.
We appreciate your understanding and thank you again for your valuable feedback.