In our driveway I have a work area, and attached to that work area are three sidewalks: #1, #2, and #3. (Sidewalk #3 is the middle sidewalk.) The following works great:
A) A work plan of the work area followed by sidewalk #1.
B) A work plan of the work area followed by sidewalk #2.
C) A work plan of the work area followed by sidewalk #3.
D) A work plan of the work area followed by sidewalk #1 followed by sidewalk #2.
Here is what will not work, I always get the WP005 error:
E) A work plan of the work area followed by sidewalk #1 followed by sidewalk #2 followed by sidewalk #3.
I wonder if a pathway connecting the sidewalks at the front of them might fix the glitch. They might not be quite 3.3ft into the area. The first one (1) looks a little short and has that curve in it.
Could you please submit a support ticket for this issue? It may require further investigation from our team to understand what’s causing the WP005 error.
I also wonder if it’s trying to “merge” them into 1 sidewalk and wants to travel down one, turn onto the next and come back…they did say they were working on changing/fixing that behavior too
I’m not understanding your thinking here. Each sidewalk gets worked on just fine, and a work plan of #1 and #2 also works fine, the only problem is when I have a work plan that involves all three sidewalks. What is it you’re saying about sidewalk #1 that results in a work plan with all three sidewalks failing? I’m probably not thinking about something correctly.
The error message is basically saying it can’t calculate a route and this is usually a pathway issue. Independently they work but together they may be getting merged due to closeness and it can’t calculate how to get from one sidewalk to the next. Sidewalks have to start in an area or a pathway. If the sidewalk is too short for it to maneuver to the next, it might think there’s no area or pathway when they are merged vs when they aren’t. You could try it, or open a ticket and wait for them to analyze what the issue is.
I have the three sidewalks I identified in the screenshot up in the first post. Then, overlapping them for about 18” are the three sidewalks you can see in that screenshot to the left of those sidewalks. In the screenshot they might deceptively appear to be butted up against each other, but in fact they overlap a little bit.
Instead of parallel sidewalks, I map as an area. Then use slope mode and specify that the slope is in the direction I would have run the sidewalks. It’s less work to map than multiple sidewalks. Yarbo does a multiple-sidewalk-like pattern. I use it at the road end of my driveway, so it does several passes back and forth perpendicular to the road. It doesn’t throw much into the road because it throws to the side, then backs up before turning. The auger is running but there is no snow in front of it. Not sure how narrow a space this can do. I think it could to a two or three blower width area. That seems to be enough to make the turns.
My slope mode is supper buggy, but I think it’s related to overlapping zones…when it crosses a boundary from another area it isn’t in it sometimes does crazy zero turns in that spot, often getting stuck…it’s weird though as I had an area set up to run that it was doing fine on with mowing areas underneath and then I edited it to get it a little more optimized and all of a sudden started doing crap and getting stuck constantly
