VESC Tool

Hey! I'm new to this forum and VESC in general

I'm trying to run sensored FOC mode, but the motor is jerking basically, please take a look at video I've recorded.

My setup is VESC-tool 0.94, VESC: HW 410, FW 3.38, Sensor: AMT102-V

Both, motor and sensor are detected fine. BLDC and sensorless FOC modes are working fine.

Hey there,

Still trying to figure out the best control method for my eBike. From stand-still, applying slight throttle creates a motor stutter. Is the motor not receiving enough amperage from the battery? I'm using Current control on ADC app input. 

All information is appreciated!

My app configuration is UART and my motor configuration is BLDC with HAL sensor. When I use arrow keys to change duty cycle, after a while (usually less than 10 seconds) of moving back between left and right arrow key (-10% and 18% respectively), the vesc motor control will suddenly become unresponsive, causing the motor to not move but the current draw to stay around whatever value it stuck on (the value still fluctuates +- 0.1 A ).

So I'm trying to get a full understanding of BLDC motors and I keep running into how the BLDC tool's autodetection is a bit of a black box. Is it giving me the resistance and inductance of each coil per phase? How does it know how many coils there are per phase? I tried going through the VESC Tool source code, but it looks like it only passes the DetectMotorParam command to the board which does the calculations, so I can't see how it does it. Is there any documentation on what the actual process and algorithm used is?

Hi,

I've been trying to run a KDE 2814XF-515 motor through the VESC. Its for a UAV and to be paired with a 12.5 inch propellor (and put into a coaxial configuration). I'm using a VESC 6 and the VESC tool. Information on that motor can be found at:

https://www.kdedirect.com/products/kde2814xf-515

It's being run at 6S on a tattu 18000 mAh, 15C battery, so I don't think there's any lack of power availability for these tests.

When I was updating the firmware on my 4.12 hardware I accidentally selected hardware version 48 and uploaded the firmware for that version. All motor detections fail. Is there any way for my to fix this problem without a bootloader? I found this post by someone with a similar problem https://vesc-project.com/node/149. I know it was a stupid mistake but I'm just looking for some advice. Thank you

Have an flipsky nrf15288 and can conect to it with vesc tool 0.92 but not on 0.95, guess the firmware is outdated on the module...

dosent any one have the mobile version of 0.92??

or any idée o how to flash the module?

link to the module below: https://flipsky.net/collections/accessories/products/core51822-ble4-0-bl...

I can't change default setting of Beta Value for Motor Thermistor. No mater what I do it gos back to 3380.0 K.

I think that I'm  doing everything correctly.

Developer -> Parameter Editor Mcconf -> m_ntc_motor_beta (Beta Value for Motor Thermistor) -> change from default 3380.00000000 to 3950.00000000 -> save (I get parameter updated in green in right bottom corner) I go back to General -> Advaced -> to check  Beta Value for Motor Thermistor and get the same default 3380.0 K

we are getting the encoder readings from the vesc using basic arduino but the issue is that the readings or anaolg value for revolution is varying in two directions..i.e for  example  if the motor is rotating right for 10sec the encoder reading is 200 and if the motor is rotating left for 10sec the encoder reading is somwere around 300 or 100 .its is keep on varying but not a constant value.What is actual problem??? Can anyone solve this out??