I’m sorry to hear about the issue you’re experiencing. I’ve reviewed your ticket, and it’s now in the standard after-sales process. I’ll make sure to follow up on it to ensure you receive smooth and timely after-sales support.
Tallman, mine started last saturday, no firmware, just started acting up after it had mowed for 3.5 hours and was going back to recharge. After working with support, I was just told they have to send me a replacement unit. So I am in the waiting period of 5-7 days. Meaning my guy will be out of service for almost 2 weeks. What I did in the mean time, was to change my pathways height to match my section heights to reduce the amount of times it had to change the mower height. Then after multiple attempts to make sure nothing was blocking the blades, mower height, etc. it would start working. It seemed to be after a period of cooldown as I was working in my garage where is was shaded. Then once they would stay at a height, I could go mow again. The problem always came back, and it was after the recharge. For some reason (might be user error), when Yarbo would dock it would try and change the height of the mower blades. I didn’t see a way to set the height on the charging dock. The only thing I could do to bypass that issue was to not let it go back to the dock and use the external power adaptor to charge the unit.
I know that is a lot of workarounds, but I mow almost 4.5 acres and every hour counts, as some of my sections take over 11 hours to complete.
I hope you don’t have the same problem, but thought I would share.
1 Like
The blades are lowered when on the Docking Station so you can do maintenance. It’s a convenience.
2 Likes
Or a issue if you have the cutting height error, even though there is nothing stoping the cutting heads from moving. 
1 Like
Thanks for the info!
Man it’s not great hearing others with the same issue. Or maybe it’s good to not be alone idk. This morning I was still waiting to hear from support so I figured I would just see if I could raise or lower the cut height. And it worked fine moved it up let it sit moved it down let it sit no issues unlike yesterday. I sent it out to mow it completed without issue. Yesterday I was getting the error right away and it wouldn’t stop. Guess we’ll see what it’s got for me in the morning.
Chris
1 Like
There may have been some buildup on the tube that the motors are attached to that moves the blades down and up. Maybe it just worked its self loose. Also, if you don’t clear the error, it persists but may go away with a reboot.
1 Like
Yeah I cleaned it, used the air compressor to blow anything out. Cleared the error many times. Did the battery unplug multiple times.
Everything short of taking it all apart. Guess it just wanted a day off.
1 Like
Who knew AI would get lazy? 
2 Likes
My Cutting Height Motor Drive Issue started yesterday mid mow. (Ticket # 100637 blade height motor overcurrent).
I stumbled through the detach/reattach process and the issue cleared.
I didn’t know that was a thing but I “had” to try out the Blower that came in. So, yeah, stumbled into it.
I was able to finish mowing the current work plan and I thought I was out of the woods.
During my troubleshooting, I noticed the cutting disk motors were right proper stuck in place!
There was no “play” that I was used to seeing.
This is what I’m used to seeing as far as “play” goes.
Little did I know…
This morning I started a work plan on the lawn next to the driveway that goes back to my shop. After running for a bit, I saw the alert about the Cutting Height Motor Drive Issue.
I walked over to where Yarbo was resting and check for an obstruction there was no obstruction.
There were however two crop circles under the mower deck.
Based on these crop circles, I can confirm the cutting disks rotate in opposite directions. At least in crop circle mode. 
I don’t think you get those at 2.7 inch cut.
I shutdown Yarbo and removed the cable to the mower. I then restarted Yarbo and he noticed there was no module.
I shut him down and reattached the cable and powered him up. He noticed the mower and was ready for work. However the mowing disks would not raise or lower and the Cutting Height Motor Drive Issue came back.
OK fine. Yarbo gets the day off. I was getting ready to drive Yarbo back to the charging station when I noticed this neat pattern in the lawn.
Its as if Yarbo bumped the fence post noticed the obstruction and created a new path to get around the obstruction but forgot to carry forward the cutting height.
Clearly after getting around the obstruction the blade height went back to the configured 2.7 inches.
As far as obstructions for the cut height motor. I hosed off the mower and there clearly are no obstructions.
This “feels” like the cutting height motor has been driven to the end stop.
(Ticket # 100788)
@Yarbo-Forum any advice on how to proceed?
In the mean time, Happy Fourth of July to my US colleges. Yarbo and I will be chilling in the shade waiting for suggestions from Team Yarbo.
Ok, I’m going inside. It’s hot out here.
2 Likes
Seems worse than what I had.
I didn’t have noticeable height differences in the yard. The error mostly seemed to happen before or after a mow when it raises the height for the pathways. But once it starts it would just happen all the time didn’t matter if the motor was in use or not. Then it would go away the next day for awhile. I got the new firmware and now the error just comes and goes on its own. Almost like it flickers on/off its odd. But it does allow me to get mows in. Support is replacing the module new one shipped Thursday.
1 Like