I'm a long time roomba tinkerer, but just recently was gifted a malfunctioning Botvac
D85 with a code 3000 error. I've been looking over this forum for the past couple of days and have a theory or two, but my issue seems slightly different than those I've read about in that my motor does not appear to be dead (but may be dying).
As a cleaning cycle begins, the D85 attempts to spin up the lidar housing, but can't seem to get it up to speed. It definitely moves, but its speed oscillates between stopped and (what appears to be) nearly spinning fast enough. This happens several times until the code 3000 error appears.
The odd thing is, if I activate the LDS through Neato Control, cycling the test on and off several times (can take a minute or two), eventually the lidar gets up the correct speed (300 rpm). However, in some cases, the speed doubles to 600 rpm and stays there. This makes me think there is either something failing in the motor that can be overcome (at least for now) with a 'kick start', or that something seriously weird is going on with the PWM controller. In fact, once I've got the lidar working via Neato Control 'kick start', I can take it out of test mode, disconnect from my pc, and have it successfully complete a cleaning cycle. Has anyone experienced a similar problem?
Thanks in advance!