Erwin P
Well-known member
- Likes
- 242
- Location
- Netherlands
was able to load it from germany. Connection worked, I have to adjust font size though. Thank you for this great work!Ok, I believe I've sorted that issue out as Google just defaults to US & UK for closed testing. I opened it up to the entire world so hopefully that lets you all see the app and install it now.
Should i be worried over those 2 cells?
View attachment 14538
Imho this prototype, version 1.0.0 (or so) app has less connection problems than their OEM version. I have the EX since the beginning of march and theI was thinking the same. I could see them start talking "about" warranty since i've come to know this through not their software.
How close are you to end of warranty?Should i be worried over those 2 cells?
View attachment 14538
Should i be worried over those 2 cells?
View attachment 14538
I was thinking the same. I could see them start talking "about" warranty since i've come to know this through not their software.
Thanks! The screenshot is very helpful, I'll keep working on getting the display of items fixed for different screen-sizes and layouts.First ride, left arkenstone at home.
Connection shows up a PIN each time, but it can’t be entered and it connects anyway. Took font size to the smallest size possible but ODO is clipped on start screen and
advanced measures overlap speed.
(Must learn taking screenshots on android
View attachment 14539
While I will probably eventually investigate editing charging rates and maybe some basic settings, the map settings is a bit trickier issue. I suspect that the VCU has no concept of whether a bike is configured for 60 or 80hp, and since I can't actually read data from your Stark account it would be impossible for me to limit the power you could configure like Stark does. Obviously for a lot of people this would be a great thing since its a free upgrade, but also likely would cause Stark to crack down on this type of access and potentially heavily limit what a third-party app could do.It would be nice to add information on operation hours and other statistics and of course current maps set. Changing map settings in application is a necessary function. I am even ready to pay for it.
Ah one other thing I thought of on this point, I am relatively sure most of this data is available over the OBDII/diagnostics interface. It'd be cool to eventually poke at that but honestly I've been too lazy to pull the plastics off and find the connector. If the data is available it'd make support requests around it a bit more reasonable and would prevent Stark from voiding your warranty, both as the terms don't mention anything about that and as the EU and other regions generally have protections around OBD/diagnostic vehicle data.I was thinking the same. I could see them start talking "about" warranty since i've come to know this through not their software.
This was during charging. Afterwards it were just 0's.Interesting, are you on an EX or MX? My guess is these readings are wrong as that low of a cell voltage is basically impossible (unless the connection to the cells is severed completely). It's also very suspicious that both readings are so close to eachother, and they also look like a delta reading since 0.015v would be a very common cell-delta. If your on an MX I would guess the firmware is maybe a little different or possibly I need to do some more investigation. Either way if you want to use the "export diagnostics" feature and send me the resulting file I can at least take a look to see if there is an obvious bug in the app.
Yea this has been part of my concern as well. In Stark's defense I can understand not wanting to expose all this information to users until its accurate and refined enough to actually be useful. There is also arguably a lot of work they need to do on the manual and general documentation to avoid the situation of users reaching out for non-issues or because they are confused by the data they are seeing.
It's an MX and thus doesn't have an OBD gate.Ah one other thing I thought of on this point, I am relatively sure most of this data is available over the OBDII/diagnostics interface. It'd be cool to eventually poke at that but honestly I've been too lazy to pull the plastics off and find the connector. If the data is available it'd make support requests around it a bit more reasonable and would prevent Stark from voiding your warranty, both as the terms don't mention anything about that and as the EU and other regions generally have protections around OBD/diagnostic vehicle data.
Interesting, I can't promise everything is compatible with the MX series, from what I understand the app for it (unless its been updated to match the EX one) uses a different Bluetooth interface/version. Given that it's possible some data is incorrect or nonsense on the MX series. I do believe they are working towards getting the MX series onto the new interface and app, so thats probably why a lot of stuff is working okay.This was during charging. Afterwards it were just 0's.
I wanted to look into it some hours later and the app couldn't find my bike. Will try again today.
This bike (MX 2023) has warranty until november. With this info i will make use of their extended warranty i guess![]()