I am surprised I can’t find this as a topic. My feeling is that a work plan should include some of the area adjustments, and the area settings should just be default for the plan. I understand things like pattern, but even that should be subject.
Speed, height, no go zone mowing, laps etc should be part of the plan.
If pattern is parallel then angle should also be part of the plan.
Currently the plan is just an area selection. One must modify the area each time before a plan runs to modify. Seems backwards to me.
I have two properties to run my Yarbo on. Right now, the “Home” work plan consists of 4 work zones (soon to be 5). The “Farm” work plan will be about 8 or so work zones once my new mower pro arrives.
I like the fact that the attributes of a work zone are separate and unique from other work zones. I have a zone that is diamond pattern, two zones that are parallel, and one that is spiral (and might change to parallel). I also set one zone with a higher cut height. Each area has its own requirements. They are chained in the work plan and re-ordered as weather and growing changes. They are disabled and enabled based on the same variables.
If the work plan is to have the aforementioned attributes assigned as an overarching policy, then maybe it can be set as you describe, and opt-in each of the work zones to that main policy. Else, the work zones will use their locally set parameters. If that is what you are describing, that could be a worthwhile feature for a baseline that all zones of the plan can participate in by opting-in.
I like the concept of global settings to override the Yarbo defaults. And then area settings, where you can override the global default. Ideally, there would also be a push button toggle to reset all area settings to the global settings for a quick change on all areas. very much like parent and child relationships with inheritance.
I never considered propellerheads scenario. I guess all of my areas are pretty large and not done in away that I would have so many areas in a work plan. Typically I want my property to look the same. I will not lie, part of this is so I can just use parallel and set my angles so all areas stay aligned. Another reason is I adjust speed depending on height and possibly mow height as well. Sometimes I don’t want to mow around no go zones and other times I do. This is to “catch up” with rain and fast growing grass, as well as maintenance and not wearing patterns. My areas do not grow at the same rates. Bryan’s suggestion would indeed satisfy both scenarios. I very much agree with parent child way of working.
I mostly was confused by “work plan” . There was nothing, but choosing the area. Then you can schedule that area, seemed redundant. I find myself going everywhere in the app. Part of it is being a newb. Propellerheads comment does make me see some benefit in by area.
+12 to this. Now that my Yarbo is well setup, I’d really, really like to refine my workplans… Continuous mode, “work hours” “non mow hours”, customize settings depending on the workplan, etc…
Alternatively we could program our own scheduler… If only they provided an API access…
The work plan is more of a grouping. Like you could add 3 areas, 2 dead ends, 4 sidewalks to one plan and then schedule or execute the plan. I do see utility in being able to have different settings for each work plan too. Summer mode, cut my grass at 4 inches. Spring/fall mode, cut my grass at 3 inches. I don’t even have to think about it. Just execute summer plan or schedule it.
Thanks so much for your thoughtful suggestion! You’ve made some great points, and I completely understand how having those settings tied directly to the work plan would make things more efficient. I’ll be sure to share this with our product team for their consideration!