This is my dual drive 6" mini AT. Running flipsky 6355 190kvs and dual 4.2. Rode it for 12km in the morning without any issues.
As I was about to ride home after work. In the first few minutes I rode up a tiny kerb (1" or so). Once I cleared the kerb my drive started to cog and sputter.
I had a Bluetooth adapter so I went in and try to see what’s wrong. One of the motors just refused to turn properly any more. FOC detection was wonky, hall sensor would not even detect. Wires were intact and didn’t pop out. Almost certain the motor itself wouldn’t have been impacted because of the clearance with 6" wheels.
Now even with the motor running sensor less it won’t spin properly.
Anyone knows what might be the root cause?
Will try to disect it further on the bench but would be good to know where I should be looking.
I would take the motor appart and have a look inside. sounds like your magnets are the source of the problems, or at least could be.
If this is the case will the motor spin by hand freely?
well I guess it depends on alot of factors. if the magnets shattered or not and if they damaged anything else inside or not. when you open it don’t try to force a screwdriver into the motor to pry it open. because that can damage the windings when it slips… been there done that. just get rid of the sir clip and open it carefully.
have a look and see if there is a retaining ring for the magnets or not, glue them down if not.
Ok this is weird… So on the bench I removed the wheel gear so the motor is free to turn unobstructed.
FOC and Hall sensor detection now seem to work, but the motor just clicks when firing up and doesn’t turn at all.
Try removing the can and checking out the inside if anything seems off
Also try another motor on that esc. Careful though about trying the motor on another esc in case the motor’s bad, could kill the esc.
Hmm also try swapping ppm cable.
Maybe the wires are loose, same thing happened to me with this one prebuilt with a kicktail
So i ran a few more tests.
For some odd reason, motor detection no longer works, neither BLDC or FOC. Either bad detection (BLDC) or R is 0 (FOC).
The red light on the ESC also blinks when I try to run the detection.
Swapping to another motor results in the same problem.
Now I suspect the DRV is blown, how exactly this would happen is beyond me. My only idea is that it was something to do with traction control (it was turned on).
Anyone else has any ideas before I swap out the ESC for a new one?
checked, and re-checked… wires were solid…
Oh and terminal says FAULT_CODE_DRV
So motor didn’t die? But the VESC?
Seems to be the case… Yes
Nope… I swapped the motors around (known good motor to bad half of esc first)… Same problem…
Swapped motor on bad side to good esc side. Motor detects and works just fine…
So it’s basically a dead DVR or something else on the vesc. What I don’t understand is how this would even happen considering how slow I was going and the tiny obstacle I rode over.
I am certain my ERPM limit was set to 60k. Traction control was on if I remember correctly.
The moment I cleared the 1" kerb, the motor started to cog… Then the more I tested the worse it got until now where I can’t even get the motor to detect…
I don’t even know how I managed to get it to detect on the bench last night.
Do DRVs fail slowly like this?
Drv error does not alawys mean a dead drv, failed detection will cause drv error in the terminal
But don’t get your hopes up
I’ve blown a random drv chip like this on a focbox I just had the drv wizzard fix them.up
Is it possible that maybe clearing the 1in curb was enough of a jostle to cause something in the vesc’s pcba to fail?
What else can cause failed detection?
No idea to be honest… Every thing looks intact visually