I’m wondering what is the GPS / RTK / Mapping Route Accuracy of Yarbo? I’ve created some Deadend routes for mine where I need it to mow between some items that are 2 or 3 feet apart. There is enough room between this row of items for Yarbo to make two trips. But when I run the Deaded routes it ALWAYS bumps into either the one on the left or the one on the right and moves the objects. Either the objects are too light to trigger the pressure bumper or the pressure bumper and obstical avoidance is completley disabled in Deadend mode? I need to figure out how to get it to mow between them and fairely close to them without bumping into them and moving them. Any ideas?
Does it hit on the corners or near the corners of the bumpers? That is almost a dead zone. It takes a lot of pressure in those 2 areas to activate the bumper sensor. Everywhere else is pretty sensitive.
Yarbo’s RTK positioning offers centimeter-level accuracy under optimal conditions. Based on your description, if the space between the objects is around 2–3 feet, it indeed requires highly precise mapping during the initial setup to ensure smooth navigation.
However, please note that in areas where the GPS signal fluctuates or becomes weak, a slight positional deviation of a few centimeters may occur. This could increase the risk of Yarbo accidentally bumping into objects if the boundaries are set too close to them.
Regarding obstacle avoidance on the Deadend, we’d like to confirm that the bumper is indeed active. As Bryan mentioned, the bumper is generally very sensitive except for the 2 deadzones.
Maybe you can consider leave more buffer zone for the smooth operation of it!
It does seem to hit mostly on the corners when it bumps into the boxes. Yesterday I decided to set them on 8 inch cinder blocks, so it would bump into the cinder blocks instead, which are much heavier and harder to move on the ground. So two cinder blocks laying side by side on the ground and them a box sitting on top of each one. It actually bumps into the cinder blocks and scoots them an inch or two, then realizes it hit something and stops and tries to re-adjust it’s route. It will then overshoot and hit the blocks on the other side and after a few times of that it just gives up and goes into suspended mode. There is a 3 foot runway between the blocks. Sometimes it even bumps all the way over in the center of the blocks. I’ve just about given up on this idea of mowing this area with Yarbo.. I’ll attach a picture of the area. You can see the ones I tried putting on cinder blocks on the right. I’m thinking I’ll probably eithe rhave to spread them out more or build stands that yarbo can drive under. Both of which I really don’t have time for right now, lol.
I would suggest if you are amenable to trying a few more times, you could scroll down to the bottom of the diagnostics screen and enable issue record. Note the time you start it. Start your work plan and video it in action. Note the times or round about the times it impacts and causes the issue(s). A quick screenshot of the app is the easy way to get the map display and the time. Turn off issue record when done and then submit a ticket. Yarbo support will download the record and review the video and screenshots and might be able to see if there is a solution or pass it over to engineering for some possible code updates or bug fixes. In the interim you could manually mow this with the Yarbo. I think there is some issues with dead ends right now that may be fixed in an upcoming hotfix. It may just sort itself out, but the extra data could help Yarbo dial it in even more. At least for you particular situation. Might just need a tweak to your settings or something simple.
We’re sorry to hear about the inconvenience this has caused. We understand that it can be time-consuming to readjust the setup or build stands. Could you please submit a support ticket with the details of your issue, including the timestamp when it hits the cinder blocks? This will help us investigate further and see if there are any other solutions we can offer to improve the situation. Thank you for your understanding!
I’ve tried several more times with no luck. So I am thinking next time I try I will record the process as Brian mentioned above, and then submit a support ticket. I don’t think there is anything wrong with my Yarbo, I think I’m just asking it to do something extremley challenging and maybe I’m not doing it the best way for the best results.
Is there not an options somewhere that would allow me to manually mow or map exactly where I want the unit to mow and backup, etc. Basically recording my every move while I manually mow the area, and then duplicating that exactly for future autonomous jobs?
There is no “record and playback” at this time, @jsnbrgg. Sometimes I wish there was a more refined way to tell Yarbo how to do its job – sometimes we know better than the machine!
Your picture reminded me…Yesterday afternoon while doing a Work Plan my rover backed up over the Area border and crunched an old cheap/plastic border and nearly shoved its butt into an Arborvitae. Ugh. Well, that location had fairly awful mapping, so I deleted a bunch of stuff and re-mapped. In hindsight I should have left it as-is and opened a ticket, as you’re doing. I know Yarbo’s working on this stuff, and the more examples the better. Will do so especially after the next update if odd stuff still happens.
I suspect my Data Center wiggles in the wind, too, and it was windy. I need to get some wire on it to tie it securely. So I can’t put all of what I saw yesterday on Yarbo – some could be my bad. Map, test, tweak, test…
Good luck with your continued adventures, and thank you for reporting on them, as it improves the product for all of us.
@jsnbrgg , I don’t think you’ve mentioned, yet, but what collision-avoidance options are you using for this?
I’m going to have a similar thing to tackle, so I’m curious if that option has any effect.
