Since the 3.9.10 firmware update, Grasscutter is detecting a parked trailer (and IBC tote) off to one side of its path as a vehicle, and refusing to continue on to its charger. The charge pad is straight ahead in this picture over the top of it. It seems like it should be able to continue to me as it’s not going to hit the “vehicle”, but maybe it’s worried about it moving? I note it doesn’t have any issues on its way out via that pathway, so this spurious detection seems path related.
Did any settings for vision adjustment get added to pathways? (it’s mowing now, so can’t check myself). Or would a no-vision zone be useful here?
Yes obstacle avoidance was added as a beta feature enabled by default. You can disable it in the pathway settings or make that area a no vision zone so it closes its eyes in the zone. Just know that either of those turns off vision and obstacle avoidance and relies solely on the bumper.
Yeah, I know it was added in 3.9.10, that’s why I called out the firmware version. It’s still overreacting to a trailer that is not in its path. I will check out the path settings when I get a chance too.
I also find it interesting that I have the area it’s headed into (that has the trailer in it) marked for “limited vision” or whatever the setting is called (can’t check because it’s passed in the middle of a job as it’s outside schedule hours atm), and it has no problem headed out there. Hey Yarbo, what sort of things that are check for on the various vision settings would make good weekly post!
So @bryan.wheeler I haven’t tried no-vision zones yet. Would I put one over the trailer to tell it to ignore that, or on the path to tell to tell it not to use vision detect there? Although if that’s the case, maybe I just throw a no-go zone over the trailer and see if that gets it to ignore it.
You would put it over wherever it is triggering in the pathway. So wherever that trailer is visible in the pathway. I don’t think a No Go Zone would get it to ignore it in this case.
Thanks. So on the pathway where it’s getting stuck makes sense. It’s just a short connector path though, so I’ll probably just turn it off for that pathway when I get a chance.
I’ve had similiar issues. The unit followed the pathway successfully to start the job but after it was finished it identified my truck as being in its way. The truck is in a no-go zone and the pathway loops around it. I believe the whole point of this new feature is for scenerios like mine. Someone comes home and pulls too far up into the pathway. I dont want to put a no-vision zone there because that would defeat the whole purpose, I would want it to stop if its blocked and not have itself get wedged under my truck so far that I have to get a floor jack to get it out. Yes, that did happen.
Thank you for bringing this to our attention. It seems that the parked trailer might be within the Field of View (FOV) of your Yarbo, which could be triggering the obstacle detection feature, causing the Yarbo to stop.
Unfortunately, placing a no-vision or no-go zone won’t be effective in this case. If you feel it’s safe for your Yarbo to continue without the obstacle detection, you can turn off this feature. This should allow it to navigate the pathway more smoothly.
Yep, I used a No-vision Zone so the rover would get in the doghouse. No-vision Zones have the advantage of not turning off vehicle detection in the entire path.
That being said, I tested the No-vision Zone once or twice, and it worked OK, but I later turned off vehicle detection for most of the Pathways around there because I have a few carts and stuff nearby, so I “should” go back and Test No-vision Zones specifically Better. If anyone finds out No-vision Zones don’t work to turn off vehicle detection on Pathways, please let me know.
Reminder: No-vision Zones are plopped on top of where the rover will be when it sees something, not on the object it’s detecting.
