Voltage is the same
EX Custom iOS/Android App
- Thread starter brongle
- Start date
@brongle what are the parameters for the delta V warning if I can ask?
I have a delta v of .076 but having no reference points, I don't know how out of spec this is. I'd rather avoid the discussion with Stark support on how I got alerted there might be an issue.
I also can't seem to charge over 98% and have a DC bus of 412.5v. Just trying to get a read on the severity of the issue, if there is one. EX model, bike isn't a month old.
I have a delta v of .076 but having no reference points, I don't know how out of spec this is. I'd rather avoid the discussion with Stark support on how I got alerted there might be an issue.
I also can't seem to charge over 98% and have a DC bus of 412.5v. Just trying to get a read on the severity of the issue, if there is one. EX model, bike isn't a month old.
That is quite high for a dV, I can't give you exact numbers because it depends a lot on pack layout and other internal factors but I based the numbers in the app off some research I did. Svag considers anything over 0.045 "high" as that's an ok mark to balance the battery at (which is the intention of the warning).
If the bike doesn't charge past 412.5v and it's brand new something is definitely wrong, I'd say just the fact it stops at 98% is enough to ask Stark for help. After 5000 miles on my EX over the past few months my battery will still reach just over 419v at full charge which is much more in line with the level of pack degradation you should expect. I don't think I've seen a dV of over 0.030 even after lots of short charging cycles and heavy use.
My guess would be Stark's internal charging logic will cut out somewhere around 0.075 or 0.080 dV which would probably make sense for a safety mechanism. Have you tried doing a balance charge by lowering the battery below 20% (in this case I'd personal target around 5%), charging to full, and then letting the bike sit on the charger for at least a few hours? I'm guessing this would be Starks first recommendation unless they have other data to point to a fault.
AbnormalWrench
Active member
- Likes
- 43
- Location
- Seattle, WA, USA
I can't get the app to connect to the bike anymore. Anyone else have this problem? It no longer shows the bike in the pairing screen, in the app or in the Bluetooth settings. I have tried with both my Pixel9 and the stock phone. I'm starting to suspect Stark changed things to make it more difficult for nonstock apps to get data
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 sending telemetry data). Usually if I unpair the bike from the Bluetooth settings on my phone or just wait a bit it will start working again. Also worth noting something is weird in the current app release and I don't think (at least on iOS) the "bluetooth disabled" warning shows, so it's possible your phone Bluetooth is off?
I haven't seen any firmware or app updates so guessing its just the VCU being trash, but let me know if you can't get it working and I can look at the app debug data to see if there is something more obviously wrong.
AbnormalWrench
Active member
- Likes
- 43
- Location
- Seattle, WA, USA
I'll try rebooting the bike tonight. I hadn't tried that. It hasn't worked on either phone for the last three rides, but the stark app works fine, which seemed weird. It is kind of crazy how often something weird happens that requires rebooting the bike. My headlight and turn signals randomly won't work sometimes twice a week and requires a reboot
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 something is has been changed, but if its 1.2.8 I'd be surprised.
App Version 1.5.0.
It was connected, the data that was shown in svag worked (like the speedo, powermode, blinkers,.. but no voltage or temps.)
My bike should have the latest firmware.
Also when I tried your app some weeks ago everything worked flawless.
I can try again today or tomorrow if I get the same result, but I thought I'd already shared my experiences.
Greets,
Yannick.
leadingedge
New member
- Likes
- 2
- Location
- USA
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 now all the communication is done via Bluetooth, so for any kind of remote monitoring would need a middleman. At least for the app this isn't something I'd build as it can drastically complicate the app review/release process (which is already proving to be quite difficult) as I'd probably need to receive and process data for forwarding.
Is your use case just tracking SOC/charging remotely? I have a prototype dedicated display unit I'm working on that could possibly allow you to connect it via wifi for remote viewing of soc/telemetry, but thats probably pretty far off in the future.
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 existing app experience, unless they really want the bike to be remotely connected. All of the current telemetry data could easily be sent purely over the phone so the fact the VCU has LTE at all seems super suggestive this is the future. It probably won't happen anytime soon as Stark seems to be pretty bad at building software, but it'd be pretty cool if they managed to make it work, and definitely would quiet the concerns of the VCU being remotely trackable/brickable.
leadingedge
New member
- Likes
- 2
- Location
- USA
Yep, I'm mainly interested in checking my battery level while not with the bike. Is there perhaps a possibility of a standalone monitoring app that can be installed on the Arkenstone for Stark battery level monitoring?
For interest sake for anyone who wants to track the location of your bike, use the Google "find my phone" feature to track the Arkenstone signed in to your Google account - so at least that part of remote tracking is an easy solution. It's also handy if your Arkenstone jumps out of it's holder while riding and you need to backtrack and find it....ask me how I know. The "play sound" feature in the Google "Find my phone" helped me locate it off the side of a trail in the bushes the other day after it went flying during a ride and I didn't know exactly where.
For family/friends tracking of your ride, I've found the easiest way is to install Google maps on the Arkenstone, and allow location sharing directly from Google Maps to whoever you want to follow your ride.
leadingedge
New member
- Likes
- 2
- Location
- USA
That would be great!
Wow, so the VCU itself has its own LTE and a data connection completely separate from the phone? I thought it was only the phone that allowed the connection.
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 battery status and health. I'll try to get it in a version of the app soon as I'm guessing this might hint to whats wrong with your pack.
AbnormalWrench
Active member
- Likes
- 43
- Location
- Seattle, WA, USA
I tried rebooting the bike twice, just to make sure, but I still have no bluetooth connection with either phone. Any other suggestions?
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 have to do some testing on an Android device. If it doesn't show up, but your Stark phone does connect, then something very weird is going on. In that case can you check the firmware version in the Stark app? And just double checking you've tried un-pairing the VIN from your Bluetooth devices in system settings?
AbnormalWrench
Active member
- Likes
- 43
- Location
- Seattle, WA, USA
I went out and grabbed the Stark phone and was walking towards the house to get it out of bluetooth range, and just to make sure, I went to turn it off. But after unlocking the phone, now suddenly the bluetooth sensed the bike. No idea why NOW it decided to work. I've tried it over a dozen times in the last week, this is the first time it worked. But after the Stark phone started working, I tried my Pixel and it works now too.
I guess rebooting the bike took a while to completely reset everything? That is the only thing I can think of.
I guess rebooting the bike took a while to completely reset everything? That is the only thing I can think of.
See this:
Poll: Are you using the original Stark Varg Stand/Charger as intended?
I am not going to lift that massive weight onto any stand I use a lift stand and plug the charger in beside the bike I think most people would charge the bike this way
electricdirtriders.com
Just a reminder to make a new Google account specifically for the Varg and not use your personal Google account since the Arkenstone does not lock.
AbnormalWrench
Active member
- Likes
- 43
- Location
- Seattle, WA, USA
What do you mean? the dang thing locks every 10 seconds. There is probably a way to extend that, but in stock form, it is really annoying.
