AL_V
Well-known member
- Likes
- 314
- Location
- Canton, Ohio
There is already 12v "available" for the docking station, the radiator fan, and the water pump.the dc-dc converter.
converting the batteryvoltage 400V to boardvoltage(s) 12V, 5V, whatever
EX Custom iOS/Android App
- Thread starter brongle
- Start date
leadingedge
Member
- Likes
- 8
- Location
- USA
leadingedge
Member
- Likes
- 8
- Location
- USA
Yep, it was on. Who knows, maybe they need a bigger deviation before activation of the fault selectors.
- Likes
- 409
- Location
- Netherlands
My app on Android doesn't seem to connect to my MX 1.0 any more. Any suggestions?
I have mx with fw 1.2.8 work OK
Need update and off default phone
What version are you running? I think I know what I broke but just wanna double check.
Ah interesting, I guess we will see what it holds. Good to see the app still works and connects on that firmware version. Does he have a lot of ride-time on his MX?
- Likes
- 409
- Location
- Netherlands
Version? Of your app?
1.6.0
1.6.0
Ah yea thats the one sorry, I should be more specific when talking about versions...
I have a new build pending review on Android/iOS which should hopefully fix the MX issue. It also heavily changes how the app syncs some data over Bluetooth to be a bit nicer to the VCU and also use a fair bit less phone battery. Some screens will now take a moment to load in depending on what types of data they require, you will notice this more in the service menu as much of that data used there is specialized. In the future I'll add some better "empty" and "loading" states to these screens so they don't just show up blank or with weird values, but I've been busy with other projects recently so I haven't had the time for tweaking the UI yet.
About 300 hours
after upgrade he have problem with power train system stark say...
Does v1.6.1 (build #36 on android) fix connecting to your MX by chance? It should be available in closed testing.
- Likes
- 409
- Location
- Netherlands
I will test it today 
AbnormalWrench
Well-known member
- Likes
- 50
- Location
- Seattle, WA, USA
I've been trying to use the Stark phone, it was working OK for a while....I would have to fire up the app, wait for the Stark app try to take over, switch back over....then the phone would try to go to sleep, I'd wake it up, then unlock it....and THEN it would work fine. But recently, that no longer works. I think the Stark app is steamrolling the Svag app. I can get the Svag app to link up and open, but it has an extremely slow refresh rate. It will have something like a 5 minute delay. Button response is also extremely slow. I have tried rebooting the phone, but it doesn't matter. You can't close the Stark app, it just immediately restarts. Anyone else having this problem? Any work around?
The best starting point would be the svag-mini repository, that implements all of what you want above. Because I built that on the ESP32 BLE stack it doesn't contain any of the PIN generation code because I found that wasn't required.
I'd like to publish the app but I decided to wait as Stark did reach out a bit ago and confirmed they are working towards improving the security of the app/vcu connection. That's a great sign and I'm glad to see they care about this stuff, but I'd rather wait for those changes (which admittedly might be on the Stark timeline of taking quite a while...), since its not clear to me whether they will be changing the underlying PIN-generation. If they don't change that, I'd rather not have it published on GitHub so I'll have to sort something else out for open-source. If they do end up changing that, or perhaps improving things to the point where Svag can't function anymore, I'd happily push stuff for reference, although obviously its a lot less useful then.
)