memory path toggle dont reverse back. am really happy with my new trimmer. only has line feed errors when i use it manually. works well with memory path but have experienced 2 times that yarbo will reverse back on the memory path. when you have to be in an area to complete the memory path then you would think that yarbo would continue on to the next task from there.
Can you elaborate? I’m not completely understanding.
so you can use the memory path as a dead end and reverse back or use the memory path as a pathway from A to B and so on to the next task
I don’t think this would be a good idea with the trimmer hanging off the back. You could maybe loop around and bring it back into the area?
Now I get it and agree, I want it driving forward whenever possible and looping back into the area.
Yes, I will too. But I see it starting to back up when it ends the memory path even though it is in an area and can continue forward.
The core does a lot of backing up and it’s all because of the path planning. Instead of just continuing forward in a smooth arc, it reverses and twists on the angles. Definitely a problem with the trimmer on the back if it is too close to something that it will run it into. I know sometimes it will back up the entire length of a memory path. That is a bug that sometimes triggers. That isn’t expected behavior and I don’t think reversing down a memory path as an option either is ideal. Too many things for the trimmer to potentially snag on in reverse and also the limit of its reach is very small on reverse. So it will potentially hit the limit angle quite frequently on reverse. For dead end type situations, start in an open area, go out of the area and complete the trimming task, then loop around and drive straight back into the open area to complete it. IMHO, it should always just continue moving forward. But Yarbo also has this weird quirk where if you start a plan in an area, it tends to reverse first for no apparent good reason. So this could also be what you are seeing. These idosyncracies ideally need to be fleshed out.
Hi there, thanks for sharing your feedback. I understand there is still room for improvement when it comes to the Memory Path behavior, especially regarding the reversing logic. We’ll continue following up on the community’s ideas and feedback around this topic with the team.
It’s not just Memory Path. It does all sorts of unneeded twitching and carrying on to start plans, aligns it’s start angle at 90 degrees then zero turns into the correct heading. It’s gotten much worse since the winter update.
Agreed.
okay thanks. happy. it’s a bug yarbo reversing on the memory path. yes there is room for improvement but am really happy with the trimmer attachment overall. 