Hi! I want to modify actual firwmare on my vesc in order to implement a particular communication protocol with my pc. So I downloaded default firmware from vedder's site and change some lines.
Now how I can compile it? Once compiled, can I upload it with bldc tool?
Using the VESC tool, I updated my 4.12 Flier VESC from 2.54 Firmware to 3.34 Firmware. The update was successful (according to the VESC tool), but now the VESC will not respond to input from the controller. The VESC was communicating fine with the receiver until after the firmware update. I have tried a few things to troubleshoot this, but no success.
Transmitter/receiver –
Hi there,
i'm new and i own now two vesc 4.12, soldered by myself and flashed today a bootloader and firmware through the stlink v2. After updating the firmware with vesc tool free it tells me that i got hardware version 410 but on the pcb stands 4.12. So it have to be HW version 412 or not ? What did i wrong.
have a nice weekend
Hi not sure if I'm posting this in the right topic. My experience with can bus communication is from the automotive industry. While I never had to spend to much time diagnosing can bus issues I remember that the harness was always twisted pair. I never see it mentioned with the Vesc esc though. Is a twisted pair not needed with the short harness length? Is crosstalk not an issue? I'm getting ready to wire up dual Vesc 6s on a longboard and was wondering if I need to twist the wires or not?
I am trying to work out what dumb thing I have done.
I bought an assembled and working VESC. I wanted to create a custom firmware so followed the instructions with the example on vedder.se, and uploaded it with the STlink
I first used the default ubuntu 16.04 toolchain, but have since upgraded using the instructions here
http://vesc-project.com/node/310
I have since gone back to using the vanilla version from the github repository.
I am working on custom board based on VESC6 for 200A+, but it is not managing to track the motor position properly.
The board has 10k pull down resistors on the mosfet gates which I think are causing a voltage offset on the phases.
This means the absolute voltage on each phase does not go below 0 when the motor is free running. So I tried turning the motor with a drill and the BEMF plot looks nice but the tracking oscillates between 45 and 65 degrees.
Hi!
I'm new to VESC and have some troubles to get the right data when using PYVESC over UART. When I loop thru the GET_VALUE response package I get ok variable names but the data seems wrong. Could some one please make sense out of this?!
Hello everyone,
Connect your VESC (FOC mode & Hall), enable RT and watch the tachometer. It will change of course when the motor is moving, mut its value will also change when you do a Full Brake or Stop and turn the motor by hand.
Except when you turn on handbrake and turn the motor by hand. Now the tachometer does not change.
Would be good if it does, because then you know that the handbrake level is not high enough.
I tried to locate the bug in the source code but failed to find the appropriate line.
I have two new VESC V6.41 that I am using to replace an older VESC V4.10. The setup includes a 63mm Alien Power Systems Motor connected to the VESC powered by a 6 cell 5000mAh Lipo.
