hSoftware Garmin Connect IQ Apps

Did some more testing. It seems that this 2m30s is very random. Sometimes it already freezes after seconds for example. Also, it seems that the field is not completely frozen, but updates once in a while (e.g. once every minute or so). Finally, when placing the watch on a desk, and starting an activity, the problem does not seem to occur. Only when really moving (riding, running), the hRecent field freezes after a while. Let me know if I can do more tests if it's useful for you to troubleshoot.

Thank yo for the message. Could you please provide some more details? Where you moving at the time, and had a good quality GPS signal? If you have access to the saved FIT Garmin file, and would be happy to provide it, that would be excellent.

Thanks for the reply. I was moving at the time (outdoors), and GPS signal was excellent. I don't have the FIT anymore, but just repeated the experiment and saved the new FIT. Problem is identical to last time. Now, the field froze somewhere between 2 and 3 minutes in time (don't know the exact time). See here for the .fit file: https://drive.google.com/file/d/1T5bvw657mMC0S7Qks8KKFsH5jGb1KwWo/view?usp=sharing

Thank you. The Garmin tools will allow me to replay this through the Data Field. I will let you know what I find.

Development work to complete this case has now started.

Hi, sorry I can't seem to find an issue. The Data Field continues to process the data. I am wondering if your settings (default would be over 500 metres) and speed mean the recent pace doesn't need to update very often, giving the impression that the figure is stuck (I saw 14:12 minutes per mile). It will move around very quickly at the beginning as it calibrates, however once enough data has been captured it will trigger every 100 metres (on a setting of 500 metres). You may want to lower this settings for these speeds to say 200 metres? Hope this helps Chris

No, it's not that the update is just slow because of small pace differences. Next to the hRecent, I have the Garmin field that shows lap pace. I matched the averaging distances (1km), so they should match. The Garmin field is constantly changing (by small increments though), but the hRecent field is really stuck. I tried by walking somewhat faster to see if it updates. The Garmin field indeed showed increased pace, but the hRecent one kept being stuck on the same number. After a while, the hRecent field suddenly updates, and at that moment it matches perfectly again with the Garmin field. But the update is just for a second or so, then it is stuck again till the next update in a minute or so. I tried the same with much higher paces, but same issue. Do you have the possibility to test on a real watch, outside? Maybe the simulator doesn't have the memory issues a real watch has?

Hi, Yes, the simulator restricts memory, however it could be your watch is busy and therefore the Data Field is not getting the necessary refresh rate. I have a Fenix 3HR, Fenix 5, Forerunner, Vivoactive and Edge 1000. Can I ask what settings you have? Please remember that a live pace will differ than once of a recent distance.

Hi, which Forerunner do you have? Did you test it outside during an activity? The live pace will indeed differ from the recent pace. I'm comparing to the Garmin lap pace however, which is also the average over 1km, restarting each lap (which is exactly what the hRecent is doing as well using my settings). It is set to average over 1km, and resetting every lap (1km as well in my case). Is this what you meant by the settings? Let me know if you need to no more, I'm happy to provide all the details.

Thanks for the update. By using a 1km, it will measure your pace over that distance. So in would only change once every km, or based on your pace about every 9 minutes. The Data Field will actually sample 5 times in that period, so I would expect any change to occur once every 2 minutes. How often does the lap get triggered?

I’ve just noticed you’ve got an 1km Laps. Sorry this will deliver the outcome you are seeing. The idea of the Data Field is to give you a pace over the last given distance. For example if you are running a 10k, current pace will be what you are on, average will be since the start and this Data Field will be over the last period. This helps you pace, without the constant changes given in current pace. Hope this helps.

Ah, okay. Thanks for the explanation. I was under the impression that it would constantly update, showing the average pace which is constantly updated with a 'moving average' over the last 1km (when the 'reset on lap' is disabled), or average since the beginning of the lap when 'reset on lap' is enabled. I think what you describe indeed explains the behavior I see.

Case closed as Data Field working as designed.