Step count in Running dynamics

Hi! I want to determine the step count using Running Dynamics, but it seems this field is always 0 when i access it. All other fields are filled. I am using a HRM Run for my tests. Is there something I can try to get the data? Thanks!

0 jim_m_58 over 4 years ago

In the API doc. you'll see that Step Count for RD is only 0-127 and rolls.

stepCount

Step count (rolls over!) (0 - 127 steps).

If you want actual step count, look at ActivityMonitor

0 Travis.ConnectIQ over 4 years ago

Are you testing on the ConnectIQ simulator, are you on device?

0 Woody over 4 years ago in reply to jim_m_58

Yes, i saw that. If i determine the number on a seconds interval it should never roll over, to my understanding. I did implement the count using Activity Monitor but it his highly dependent on the arm swing, so looking onto the watch seems to be enough to miss several steps it seems, so i tried to avoid that by using the data from HRM Run.

Checking step count on a seconds interval should basically be possible to use, or is it not supported by all running dynamics devices (e.g. like HRM Run)?

0 Woody over 4 years ago in reply to Travis.ConnectIQ

I'm testing it directly on the watch. I wrote a simple data field and output the step count value on the screen and into a log file, but it's always zero. Other fields like cadence do have a value.

0 jim_m_58 over 4 years ago in reply to Woody

It may be something that only works with an RD pod and not a HRM. The RD pod is worn on the lower back and may be able to count steps.

www.dcrainmaker.com/.../garmins-running-dynamics-pod-rd-pod-everything-you-ever-wanted-to-know.html

What Garmin watch are you testing with?

0 Woody over 4 years ago in reply to jim_m_58

That's possible. It's a pity, i hoped the hrm run would be able to determine steps. I'm using a Fenix 6. Thanks for your help, i appreciate it!

0 jim_m_58 over 4 years ago in reply to Woody

One other thing. When you've been testing, you actually are running, correct? A real run, and not just a few steps, right?

0 Woody over 4 years ago in reply to jim_m_58

You have a point here. Because i wanted to make sure that it works before using it for a real run, i tested it with a few steps first. I was positive that it would be fine because other fields like cadence were filled. I'll make sure I'll test it in a run and see if the field gets filled.

0 Woody over 4 years ago in reply to Woody

In case that some Running Dynamics devices do not support specific features of the RunningDynamicsData fields, I think there should be a hint in the documentation, or at least the fields that are not supported should remain null. Because how it is now, I have no chance to find out if, for example, stepCount is supported because it gets the value 0 in the beginning, not null. Maybe the Garmin team can take it as a request to update their documentation :)

0 Travis.ConnectIQ over 4 years ago in reply to Woody

If running dynamics are supported, then all the fields should be filled.