So then the answer to “why” is that Benjamin doesn’t want to work on firmware anymore for a while, and that version 4 was killing 75/300 VESCs the whole time version 5 wasn’t released.
Well maybe if @Trampa led with that, then it all would make sense. But the omissions and deflections make them seem really shady when there is an actual serious reason.
Every day I think more and more we should just ignore everything @Trampa says and only listen to @Deodand, @Pimousse, @Blasto et cetera. (Vedder too, but he refuses to use this forum and his forum is on ancient software that is super annoying to use)
So, stop barking please. Because yes, that does appear to be the answer to the “why” question. The question Trampa vehemently refused to answer.
I’m definitely no knight. I just use esk8 for transportation – partially because it’s fun – and partially because it’s the responsible thing to do regarding climate change. If that means people like you feel the need to attack me, then that says a lot about you.
So again, stop barking please, because that’s not my interpretation, it’s what Vedder actually said. I calmly asked “why” a long time ago – and just because some corporation decides to deflect and try to turn this into a PR circus doesn’t give you a license to be a dick.
You should try to work together instead of against people who are actually on the same team as you.
We actually saged a temperature monitored 12s3P Sony VTC6 pack to see if we can overheat it. We couldn’t.
The only option I see is a list of all known cells, so that you can describe your pack in the Wizard, selecting the configuration and cell type. I have a set of data from a lot of known cells to hand. But surely it would need to be updated.
That’s disappointing. One of the reasons METR. Is good is because his addresses an ecosystem that Ben has ignored and offers things the VESC Tool doesn’t. I see no reason why everything centered around the VESC should be open sourced if it’s not the VESC itself. @rpasichnyk has put in a lot of time and effort into METR.
@drone001 may you some day join us miscreants in derail jail
also off topic, i swore off windows some twenty years ago, and live in a windows-free household. now that my own kids are asking for a windows system to play games on, it is rekindling my frustrations from years past
If they really need a game that doesn’t work fine with Steam’s Proton or PlayOnLinux, you could add another GPU to your system, and pass it through to a virtual machine. If they really need to play something with a nasty DRM like Valorant, then make them save up money for their own computer and separate home network, like my brother has done
Brian, I had criticisms and concerns so I literally got on a 15 hour train, last minute, to go have a discussion with Ben and Jeff about said concerns. And imagine that, I came out with lot more understanding and perspective on what Ben is facing and have committed further to contributions on the VESC-Project.
If you are unhappy with how this open source project is developing, then I suggest you contribute rather than loudly complain as a user. I’ve made this suggestion before and you told me you were too busy. Your call.
I think he has helped in many ways, but he also damages the project sometimes (in my opinion) with his over-aggressive stances and forcing everything into black-and-white. Complaints are actually an important part of development, but yes at times it can be frustrating. My number one ask would be just a more polite tone, but I am not sure that is something we will get.
Updating via the PC tool took about 10 seconds and was fairly easy to reconfigure. I lost my temp sensor readings but @Deodand says that FW 5.2 should fix this thankfully.
I miss the push time to power down parameter in the switch settings but that’s very minor and I hope they add it to the VESC tool.
Motor detection seemed much more “thorough” or “comprehensive” compared to FW 23.46. I don’t really know how to describe it but it was noticible. I have not ridden on FW5.x because I reverted back.
I don’t think so but I don’t have my desktop set up right now so I can’t check immediately. I don’t remember seeing any parameter besides the power off timeout setting.
