EX Custom iOS/Android App

[brongle]

Could you take a look at the battery sells if they're all the same or also 2 0's?

His delta V is so low I assume his cell groups are reading normally. Really does seem like your pack has two cell groups out, still very surprising to me that doesn't trigger a BMS fault or other warning on the display.

Everything works well for me on mx

it's strange only with the version in the stark application it shows 1.2.0 in your application 1.2.8 which seems to be true since there were no more updates

View attachment 14543

There is a versions page in the service menu that displays all the firmware versions for things, its possible I'm using the wrong one for the MX series.

 

[AL_V]

Could you take a look at the battery sells if they're all the same or also 2 0's?

I have 2 MX bikes, and I had a couple of slightly lower cells on the one that just got a new battery (but the battery percentage was below 30% at that point).
The lowest one was 3.917 and highest was 3.947 (.03 delta).
After charging the battery pack up into the 80ish percent, the delta is .01, and all cells are shown as green.

 

[Erwin P]

Well that's a clear picture. Mine probably has failed cells. What is your 100% voltage?

 

[AL_V]

Well that's a clear picture. Mine probably has failed cells. What is your 100% voltage?

I am going to charge to 100% tonight for tomorrow's ride, so I will post that later tonight or tomorrow.

 

[Erwin P]

Super, my 100% is around 409V just after charging. Will look again tomorrow morning.

 

[brongle]

I have 2 MX bikes, and I had a couple of slightly lower cells on the one that just got a new battery (but the battery percentage was below 30% at that point).
The lowest one was 3.917 and highest was 3.947 (.03 delta).
After charging the battery pack up into the 80ish percent, the delta is .01, and all cells are shown as green.

FWIW I assume the pack layout is the same so its very common for the first, last, and middle two (50/51 in the app) cell groups to be farther out, these are the ends of the two pack halves so they dip a bit compared to the others. Anything below .015 on a full charge I would consider very healthy. Personally I do a balance charge when it gets past .02 but thats overkill, .040 is probably a better threshold to balance at.

Super, my 100% is around 409V just after charging. Will look again tomorrow morning.

Yea that pretty much confirms it, pack should really be at 410v or above and even that low of a voltage would imply maybe 500+ charge cycles. My EX pack (obviously different cells) is only down about 1v at 100% SOC and thats after 4000 miles. Good luck reaching out to Stark hopefully they do the responsible thing and warranty the pack.

I don’t know how the internals work but two cell groups missing seems insanely dangerous to just ignore unless they have some common failure mode they feel safe ignoring.

 

[AL_V]

Well that's a clear picture. Mine probably has failed cells. What is your 100% voltage?

419, this is a brand new battery just replaced under warranty.
Well, I assume it’s brand new, it could also be “rebuilt”, “restored”, “renewed”, etc

 

[Erwin P]

Thanks, that's roughly the voltage of 2 cells and a bit of degradation that i'm missing.

 

[brongle]

An updated version of the app is now available on both platforms for testing, only two main things to test here:
- Updated the dashboard screen for Android to fix the speedometer overflowing and a few other spacing/display issues.
- Reworked how the underlying recording format works to make it much more efficient, recordings now store about 1mb of data per hour of riding.

If you'd like to expore the recording format more, I've also published a very early version of the simple browser-based software for viewing the recording formats at Svag Viewer. As I mentioned previously all the data processing is done in-browser and remains local on your device. Support for automatically recording rides and improvements to the viewer will come later down the road, for now this is more a proof of concept and helps me identify how people might use this in the future.

Thanks again for all the testers and feedback, I'll keep chipping away at the Android and smaller-screen layout issues.

 

[Hinkelstein]

An updated version of the app is now available on both platforms for testing, only two main things to test here:
- Updated the dashboard screen for Android to fix the speedometer overflowing and a few other spacing/display issues.
- Reworked how the underlying recording format works to make it much more efficient, recordings now store about 1mb of data per hour of riding.

If you'd like to expore the recording format more, I've also published a very early version of the simple browser-based software for viewing the recording formats at Svag Viewer. As I mentioned previously all the data processing is done in-browser and remains local on your device. Support for automatically recording rides and improvements to the viewer will come later down the road, for now this is more a proof of concept and helps me identify how people might use this in the future.

Thanks again for all the testers and feedback, I'll keep chipping away at the Android and smaller-screen layout issues.

Great! I can test it tomorrow. Do you know if it is the normal update procedure on android or ist it anyway special?

UPDATE: I updated via play store and now my app version on android is 1.2.0, native build 18. Is that correct?

 

[brongle]

Great! I can test it tomorrow. Do you know if it is the normal update procedure on android or ist it anyway special?

UPDATE: I updated via play store and now my app version on android is 1.2.0, native build 18. Is that correct?

On Android its the normal play store update process; 1.2.0 build 18 is the latest. On iOS you need to open the Test Flight app and update from there; 1.2.0 build 85 is the latest.

 

