Runn Calibration Procedure Fails to Complete

Follow

Robert Wisbey

• January 24, 2020 16:33

Hi, I followed the Runn calibration procedure with the appropriate button presses (double press, single press, LEDs alternating, then long 6 second press), but then nothing else happens such as a LED confirming the calibration. See the YouTube video here for a visual description of the issue (the video shows two failed attempts) : https://youtu.be/kbl4-ZjXTzo Here is the history to the issue: - initially out of the factory, without any calibration the speed on your app was showing 6 km/h when the treadmill was at 5 km/h, and the incline was way off from 0 degrees - I tried calibrating for a first time (with one reflective strip), and never recollect seeing a confirmation LED. However at this point in your app the speed did seem to be at 5 km/h in accordance to the treadmill. At this point the incline still was not 0, but at 2.7 degrees. I then noticed the Runn was not seated flat, but at an angle. So I correctly re-seated the Runn in the support so the incline was close to 0 (the app reads 0.1 incline). At this point, the speed then reported by your app was 5.2 km/h even though the treadmill was set to 5 km/h. I figured this was due to fact the the calibration was done when the Runn wasn’t seated ‘flat’ in the bracket. Having said that, I never remember seeing a calibration confirmation LED as your video and instructions indicate. - after my initial ’non flat’ calibration attempt that never seemed to have had confirmation as described above, I have retried multiple times as shown in the YouTube video (with three reflective strips to try to improve accuracy). I never get a confirmation LED, and the speed remains at 5.2 km/h even with three reflective strips opposed to one. - I then tried walking at 5 km/h, then leave the treadmill, and noticed that Runn reported up to 5.6 km/h (probable the treadmill speeding up to compensate after the foot is not present) - another thing I noticed is that even if the incline seems ok at 0 degrees, with your app showing -0.1, when I incline the treadmill to 15 degrees, Runn shows 13.4 degrees in your App. - as a result of not being able to confirm the calibration, my Garmin 945 reports a pace of 4:45 for a treadmill speed of 12 km/h (5:00 pace). Any advice on performing a factory reset so I can re-try the calibration procedure would be great. Also, can you suggest other steps I can try to perform, and whether it’s normal that I never see a confirmation LED for a successful calibration. Thanks, Rob

0

• Official comment

  

  Erin Eskew

  • January 24, 2020 16:37

  Hi Robert! I am going to open a support ticket so I am get a few more details from you.

  Comment actions Permalink
• 

  Robert Wisbey

  • January 24, 2020 17:12

  Thanks Erin,

  One thing that I have just realized after writing this support post, and reading your LED FAQs, is that in my video, I guess I’m holding the button longer than 6 seconds and performing a factory reset, because the LEDs are going forward.

  Having said that, the reason I’m doing this is because when holding the button down for a period of time, the reverse LED sequence to initiate the calibration procedure never seems to appear.

  0

  Comment actions Permalink
• 

  Erin Eskew

  • January 24, 2020 17:17

  The LEDs will start reverse sequencing after releasing the button, you might need to wait a few seconds after releasing to see this.

  0

  Comment actions Permalink
• 

  Robert Wisbey

  • January 24, 2020 17:41
  • Edited

  Thanks Erin,

  Ok, I’ll try this on Sunday evening (I’m away for the weekend). I’ll keep you posted.

  It could be a good idea to update your online documentation to include this subtlety, as I suspect that many end users (me included) expect the Runn to activate the LED sequence and then release the button (which actually invokes the factory reset) instead of counting six seconds, releasing the button, and observing the reverse LED sequence.

  Have a great weekend :-)

  0

  Comment actions Permalink
• 

  Erin Eskew

  • January 24, 2020 17:39

  We will work on that!

  0

  Comment actions Permalink
• 

  Robert Wisbey

  • January 26, 2020 23:59
  • Edited

  Hi,

   

  I'm just reporting back.

  So tonight I got back home, and this time, as instructed, I counted 6-7 seconds and then let go of the button.

  When doing this, and not waiting for the LEDs to start moving, the LEDs do indeed go in the reverse right to left direction, and the calibration works.

  One minor quibble, but I guess it doesn't really impact the accuracy that much (and Garmin watches, etc. can be compensated anyway with a calibration factor), is that the calibration is done at 5 MPH, which equals 8.05 km/h. Of course, many treadmills are in km/h with 0.1 km/h increments. So of course, when calibrating on such "metric" systems, there is no way to set the treadmill exactly to 8.05 km/h.

  Regarding the incline, in my treadmill maintenance menu, I re-preformed an incline calibration where the treadmill will go through its extremities (-3 to +15). When the treadmill incline calibration finished at the top end, the GymTrakr app showed an incline of 15.6. Then, when the treadmill finished the entire incline calibration returning to 0, GymTrakr showed just above 0 (0.1 or 0.2 I think). So I re-performed an Runn calibration, at which point the GymTrakr app showed an incline of 0. Then setting the treadmill incline to 15, GymTrakr shows 14, and when the treadmill is at -3 GymTrakr shows -2.6. My guess is maybe the treadmill incline sensor is off, and I should try the maintenance menu incline calibration multiple times ??

  There was a 1 degree difference between the iPhone and the Runn.

   

  0

  Comment actions Permalink

Please sign in to leave a comment.