My driveway is long and narrow, and Yarbo’s automatically configured blowing map doesn’t work for me as it is excessive, is there a way to create a pathway and just schedule pathway blowing only?
1 Like
Unfortunately not at the moment, but it is a feature we have been asking for.
1 Like
Hi there,
Sorry—this isn’t supported yet (you can’t schedule a pathway-only blowing job). We understand the need for long, narrow driveways, and we’ve logged this request for our product team to review.
3 Likes
It sounds like you can’t have a plan with only a pathway, so add an area big enough to blow and put it at the end of the pathway. Something kinda like this 15’x20’ area in my driveway (except in your case, I would map the pathway to go out to the street and then back to the small area):
1 Like
Is pathway blowing supported? It sounds like it is looking at the Pathway settings, but it didn’t blow when I tested it.
Certainly looks like it’s supported. Maybe try turning it off, saving, and turning it back on. Stranger things.
1 Like
Tried both. No luck.
Seems like a bug then.
1 Like
@Yarbo-Forum What’s the best way to get this investigated and resolved? Ticket #121752
The blower isn’t operating when travelling on a pathway to an area. It only blows in the area.
2 Likes
Hello Greg—yes, Pathway blowing is supported. I’ve checked your support ticket in our system; it’s currently with our first-level support team, and they’ll follow up to resolve this. Thanks for testing it and for your patience!
2 Likes
Yes pathway blowing has many bugs. If there is another pathway crossing the path Yarbo is flabbergasted, also it will think there is an obstacle and go back and forth like 5 times then gives up with tantrum.
I still haven’t find efficient way to blow my 250 foot driveway. Technically Yarbo can blow and go to the end of the driveway and do a U turn to come back but this time keep left of the pathway so blowing is overlapped.
3 Likes
Oh! I’ve also noticed a similar problem (bug) when Yarbo is trying to blow my driveway.
In my case, I have Yarbo set up to blow a section of yard as task 1, then as a secondary task, it’s supposed to drive onto my driveway to clean up the leaves that scattered onto the driveway. Well, when it tries to transition from the end of task 1 and start task 2, it’ll just drive back and forth over and over saying an obstacle is detected.
If I leave it that way, it eventually gives up and ends the task. But I noticed that if I pause the task then continue it while it’s in that confused state, it will keep working. It’s like pausing it clears whatever is causing the bug.
3 Likes
Might be worth a “record issue”, duplicate the problem, then turn off record issue. Note the date and time of the capture and open a ticket. They can then get the debug logs for the appropriate timeframe.
Then maybe they can fix it.
2 Likes
Support helped me figure out the issue - Pathways need to have the blowing direction set, which is great, but not expected and not in the knowledgebase. I mean why have a toggle to turn the fan on on a path but not tell the user they need to go configure the path.
Would be a good thing to app to both the App and the KB.
Leaf blowing up and down my 350’ driveway is working now!
3 Likes
An error like for areas without a blowing direction set would certainly be helpful. Especially if it popped up when you hit enable.
1 Like
That caught me too. And work areas that you are traveling thru to get to the actual area to leaf blow. Took me a bit to figure those two things out.
1 Like
I experience the same issues.
App is always referencing some mapping guidelines but I was not able to find detailed guidelines on forum & wiki. If somebody have clear guidelines with detailed rules and restrictions please share. My expectation is rules and restrictions from code translated to the simple language for to the users. If app knows that yard is not according to the guidelines rules and restrictions exist and are processed in code and should be published for user to simplify yard mapping.
Currently I am trying kind of find restrictions by reverse engineering by checking my ideas on the ground, but this is time consuming and sometimes results are not repeatable especially after firmware updates.
What is best practice for the mapping current yarbo code is able to process? For example
Areas: intersected or with gap, why pathway required if area are intersected and yarbo can cross in any point or near border (like my Mammotion Luba 2AWD), if with gap pathway is required.
Pathway: single long pathway thru all areas or many pathways connecting just only neighbour 2 areas, pathway crossing on intersection of 3 or more areas etc.
Currently my Yarbo starts to dance and stop with the message about avoiding non existing obstacles in most simple mapping with 2 areas with small intersection in the border and long pathway thru both areas and to the dock on the one end.
The same story with 2 parallel pathways crossing all areas to blow to one direction on the way from docking station to the most distant area and blow to the another direction on the way back. Yarbo starts to dance on the intersection points of areas.
In the video attached yarbo after completing area1 should go down by the road to the area2 in 1 motion instead of dancing 1.5minutes and resulting to the obstacle avoidance error as mentioned in the message I am replying to. Such rotations on the single spot should be forbidden by design, concrete will handle it, but I cant image what will happen with the lawn after the same dancing sequence.
That error typically means it’s a pathway issue. You can troubleshoot by driving the core to the furthest area and hit recharge. When the error stops and it goes back, you’ve found the broken pathway chain further up.
Also, It doesn’t connect areas through an overlap. You need to have a pathway outside of the overlapped area. Typically about 3.3ft minimum on both sides of the pathway. Cannot end or start in an overlapped area.
1 Like
Actually starting/ending point during editing maps is also not implemented well. I experienced case today/ Start button appears regardless conditions on the ground (except if yarbo is outside of area). Next button appears as soon as Yarbo touches border of the destination. But in many cases this results to pathway image on the map in the app which is actually not connecting anything and resulting to the map calculation error.
I noticed that pathway works only (similar with area editing) if yarbo icon is completely within area on the map, docking station etc. Starting/ending line on the edge is not safe.
My Mammotion Lawn mower displays start button for the pathway, area etc only if robot is close to the border and this results to the always correct outcome (if app is not hanging, but this is another story). Yarbo app allows to start working with Area, Pathway etc from any point (instead of the border only) and in many cases this ends up with no results.
2 Likes
Yes, I see the same issue. Next time, when it starts ‘dancing’, just pause the job, wait like 10 seconds and then resume it. For me, that clears the bug. I’m curious to hear if it works for you as well.
3 Likes