The sidewalk im having issues with is an s curve as well. Maybe thats a troubleshooting lead..?
It seemed to be turning it on and off intermittently. The slope mode sometimes does the same on the return path, iirc.
Slope mode is designed to turn off the auger on the uphill jaunt back.
Itās as stupid as backing down a dead end with the mower.
Yes, the mower doesnāt get stuck but it doesnāt mow the grass at the end but the S1 will get stuck in the snow.
Maybe itās the same algorithm that if yarbo drives up to a dead end and is closest to the start with the rear end then it backs down into it instead of turning almost 180°
Dead ends are based on sidewalks..,so Iām sure it is.
So I deleted the area my sidewalk was operating in and the S curve performed as expected. (Changed the length up a little from before) Iām not saying my underlying area was an issue but it feels that way. The area deleted did have āSlopeā enable and my sidewalk was perpendicular to the slope direction.
Hope you can have sidewalks in an area without them reversing. For now I am going to use sidewalks in lieu of an area in this circumstance.
Anybody tried a sidewalk from the charging station that is drive in, reverse out? Would that stop the zero turn? Probably have to turn off the charging station snow clearing though.
Interesting. Glad you figured out how to make it work!
Iāll have to do some more experimenting when I get free time
This likewise explains why some dead-ends are run twice when mowing. The dead-ends (and sidewalks) get chained together by the 0.3m rule, then the 2nd one is executed again because itās part of the plan.
Thank you for this level of detail in the response, @Yarbo-Forum .
It is extremely helpful, and very much appreciated.
@Yarbo-Forum any update on when we can expect a fix for the backwards sidewalks? Iām still getting them fairly regularly.
Letās start mapping them in reverse! That would have to workā![]()
Iām going to test two tomorrow in the middle of the driveway- map one forward and one reverse.
I tested one yesterday for the first time in a long time. A āsidewalkā path I created to clear snow to the barn behind the house. It actually worked!
Iām still not ready to trust Yarbo to clear my actual sidewalk in the front of the house, but at least this one test yesterday was a success.
LOL Nice! Let us know how that goes.
Yeah thatās the annoying part, is itās still intermittently doing random ones backwardsā¦there are definitely certain ones it usually does correctly but if you mix the order around in the plan or run them by themselves thereās different behaviorsā![]()
Itās really disappointing that the sidewalks are not reliable. I had created snowblowing sidewalks for all sorts of purposes that canāt be trusted now.
Yeah that should have been considered one of the core features knowing the rest of the software is kinda flaky/betaā![]()
Has the M1 ever done this with a dead end? Because one would assume itās the same framework just renamed, no?
I just canāt figure out their programming tree. Itās like all modules have their own silo of programming that canāt be shared/cut and pasted/cloned/.cross referenced.
For instance we can rotate the M1 mow pattern by various degrees so to not run the same pattern.
Why not B1 or S1?
The throw or blow parameter shouldnāt dictate the pattern of the core either. Would be nice for me to control a slider to select the direction I want the core to move. Much like the slope mode/plow idea.
Iām no engineer but Iām here for it.
The code is all reused. Sidewalks are just super pathways. Dead ends and patrol lines are essentially sidewalks. To answer you first question, yes dead ends do this too. I suspect the same issue is plaguing both.
To your other point, Iād much rather the code, settings, capabilities, etc was universal across all modules. Iām sure it would make things simpler from a development standpoint too. No weird exceptions based on what module is attached.


