Suddenly as of this morning, my Lymow One Plus throws “ERROR_MCU_COMM_LOST (E37)” when I try to start mowing a zone and then seems to be completely dead until I pull power and fully reboot the thing. Has anyone seen this one before? I've submitted a ticket but looks like those are about a week and a half out on responses and I'll be past my 30 day return window by then so trying to get this sorted to see if it's even worth keeping the thing...
Issue description:
- The mower leaves the dock and begins navigating toward the mowing zone
- After it does the deck height calibration and then moves a few feet, it stops and throws ERROR_MCU_COMM_LOST (E37)
- Immediately after the error, the mower becomes completely unreachable/offline in the app
- If I force close the app on my phone and reopen it, the mower actually disappears entirely from the app
- I cannot reconnect to it at all until I remove power (battery pull), reboot it, and re-enter the PIN on the mower
- After rebooting the mower and force closing/opening the app, it connects in the app and behaves normally until I try to mow again and the error repeats
- The issue is consistent and reproducible on demand
Troubleshooting already attempted (none worked):
- Rebooted the mower
- Removed battery, waited 30 minutes and reinstalled battery
- Cleared errors in the app
- Force closed and reopened app
- Logged out and back into app
- Cancelled task in app and restarted task many times
- Tried mowing different zones
- Tried manually driving the mower into a zone and then initiating the mow
- Performed a firmware OTA update that was available
- Confirmed RTK positioning is updating in app
- Confirmed Wifi/4g/Bluetooth all appear to function in app
- Confirmed manual driving works
- Confirmed manual blade activation works
- Confirmed blades spin freely/easily by hand
- Confirmed blades spin freely by hand
- Confirmed there is no debris in the cutting deck
- Confirmed it can still dock itself
- It has not been in any recent rain or water had exposure
- Outdoor temperatures are ideal (~70°F)
Seems to me like a hardware issue where one of the obstacle sensors maybe isn't responding which is causing the whole thing to shut down and not recover? That's the only thing that makes sense to me considering all of the manual functions still work fine