Logs send before and alter thé probleme.
Thanks
yes for FW. I just tested my different modes with the Metr.at module that I had before: no problem after several mode changes …
I just re testing with metr.pro: first mode change … master wheel lock ID0 … re setting😡
I doubt @rpasichnyk built his own firmware. Otherwise it would be easy to publish a new one that solves the Oreo problem. Everything he added must either come via AT commands or is coded into the App.
@Pimousse yeah my wording was probably not perfect there But since it worked before the oreo update I kind of see the problem on the Android side for being too strict where it might not have been necessary. When you update only one part and the system does not work anymore after the update you always see the problem in the thing you changed no?
check post #94
The official VESC Tool does not support BLE on Windows. You can use the compiled version from my GitHub. There are no source code modifications, just slightly different version of Qt library. I hope Benjamin can use the procedure that I described to provide BLE support on Windows in the future.
A lot of users still prefer Win 7 over Win 10 and they will use it till 2020. I bet that Microsoft will extend their support even longer.
So the VESC-Tool should be able to run on
Win 7. Locking out users is no good idea. Software should be compatible with active and used operating systems.
The mobile VESC-Tool works quite well for wireless configuration. In addition to that you can use your smartphone as a bridge between your computer and board.
Personally I prefer using my android tablet that has the full VESC-Tool installed.
Plenty of options on the table already…
You’re 100% right !
So let users go with Metr Pro and all other “third-party” Hardware / devices / app / (i)OS.
This is a reward for the VESC project, not a theft.
Placed an order earlier today for the Metr Pro with internal antenna - fingers crossed I managed to get in on the current batch Thanks - you guys rock!