Took the boat out with updated app and old firmware on core this morning. It sat in garage with corded charger and is now updated to. 9.16.
Sent it out. It runs it’s track lines between no go zone boundary laps, but still cuts across the main pattern to boundary laps.
Still can’t upload photo from android.
Ohhh lordy, is that frustrating or what, @Deixi? Worked, now doesn’t. Wut? Ayup, been there – a Pathway next to my Dog Pen sometimes works, sometimes doesn’t. So I have three between those Areas now (with my Stubby Deadends to vary the paths taken). Solved.
OK, generally it’s a Pathway thing. The problem is finding it. Probably the easiest way to do that is to create a scratch Work Plan with one Area and see what Areas you CAN start that Work Plan for if on your Docking Station. Repeat 'til you find where the breakage may be. Or move the rover halfway and try creating a Work Plan for Areas out more or back more, and see what Work Plans will start. You can also drive the rover somewhere on your map and hit Recharge. If it fails, you know there’s a bad something-or-other between there and the Docking Station. Try to narrow it down using whatever technique. Eventually you’ll corral this and figure out what is not working correctly so you can re-create it.
(“Find the wolf in Alaska,” if you’re familiar with that ancient computer programming saw.)
So the Android App updated but not the firmware. I know it’s done separately. On the previous version of the App I scheduled the firmware update to happen at 1am.
But since the App updated I no longer see the schedule firmware update option. So when will my firmware be updated? Bug?
@Pappa60 - You update the App manually (which you did), and you update the Data Center firmware manually, so make sure that’s done, too (I found someone today who hadn’t).
The rover firmware is sent out by Yarbo in batches, so you’ll have to wait 'til it gets to you. Make sure your rover is powered up and connected to the Internet (HaLow to Data Center to Internet counts), and make the rover quiet by closing out your App and letting the rover sit as usual on the Docking Station. That’s it. It’s then up to Yarbo’s servers.
You will eventually hear the “Ready To Work!” voice as the rover reboots when it’s been updated.
If the update doesn’t get to you in, say, a week or so (may be just over a week), you’ll need to contact Support.
Yarbo is updating those 2 firmware revs back first. Those of us who got V3.9.10 are at the end of the line this time.
Ken,
Thank you for the detailed reply. I understand that it’s up to Yarbo’s servers to send me the firmware update. My data center has the latest version too.
It just seems “odd” to me that the “schedule firmware” setting would “disappear” after the latest App update, since it was there in the previous version. Why remove it?
Regards…
I do not recall that setting, maybe I never stumbled on it, or maybe it’s a feature for the 2023 Core – or was – and is now removed? Got me on that one!
I’ve seen Yarbo state several times this is available, but I’ve never seen it. I’ve been running beta apps and firmware though so I don’t know if that’s a factor.
It “was” under “Yarbo Settings” / “Version Information” / “Firmware Version”.
No longer there for me with App v3.15.4 with Firmware v3.9.10
I’m really sorry to hear about the issue. It’s not clear yet whether it’s related to the update, so our support team will need to investigate further. They’re currently requesting some detailed information in order to proceed with the next steps. We’d really appreciate it if you could provide that information through your support ticket. Thank you!
We haven’t removed that setting. Since you’re currently on firmware 3.9.10, the latest update is being rolled out in phases—starting with users still on firmware 3.8.18, and then to those on 3.9.10. This is the expected rollout sequence, so the update should reach your device soon. Thank you for your patience!
For me, unfortunately, nothing is working as it was anymore, ticket #100384.
Today I was able to start another area, but before doing that I had to correct map drift. After starting, about 20 minutes into the Job, it was standing in the area telling me it’s out of boundary. Got a notification on the phone this time, pressed resume and it did without a problem.
But it’s now doing strange pathing (red circle}
Regarding the problem from yesterday it does not let me start the map at all it tells me it is not connected anymore. WTF.
That’s the new downhill speed:
Mowing downhill after the update
And, like other said itakes zero turns, although it is set to u-turn:
Zero-turn instead of U-turn
It looks like your pathway from the dock ends in an overlapping area. I’m surprised this ever worked. Pathways cannot start or end in overlaps. Maybe this might be your problem. General recommendation is to start at least 3 ft into an area and end 3 ft into the next area. If there is an overlap, then 3ft past that.
I don’t know what to tell you, but the connections between areas always worked, so they changed something in the update.
Your turning video is showing U-turning into the next cutting path exactly as it should. That is not a zero turn.
@bryan.wheeler - To me the behavior of Pathways with endpoints in overlaps appears undefined. The Pathway may work, it may not. I try it if it’s the best option at the moment, and if it works, GREAT! And the next day? Who knows! It seems to change. This use case needs consistency through definition and some code changes.
Yarbo had some related changes in mind to handle overlapping snowblower and mower maps. I’ll have to dig that out and request an update.
Yes but they’ve stated that it’s not supported on numerous occasions which if done will eventually lead to inconsistencies and issues. They need to make it more clear and well defined, I agree. It should not let you create them this way if it’s not supported and the error message about it should be very clear. Along with the tutorial in the app and the documentation on the website.
Really? What it does now is ruining my lawn, what it did past week without changing a thing was ok. So please you tell me where the difference is.
Overnight I was updated to 3.9.16. When I opened the app this morning the cutting blade overcurrent error message was displayed. I rebooted the DC and the rover before I went to bed because it kept using 4G. After the DC was rebooted HaLow started working, no error message was thrown. I cleared the error this morning but cant run any plans or check for blockages until later today. I just thought it was odd that the error popped up only after the update.
Same thing happened … Marvin the depressed lawn mower didn’t start on schedule after getting an update last night. It couldn’t acquire GPS. I rebooted the Yarbo (Under the gear > Safety Settings). After he came back on line I was able to start a plan. Hopes this helps.
How was it handling area turns previously?
