Both 3.100 and 3.101 are supported, make sure you have the latest version of the app v.2.2.37. I also added support for them in Perimetr as well as original fw3.38.
Other nice addition is Portuguese translation contributed by @Pedrodemio. Thank you very much!
Awesome! I did see there was an update after I posted this - will check it out in a bit
Edit - just checked and it still wasn’t working - well it was reading battery but nothing else, seems it works in standard baud rate 115200 as once I changed that back it came good!
@TehAtheist I’ll check it out, thank you for details
@Pimousse Yes, it’s unfortunate HM-10 Oreo problem. I am working on this.
@Pedrodemio oops , I forgot to add one thing, it is fixed with v2.2.38
@rpasichnyk I saw that the Wh calculation was corrected (I didn’t notice it was wrong). Does this change affect previous records? I swear that the range test of my board was 350Wh used, but now I was looking and it is 377Wh
If now it’s correct than that’s great, since the theoretical capacity of my pack is 380Wh
@rpasichnyk I think I found another bug or something like that, look at this record
You can see by the GPS data that on 17:31:27 I stopped and at 17:33:00 started moving again (Watching a nice sunset), but if you look at the current data it’s all zero long before I start moving again
Same goes for the top speed of 40 km/h, that according to GPS occurred while I’m stopped lol!
It appears that the GPS data and Bluetooth data are out of sync, I will look at older records to see if happening in other occasions, this is my first ride after the last update
Cheers
EDIT: Just looked at older records, they are all in sync
I don’t know, but for looks like VESC was reporting some false data back to the app. Like negative duty cycle, how is that possible? What VESC firmware do you have?
Hi @rpasichnyk, a quick question I hope you will try help me with. I’ve been using your module for more than a year with my iPhone - works perfectly! Now I have bought a Kingwear 88 watch that runs a full Android 5.1 and tries to connect to the module. It does find it and connect, but it keeps disconnecting and reconnecting in an endless cycle. Do you have any idea why that may be? To be honest I have absolutely NO android knowledge, so if it’s some kind of basic setting I should change, I’d love to try it out! Thanks
@rpasichnyk@Pedrodemio
Negative duty cycle can happen if you move the board backwards. Like if you’re standing and moving the board back and forth under your feet. I do it all the time which is how I know lol. You were probably doing something similar.
E: it doesn’t mean the command is negative, but the feedback is.
You could add throttle position to the record and that would tell you the difference between command and actual. Could also be useful for throttle tuning.
The problem is definitely gps/bt data being misaligned. You can see in the first minute of the file, your speed is zero yet your gps is moving. Same thing at the end of the file, GPS stopped before bt data did.