Running Dynamics Pod not connecting to fenix 6 Pro

SW Rev 4.10

Sensor Hub 2.50

ANT / BLE / BT 3.70

Hi, I can't obtain a stable ANT+ connection to the Running Dynamics Pod (SW 2.40) - no stable connection is established.

Tried 2 different RDPs already and exchanged batteries CR1632. To no avail.

Any experiences in the forum ?

Thanks for  feeding back.

- Road.

  • I have 2.60 and had to re-add RD pod today. 

  • Former Member
    0 Former Member over 5 years ago in reply to grabrus

    Same for me. In the sensor menu it says it's connected but when starting an activity the RD logo is "blinking" and no data is recorded/transmitted. It's really frustrating.....

    Instead of fixing music volume and other secondary stuff, Garmin should focus on the key functions of their products. Hope the Garmin development team is reading....

  • Me too. Hope to see a solution soon.

  • I got the update, but it dodn't fix my sensor.

  • Yep, not fixed under Sensor Hub Rev 2.60, I think this was not the purpose with this very revision, which addressed the elevation recording.

    I'm still on my pod removal / re-assignment procedure, which works, yet is nervy. As all of you, I am waiting on Garmin's solution.

    Best, Road.

  • Former Member
    0 Former Member over 5 years ago

    same problem.

    my fenix 6x say connected to running dynamics but doesnt works. there is no no number in display when i m running.

    i tried  reboot but nothing...

  • same here ... Fenix 6 works just fine - even after update to 4.30 
    Fenix 6 x pro doesn't work (yet on 4.20) even after complete watch reset. 

  • [admittedly its a stinks to do this to begin with.  I understand, accept that]

    The workaround still works for me me with my 6x. Not for this to work you need to start from a condition in which the RD POD is not an added sensor.  So dont just disable it, remove it all together.  Maybe not necessary, but reboot watch after removing the RD pod.


    1) I enter into a an activity (e.g. run).

    2) before I hit start for the activity, meaning the time the 6x would be connected to peripherals, lockings GPS, etc.  I long press the left "menu button".  I scroll to sensors and ADD the RD pod.  It should find it,  click to "add" then wait for a few more moments, and you should get the 2nd  indication/alert that its connected.

    3) press back/lap button to return back into the [run] activity.  the RD pod logo should be there, and if you got that 2nd alert from step #2 it should be solid, not blinking.

    4) start your activity 

    5) finish your activity

    6)after exiting the activity, go back into the sensor menu options and REMOVE the RD pod.  That way when you start an activity again tomorrow, you can start again with step 1 and 2 (add the RD pod).

    Its been working for me since hub 4.20 came out (possibly longer).  I get all the RD metrics saved.   Hope it helps you  until a true fix comes along.

  • 2Jetguat ... very .... overhaed-ish solution ... but it works ...however - I had to switch off/on the watch after POD removal ... without power off/on it didn't work ... only once I turned the watch off, the POD signed even in activity as connected - without switching off it didn't show up in activity anyways.

  • one time I did have to power cycle also.   Not sure why.  but in my haste, I think after I added the RD pod in step 2,  I jumped back into the run activity quickly..  and the PD icon remained blinking and never connected.

    one of the attempt I also have BT headphone running.  and I wondered if having them running at the time screwed up the sensor hub some. like they were conflicting with each other.