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

IQ datafields not loading 50% of the time?

1848381

So about 50% of the times I start the 1050, the iq datafields (all of them) won't load, when a ride is already in progress it seems to work more often than not, but a "cold" boot is a coin flip at the moment.

A reboot will usually fix it, but the next day it'll likely occur in the morning as well.

  • 0

    https://forums.garmin.com/developer/connect-iq/f/discussion/242411/fit-contributions-limit

    Do you think you have more than 15 contributions to your .fit file via data fields? For example the Core Body Temp records at least 4 to the fit file. Skin temp, core temp, data quality, and one more. My Bike Radar Traffic records location and passing speeds and other things. You can get to 16 pretty fast and when you do, fields crash.

    I had this exact same thing on my 1040, and it moved to my 1050 even though I didn't migrate profile over. After some digging around, the .fit file contribution limit was the issue. I had to cut a data field that I liked out of the mix. On the 1040 the double reboot fixed it usually. On the 1050 I didn't feel like messing with it all the time.

    Take a look at the data fields, and then at your .fit file, and see if you're hitting that limit. I'm willing to bet you are.

  • 0 in reply to cycleanalyze

    Hmm, took a peek, but I didn't see any errors in there.

    We're talking about an activity fit file, correct?

    = TYPE=12 NAME=record NUMBER=20
    --- timestamp=1107706376=2025-02-05T16:12:56Z
    --- position_lat=619364198=51.9145074 deg
    --- position_long=52527532=4.4028069 deg
    --- distance=692614=6926.14 m
    --- enhanced_speed=3900=14.040 km/h
    --- enhanced_altitude=2520=4.0 m
    --- heart_rate=127=127 bpm
    --- cadence=41=41 rpm
    --- temperature=15=15 deg.C
    --- fractional_cadence=0=0.00 rpm
    --- xxx107=1=1
    --- xxx137=91=91
    --- xxx138=91=91
    --- xxx144=127=127
    --- 0_1_devicebattery=72=72
    --- 0_2_frontShift=0=0
    --- 0_3_rearShift=0=0
    --- 1_0_headlight_mode=0=0

    (Random point during a ride)

  • 0 in reply to 1848381

    Contributions to fit file I mean data written to the fit file by data fields. At more than 15 the IQ fields crash. If I could attach an image to a forum post I would show you that there are 13 fit file contributions in a fit file that I have

  • +1 in reply to cycleanalyze

    Where can I find what the contributations are?

    Which file?  Above was an excerpt of what gets logged every second on my system.

    I only use....  4 at the moment?,  smart bike lights,  all in one and a water points radar.

    The all in one had the ability to log the battery and the smart bike light the light mode,  I turned all those off and it still happened this afternoon.

    Didn't have this problem with my 1030 plus either :/

  • 0 in reply to 1848381

    All in One is the datafield I created.
    I don‘t think that fit contributions are your problem.
    There must be another problem with your device. I know, it‘s a pita, but I would suggest a hard reset of your device.

  • 0 in reply to mcinner1

    Yea,  I wasn't expecting it or smart bike lights to be the cause, but it's always better to rule everything out.

    A hard reset did seem to "fix" it for now.

    Did learn that the profile backups are not up to date or complete though and (android/the 1050) dont have the "backup now"  functionality that is claimed in connect.

    To be sure I gave it another hard reset and set it up from 0, just to rule out profile shenanigans.

  • 0 in reply to 1848381

    …and to rule out IQ datafields: add one after another with inbetween testing…

  • 0 in reply to mcinner1

    Just wanted to confirm after about a week of usage.

    The problem did not return.

    So for others running into this in the future and ending up here, just do a hard reset and stay away from the backup of other systems... Just start fresh when you get a new unit and save yourself a headace troubleshooting weird bugs :/

Copyright © 1996-2025 Garmin Ltd. or its subsidiaries