A new notification for me:
Interesting…
Yep. I’d call that out of bounds.
And by quite a bit…
We don’t mow over there yet Yarbo… To much trash over there for you right now…
I’ll speculate that Yarbo lost GPS out by the shop. It’s a metal building.
And continued (for too long) on cached data.
I believe the loss of GPS in the new firmware is quicker in halting travel than the old version.
Still waiting on the new version…
Yawp, check your GPS diagnostics. I have been calling this the “GPS Threshold” issue where it’ll go far too long when it really shouldn’t.
Mine decapitated a baby maple and went at my forsythia, then it stopped just short of my road. (The plants aren’t a big deal, but the rover doing any damage is.)
GPS is “different” in the latest FW/App combo, where it won’t go green for longer or requires more of a move into open GPS to get it green – but, hey, that could be my imagination. I haven’t tried my mower in the Area where it ate the baby maple to see if the rover won’t go out of bounds now. It’s an area with bad GPS spots, pretty reliable for seeing that “GPS Threshold” issue.
White - boundary, Red - where it went that day. Then I got GPS back and in less than a minute it went out of boundary at the road. eek!
Yikes! Stay out of the road Yarbo!
Thankfully it’s a private road, but the traffic is heavy for what it is. Who knew 8 houses had so much car/truck traffic! I put cones out when Yarbo’s “intentionally” near the road, but Yarbo takes its life into its own hands when it goes rogue.
I have to try that bad GPS Area again, maybe this afternoon, to see if anything has changed in the new firmware.
