0

On vs. Recording

Paul Davis

May 15, 2015 13:20

None

Follow

Just got my runScribe and am going out for my first run with it today. Can't wait. However, had an initial question as I was setting up my rS. It obviously turns on if I just turn it back and forth or shake it, but it also obviously does not start tracking data just because it is on. So my question is what triggers rS to start recording data? Is it some level of impact (from actually running or walking) that causes it to start recording? And what causes it to stop recording (the lack of impact after the TimeOut period setup in Config)?

And lastly, if it is the impact of running/walking that causes rS to start recording, I'm guessing that the Sensitivity setting in Config is what you use to adjust the amount of force/impact that is required to get rS to start recording? If that is the case, if I want it to record when I'm running (vs. walking) theoretically I could adjust the Sensitivity to a higher level so it would be more likely to ignore my walking and only record my running. Am I on track or way off base?

Just trying to understand the settings so as I start to run with it more I can start making adjustments to fit how I use it.

Thanks and again, excited to be part of the testing!
Paul

• Facebook
• Twitter
• LinkedIn

2 comments

• 0
  
  John Litschert May 15, 2015 23:36

  Hi Paul,
  You are mostly correct. When it is flashing blue it is awake but not recording data. It is only recording data when it is blinking red and a relatively slow rate.
  A combination of impacts and frequency of motion is what is required to start the recording process. And yes the sensitivity setting is what controls how easily it starts up. A HIGHER setting will make it more sensitive and make it easier to start. So less motion is required to start it. A LOWER setting will make it less sensitive and more motion and impacts are required to start it. I've had pretty good luck with a setting of 6 or 7. It starts when I run but usually not when I walk. I have found that on a treadmill I need to set it a little higher. I think because there is a little shock absorption inherent in most treadmills.
  And yes, the timeout setting is how many seconds of no motion is required to shut it down. If you tend to stop during your runs you might want to set it higher but if not then setting it lower is more convenient. You should know that if you set it for say 120 and you stop for some length of time less than that it will not shut down and that period of no running is figured into your overall pace.
  We plan to add the ability to start/stop and pause to the app but you will need to carry your phone with you.

• 0
  
  Paul Davis May 16, 2015 01:47

  That’s what I thought. Thanks for confirming. I was off on the direction of the Sensitivity setting, but got it now. That actually really works for me IF I can find that fine line in the Sensitivity setting b/w running and walking. I’ll play around with it and see how it works. On the treadmill I tend to finish a run by reducing the speed down to a walk for a cool down and it would be nice if I could get the Sensitivity right so it stops recording when I stop running. When I’m running outside I think I’ll just stop and pull the runScribes off and hold them while I walk off my run.

  As for the start/stop and pause it’s an interesting dilemma. I thought about that a bit today during my run, too, and have some thoughts. I’ll share them in a separate post as I know a lot of people have already commented on it.