VESC Firmware

I'm having an issue with my flipsky 4.20 dual plus after updating to the newest firmware. First being wobbles over 25 or 26 mph. Also if I change a setting on the app it won't write then kicks my phone off the app (Android 10) and I cannot even connect to the board till I plug it into a computer and do a set up wizard.  When I try to connect to the app it says. "Could not read firmware version. Make sure the selected port really belongs to the vesc."

Any help would be appreciated. Thanks. 

OK, So trying to change some stuff on the firmware I completely broke it..

I can still flash using STLink, it says success but VESC does not show on the serial...

Hello everyone,

let's start with I'm a noob developing rtos systems and st micro controllers, I play around with arduinos, teensys, esp, but nothing close to VESC firmware.

I downloaded the source code, and made some changes, basically updating the ws2811 library. I complied it and flashed on the vesc (i'm using a 4.12 hardware to test) but it did not work.

Is there a way to print statements to terminal, to understand what is going on? 

I'm using an ST Link v2 to upload and flash the firmware. But I also get a segger mini.

Has anyone tried to implement an simple "breaking" light on VESC firmware? 

I'm working on a onewheel now, and was thinking about having ws2812b on te front and on the back, illuminating them accordingly, and changing intensity to have a "breaking" light.

Hi, I just flashed the MK3 firmware to my MK3 (Trammpa), and the IMU plot shows the yaw drifting constantly.  In the gyro plot, the offset is about 2 DPS for Z, and -1 DPS for X.  It's odd that only the yaw is drifting, given the non-zero (and quite noticeable) bias for the gyro.  I tried doing the "figure-8" calibration movement, in case the magnetometer needs to be calibrated for the AHRS use, but it doesn't seem to make a difference.

Does anybody know if the AHRS is supposed to self-calibrate and reject DC drift?

I have attached a generic powerstage to an stm32f407 discovery board, and have gotten it working on the motor drive part.

However, for some reason when I change and upload a non-default motor/app configuration, it will reset to default upon power cycling/resetting the board.

If I do not reset the board, vesc tool will read out the correct value I wrote. bit hte value resets to default as soon as a reset occurs.

I have tried in 2 discovery boards. one with the stlink removed.

Where did the no hardware limits firmware go with vesc tool 2.0 and 3.66 firmware? Now I can't use it since it's locked to 57 volts max and I have a voltage of 58.8 volt when the battery is fully charged. 



Edit:I'm stupid, I hadn't checked the show other versions box...

Hi guys,

I have "60" hardwear (new unreleased torqueboards VESC6's). I'm getting the error saying that if I use FW 3.63 that at high current my throttle could get stuck if using a PPM based controler (I am).

I've never had to upload FW to the tool, I think I found the FW code but can some double confirm for me how I get that into the VESC tool itself?

Thanks in advance.

Hi Benjamin, you indicated in the 'original HW' forum that you would upload the MK3 schematic--which I am looking forward to.  But I am actually more keen to try modifying the FW on the MK3.  Do you plan to push the mk3 FW to the bldc repo as well?

w/ regards

I want to customize the VESC firmware for my custom hardware configuration. I have set up most things, but I have issues configuring the ADC vector. Specifically, I don't fully understand the hw_setup_adc_channels() function and the relationship between vector index, pins, ADC device and channels. How can I configure the vector and the pads according to my needs?

I have SENS1...SENS3, CURR1 and CURR2 (2 shunts), EXT for throttle, SIN and COS for encoder (maybe EXT2 and EXT3?), TEMP_MOTOR, TEMP_MOS and AN_IN (Vbus sense).