Guys, just started riding on a pretty new board I bought from a fellow here. Riding on the trails at 10-12mph and started feeling no throttle, then the brakes would lock up once every few seconds. Few more minutes, then absolutely no more response at all. Pedaled home and that’s not a good feeling with 2+ miles on this thing. Never abused this board and treat her like a gem. I have no idea what happened. I still see a solid blue LED and then there’s another solid smaller green LED. But the motor does not move. I’ve plugged another RC servo into my 2.4GHz receiver so it’s not that as it responds normally (the RC servo). I got it to rev a few times but never again. I first thought it was just the receiver glitching or something but I even changed out the receiver to a standard RC 27MHz AM receiver and still the VESC is the same. I have yet to plug it up to my PC tonight but will try it tomorrow. I have NEVER actually plugged it up. Is this a common problem with these VESCs? If that’s the case, these things are not ready for the mainstream market. I mean if the user did absolutely nothing wrong, it should not fail within 20-30 miles of light cruising. Getting really frustrated with these VESCs. If I can’t fix this, there will be nomore that I will be purchasing. I’d rather have a cheapo RC ESC with limited easy tuning and sacrifice all the little tuning capabilities but prone to be damaged easily and drop more money into this already expensive hobby.
where did u get it from?
I think the VESC is from Enertion. I can post pictures up in the morning after I clean it up and plug it into my PC. Anyone think it’s fried? I doubt it because motor was barely warm, 65-70 degree outside in the evening. Nothing was really warm or even hot to the touch. I check it because I want to see how far I could ride from a full charge. I barely used up 20% from the Space Cell
well i do know that the red ones from enertion are prone to drv failures and such, so check ur DRV and if its not that just post a couple photos so i can see if anything is fried. Also sniff for burned electronics
willpark16 i sniffed it and doesn’t seem like anything was burnt. None of those 3 capacitors or whatever just hanging seems to have leaked or buldging. Give me a few minutes I’ll take a few shots for everyone now.
Make sure to get a nice shot of your DRV
OK here are a few shots. I don’t even know what version they are. And earlier I was reading posts about people frying their DRV chips with new firmware or whatever…I never did any upgrades, just got it as is. Anyhow here are some pictures.
Connect it to BLDC-tool while still on your board and connected to the batteries.
Activate live sampling
Pull the throttle trigger and watch what happens to the LEDS.
Take a screenshot of the live sampling window
Type “FAULTS” in the terminal pane, this should return a list of faults encountered since last power-up.
Report back with results.
Thanks guys for the help. I’ll try it in the morning as it’s 1230AM here and got to work tomorrow. Hopefully I can revive it with all of your help. Probably can’t sleep tonight!
Are you sure that this PPM cable you are using is ok? Everything you’re describing here indicates a PPM issue somewhere. Vibrations can cause a lot of troubles.
While you have your vesc connected to BLDC tool, you can use the arrow keys to run the motor.
This can potentially give you a clue if the PWM cable or input aren’t working correctly.
@c4Lvin Check your connections from the VESC to the motor and make sure they are still fully connected and that there are no shorts. If any one of those cables is lose, vibration can knock them around so that they disconnect while you’re riding. I highly recommend taping them.
I see some carbon fiber in the background. Your VESC wasn’t resting on that was it? Or possibly bumped into it?
guys, i’m trying to bring an old laptop in the garage to try out the first time plugged into BLDC tool. Would it work with a Windows XP machine? That way I could just leave that old silly laptop there for tuning future e-board projects. @FLATLINEcustoms Yes it’s carbon fiber but the VESC was carefully wrapped in some form of partial bicycle tire tubing and electrical tape with the bottom being double sided tape down so I don’t think it would have shorted out in that way. Let me get this started. Thanks guys for all the input. Do appreciate it.
I got it connected now. But it states that my firmware was too old and is limited? Firmware on now is 1.14. Supported Firmwares (for this version of BLDC tool) is 2.17 and 2.18. Where do I go from here guys? I don’t want to proceed without anyone’s advice. Thank you.
So I downloaded the correct BLDC tool for my 1.14FW and got it going. I guess I can worry about the FW later if that’s the case. Anyways, when I go into “start detection” bad detection result received on the bottom right hand corner. No clue what to do now. Checked all motor settings, etc.
here’s the “faults” from terminal panel:
and the realtime data:
I’d say the DRV chip is fried. Not uncommon.
thanks pal. I asked if anyone can help me replace just that chip to give it a shot. I’m afraid to setup the new one (exactly the same) at the moment. There goes all the hard savings
Did you configure your VESC at all or did you just use it out of the box? The VESC isn’t plug and play. You have to configure it.
I personally did not configure it. I believe that the original owner did in some way. I seriously cannot tell.