Running Dynamics Pod not connecting to fenix 6 Pro

No. 

When i tested yesterday - I had around the Tempe sensor which connected instantly

When i tested this morning - no other device again, including Tempe which remained at home(4km away from me :))) )

What I also observed strange: i've followed those steps and ending up in POD connected in the sensors menu. 

Then I went for a coffee break, 3 floors down, outside of the building. The POD was still showing up as connected. I doubt that it will have such a range thru walls 

I had a chat with Garmin support on this RD Pod topic - bottom line there are TWO customers with the same issue, and they opened a Product Support Case for me. I have to be patient and wait for a resolution

Detailed chat here:

[05:14:25] EyessOnlyy: I cannot manage to have RD POD working with my F6Saphire
[05:14:25] Session started between EyessOnlyy: and Chris
[05:14:50] EyessOnlyy: I can connect the RD Pod in the Sensors&Accessories menu. It shows connected Then, when i start the run app the icon which shows the RD Pod keeps blinking all the time and the sensor is not detected. Of course, when starting an activity, no data is received from the Pod. If I go to the sensors menu again it still tells me connected. I have tried several workardounds - reset the watch to default settings - remove sensor, switch off watch, switch on, add sensor again, go to run app - replace battery(even if the About section tells me battery OK) Also, this morning the POD was at the 3rd floor of the office building. I was outside of the building(many walls between watch and POD) The watch was showing the POD as still connnected in the sensors mehu There is no issue in detecting other ANT+ sensors: e.g. Tempe or HeartRate band sensors are detected instantly On the watch I'm using - all the released sensor/sw versions - beta sw version 4.11 On the sensor - it tells me 2.40 SW
[05:15:15] Chris Hi Ilie
[05:15:47] Chris is this a 3rd party sensor?
[05:16:05] EyessOnlyy: no, your Garmin RD POD
[05:19:20] Chris oh, running dynamic pod
[05:19:30] Chris just looking into this
[05:20:16] EyessOnlyy: yes, Running Dynamic POD :)
[05:20:49] Chris is this a brand new sensor?
[05:21:02] Chris has it worked previously?
[05:21:11] EyessOnlyy: yes, received it yesterday
[05:21:44] EyessOnlyy: and it's detected very fast in the Sensors&Accessories menu
[05:22:08] Chris are you using it with your Fenix 6?
[05:22:33] EyessOnlyy: I'm trying to use it with the F6, but it does not connect in the running app view
[05:24:07] Chris can you remove the sensor again
[05:24:18] Chris then follow the exact steps on this link.
www8.garmin.com/.../GUID-0AA57B88-BA13-4983-ADAC-7EA7DABC735D.html
[05:26:16] EyessOnlyy: done - it was removed, i added it again(for the 10th time). It does not show connected in the Run app
[05:29:08] EyessOnlyy: it just blinks, like it did all the times i've tried - yesterday i kept opened the run app view for almost 40 minutes, no success
[05:29:10] Chris just seeing if there any reports of this issue
[05:29:30] Chris have you tested the sensor on any other device by any chnace?
[05:30:02] EyessOnlyy: i do not have another 900Euros to spend on another expensive watch to test it
[05:30:20] Chris okay that's fine
[05:30:29] Chris i thought you may have an older watch
[05:30:35] Chris can see you have a few Edges also
[05:30:50] Chris okay so I have found a similar report on our end
[05:30:51] EyessOnlyy: yes, that's correct
[05:31:13] Chris so far two other customer have had this same issue
[05:31:20] EyessOnlyy: I've also sent an email on this topic - but got no answer
[05:31:21] Chris I can add you to the investigation
[05:31:22] EyessOnlyy: I know you don't care what other users say on forums - but you an see a lot of reports here: forums.garmin.com/.../running-dynamics-pod-not-connecting-to-fenix-6-pro
[05:33:08] Chris can you also confirm the software version of the device
[05:33:16] Chris under Menu > Settings > About
[05:33:26] EyessOnlyy: one moment
[05:33:35] Chris and do we have permission to access your account if needed
[05:34:34] EyessOnlyy: ID: 669959, SW Version: 2.40, Serial Nr. 3308927239, model: 2593
[05:34:48] EyessOnlyy: yes, you have my permission to access the account, if needed
[05:36:12] Chris I have now created a Product Support Case with the information you have provided to us.

[05:36:31] Chris Please be patient whilst we investigate the issue you are experiencing and we will be in touch with any updates as soon as possible.
[05:37:21] EyessOnlyy: can i have an IDentification number for this support case? so I can refer it for further questions, updates if any
[05:38:51] Chris it will be on your account
[05:38:56] Chris and I will leave it on the notes
[05:39:38] EyessOnlyy: ok
[05:40:10] Chris okay so we will update you as soon as possible
[05:41:06] EyessOnlyy: Thx, Chris! and have a nice day
[05:42:11] Chris you too :)
[05:42:14] Chris The conversation has ended. If you still need help please get back in touch!
[05:42:14]

Hi, EyessOnlyy, thanks for contacting the Garmin support, this might be quite helpful and may speed up to sort out the RDP issue.

Best, Road.

Yes, thats what I've seen the past two days.  Prior to that, these steps did seem to be a good workaround.  but this work around for reasons I cannot understand are not working anymore on the 4.10 firmware.  We'll get an update from Garmin.  I'm confident.  Hopefully its soon.

Very good, EyessOnlyy, another way of biasing the connectivity f6 / RDP problems.

I leave my f6 switched off anyway once I'm not doing a training session. So the watch ON / OFF is no extra thing on my side.

After a running session and prior to switch off the watch (or prior to the GC transfer) I REMOVE the RDP and forget about the pod until I am about to have another run.

Prior to the next run, I switch ON the watch anyway, and the next thing I do is searching the RDP. Will be always found. From this I immediately open the running app, where I find the RDP stably connected. Then going for the run, all running metrics are recorded.

Works for me very well, but of course it's not the real thing. Especially prior to competition races, I do not like to play around with my watch prior to the start.

Anyway Good Luck, I'm quite optimistic that Garmin will be sorting this out (often experienced in older devices, they will be quite bug-free (or more precise "bug-poor") several months after release).

Best,

Road.

On the new 4.20 firmware, I followed (for the most part) EyessOnlyy steps.  Had the run app open, and i added the RD pod.  Waited for conneted (pretty quick) and I had a solid icon.  so just went off running as it worked  the whole time.  When I was complete with the run, I turn the sensor "off" but did not delete it.

tomorrow I'll try the "turn the sensor" on approach

when i got home today I woke up the Pod sensor and follow the same steps as yesterday

- open run app view

- go to settings and switched ON the sensor

- it connected instantly and showed the RD Pod connected message

On the other hand, after yesterday's chat with Garmin Support i received an inquiry email asking for more details and precise data. I provided all what was possible(including the link to this topic)

Let's see if they are able to figure out the solution in a decent time frame.

Unfortunately 4.2 did not solve the RD Pod issue. Very annoying!

Did not solve?  Yours doesnt work at all?   Myself and others have the rd pod working on 4.20 so far.

One of my guess with v4.10 was that there was the sensor "cleanup" issues.  Meaning when an activity was over that used sensors, or when music stopped (BT headphones) there were remnants that over time made the sensors not work.   On 4.10 both RD pod and BT phones worked.  But as I accumulated more activities and attempts to use them, they ability for connections diminished.

I've only got one sample on 4.20 for RD pod and BT headphones.  We'll see tomorrow if they continue to work.