Recent content by brongle

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?

The EX/1.2 drivetrain & pack have supported 6.6kw charging from the getgo, but it was only enabled for some users (mostly Stark staff and I guess a few competitors). I'm guessing this is either a bug on their side with the account-flagging or they are potentially slowly rolling out a higher...

Hmmm and you checked with the bike on? It's possible they don't do/mean anything yet and they just added them for testing with newer firmware.

Ah I put them on the battery page under the service menu, should look something like this: The field names are basically directly what Stark calls them so I'm not 100% sure what "No Vicor" (voltage?) and Danger Score (lol) mean.

For the most part yes, the internal builds seem to be 99% automated although sometimes they do take a bit of time to be "approved". The annoying part is that the review is for an older build that I marked for public release on the app store, but while it's in review no other changes go through...

Yep, I sent you off a link to the latest build. And the issue is with my app, the Stark app doesn't reveal the internal pack layout (I just gathered that based on the cell groups on the ends of the two pack sides showing different voltages) or how they identify cells so the in-app numbering is...

The EX phone is produced by a Chinese company Shenzhen Emdoor Information Co., Ltd. and Stark uses their MDM (Mobile Device Management) service to manage the OS version and I assume other device config. It's not too surprising you'd see notifications in Chinese as most of the internal services...

Yea the numbering is probably off by one. Bike is probably off so the contactors are open, that measurement will be garbage in this case. I don't know enough to say whether that amount of imbalance in one cell group is fatal. It's very possible a proper bottom balance would recover things to...

I don't think 14/47 with 17s would even get close to 154kmh on the current motor so I wonder how inflated that number is. It's a cleaned up Surron. Unless companies want to develop actual battery technology a 22S pack is not going to compete in performance with a 100S.

With the Stark phone off and the Svag app exited out everywhere I would try a generic BLE scanner tool and see if your bike shows up in its device list. It should be labeled by its VIN. If it does show up in the BLE app but not in Svag then something funky is going on with my app code and I'll...

Yes, it's how all firmware updates are done and (purely guessing, I haven't really investigated it much) it sends some level of live telemetry data back to Stark. Actually I was just looking through the latest app version and it seems Stark is now reading some more data from the VCU regarding...

Oh also worth noting I think Anton really wants to replicate a Tesla like experience with their app, where you could control and monitor most aspects of the bike remotely via the VCU LTE. I can't imagine another reason they would have wasted so much effort and money on the quite frankly terrible...

Ah sorry I meant the page with all the bike component/firmware versions, I was wondering if maybe a component (or the VCU firmware) got updated for you which could indeed break something. Still I'd be surprised as the latest Stark app version (2.6.0) doesn't seem to be notably different. Right...

Hmmm, what does it show under service -> versions? It's reading at least some of the app data (unless that's all stale, does it still connect to the bike if you force quit the app and clean start it?) since it thinks its connected. It's possible if you guys have different firmware versions...

I've had situations before where the VCU seems to lock up in a weird half-state and not allow connections. Sometimes the bike won't show up in the list and sometimes it will but just gets stuck at "syncing" (meaning the BT connection established but we're still waiting for the VCU to start...