VESC Firmware

symptom:

I can run "RL" and "Lambda" detection in the "Motor Settings"->"FOC" tab successfully.  During the "Lambda" detection process, the motor does spin.  

The problem is when I try to

"Wizards" -> "Setup Motors FOC" then, after hearing some sound, "VESC Disconnected During Detection"

I checked the voltage for the MCU, there is no obvious drop during the detection. For my case, it's not a MOSFET related issue. 

fix:

in conf_general.c

Hi just connect vesc firmware based controller to my ebike

I setup my battery amps to 40a as maximum that it can handle 

And vesc rt shows that I draw 40a

But my bms shows that the amps that are been used is like 1a-5a

And of course  the ebike is slow

What I can do to fix it? 

Or what I'm doing wrong

I run the motor configurator

And the input

Is and ebike adc tbrottle

Hi,

I didnt find the usage of the observer gain anywhere else as in those codelines:

https://github.com/vedderb/bldc/blob/2d28ccbb05b442fbd4306cca6fcb5de1925...

I dont really understand how this code affects the sensorless position estimation used for FOC current control.

Hi I was wondering if anyone could help with my problem,

I have a dual fsesc75100 motor controller from flipsky and 2 motors from flipsky (both the same model).

When i connect my controller to a power supply, both blue LEDs light up, but the controller on the right is a bit dimmer. In addition the green LED on the controller on the right doesn't light up - only the one on the left does.

Hey, I'm trying to figure out a way to change the direction of a motor I'm controlling with a joystick connected to an arduino thats sending PPM to the vesc. The issue is that the vesc is configured to accelerate when the joystick is pushed forward and brake when its pushed backwards. Which works just fine, but I want a switch to my arduino that changes the direction of the motor. However since I am simply sending :

"esc.writeMicroseconds(map(analogRead(PotentiometerPin), 520 , 1023, 1500, 2000))"

Hi all, I have a brand new MakerX D60 vesc and it won't connect to my computer anymore. I also have a MakerX DV6 that I was using for a bit, but I switched to the D60 to see how they compare. The D60 worked well for a while, but after plugging it back in to my laptop and VESC Tool, it immediatly reset the vesc to factory values and erased all my settings and values I'd set up for my eboard. I disconnected the vesc and reconnected it to see if it was just a bug, but my settings still weren't there.

Hello All, 

I am trying to drive synchronous reluctance motor using VESC Controller (Flipsky 75200). 

Currently, There is no back EMF in this reluctance motor, which is causing problem while driving this motor with PMSM controller. 

Can we drive this magnetless synchronous reluctance motor with VESC controller. 

I'm open for both sensor-less and sensor-ed control. I have sine/cosine sensor installed on the motor. 

Thanks in advance,

Mandar. 

Could a newbie to the VESC project get guidance on the throttle routines that the VESC firmware employees? Specifically, where to find them in the code base and best practices for modifying.

Background:

OKay so i bought ..well traded a 300$ new drill i got for free for this a  dual fsesc6.6 and it has the sk8 149kv motors but it didnt come with a battery (which i thought was strange) so i got a battery from another board i have 22.2v 8000mah 6s and im not able to get the current firmware to sucessfuly download ...i mean it starts and finishes the download it just says a error message to fast and small to read on the bottom right and then it says i might have to do a bootleg or something firmware so idk ive tried so many things i hope i didnt break anything any tips?

I upgraded the firmware on my VESC to 6.02 while troubleshooting why my CAN Bus wasn't working. I am now trying to downgrade back to 5.03 as I resolved my issue. However, I am having trouble with the archive download of 5.03 firmware in VESC Tool and trouble with making the file after checking out the Github repo and checking out release 5.03. Any recommendations for getting the proper firmware file for 5.03?