I just connected my vesc to my board and hooked up my remote. the vesc flashes red and blue then solid blue. when I try to use the remote the vesc flashes green? do I need to do a motor detection.
I will post you some screens from my settings. which motor is it btw? I’ve got the dual 6355’s
And a link for the proper receiver wiring:
Hope this helps
2 Likes
Maybe This will help you. You need to Configure the remote and the Motor, on brand new VESC, or each time you change a component.
@gmcgaffey - you need to do a motor detection! These are not fully “plug-n-play” speed controllers.
follow the directions or youtube video vedder posted up and it should only take a few minutes. Until you do this, you are likely going to have it not work at all, or possibly damage the VESC. So make sure you get it configured for your motor!
GL!
motor detection failed?
check your connectors - swap to a different or shorter USB cable next - retry.
must. detect. motor! Otherwise you have a $100+ paper weight.
OK I feel like enertion sent me a bad vesc
it says under voltage in the terminal
What’s the voltage of the pack you’re hooking up to it? I’d verify with a voltmeter/multimeter
it’s two lipos wired in series. there 5s 5000mah my voltage meter says 18.4v each
that sounds reasonable. 
How about you give details on why you think this? I read “how do i do motor detection”, followed by “it’s a bad VESC”… Hmm…
giving you a hard time (deservedly), but we can help if you provide some detailed steps and error codes.
under voltage - what are your voltage settings in BLDC tool? I configure mine on 12v (lab power supply w/ minimal amperage) - to avoid any possible issue. So configuring should not need 12s 100A voltages…
Where are you located? perhaps someone local can lend a hand?
GL!
I am in Vancouver wa. the absolute max is 130 a
the voltage limits are (max=42v,min=8v)
voltage limits look good. 8-42v should not be giving you any under voltage errors.
using a small single battery (i like the small 1k-1500mAh 3s, or 12v lab power), does it connect up in BLDC tool? are you using the correct ported one in Windows, or did you compile in linux? What firmware and hardware is your VESC? Single or dual VESCs?
I can let you know my motor detection settings for my R-Spec - but that’s definitely not ideal. They do vary and mine are the original Red versions.
Last - i’m in Seattle, are you ever up this way?
I connects to bldc tool on Windows and says firm ware 2.18
there were easily 3 or 4 other questions…
let’s try again.
OK - FW 2.18. what version of the Windows ported BLDC are you using? And where did you d/l it from?
Only a single VESC then?
Did you try a few other USB cables - especially shorter ones if you had a 10ft USB charging cable for a phone…
Let’ shoot for more than a single line response huh? I’d like to help, but seriously we shouldn’t need to hold your hand and do it for you. If this is beyond your ability to follow (more specifically the step-by-step videos on youtube from Vedder), then perhaps you should cut your losses and get a simpler ESC (DIYes is a good one - i’d avoid Flyer/APS), or XERUN/FVT if you can keep 6s or less.
If you did not do the motor detection and still tried to use it, it’s also possible you damaged your VESC. That would suck. Have you reached out to @onloop or enertion support?
I also think there was someone who was willing to do remote support for VESC at some reasonable cost. Likely a remote teamviewer session to help - this might be a good idea. I’d of course see what enertion can do to help first.
best of luck.