VESC Firmware

This has been a headache. I just intended to play with the VESC and ended up putting 48 firmware on it. I blew my drv chip but was able to replace it, but it still has the wrong firmware and nothing I do changes that. I went ahead and ordered a ST-link v2. Is it possible to fix firmware without it? If I do need it how do I use it? I have not been able to find a pinout diagram and want to make sure im using the most current bootloader.

Hello 

i'm new in the vesc world, and first of all i want to thank benjamin for all his work. vesc is the best solution for a brushless dc motor. second, sorry for my english. i normely speak german.

there are a lot of discussion about foc, bldc, sensored and sensorless motors. all of them has their advantages and disadvantages. foc mode have great torque and is quieter on the start but louses his benefits at high erpm because of switchinglosses (speciali on the vesc 4.xx because of the limitation of 20khz for the mosfet).

// Apply current limits
// TODO: Consider D axis current for the input current as well.
const float mod_q = m_motor_state.mod_q;
if (mod_q > 0.001) {
utils_truncate_number(&iq_set_tmp, m_conf->lo_in_current_min / mod_q, m_conf->lo_in_current_max / mod_q);
} else if (mod_q utils_truncate_number(&iq_set_tmp, m_conf->lo_in_current_max / mod_q, m_conf->lo_in_current_min / mod_q);
}

Hello,

I have been compiling the VESC firmware and have successfully gotten it operating in BLDC mode. However when I try to use the FOC functionality, I keep getting an IACCVIOL hard fault (Instruction access violation). It is reproduced by sending a brake current (any brake current) to the motor, or attempting to run the inductance measurement. 

what is maximum eRPM for the VESC?

I am working on a personal project where I am using a VESC to winch a load. I am controlling the VESC in current mode. I had trouble getting FOC mode to work, mostly because the acceleration/torque were too high and my speed loops would not close. BLDC works well, but I get some very nasty RPM spikes at low speed (<1000rpm) mostly when the motor transitions from one direction to the other.

Hi all,

I'm seeing some bugs manifesting as replies being sent to the wrong channel and occasional CRC errors when using both UART and USB (VESC tool) at the same time.

I think I got most of them fixed, so if you encounter the same issues maybe this will come useful : https://github.com/Flytrex/bldc/tree/serial-thread-safety

It can probably use some more stress testing before it's PR-worthy.

hi,

Has someone changed the firmware to use a PT-1000 temperature sensor instead of a 10k ohm NTC, to measure motor temperature?

I imagine it is only a small change in te firmware, but maybe more people are interested in using different temperature sensors. 

Hello

Iv'e been "designing" an 10s compatible esc so I was looking through the firmware source but I find it hard to get a grasp on where to find what.

I'd for example want to edit:

• Current sense values
• Phase and source voltage values
• Pins for fet hi/lo, current sense, voltage sense etc. (I've not checked the datasheet to see if any other pins is suitable for adc)

Hi!

Is there any timers left on STM32 that could be used for generating PWM to control an external fan in closed loop with pcb temperature? Is this feature interesting enough to be supported in official firmware?

Thanks.