u/DomOnDeck

I got my mower 2 weeks ago. It mowed great on day one. The next day, it was unusable.

For the next 2 weeks, I tried everything (given the lack of support). Power cycles. Base station positioning. RTK positioning. Power supply checks. Resets. Rebinding. Delete and add mower. Remap everything. Backup map.

You name it, I tried it. E15, E16, E21 errors. Weak RTK. Location service init failed. Mower stuck. All of this despite perfect RTK accuracy of less than 1 centimeter.

Today, in a last ditch effort, I deleted everything and decided to start from scratch to see if I could find any connection to what was causing the mower to glitch out.

After starting fresh, I could finally control the mower through Bluetooth.

I completed a mowing zone mapping. No issues. Went up to the base of a tree in the zone to map a no go zone. Finished no go zone. Immediately after completing the no go zone, the mower glitched out. Same symptoms. E16 error. Location service failed.

Go into app, delete the no go zone. I can regain control of the mower immediately.

I tested this in various zones with various no go zones. The size, shape, and proximity to the perimeter of the no go zone didn’t make a difference. It was almost as if the mowers location service completely locked up after finishing the mapping of a no go zone, despite high RTK accuracy.

For now, I will turn on smart obstacle detection to deal with some of the trees in the zones.

But I would really like to be able to use the no go zones. I need them for some mulch beds, septic tank, large trees, wood piles, etc.

I know the no go zones in the app can be glitchy. But has anyone else experienced this? Besides reporting to Lymow’s team and submitting a lot in the app, is there anything else I should try.

I knew from the beginning it was a firmware glitch causing the issues I was having. I just couldn’t put my finger on it.

If anyone else is having E15, E16, or E20 errors, back up your map, delete all your no go zones, and try to mow again.

I am shocked that no go zones are what was causing this bizarre locking up/braking/unable to control manually/error behavior.

Fingers crossed that a future firmware update can fix it.

Does anyone know what could be causing this behavior?

The mower worked perfectly on day one. Today, I took it out to map some more zones. After mapping a large zone, the mower acted like it locked up. I have a good link on the RTK and with Bluetooth. With the mower unlocked, I can see on the screen that it’s getting the input to move forward. But it only limps and jerks along.

One thing I found strange: the first day I had it, I didn’t need RTK to drive the mower with Bluetooth. I drove it around outside before the RTK was even set up. Now, it won’t even move at all until the RTK signal goes below .05 (green icon).

My RTK is consistently .02 or less.

I’ve tried restarting, resetting, rebinding, you name it.

It will try to mow the one zone I had set up. But it gets about 3 passes in. After jerking to a stop so many times it just gives up and throws an E21 mower stuck error.

I can move the tracks with the mower off.

It’s almost like it’s being given a brake signal when it doesn’t need it. Obstacle avoidance set to touch only, so it’s nothing to do with the cameras or sensors.

UPDATE:
I believe we are back up and running after a 10 hour battery reset. Sent out to mow small test zone. Worked fine.

Even after powering back up and resetting by pressing home and power about 10 cycles, I had nothing.

I did a number of things, so I have no clue what ultimately worked.

Toggled handbrake on and off about a million times.

Tried to map a new zone (continued to get location initialization errors).

Picked the robot up and walked back and forth with it about 10 yards in all directions.

Opened debug mode and looked at about every screen but didn’t actually run any tests.

At some point I got back on manual control and the robot started moving and allowed me to map.

Mowed 15x15 small test zone. No stops. No errors.

On to larger test zone.

No go zones breaking Lymow