VESC Firmware

So I have a 75100 pro v2 controller and was using a vx2 remote and had the motor running with this set up before using the vesc tool. I was watching a tutorial on how to use the vesc tool and the first thing they said to do was to update the firmware. After doing this I no longer got any response from my remote, it seems like it is still paired to the vesc but I cannot accelerate or anything.

If anyone has any ideas on what i did wrong, some help would be greatly appreciated.

Hi,

Does someone use firmware V6.06 and VESC tool V6.05?

I built and upload the bin file, but VESC tool couldn't read/write motor and APP configuration.

Does someone meet the same problem?

I got the latest firmware from github, https://github.com/vedderb/bldc, and VESC tool

Hi there

I have a wheel :

And Controller:

All is installed and with a servo-tester the wheel drives "somehow"

I donloaded the VESC-tool, connected it and got mnessage, the FW is too old.

I updated it and got message 

fisrt  i know , it need to 

1. Build and flash the bootloader first in stm program ,then  bootloader again  in vesc tool

and then  wen can find 60 in hardware .  and choose fw.

but  how !!!!!!!! to get the first bootloader for 60....

Hello everyone,

I am currently designing my own vesc hardware.
Now my question is, if the voltage readings also have a plausibility check, similar to the current measurements, implemented in the firmware? So that a disconnected or stuck sensor signal can be detected by the firmware or do I have to safeguard against such failures in hardware.

Hello to everyone! I have Enertion Raptor 2.0 that I had to replace the remote since the Nano-X on/off switch broke. I purchased a Flipsky Remote VX1 with the receiver and installed it. It works but with an issue.

The motors are braking without input. The wheels free spin only when I apply lite power. I guess the signal must be calibrated.

I download VESC and connect to the original Raptor 2.0 (dual) focbox. The software claims that my VESC has too old firmware, possible 2.80 and for that only limited communication is allowed.

Hi,
I'm having issues with trying to program my vesc. I don't know where to start and support wasn't helpful, just sent me a video from 5 years ago.
Any help would be appreciated. TIA

Hi, I have a Flipsky 75100 V2 with modified R005 shunts

I can see this specific version was added in "bldc /hwconf /flipsky":

But it's not showing up on the tool in the compatible firmware list:

How could I load this firmware to my VESC?

(Sorry if this is a stupid question, I tried to fix it by myself, but I'm running out of ideas)

Based on the documentation , you can send all the commands specified in commands.c by dividing the command over multiple frames. My question is how to format the frames? My understanding so far is to send a frame with the id: COM_CAN_FILL_RX_BUFFER << 8 | CAN_ID and then send another frame with the id COM_CAN_PROCESS_RX_BUFFER << 8 | CAN_ID to process the command in the rx buffer.