Di2 not showing accurate information
Answered
-
I have the same issue. Found after unpairing all my sensors and then pairing di2 it worked as I’d expected. But as I added more and more sensor it just got slower. Reached out for help but was told it’s more to do with shimano’s protocol than the Karoo. Who knows but agree not worth using with such a slow reaction to input.
-
Thanks Paul, at least I’m not the only one. I struggle a bit with blaming it on Shimano as Garmin have this working pretty reliably. I’ll try unpairing stuff and starting again, but really disappointed that a device/software combination has still got such significant issues after 2 years. I’ll have to think more carefully about spendIng $400 on the new version as this is a feature that’s important to me.
Ah well, back to Garmin!
-
@Chris: Sorry for the trouble caused due to the issues with Di2 connection. As Paul suggested, please unpair all the sensors from your Karoo and reboot it. Once you turn it on, please pair the Di2 first before pairing other sensors as it works on a slightly different frequency than any other sensors. Also, please check if there is any firmware update pending for the Di2 and make sure that the Di2 is sufficiently charged which could other possible reasons for this issue to occur.
-
Thanks Hari, I forgot the need to reboot after unpairing. One other observation, when I unpair, and reload with Di2 first I find movement still slow. Not as bad as previously. However when I slide Di2 up the list the speed improves noticeably. Not sure yet how long the improvement will last as I still have my HR to be added.
-
Thanks to both of you. I'll try all that and let you know how I get on.
To be honest, I can live without the screen swiping - it's nice to have but not essential. However, having a reliable view of my battery and gear ratios is important. I have a planned ride for tomorrow, so I'll report back after that.
One other point that may be relevant: I only have the the Di2 wireless unit (WU111) transmitting in ANT+. I switched off the BT to help with battery life and security - would that impact the connectivity?
-
Quick update:-
After removing all sensors and re-booting, then adding in Di2 as the 1st sensor and ensuring it stayed at the top after adding others, the responsiveness was much better - the odd hiccup, but very usable.
However, I tried to add my other bike's Di2 as I was taking that our for a spin and although it added fine, it wouldn't connect after that no matter what I did. So no Di2 data on that ride. I haven't had time to troubleshoot yet, but any ideas would be welcome.
-
Chris, Can't say I had success after following the latest suggestions. I just think I'm about 1 or two devices too heavy, causing a noticeable slow down in page changes and information grab. I'm coming to the conclusion that if I want to use the Di2 features, I will need to use my Garmin if they prove to be that important. The Karoo is just not working well for me in this department for reasons I just can't figure out.
-
Paul. I feel your pain. I really want to like the Karoo but it’s been a challenge to get it up and running and getting my sensors running effectively where most of the competitors seem to have been doing reliably for some time.
I love the screen clarity and the routing works very well, but if I can’t get all the data I need, then I may also had e to go back to my Garmin.
The thing is, I’m not unfamiliar with technology, I work in IT mobility solutions and technical support and understand better than most how finicky things can be. But.... I assumed that after 2 years developing this software that all the basics around sensor pairing and data collection would be nailed by now.
-
Hey Chris, Paul.
Sorry for the inconvinience caused to you for the issues with the sensors.
Well, I would like to inform you that Di2 work differently than any other e-drive chain. It's not ANT+ but custom ANT profile which is why it operates at different frequency than any other sensors, specially for android. For this we ask users to pair it first.
Now the connection itself takes longer and that depends on how far the WU is from Karoo. We know that we need to work further on the sensor management and it's the top priority fix for us. This is the reason we delivering the sensor improvement incrementally.
In addition to this, for the DI2 to work on your other bike, I would request you to follow the instruction(as mentioned by Hari). Unpaire the sensors, reboot your Karoo and pair Di2 on precedence over any other sensors.
-
Thanks Abhishek,
I appreciate your response. However, having to remove sensors, reboot, and re-add them when I swap bikes is not a sustainable or desirable solution, especially when I don't need to do that with my competitor device.
Perhaps a possible future path for the Dev team, would be to group sensors by Bike and then have the system enable or disable sensors based on the selected bike before the ride starts.
I look forward improvements in this area in the future and I'll keep a close eye on how things are going, but for now it's difficult for me to rely on the Karoo for my needs.
Please sign in to leave a comment.
Comments
10 comments