There was also a loud "hiss" from the high-frequency components of the pulses, that was very annoying, and could be heard over other noises as I rode the trike. With me on it, vibrations would shake the trike from teh low frequency components of these pulses, as if I had an internal combustion engine idling on there instead of an electric motor, when the trike was just sitting still, not moving. I have a cheap ESC and a servo tester coming from HK as my next step.Ī controller should not do anything at all until you command it to, but some FOC controllers do, by continuously sending "random" (not really) "noise" pulses to the phases to get feedback from teh motor coils to determine motor position and rotation speed.įor example, Incememed's SFOC5 controller: When I first started beta testing it, this was a severe problem on my heavy SB Cruiser trike, in that it would actually move the trike back and forth just sitting there, without me on it, a tiny amount. I pulled apart my motor and there doesn't seem to be any issue that I can see. I have no idea how I would have blown a FET simply plugging in phases other than a short somewhere.
I figured what the hell and plugged the throttle into the ADC inputs afterwards and BLDC shows the throttle working through the controller. The middle phase has no resistance to +/-, same as my trail bike controller when I blew a FET a few weeks ago. I didn't get as far as plugging in the throttle because upon plugging the phases in I knew something was wrong.
I was pretty much just plugging in to set it up and make sure the throttle setup worked. As far as I know both FOCBOXes were brand new with default settings. Didn't get a chance to run motor detect until after. I didn't have a throttle plugged in when the damage occurred. I plugged in my battery and the phases and got twitching on the first controller, the weird noise on the second controller. That's exactly what I can't get my head around. Why are the phases being driven while you are hooking up the motor? Throttle settings?Įven if the motor is faulty or a mosfet has failed in short circuit, you wouldn't expect things to blow until you drive the gates by giving some throttle or running motor detection. How do I test this? How easy is it to take apart? Is it just the little c-clip on the shaft? And while I'm at it, does anyone know if there anyone around doing VESC repairs? So I'm pretty sure the motor has a short somewhere, even though it's brand new, but I'm not positive. Now it's behaving the same as the first FBOX. I pulled it out quick but not quick enough. This time the motor made a high pitched whine for a second when the second phase was plugged in. I tested the phases and I plugged in a second FOCBOX. I ASSumed the controller was the issue since I picked it up on ES.
I tested the the phases on the FOCBOX and the middle one tests like there's a bad FET. I can see in ADC programming that my throttle is working properly, it's just not powering the motor. In BLDC Tool I'm getting detection fails on some things and not others. I plugged in one phase wire and as soon as I got the second one in the motor started twitching and suddenly stopped. I'm using an FOCBOX and a Turnigy 6354 260kv. So I finally got around to setting up my Kepler Drive commuter this weekend and I think I killed 2 VESCs.