Hello, friends. I read Benjamin's serial communication tutorial, but I'm a novice, and I don't need to use the system to read my VESC data. Can you provide me with routines? I use stm32f4, C, and KEIL development environment,thank you!
I understand that the blue LED indicates that DC-Power is present.
But what do the red and green LED indicate?
Hello, friends, my firmware version number was 2.16. When I uploaded firmware to my VESC4 using STM32 ST-Link Utility software, USB could not be recognized by my computer. It was recognized before upgrading. Before uploading firmware, I performed a full erase. The chip address in the software was 0x8000000, size: 0x31. 5cc, 32bit data width, other default settings, I do not know how to solve this problem, can someone help me? the hardware version is VESC4.11.thank you!
Hello,
I'm trying to make an electric bike with vesc 6 (purchased from flipsky) and a 1720w motor. It's based on Tom Stanton's project. I want to have a switch to change between throttle and cadence controls. For the throttle the ADC app works fine, but I couldn't find a way to implement a cadence sensor without modifying the firmware.
Hi all,
Hey!
I am using vesc with firmware 3.56. Vesc tool says that the supported firmware is 3.57. I can't find anywhere that firmware to download. Help? Where can I find it?
Regards, Ron.
Does anyone have an older version of the VESC Tool that has support for FW 3.56? My Flipsky 4.12 single VESC is on FW 3.56 and I can't update the firmware for whatever reason.
Hello all,
Im trying to write a UART library in Espruino for the VESC6+.
Im wondering how if the VESC just spits out UART data or do i need to call a function to get the data over UART?
Thanks
/Gustav
Hi all,
I am working on implementing scalar control and foc control for induction machines, so I am wondering what the recommendations are in order to carry on with the programming. After reviewing the firmware source code, my first thoughts were to copy/rename/overwrite "mcpwm_foc.h" and "mcpwm_foc.c", so the microcontroller-related code could stay and I would focus on the motor control.
Could any of you with more experience in VESC firmware suggests me the best approach, best practices?, warnings are also welcome.
Thanks.
