When using the slope beta setting for the snow blower module, I notice that the Yarbo lifts the blower to turn around and return to the top of the slope. When it’s facing the direction to return to the high point it lowers the module back down. This seems to cause issues with its traction and climbing abilities as the scraper bar is more likely to snag when heading up. There should be a way to keep the module raised as it returns to the top of the slope to reduce snagging on pavement imperfections.
5 Likes
I agree completely. I put in this suggestion a couple of weeks ago via a ticket to technical support. They seem interested in my thoughts (very encouraging!) and are apparently discussing it internally.
You may want to formally request this change in the algorithm as well via the ticket process. If enough of us suggest the same thing they are more likely to take the suggestion seriously.
2 Likes
Really appreciate you sharing this idea with us and explaining the issue so clearly. I’ve passed your suggestion to our team for consideration. Thank you for taking the time to provide such thoughtful feedback.
1 Like
Note that I sent a follow-up to my conversation with Yarbo regarding slope mode making an additional suggestion. Copied and pasted below for everyone’s information and comments
"
Note that, as an alternative solution for my Yarbo struggling going up my steep driveway, if I had the ability in the SIDEWALK function to set the auger height to a different value (height) on its return path, then this would increase the likelihood that Yarbo could successfully clear my driveway.
I would define the driveway as a series of parallel sidewalks, with a lower auger ( example 0.3") setting on the way down (clearing action) and with a higher auger setting (example 2") on the way up.
Is a function change like this for the Sidewalk feature for the Snowblower module something that Yarbo would be interested in considering implementing? It seems like it would be relatively simple to implement.
It may be easier for you to implement that broader changes to the slope beta function for Areas.
Thoughts?
"
6 Likes
@Yarbo-Forum As a data point, I’m using the slope function to mitigate a poor GPS area, since the Slope function does not require a perimeter.
The ideal solution, for me, would be to “Reverse Back” at the end of a lane, instead of the present “Zero Turn”. I’m using Slope Mode to mitigate GPS, force directions, and avoid perimeter laps that simply cannot be completed. Ever.
As for now, the core performs a zero turn and leaves the auger at the area height. It is effectively a plow (and it does resolve getting stuck on things extremely well), but it leaves a snow bank at the start of each lane.
Ideas that will solve most use-cases:
- Option for Zero Turn vs Reverse Back, just like sidewalks.
- If Reverse Back, path solver will lift the auger to max height.
- If Zero Turn, app GUI enables option for auger height on the return trip. Default to max height.
- If return auger is not max height, enable the auger on the return trip. If return auger is max height, leave it off. That’ll handle zero-turn and reverse-back with auger off.
…assuming we’re not in Plow mode.
Cheers
2 Likes
Regarding #2 (reverse back). If auger height is Max and Yarbo reverses back up a slope it becomes front heavy (weight of auger vs counterweight of core) and most of the track surface is off the ground. I experimented with this manually and it isn’t effective to back up a slope with auger raised (but going up forward with auger raised works fine).
So if the slope is real (vs using the slope function when it isn’t really a slope) this isn’t necessarily effective imho.
Although #3 would help me out and would be effective for what I am doing (real sloped driveway).
I think Steve runs a weight back on the rear of his core. If memory serves.
Correct.
The Reverse Back option would not be used on a slope. It would be used on a perfectly flat concrete pad where no other pattern works because of chute logic or GPS issues. Or on a wide sidewalk, for example.
1 Like