Hi all,
Firstly, I would like to congratulate and thank Benjamin on how much progress he is making, and his hard work with this amazing open source motor controller platform!
I stupidly corrupted the bootloader on my new VESC 75/300 :(
Hi,
I am looking for a motor controller or to modify a motor controller to operate a very low inductance motor at high voltage.
The motor is a 5-10uh motor, and I intend to operate it at around 180-200v~
With such a low inductance, with most controllers, current decays to 0 before the next PWM cycle, leading to massive eddy current losses, hysteresis losses, skin effect losses and the controllers have issues regulating/controlling the current.
Hi,
My VESC is after DRV8302 replacement, because I shorted outputs when running engine. I corrected all pins seperately, they are connected neatly and properly to PCB now. Blue and green LED are on.
VESC tool connects to the device on limited mode (old firmware windows pops on on connection, and recommends to upgrade). When I go to firmware tab I see no firmware's available on the list, and whatsmore in this tab I can't connect to the target although I am actually connected to device, I see connected (limited) in right bottom corner.
Hi Im new to VESC.
I have purchased a Flipsky VESC 6.6 with the firmware (VESC_default_no_hw_limits).
I am trying to interface using B Vedder's (VESC® Tool 1.08).
I am getting an error message saying firmware not compatible.
I need to know if I am using the correct version of B Vedder's VESC tool? or will I have to change the firmware on my new VESC ( which I am reluctant too)?
Any advice appreciated
Thanks
Chris
Hi all,
i want to buy a vesc 4.12 with the firmware 2.18. But i only can find the vesc 4.12 with a newer firmware (i.e. firmware 3.38)
Well, my question is:
If i buy a vesc 4.12 with the firmware 3.38, can i flash back the vesc to the firmware 2.18? Is that possible? And how can i do that?
I did not work with the vesc in the past. So i am very new.
Thank you.
Just as a heads up, we created a pull request to add our virtual motor support code.
With our virtual-motor branch you can engage a virtual motor using the vesc terminal and start playing with it.
More info and fancy screenshots in the Pull Request
https://github.com/vedderb/bldc/pull/82
Maybe someone finds it useful and can't wait for Benjamin to review it.
Hi,
I already mentioned one issue here: https://vesc-project.com/node/859
EDIT: NVM there are additional issues with the timeout code. There are several wait loops that will fail if the WDT is never initialized, those also need ot be commented out. Mod can delete this.
Hi,
I have a Flipsky 4.12 hardware based mini VESC. I did a git pull on my clone of the bldc firmware repo, and then changed the configuration files to uncomment the following:
> #define HW_SOURCE "hw_410.c" // Also for 4.11 and 4.12
> #define HW_HEADER "hw_410.h" // Also for 4.11 and 4.12
When I load the firmware, however, I have no USB VCP.
Any ideas what might be wrong? Did I miss a source config step? If I use hardware 60 I do get USB VCP, so I know the board is fine.
Hello,
I'm currently trying to develop a 60kW motor drive for Emrax 188 motors. I'm in the very early stages of the design process, building a basic block diagram and researching specific part numbers. I've taken a majority of my inspiration from Marco's 150kW VESC design.
Dear all,
i have a Problem with a custom app and FW 3.53:
This is the Custom app Thread
