Allow Memory Paths outside of a work area

The Memory Path feature is excellent for setting a precise path for the trimmer to follow.

One annoying observation though - You can’t have a memory path that extends out of a work area. I don’t think that is ideal.

I might have a mowing area that keeps Yarbo say 8 inches away from an object while mowing. But I would want the memory path to get Yarbo closer to the object for trimming. I currently cannot do that. When drawing the memory path, you aren’t allowed to draw it beyond the mowing zone.

So I propose that Memory Paths should be allowed to extend beyond any other work areas or zones. Basically, Yarbo should be able to follow the path wherever I draw it, whether there is a mow zone there or not.

I agree, it is called a memory path, it does what you does, so it should be ok.

I have made memory paths go outside a mowing zone. It just has to start and stop in a mowing zone.

Thanks for sharing your thoughts and feedback! I’ll make sure to pass your suggestion along to our product team for their consideration.

Challenging area in a tree nursery,

I am hoping to get some suggestions on a challenging area in a tree nursery. We have an area with multiple tree beds. Between the tree beds in the area we have say 4 feet. In each tree bed we have two rows near the bed boundary, between the two tree lines in the bed we have about 3 ft of space. And we want to mow and trim the weed between the two tree lines in tree bed.
Should I make NGZ’s of the tree bed’s and then run Yarbo with trimmer with a memory path through the tree bed up-turn-and back? Connect multiple split area’s? Any suggestion how set up such an area?

Yes, I would make each tree bed a rectangular NGZ. Then start building individual Memory Paths to trim each of the tree beds.

I highly suggest making each tree bed its own memory path. That will allow you much more flexibility in making changes to the memory paths as you learn how to improve them without needing to recreate everything all at once.

I agree and I would create each one and test it immediately afterwards. Then create your work plan and test them all. Make sure the entrances to each memory path (the start points) are staggered so that the rear of the core isn’t closest to the next memory path entrance and that they don’t overlap. This way it can navigate a little distance to enter the next memory path appropriately.

This is the way.

It really is critical to test and iterate each of the memory paths until you have confidence Yarbo will do what is desired, and without supervision.

And like Bryan said, path 2 should start a few feet ahead of path 1’s ending point. And so on.

Then, when each of the paths work properly individually, you make a work plan that incorporates all of them in sequential order. Do a few test runs of the entire sequence, and make any necessary changes.

Be careful there is a known bug where it will try to do a memory path in reverse!

Hi, thanks for for sharing your ideas, we will try this and come back once we have some results.

You’re welcome. Good luck!

Take it slow and experiment. As you learn the pros & cons of the trimmer and how it works, your memory path designs will likely evolve to accommodate.

My rectangular memory paths end up looking something like this…

I don’t completely understand what you are trying to do,

but you can definitely do MPs outside a WA. They have to START in a WA, and END in a WA. It doesn’t have to be the same WA / the MP can go wherever during that time, including outside WAs.

I’m doing cedar-fence line mowing, which has similar challenges - Mapping approaches for split-rail cedar fence line mowing (Mower & Trimmer module)

The “reverses along MPs” brought up above might kill you. I would do a few tests. Plan for lots of testing and reworking.

Plan that for the rest of this season at least you will spend more time trying to get Yarbo to do what you want vs you just manually doing whatever you were doing before. Hopefully in 2027 it will be a time-saver.