Hi everyone
I am quite new in all this field, I have some general questions, hope you guys can help me
1. When I enter the "Firmware Changelog" tab in the software I can see that the latest updated firmware is 4.02, right?
Is it work with any version of hardware?, in my case my hardware version is 4.12
Hi everyone
for a personal project I need more features via UAVCAN protocol:
Hi all,
I am currently developing my own hardware based on the VESC 6.
The device will be rather small and so the physical size of the LQFP-64 Package is a problem. There are STM32F4s in a QFP48 Package, which would be a good fit and is still hand-solderable with hot air.
Can you "port" the VESC Firmware to the other package? Will there be enough pins with the necessary functionalities (timers, etc.)?
Memory and other hardware features should be the same, so not a problem?
Bests and thanks,
Jakob
Hallo, ich habe zwei Teile, vesc hw6.41, in meinem Trampa-Board installiert, die über einen Dosenbus miteinander verbunden sind. Leider hat einer der beiden einen defekten Micro-USB-Anschluss. Jetzt sagt das vesc-Tool, dass ich ein Update machen soll.
Hello,
I have the Flipsky High Current FSESC 200A and a Flying Rodeo motor along with the Maytech waterproof remote control. I am having trouble programming the VESC. First off, I've been using the VESC tool for Mac v2.03 available from here.
Says the fireware is 4.2, Hw: 60
Hi everyone,
I just started using Vesc tool few days ago, and I would like to drive the motor in both senses with same duty cycle CAN frame, so for a 0 payload frame I would like a "-1" duty cycle.
I tried to re-load a custom firmware after modifing the code line in "comm_can":
buffer_append_int32(buffer, (int32_t)(duty * 100000.0), &send_index);
by: buffer_append_int32(buffer, (int32_t)((duty+1) * 50000.0), &send_index);
Hello everyone,
I'm enabling the ws2811 inside the firmware, I'm able to compile and upload to my vesc,
Added some print statements just to make sure that the code was executing and I see my print statements on vesc terinal.
But I don't see anything on GPIOB 6, or 7. I tried using channel 1 and channel 2, no luck, they keep stuck around 2.7V.
Im checking the output with mu osciloscope, nothing...
Any ideas?
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.
