Runn speed jumps considerably
Just got Runn. Set it up as instructed. The speed is going well for most of the run, but jumps considerably (goes from 13 km/hr which is normal, to between 18 km/hr and 30 km/hr) for a split second. Enough to register and really throw off my stats for max speed, max pace etc. Then goes back down to around normal, then spikes again and the pattern repeats. In a 5 km run, there are approximately 8-10 slipt second spike in all. I have moved the sensor to different places on the treadmill, used the Configurez app to calibrate, tried factory resetting and using uncalibrated, played with how close the sensor is to the belt, added additional strips to the belt (ensured all are at least 18" apart). I have tried everything I have read online and anything else I can think of. I have reached out to NPE support and I'm waiting for a response. Has anyone else had this issue and what (if anything) did you do to fix it? Many thanks!
-
Not sure if this'll be of much help, but the one time this happened to me was when I had moved the Runn off its mount and then placed it too far back so that it couldn't reliably read the sensors. After I moved it back to where it was dead center with the sensor strips, and moved it to its lowest position without touching the treadmill, it started reading reliably again.
-
I have had this problem and Runn had to send me a new on. Still having the same issue. I sent them all the pictures of my setup, etc. What is weird is that is was working just fine until one of their recent updates to the OS. I use this on Zwift with a Woodway treadmill. I don't know what to do at this point as I have been working with NPE on this with no fixes yet.
-
Sad there is no resolution for this problem. All NPE support could say is that maybe this device just won't work for me. Silly. Clearly is an issue with the device. They should have a feature where speed and cadence remains the same as last reading until connection is re-established. This would prevent the spikes everyone is seeing. That is the easiest fix that can just be done in the code with a simple update. At least they should do this until a permanent solution can be implemented. I ended up returning my device (2nd one) because of this issue. I have found another option (not NPE) that works perfectly.
Please sign in to leave a comment.
Comments
7 comments