@dcgero - I remember your snowblower use case and how you dealt with it. Have you considered writing something up with a few screenshots to describe what you did? It would make a great Tip, or I’m sure I could assemble a document with some material from you and find a home for it in the Wiki.
I’m not doing a border setback. There are a couple troubles spots with that about every 4th or 5th mow. Depending on how Yarbo turns he may get a track caught on the fence and I have to go rescue him.
I mow at the fastest setting. He does miss a spot or two but does ok. My wife points out spots he misses that bothers her and I’ll drive Yarbo over to mow them.
As far as GPS signal, I have a couple spots where GPS is challenging. Like North West corner of area 5. That is a metal building. When he gets too close to there it gets stuck, and I remotely drive him to get good signal and send him back to work. I’d say about every other mow in that area I have to drive him. I should look at mow angle and see if I can figure out which angle he likes better.
Also north end or area 3 looses GPS pretty often. The RV sits there and apparently is a good GPS signal blocker. Area 2 with the sliver of a section that goes beside the house, GPS can be an issue there too. But mostly that works most of the time.
As for cutting at the fastest speed, I believe Yarbo slows its pace when the cutting disk motor load goes up. I don’t really have any proof of that other than what I perceive. Try the fastest speed and see what you think.
As for cut quality, I just asked my wife for her opinion of how well Yarbo cuts on a scale of 1 to 10. 1 is crappy and 10 is immaculate. She rated Yarbo at a 7.
I’m not the most particular person about yard mowing. My lines don’t have to be straight and go a certain way with the house or anything like that.
I just want the grass cut so I don’t live in a jungle.
@yarbo-forum Well I was going to start my new try a Mapping Zones out. Trying to work on a great idea of what I thought would really work for me. So dumped my old map that took so long to get up and running to maybe a 50%-75% of what I wanted to do. But now having so many issues after the update, and GPS, RTK, and antennas replacement. The Latency is so unstable. Haven’t heard anything back on when it would be fixed. Can’t remap hardly anything. Should have just stayed with what I had for now. But thought it needed to work better, and the plans seemed like it would cut down on so much travel times from what I was seeing. But I know they appreciate our patience for the inconvenience
I didn’t notice if this was mentioned in any of your previous posts. Your rover should NOT be connected to your home WiFi. If it is, use Forget to disconnect it.
I feel your frustration.
Maybe try the following:
- Put Yarbo on the charger and start charging.
- Shutdown Yarbo
- Remove power from the Data Center.
- Remove power from your internet connection device.
- Re-power your internet connection device.
- Wait for the internet to come back to life.
- Power up the Data Center.
- Wait a minute.
- Start up Yarbo.
- At ready to work, try again.
I know its a lot…
Correct. It never has been. This issue has been going on for two months now. They did a remote fix. It was working great. Was able to map, and do what I needed to. Like a weight lifted. The the update hit. Then they checked after GPS loss and it went diving into the trees, broke some antennas. RTK,HaLow. They sent out replacements, because they said they saw one of the RTK cables was bad. I replaced all, cables, and antennas . Still unstable latency again, just like from the start. So they have all Support tickets listed for them. If they could just go back to whatever it was that fixed it. It would be a happy day.
No @yarbo-forum @ken.w.gregory @bryan.wheeler it’s really not. We’ve been beating this dead horse for awhile now. This really is how I start my day while having coffee now. That’s a shame it has to be that way. Trust me my wife tells me the same thing. Just hoping this nightmare gets better soon. But thanks again for everyone’s help really.
I overlap most areas by about a foot. Then the pathway from one area to the next is about 5-6 feet long. If you park in the area furthest from the DS and select recharge and get a “cannot find pathway” error, the path was not long enough. I only have one short pathway from the DS - to the area in front of it. Which in my case is a paved snowblower area, so there is no wear out the grass issue from all the turns.
My snowblower areas are a little messed up because my first two cores failed and I had to remap twice. By the third time, I reached “just get it done” mode. At that time, we could not edit areas, so they look like the Yarbo was drunk. I haven’t bothered to fix them yet because they work fine as “pathways” for the mower. Will clean it up and post something.
I recall reading your “remote fix” post previously with support indicating it might not stick and the problem might return. I didn’t see anything that indicated what the corrective action was. Does support plan to reapply whatever fix was used previously? I’d sure be curious what exactly they’re changing since The DC has wired access to you your internal network.
Same here. They didn’t say anything about what they did or anything that indicated what the corrective action was taken. But I’m thinking with that update it killed it. It really seemed to be working normally, I was able to get more than 20-25 feet away from the charging pad without losing GPS. Because the latency had calmed down to 1, instead of climbing, and restarting over and over. Seems many have been having lots of issues.