Coding all this FW is a big task and you don’t put effort into an outdated technology when you have a certain amount of time to invest.
HM 10 is slow and doesn’t really work for reliable FW updates and RT data. Remote connection is out of reach with HM 10.
The community benefits big time from all the VESC software and it evolved a lot in the past years. Everyone wants things to be like this or that, but someone has to code all the FW and software in the end. There is no way to please everyone.
After all it’s free code and capable people can ad support for HM 10 and submit a pull request. NRF is the way to go forward. Bluetooth 4 and 5 are standard these days. All new phones will feature Bluetooth 5 soon. Dual FW update within 30seconds is convenient and precise RT data is what everyone wants. You can buy a cheap generic NRF 51822 dongle on the Bay and solder on cables, flash it and use it. Have a look at Benjamins Youtube channel. Your VESC can program a generic dongle. Another feature that took time to code, for the benefit of everyone…
Price difference to a slow HM 10 is marginal.
I do applaud your companies dedication to furthering what we do, don’t know where we would be without you guys. Just not sure why you would remove support for HM-10 when that function is already there. Like you had to actually make an effort to remove support. There’s no issue with having both options so that people can choose
HM 10 was never supported in the VESC-Tool App. Cross compatibility is another task to code and in a short time no one will use these slow modules any longer. It’s better to put effort into SWD Prog and allow slightly skilled users to make their own fast dongle within 20 minutes. And as a side effect you can rescue bricked VESCs using another VESC as a programmer. This feature alone was plenty of work for Benjamin, but he took the challenge and made it happen. Cheapest NRF 51822 dongles go for 8 euro on the german bay. They are not shielded and not as good as one of ours, but still magnitudes better than a HM 10.
My advice would be to watch this: https://www.youtube.com/watch?v=PFFiVxFHDM4
No worries! Benjamin is a clever guy and when he decides to go for a certain solution, it always makes 100% sense. If you can solder some cables (or crimp some JST wire terminals), you can make your own NRF 51822 dongle with ease. If you want a worry free plug and play solution and support the project, simply get one from us.
Does hm10 module suck that bad? I’m only asking since I have zero knowledge about the subject. But I do have 2 hm10 modules that does the job on my boards.
It’s magnitudes faster. RT with HM 10 is sort of rediculous, since you only see certain fragments of the data. FW update with HM 10 is also no fun. With NRF you can quickly update the FW on both VESCs simoultaniously before a ride. 60 seconds and your done.
