This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Running Dynamics Pod Won't Connect

I'm on my second RD pod now, returned the first because I thought it was defective but this one is having same problem. 

I can connect the pod to my watch and it shows in the sensors list, however when i go to start an activity i only get a blinking man icon and it never turns solid, i get no data from the pod during or after the activity. 

I've checked pod software and it's on 2.40. I've tried shaking the pod, running a bit and then stopping and trying to connect and reconnect, switching it off and on, etc. Can't figure it out!

  • Former Member
    0 Former Member over 5 years ago

    When I had this issue, a restart of the watch fixed it.

  • Are you using FW 3.08 beta? I had the same issue with the last beta firmware but it works fine with FW 2.80 

  • I have the same issue. My work around is to go to sensor setting, turn off the rd pod, then reboot the watch, then go to the activity, except before starting hold the middle button on the left side, the goto settings and turn the rd pod back on. This only works once, meaning if you start an activity and then quit, you’ll have to do the same thing again.  The bug is related to the watch not properly shutting off the rd pod or internally disconnecting from it. You’ve probably noticed that the running dynamics screens only show up when an rd pod is connected, but the bug makes the watch think it is connected, so the screens come on whether the pod is communicating or not. the watch thinks it’s connected but the bug is blocking it from communicating. I noticed rebooted turns off the running dynamics screens but sometimes it still wouldn’t commiunicate, but if it turns the connection to the rd pod off then rebooted, it worked everytime. I’d  bet a dollar if you followed what I said, your first rd pod will work again, mine did. Now I have two rd pods but a buggy watch that can barely use them.

  • I am on the beta 3.08. I had battery life issues that the beta seems to have solved, but if the RD pod doesn't work I suppose I'll go back to 2.80. 

    Wish they'd get this solved!

  • You're right, this process worked. My original is on it's way back, but it wasn't defective, it's buggy interaction between the watch and pod as you've described. Thanks for the workaround!

  • Glad to help. I just wish Garmin had competent testing that could catch these things instead of customers having to do it.

  • I don't now if everyone has the new firmware version. I updated mine to 3.15 and now the running pod has connected properly 2 times in a row. Also, playing music via bluetooth headphones didn't cause everything to disconnect. I can't seem to figure out how to get the watch to 3.30 but it seems 3.15 fixed the connection problems.