VESC Tool

Hi,

I have two Maytech ESCs (came with hardware 4.10 firmware 3.3 upgraded to 3.40) two Maytech Hubmotors with hall sensors, and a 10S Lion battery.

The specs are:

Motors:
Size 90mm
Voltage 24-36V
Max Amps 22A
Max. Output Watt 800W
Resistance 0.557‐0.577

The motors are connected to the ESCs with a hall sensor adapter (and the three phase wires).
 
Battery:

Koowheel 5500 mAh battery
Max Amps: 30A

I tried running the motor setup wizard with these settings:

The new VESC Tool is out. I am currently working on my school project and I would love to make some modifications on VESC Tool for android. However I have some problems on setting up the QT development environment.

It would we very helpful if someone from Vesc project could finalize this page. https://vesc-project.com/node/310 

Thanks for reading

Sasan

I'm using VESC Tool v0.91 and custom VESC board with hall sensor inputs.

I spin the motor at constant RPM with my controller and all the real time data shows up in VESC Tool very well, no problems.  RPM, Duty Cycle, Motor Current, etc.

When I go to the Sampled Data tab and try to click "Sample Now" the loading bar goes to about 30% then stops and never does anything.  I've tried all the other buttons too, stopping and starting the motors, changing RPM.  The BEMF tab is the same.

Hi guys,

I have had a little problem with foc motor detection. When I measured the flux linkage the motor had trouble with spinning, because VESC use parameters that are good enough for a lot of motors but not all.

Wouldn't it be awesome if we could give some parameters such as KV, motor poles and so on to have a more smooth flux linkage detection? And it's not that hard to implement.

Thanks for reading!

Sasan

*The 2019 VESC-Tool App is about to arrive!**

For 2019 Benjamin has packed a nice present for the community.
On Saturday we will see a release of the Mobile VESC-Tool in the play store.
The new VESC-Tool is super convenient to use and is prepared to work seamless with upcoming hardware releases. Everything is fully automated and in consequence the complete setup is now nailed with 3 to 5 clicks only. Setting up a dual or quad drive takes just as long as setting up a single VESC.

Hello,

I have recently started to use the vesc-tool and a brushless motor. I am getting a fault_under_voltage code. I am still new to bldc-motors(and any other e-motor :D), so it is not obvious to me, which voltage that is. Is there a documentation for the fault codes or can someone explain the code to me?

Thanks for your answers in advance and have a nice evening

Joe_Lowtech

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?