[Hinkelstein]

Tested Android and IOS today:
- on android, the issue with the screen layout is fixed, the values for Mapping and speed are just less bold and "comic style" than on IOS.
- on IOS there is an issue when speed reaches three digits (km/h in Germany). The numbers are using two lines then and the additional gauges disappear.
This doesn't happen always, I guess it is only when the last digits are wide, like 100 or 108.

One Question: Where do I find the listing with the voltages of the single cells mentioned above?

Again, thanks for the great work!

 

[Erwin P]

In the service menu amd then battery. You have to turn on service first.

 

[TheJ0rma]

Is the gear ratio function working, and if it is how to calculate the ratio or at least in what range should the value be in?

 

[brongle]

Is the gear ratio function working, and if it is how to calculate the ratio or at least in what range should the value be in?

It should work, instead of using the KMH reported by the VCU (and adjusted based on your unit) it simply multiplies the RPM by a fixed number you provide. This calculation should be done using KM/H as the unit adjustment comes after. I believe the stock gear ratio with this setting would be around "0.010".

There is actually a page for calibrating the speed (using GPS) but it's not directly accessible in the current version and needs a bit more refinement. Will try to get that out in the next batch of updates.

Tested Android and IOS today:
- on android, the issue with the screen layout is fixed, the values for Mapping and speed are just less bold and "comic style" than on IOS.
- on IOS there is an issue when speed reaches three digits (km/h in Germany). The numbers are using two lines then and the additional gauges disappear.
This doesn't happen always, I guess it is only when the last digits are wide, like 100 or 108.

One Question: Where do I find the listing with the voltages of the single cells mentioned above?

Again, thanks for the great work!

Ah good find, I haven't really tested km/h at all so I'll take a look at fixing the text overflow. The issue on Android was related to the custom font so for the moment I just disabled it, I'll try to actually fix it properly in the future.

 

[brongle]

Thanks to Erwin's feedback I've added a few alerts to the battery page that will display when things are obviously wrong. The main conditions involve the cell group voltage, cell group deviance from the average pack voltage, and overall pack voltage delta. I can't say for sure which of these Stark's BMS internally checks for, but if the bike doesn't fault for something here it will at least show up in the app.

 

[JJ2]

Work is done.
3d printed adapter for the Varg replacing the arkenstone.
Fits like dad in mum.
Just put the iPhone15pro into the backside of the adapter.
Then use the whole thing as it was an OEM arkenstone.

3d files: Thingiverse

View attachment 14531

View attachment 14532

View attachment 14533

View attachment 14534

View attachment 14535

a really great app for iphone and android. I would just like to briefly warn against using the iphone in the adapter, because the camera stabilisation is destroyed by the high-frequency vibrations and shocks. The iphone is then defective.
Here is a link, it affects all iphones with ois and closed loop. Only the iphone 11 is an exception

Exposure to vibrations, such as those generated by high-powered motorcycle engines, may impact iPhone cameras – Apple Support (UK)

Exposing your iPhone to high-amplitude vibrations within certain frequency ranges, specifically those generated by high-power motorcycle engines, can degrade the performance of the camera system.

support.apple.com

you could work with gel dampers or other high-frequency dampers, then the iphone would be a top solution on street use.
I would definitely not use the iphone on MX tracks or enduro or on trails in general, regardless of whether it has damping. Because the shocks and vibrations from the ground will destroy the iphone camera system despite the damping.
Frequencies in the 80-200 Hz range are the most destructive, as this is the natural frequency of the iPhone's OIS mechanism.
My 15 pro max doesn't fit in the holder anyway

But just reading out all the information (also works great with an iPad) is an absolute benefit.
the torque list is also very practical, you could add a few more details, for example 35 Nm for the bolts of the handlebar mount on the triple clamp

It works perfectly for me with EX and MX, both are software 1.2.8, even if the version is displayed incorrectly on the MX. You can then see the correct version in the app

 

[2ndalpha]

Thank you brongle for awesome work!
I tested it out on iPhone, works really well on iOS. Nice to see the diagnostics information.

I'm wondering would you be willing to share the BT protocol?
I'd like to create simple ESP32 thingy with a small screen.
It would need only the gear and state of charge.
For hard enduro having a small inexpensive screen would be preferred.

 

[dezinfo]

Add an odometer to the main screen. If it is possible to display information on map settings.

 

[fedesm297]

I just installed the Android upp on my personal phone, an Oneplus 8T, the app connected on the first try and at first glance everything is working properly, even the screen visualization is perfect. Have to try the dashboard view. I have a gen 1 MX by the way, one of the early one. I will try the app also on the Stark phone, but i'll leave it on my personal phone because it'll surely work better
Edit: i don't know if it's a my-phone problem (because i always had bluetooth problems) but it keeps asking me to associate the bluetooth with the bike, and whathever or not i put the pin, it doesn't change anything