People with the trimmer… got my trimmer put on and tested a small area a few days ago between rain, worked great.
Went out to mow today and trimmer is not turning on at all… no error or anything. I selected the trimming areas… Is there some other setting that I am missing?
Also not sure if it’s the last update or the trimmer but pathing seems to have changed significantly… a lot of backing up and repositioning around the edges … which makes me think maybe it is trimmer related.
What happens when you try to manually turn the trimmer on via the app? Have you tried that?
I didn’t even think about that… lol. So paused, went to manually turn it on… nothing… hit clear error button and it worked! Thank you.
So… I guess there was an error but it wasn’t showing it? Hopefully a bug that gets fixed… because if I wasn’t watching it mow I would have no idea the trimmer was not working…
The trimmer does change the path planning and backing behaviors. I’d recommend removing the trimmer and putting it on when you want to trim. Hopefully they refine this soon so you can leave it on all the time if you want to.
I experienced something similar with my trimmer. That’s what prompted me to think of it.
It seems there is a Trimmer error condition that we do not get a visual notification of. There is no warning in the app. But pressing the clear error button resolves it.
Since this is solved, lol.
I mapped a new memory path to do some trimming. I drove yarbo a few feet away from memory path I just mapped. I then selected a plan I made for this trimming path and what did yarbo do? He got into position to do the memory path in reverse, I of course had to babysit and stop it.
I then drove it about 25 feet away and tried the plan again and it did it correctly.
So how do we know it is going to do the plan correctly and not in reverse and smash the trimmer?
Just like a Dead End. If the ass end is closest to the start point it goes in ass first.
How can they not figure this out yet? I can’t trust that it ends one part of a job and the ass is pointed the right direction for the next.
I will have to make another ticket, so then they can give me some dumb answer.
I have heard other people talk about Yarbo entering a Memory path backwards, but it hasn’t happened to me (yet).
It sure seems like a very basic thing - Yarbo should drive FORWARD, not backward. Odd that it’s still apparently an issue.
I mapped a memory path around a tree. I then drove yarbo a few feet away. Selected a plan just for this tree I made. Yarbo drove out to the farthest corner of the area the tree is in and then came back and trimmed as the memory path was mapped.
I have to say it again, why?
Same thing happens with Dead Ends. Same defective code.
It is going much closer to no go areas… not just with the trimmer but with the mower… I think it is actually bit better… although yeah a bit precarious with the trimmer swinging around.
Trimmer logic needs some tweaking too… like whenever it goes around a no go zone that you have set to trim around, whenever it passes next to the yellow line it turns the trimmer in… even if it is on the opposite side of the no go zone. Not really a big deal, just nothing to trim on that side.
I noticed that too. Almost like their logic is distance based.
I watched it turn the trimmer on even though the trimmer was pointed in the wrong direction. It just got close enough to the ‘trimming perimeter area’ that it turned it on anyway.
It’s really too bad that yarbo starts from the end of a memory path. I use the trimmer with SAM installed. Then you can use go to Waypoint to the start of the memory path start. But sometimes when a memory path ends and yarbo should continue to the next memory path, yarbo chooses to backtrack from the end to the start first. Made a post about when there would be an update for it and the collision sensor for reverse collision. yarbo said they didn’t know when there would be an update. 
Well it will become a critical update when a bunch of trimmers are broken because of this. This is very bad with the trimmer attached.
When you have a work plan with multiple memory paths you have to keep an eye on it and fix it. Pause it to drive out of the path so that it can drive on to the next path. Not that autonomous.
People are paying $800 for something they have to sit and watch? This is not going to go over well. This seems like something that could be solved easy.
Yarbo don’t do the thing in reverse.
It feels like the are just rebranding the same programming:
“Sidewalks”
“Deadends”
“Pathways”
”Memory Path”
They all will enter backwards at some point. As you logically use them in your maps.
I can’t speak for the other 3 yet but I will soon- Sidewalks are unusable for the S1.
I’m here for it.
And they all don’t make sense why it would be allowed to do them is reverse.
I believe they are removing this “design choice” in the next major release.