thatās a good one
You sir, won me over with this comment. What a great play on the arrogance of modern manā¦
Theyāre redistributing free software with (not) my logo on it!
I canāt even download vesc tool 3.0.0 from the vesc website anymore, and my experiences with constantly getting faults on fw5.3 is terrifying.
Well, we canāt trust the latest firmware. So no one really gives a shit about your opinion at this point, many others are doing it as well for this reasonā¦
Step up or step out Grampa.
VESC-Tool supports old firmware, so you can simply use the old FW if you like.
It makes no difference if you use a new or old VESC-Tool to configure your FW, as long as the FW is supported by VESC-Tool. VESC-Tool actually changes its UX, according to the FW found on the device.
I cant download vesc tool 3.0.0 from the vesc project website. Thatās a problem.
Or, you know, the link to vesc tool 3.0.0 could be available. Why do I have to jump through hoops to use stable firmware?
@xsynatic send us to jail already
Especially since itās unclear which FW version you need for which ESC hardware; vesc tool auto detects it making things easy.
Also hilarious that thereās no V3.00 branch in github, you have to cross check the release date if you want to be sure And make sure the firmware you need was actually built and pushed for that version.
@YUTW123 if trampa continues bothering you about it, you can clone / provide a download for variESC Tool to make your changes, since it has all trademarked logos removed
Because the VESC-Tool will change itself back automatically when it finds older FW.
3.01 will then become like 3.00. VESC-Tool is not static, it changes according to the FW.
The times where you need a specific Tool for a specific FW are looooooooooooong gone.
Having a specific version of the tool is still the easiest way to GET a certain firmware.
We also then donāt need to worry about whether the tool will change its UI or not, because everything is already as designed for that FW version.
This a very painful way to handle things. Since you might have the desktop version and the mobile appā¦
The app in the Google App Store will always be the latest version anyway. In consequence Vedder rather chose to code VESC-Tool to adopt to the FW found.
So instead of having version confusion, Vedder chose to code a smarter software that actually works with all older FW versions.
On a mobile platform, this makes sense. The app will auto update through the native app store and still be compatible with all FW.
On a desktop platform, however, it doesnāt make sense. The desktop VESC-Tool has no built in or external update mechanism. Therefore, for most people on the forums who run FW 5.2, all VESC-Tool 3.01 does for us over 3.00 is look pretty, at the cost of making it harder for us to reflash our ESCs.
If older versions of firmwares for all variants were easily accessible (not only by going through the GitHub commit history), I would gladly use the latest VESC-Tool on all platforms.
FW5.2 is just a few clicks awayā¦
This is the problem.
Is it? Just open a thread with FW versions and linksā¦ Downloads faster than the entire Tool and only consumes some KB on your HDD.
Agreed 100%. Itās nearly impossible to find all the firmware versions with no release tags or anything. You basically have to browse the history by date and hope you get the final release and not something pre-bug fix. Thank skateboard Jesus for the precompiled vesc tool thread.
From 5.03 and on it looks like heās adding each release as a new branch which will help.

VESC-Tool supports old firmware
This is a very bold statement, considering itās nigh impossible for the average user to figure out how to install an older version of firmware from VESC-Tool.
I can open a thread with the links to the FWs at release date.
Then you can simply click the link and you will find the FW you are looking for.
Very simple and only a few minutes of work really.

I can open a thread with the links to the FWs at release date.
Then you can simply click the link and you will find the FW you are looking for.
Very simple and only a few minutes of work really.
Github already has this functionality, you simply choose not to use it. Itās even simpler, and even less work, really.