Recent content by brongle

Just pull it up and away from the hub, the little bump (and hole above it) in the very top of your photo is the tab which indexes it onto the hub.

I did a bunch of research on this when I was exploring the inverter/motor parameters the VCU exports. I am very much a novice in this area, but the points that stuck with me are: Electric motors have a much wider range of performance properties than you might assume. Even small changes in the...

Yes, tapping into the CANBUS should be possible and would likely give 90% or more of the same data. I looked at sourcing the front-panel higo connectors last month and it seems maybe possible, that'd make it a lot easier to create a more "refined" product that just plugs in and sits up front or...

As an update for those still using Svag, I have a new version (v1.6.6) which should be available on iOS and Android (closed-testing) sometime this week. This is finally wrapping up some work I did to improve the Bluetooth connection flow, it should reduce a lot of the issues connecting (at least...

Two minor things I've noticed with 1.6.0 on my EX so far: - The contactors seem to operate much faster when turning the bike on/off - When turning off the bike under 20% it no longer seems to go into deep sleep mode automatically, it still just sits in hibernation. I noticed it coming home...

I just got 1.6.0 today, went to go for a ride and noticed the status-led having a little disco party and rapidly cycling through the colors of the rainbow. Cool effect but in the moment I assumed something was messed up (especially given the control inputs do nothing) and played around with the...

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...

I'll take a look when I get a chance, I haven't tested on the Arkenstone in a while so it's very possible I broke something.

Pretty sure 1.4.0 is the bugged release, I think 1.5.0 is the latest now although I'm not sure how they are rolling things out.

Seems like me either, and it's not like I've done anything to deserve it... 😅 I think they've been basically spending 100% of their effort aligning everything to the new VCU and firmware so that the MX/EX/SM can all share the same work and benefits. Now that they've finished that work with...

Ah! I think Alta was on to something with the simplicity and usability of their interface, its a shame Stark wants to be so fancy at the cost of any functionality... Are you pulling data from CAN or BLE?

Ah yes that was some of the inspiration for sure! I think their approach is probably better in many ways as tapping into the CAN interface lets you still connect the phone, and probably access some more data as well. I've been meaning to poke into the EX connection hub to see if there is an easy...

Slow rollouts of updates like this help catch potential issues before they cause wide-spread problems. The issue folks are seeing with the battery warnings is why you want to take an approach like this. While Stark probably should be doing a better job at internal QA you still cannot test for...

I've been wanting to build this since before starting on Svag, but it made more sense to get a better understanding of the BLE interface and build something more widely usable first. Right now this is a very early prototype which just integrates a 20x04 LCD and a small ESP32-C3 powered via a USB...

It's based mostly on mileage. I believe this time they are also rolling out the firmware to MXs first, I've seen a lot of people on old bikes having issues with battery warnings popping up now (which seems to be a bug).