Errr…that might be the case. Will ping you privatelly
Yes I am in the beta programme.
I was finally able to connect the Minnie to WiFi and update the FW. Turns out it requires a password on the WiFi which I don’t usually use as I’m far enough from anyone else.
Currently running FW 0.19.2
Beta phone and watch apps.
Account and settings tabs still cause the phone app to freeze
I accessed the wifi and update from the burger menu.
Pixel watch 2. Pixel 8. Stock ROM.
Update: Turned on “Beta Firmware updates” in settings, which the tooltip says is not recommended for normal use.
Watch works now.
Guess this isn’t “normal use”?
Also just learned how to take watch screenshots lol
How do I calibrate the cell voltage and voltage readings on the megan? Bms is showing 4.17 and is 100% soc but the megan display is off by .05 and showing 90% soc
Looked around in the metr app a bit but couldn’t find anything obvious
It’s currently not possible. I’m thinking of adding a correcting coefficient to the settings though.
It still won’t make things perfect because the error in the VESC voltage reading may be non-linear. Then if you set the correcting coefficient such that the voltage reading is correct in the fully charged state, it may still be off in the discharged state. But, hopefully it makes things at least slightly better.
We should also prefer the voltage from the BMS if available.
Thanks! Yes, firmware update is recommended to perform over Wi-Fi. Otherwise it is painfully slow. You can also enable Wi-Fi hotspot on your phone and let Minnie connect to it for the update.
Thanks for providing the screenshot for the Voyage Connect watch app. I’ll have to fix 3-digit range, I see that it does not fit. If you notice more issues, please let us know! Watch apps are currently in Beta just because there are still some issues, like this one.
I just pushed an updated Voyage Connect 0.10.5 to the Play Store. I was not able to reproduce the freezing issue. If you still have it, can you please navigate to Settings tab (now when I am typing it, may be problematic, maybe it won’t freeze if you reinstall the app?) and press Show Logs, then send to info@voyagesystems.eu)
Its a jbd bms, so maybe ill look into that uart to vesc express to can setup. Not a big deal just a nitpick. The raw aluminum looks amazing by the way. Any luck finding those davega antisink plates? Not a big deal just hoping before I commit
For the android watch app, can there be added a “keep screen awake” feature? Or maybe making a watch face that always shows board stats? Switching watch faces is almost as easy as switching apps.
Any way we can have an option to switch the 24h clock to a 12h one?
I missed that part. Other values already show up correctly (kph or mph depending on the settings), but clock is always 24h. I will fix it tomorrow, thanks for letting me know! I will also elaborate on “always on screen”.
I couldn’t find it anywhere in the guide, how do ride modes work? I set one up to test it out and with a 32kph limit I was able to hit 35kph going uphill.
Also worried if it’s safe or not, will I have brakes if my wheels exceed the set speed?
Modes work the same way as Profiles in VESC Tool. You can set same parameters with Modes in Voyage Connect. The difference is that Modes are stored ON the device itself, if you connect to another phone, all the Modes will be there. And on Megan you can use the buttons to switch between them, which is another convenience feature.
If you experience any problems with Modes, please check that Profiles in VESC Tool are working properly. If Profiles are working, but Modes are not, then it is probably a bug in Voyage Connect and we need to fix it.
Update on the freezing behavior when accessing the “settings” and “account” tabs.
The app lets me access the tabs before my board connects, but if I do, the board will never connect.
If I allow the board to connect first, accessing the tabs causes the app to freeze.
Additionally, when accessing the account tab, the message “signature timed out” appears
Yes, you will of course still have brakes if you hit the speed limit. Best to test the setup on a bench first.
This should be fixed now. The update server was providing incorrect JSON to the app, which it could not parse.
I looked at it more today and found a way to add “keep screen on” to the Wear OS app. I thought everything should be there already, but it turned out I missed some details. Please test with the new version of the app 0.10.9 and let us know if it works!
Thanks again for reporting these problems, it helps a lot!
Thanks! I now fixed that one as well, please let us know if it happens again!
Fixed