They haven’t posted the source yet but promised to “soon”. If they post the source I can help to submit it to the project. I agree that this isn’t Vedder’s (or Frank’s) responsibility, but rather falls on the MFG. I’m offering to help because I love the VESC project and want to contribute back to it.
I originally thought so, but no it has modified shunt resistances so the regular V6 firmware won’t work.
Since VESC-Tool has a custom FW tab it is easy to install third party FW anyway.
Vedder can’t add lots of FWs that all need testing. The manufacturer needs to do that and supply the FW.
that would be fine, but so far I’ve been completely unable to update the FW using the custom file. I’ll try more workarounds this evening.
Wonky. Hopefully it can get added. Makerx escs are becoming quite popular
Bruh, has a PR even been submitted? Manufacturer should have done that long before the hardware went on sale.
It’s probably months after a PR is submitted, usually the next release cycle.
MakerX’s failure to develop properly, isn’t Vedder’s problem.
so am I SOL on it being auto-loaded by VT? do I have to wait until MakerX releases a new HW or a new VT beyond 3.01?
I updated to the new VESC Tool (Win10) yesterday and while it looks a bit more fancy I noticed an extreme performance and stability drop. It was never the most responsive software but even on my decent gaming pc it takes forever to load. You can’t klick to fast otherwise it starts to not respond or even crash.
Do you need to give it special permissions to work better or is this the new norm now?
When I start the newest version I always think it crashed, takes some 30+ seconds before the main window appears…
The reason is that official VESC Tool is compiled with GCC compiler which is not optimized for Windows. This is also why bluetooth does not work. You can try this version that I built with Microsoft compiler https://github.com/rpasichnyk/vesc_tool/releases/tag/v3.0.1, it starts much faster (6s vs 25s)
You always find a way to impress me lol
Works on M1 through rosetta. I did compile an arm based version but didn’t really see much difference overall and distributing two dmgs just seemed extra work.
Yes I have a MSVC static build together that I will get into distribution I think. It does run a bit nicer.
Is the laggy performance when RT data is enabled or just overall?
I’m running @rpasichnyk MS build and it’s much smoother and has less hiccups than the stock release. it’s so much better. connecting a VESC and detecting FW also doesn’t make my gaming PC freeze up which is nice.
Thanks for the feedback. I experienced a milder difference so didn’t have it as a high priority but maybe it is just something hardware specific. I already did most of the heavy lifting on building Qt static etc so I will see if I can get this into the pipeline.
I do worry that the minggw build might still have wider compatibility across older windows versions and distributing a bunch of alternatives can be confusing to the user. I guess labelling it as windows 10 or something might make it the most obvious. Anyone running windows 8 can confirm that roman’s version doesn’t work?
I have spent the last 4 hours playing around and killing unities.
What am I doing wrong
Edit. Windows was too blame
Mac os. Vesc tool fixed swd flash
Why are you using the next beta firmware (6.0) in the first place lol
Hopefully those ESCs can still be revived by flashing firmware using the SWD method
Why? Cause. I like trying new things and destruction.
I was so confused. I thought he is flashing firmware for HW 6 escs thus fucking it up. But FW6?? So the beta 5.3 just released and BV already made the next one aka 6 available?
