Starting Tips | Ask Questions | Introductions | Categories

HELP: VESC was working fine, now wont connect or work!

So I recently made my new board and everything was working fine, I set my vesc settings in vesc tool, set one and slave and the other as master and connected them and set the appropriate settings: motor max: 60 amps min -40 Bat max: 30 min: -20, the battery cutoff, set the max erpm to 60000 and -60000, took it for a ride and everything was working perfectly, got home unplugged the loop key and came back to it 5 mins later plugged loop key back in and remote wouldn’t connected so I opened the board and plugged in the vesc and now it isn’t connecting to the computer, either of them! I tried using different cables unplugging and plugging back in but I wont connect to the pc, please help.

My boards specs: dual flipsky vesc 4.12 dual sk3 6364 190kvs 5ah Turnigy 25c lipo

Any ideads @dareno or @Winfly? Help would be appreciated

Who dares summon me?

Whats the lights on the vesc telling you?

3 Likes

Do the led turns on at all? And is there a red led lit up ( red is fault)?

there is a blue and a green light lit

Well that means the VESC still turns on. Do you have a 4.20 dual or 2 singles?

2 singles over can-bus

if you switch it off, disconnect canbus and just power one vesc up with the receiver, does it then work?

also type fault into the terminal of each vesc and post the results

the power cables are wired together so I cant only power one but I disconnected them from canbus and tried one but it still wont connect, and I cant check terminal for faults because they wont connect.

welp, i tried i got nutting

I just don’t understand because they were just working

Could be that either you USB cable is broken. Or the USB port is broken. Try wiggle the USB port to see if you get connection at some angle.

tried multiple cables, on multiple ports, across multiple computers

@Winfly @mynamesmatt now when I try to connect it, it says nor firmware read version even though it had firmware when I edited settings before. How can firmware just disappear?

Heres is the code from console when it connected:

2018-11-30 11:04:05: VESC® Tool 0.94 started 2018-11-30 11:04:05: Status: Not connected 2018-11-30 11:07:37: Status: Connected (serial) to COM3 2018-11-30 11:07:37: Status: VESC Firmware Version 3.38, Hardware: 410, UUID: 3A 00 28 00 02 50 48 47 50 34 37 20 2018-11-30 11:07:38: Status: MC configuration updated 2018-11-30 11:07:38: Status: App configuration updated 2018-11-30 11:08:08: Status: MCCONF Write OK 2018-11-30 11:08:08: Status: MC configuration updated 2018-11-30 11:08:09: Status: APPCONF Write OK 2018-11-30 11:08:17: Status: Serial port error: The I/O operation has been aborted because of either a thread exit or an application request. 2018-11-30 11:08:20: Status: Not connected 2018-11-30 11:08:40: Status: Connected (serial) to COM3 2018-11-30 11:08:40: Status: VESC Firmware Version 3.38, Hardware: 410, UUID: 3B 00 26 00 02 50 48 47 50 34 37 20 2018-11-30 11:08:48: Status: MCCONF Write OK 2018-11-30 11:08:48: Status: MC configuration updated 2018-11-30 11:08:49: Status: APPCONF Write OK 2018-11-30 11:08:54: Status: Serial port error: The I/O operation has been aborted because of either a thread exit or an application request. 2018-11-30 11:08:57: Status: Not connected 2018-11-30 11:11:12: Status: Connected (serial) to COM3 2018-11-30 11:11:15: Status: No firmware read response 2018-11-30 11:11:18: Status: Not connected 2018-11-30 11:11:20: Status: Connected (serial) to COM3 2018-11-30 11:11:23: Status: No firmware read response 2018-11-30 11:11:26: Status: Not connected 2018-11-30 11:11:38: Status: Connected (serial) to COM3 2018-11-30 11:11:38: Status: Connected (serial) to COM1 2018-11-30 11:11:39: Status: Not connected 2018-11-30 11:11:54: Status: Connected (serial) to COM1 2018-11-30 11:11:58: Status: No firmware read response 2018-11-30 11:12:00: Status: Not connected 2018-11-30 11:12:35: Status: Connected (serial) to COM1 2018-11-30 11:12:38: Status: No firmware read response 2018-11-30 12:11:16: Status: Not connected 2018-11-30 12:11:17: Status: Connected (serial) to COM1 2018-11-30 12:11:21: Status: No firmware read response 2018-11-30 12:11:25: Status: Not connected 2018-11-30 12:13:03: Status: Connected (serial) to COM1 2018-11-30 12:13:06: Status: No firmware read response 2018-11-30 12:13:10: Status: Not connected 2018-11-30 12:16:15: Status: Connected (serial) to COM1 2018-11-30 12:16:18: Status: No firmware read response 2018-11-30 12:42:55: Status: Not connected 2018-11-30 12:42:58: Status: Connected (serial) to COM1 2018-11-30 12:43:01: Status: No firmware read response 2018-11-30 12:43:04: Status: Not connected

As you can see it connected fine and had firmware, I updated the settings , went for a ride and when I came bag and plugged it in, nothing

Does anyone know what this codes means? @dareno @Winfly

@JohnnyMeduse

1 Like

Nice dodge. I have no clue.

1 Like

@AdamE3399 Can you still see if the device connects to the PC?