VESC Firmware

Hey

Using some 75300 since beginning of the year, i´m not able to update them to newer FW then the actually ones :

HW 75-300-R3 : FW 4.2
HW 75-300-R2 : FW 3.62

Using actually VESC TOOL 2.06

Having hard times setting up bigger motors,

Inrunner 5000gramm low KV (under 50) and 4000gramm Outrunners with 50kv

The R2 only works in sensored BLDC with the Inrunners (QS Motors 1000W)

With the Outrunner (APS120) the R2 just run in FOC, but having Overcurrent Faults

Unity - VESC 5.1 - Internal Uart

Is there a way to set the BAUD rate or configure the internal uart with VESC 5.1 or another method?  I am trying to use the internal uart for my DAVEGA and I think it maybe the Baud Rate that I need to change.  This is typically used for the Bluetooth module but I have a module currently I'm using with my trampa remote in the Standard Uart Port and no longer need the internal Bluetooth I'm trying to setup for my DAVEGA telemetry. Thanks

Hello guys,

I just purchased a dual Vesc from Trampaboards, a HD60.

Upon updating the FW I get the message, Vesc Tool does not include FW for your HW.

When I attempt to setup the motors in FOC mode, it only rotates one motor and disconnects.

This board is a replacement for my Filpsky dual which was fine but not so reliable.

Any ideas what the problem could be?

Hi guys,

I have a problem with a choppy signal on FOC and wrote about it here:
https://vesc-project.com/comment/6569#comment-6569

No idea why the VESC signal looks so choppy - is this some hard- or software limitation?

Hello 

Hello,

I am a beginner in software coding, so i would need your help. For my application I need the motor controller to shut down the pwm signals if there is no signal from a RS422 interface coming in. This means, the motor controller should not work, if this signal is not at high level. 

Where can I implement this the best? I use the Axiom Hardware configuration with a STM32F446 uC. 

Would be very nice, if someone could help me with this. Thanks in advise an best regards,

Florian

I've been trying to change the RX/TX pin assignments for the NRF52 code from Ben's Github repo. Unfortunately I think I'm doing something wrong because the code doesn't work after I compile the code and flash it to the NRF52832  module. I have installed the ARM and  NRF52 SDK dependencies and also changed the IS_52832 variable in the makefile to 1.

Hi all,

I've recently spent some time figuring out how to unbrick the VESC6-MK-IV. To help others with the same problem, I'll share the procedure of how I did this, as there are many ways of doing this according to the forums. My current setup is that I have an STM32407 Discovery card that can be connected to the VESC6, and I used the ST-Link together with the STM card to write the firmware to the VESC. Most of the procedure can be done using an ST-Link dongle instead.

Procedure:

As i needed a  complete overview over all can Messages, i started doing things properly following an accepted industry standard.
So i started building a dbc file for VESCs (and ofc. all other projects with the same or similar Firmware....). 

Right now, there are not all messages in there, but the rest will follow over the course of this week. Also for now, the messages are only in there for one VESC with ID 1.  So, it is far from done, but i wanted to share it anyways. If there are any thougths about posible improvements, please share them.