After VESC Firmware update, motors not detected?

ESK8 Electronics
1

Hello all!

I am a little concerned since after using the vesc tool to update my VESC firmware, I am no longer able to control the motors. I followed the firmware update instructions to the tee.

(Hardware is 48, and I updated it to firmware 3.34)

I am pretty sure VESC isn’t bricked because

  1. The remote throttle input can be read from the on the screen.
  2. When I spin the motors with my hands, the realtime data shows a change in current.
  3. It reads the firmware update and doesn’t throw any errors.

The things that isn’t working is that it can’t detect the motors. Like when I try to calibrate the BLDC parameters it just can’t detect a motor. I am using Maytech 230kv sensored motor, running sensorless. Not only that but when I use my remote after unplugging the vesc, it does nothing.

Has this ever happened to anyone? Any ideas? I made sure my battery voltage cutoff is correct as well.

2

Post your settings

Go to terminal and type in “faults”

3

The following faults were registered since start:

Fault : FAULT_CODE_OVER_TEMP_FET Current : -0.3 Current filtered : 0.0 Voltage : 45.23 Duty : 0.001 RPM : 6.6 Tacho : 3 Cycles running : 0 TIM duty : 3 TIM val samp : 1050 TIM current samp : 3150 TIM top : 4200 Comm step : 3 Temperature : 330.57

Why the hell does it say its 330 degrees when it’s not. Wow. Maybe that’s the problem, incorrect sensor reading?

4

I havent seen that before, are you running 12s? And check to see if youve blown the mosfet

Hmm bad sensors??

5

Yes 12S, how do I check to see if I’ve blown a mosfet?

6

Id say the easiest way is to look at the actual thing closely and see lol

Check for burn marks and stuff

7

yea just check and see if any of the FET’s look burned at all, post a pic here when you get a chance too

8

All of the FETS look perfect.

image.png480×640 327 KB

9

Thanks for helping me out btw, I really appreciate it.

10

Hmm look really really closely at the pins like reeaaaaly closely, and tb vesc?

If theres nothing wrong then I think the temp sensors are bad, try reflashing your vesc to ackmaniac’s

1 Like
11

The mosfets are looking perfect… I actually rode the board for about 15 miles perfectly before updating the firm.

Sorry I am not to familiar with the term “flashing” or ackmaniacs fw. How do I flash my vesc to ackmaniacs?

12

flashing = updating

  1. Click on this @Ackmaniac
  2. Under his most popular topics, find the one that says something about extended BLDC tool (should be one of the first ones)
  3. Scroll to the bottom of his first post in the thread and download the files.
  4. Unzip the files, install the program
  5. Read his directions in that thread on how to flash FW
1 Like
13

Okay I’ll try this and tell you how it works. Thanks

1 Like
14

Here check out this link

1 Like
15

I followed all the steps, installed the FW, and everything. But I still get

The following faults were registered since start:

Fault : FAULT_CODE_OVER_TEMP_FET Current : -0.3 Current filtered : 0.1 Voltage : 45.15 Duty : 0.001 RPM : 6.7 Tacho : 3 Cycles running : 0 TIM duty : 3 TIM val samp : 1050 TIM current samp : 3150 TIM top : 4200 Comm step : 2 Temperature : 377.04

So I guess it must be the temp sensors… I wish I could turn the temp settings off. Unless you have any other suggestions I think we figured out my problem. I did buy these ESC’s off a friend who got them repaired.

Thanks guys

16

I thought you should do motor detection with fully charged battery? As I can see the voltage is 45.15 not ~50.4V?

17

Overtemp fault indicates to me that you uploaded the incorrect firmware. You may have fried the PCB if you tried running a motor test.

18

Is that typical? Wrong fw blows temp resistor?

19

No but it will cause an incorrect temp measurement.

1 Like
20

It was the correct firmware from the start. I made sure of it. Plus, the motor was never detected so nothing could’ve been fried.