Updated to fw5.0 (or at least I think). When I open the Stormcore app it very quickly goes from scanning to reading but nothing more.
Tried to connect again with the Vesc-Tool with Metr app and TCP bridge but now fw version is not recognized. Not sure if something went wrong during installation of fw5.0 or if it’s because I’m using TCP bridge of Metr (that is not yet supporting it)
FYI: I needed the firmware update of the Metr module to make it work. All good now! Thanks
I can get you Unitys updated and actually have a spare Windows laptop you could borrow to do this with the tool for Windows.
So it’s working with Metr? Did you have to rename the device?
As per instructions I linked above, it works if you rename your metr device to UNITY BLE.
Yeah it’s working with Metr now! I saw Roman’s post to malJohann and renamed the module right away. Now I just need to figure out why I can’t do motor detection but that’s probably for the fw5.0 thread
Put the phone in my backpack, so nothing obstructing signal. Full logging on Unity running FW 5.0 and metr Pro module renamed as UNITY BLE!
Glad it’s working! Putting up a new build in a couple days
@sofu Have you added in the ability to change and setup the Unity/Stormcore through this app yet?
No not yet
Thanks!
Yes, it’s a temporary thing I put in there, it’s actually “engine ticks”, not rpm. I’m waiting on fw implementation before that field will have correct units and values
Small update while I’m working on adding more data breakdown to charts:
I didn’t change anything here this release, sorry. Next release for sure though… this will have more features for sure
I saw the change on the battery setup page though.
What’s this about?
When I saw the battery graphic and I changed my series setting, I thought it was going to fill the rest of the screen with 12 different little battery icons haha.
hah the rest of the view is reserved for more stuff coming soon, so it’ll look less weird after that
