Data field: Flexirunner

Hi there. I'm using a Garmin 920xt. I placed the connect IQ data field on my run layout and field. It works up until I start the run. Then it stops and shows the IQ logo with exclamation point. But the watch still works. I scroll down to a different screen and it still shows my other data and distance. It's just in the screen where I have flexirunner data field. Would really be grateful for any advice.

Hi, sorry to hear that. So you see the layout fine but as soon as you press start it crashes and the IQ logo appears? First, make sure you are running the latest version by uninstalling and reinstalling the data field. If that doesn't solve it, I can give you a debug version to try if you are able, which will help me figure out why the crash occurs (I don't have a 920XT myself to test it on, I rely on testing it in a simulator on my PC).

Very handy datafield indeed! Very useful using 1k autolaps on long tempo runs like the one I did yesterday. The only issue is the "Current lap pace" being rather optimistic for about 30 seconds (sometimes more) after a new lap starts, I don't remember the stock lap feature as doing that? There must be some "disconnect" between the timer and distance info fed into CIQ ? I'll try "Current lap moving (running) pace" to see if it helps, although since it's already optimistic it probably wouldn't.

I also use a footpod with my FR235 and have it set to use it for instant pace, Flexirunner has access to the footpod data too?

The only issue is the "Current lap pace" being rather optimistic for about 30 seconds (sometimes more) after a new lap starts, I don't remember the stock lap feature as doing that? There must be some "disconnect" between the timer and distance info fed into CIQ ? I'll try "Current lap moving (running) pace" to see if it helps, although since it's already optimistic it probably wouldn't.

Yes, current lap pace is simply current lap distance divided by current lap time. For the first 20-30 seconds this formula can be quite noisy due to the inaccuracies of GPS for short distances. As the lap progresses, the average pace value becomes more stable (signal to noise ratio increases, effectively). I think that native lap pace feature actually just reports current (instantaneous) pace for the first 20 seconds or so, it is on my todo list to investigate whether to replicate this in Flexirunner too. Sounds like it might be worth it.

I also use a footpod with my FR235 and have it set to use it for instant pace, Flexirunner has access to the footpod data too?

Me too. Flexirunner doesn't direct access to the footpod data, that isn't available in Connect IQ. The pace provided by Connect IQ (and thus reported by Flexirunner) will come from the foot pod if you have it set so in the watch settings, and/or if there is no GPS data, but there isn't the option to forcibly choose the source in Connect IQ.

This does present a theoretical quirk for the lap pace problem above, in that current pace from the foot pod requires a properly calibrated factor to be correct. If, for example, the calibration factor is out, and the first 20 seconds of lap pace is reporting current pace, then there could be a shift after 20 seconds when lap pace switches to the distance/time formula. It might turn out to be not really be a problem, I suppose. I have never paid attention to lap pace early on to test it so far.
I leave mine on auto-calibrate, though I don't know when or how it does the calibration.

In addition, cadence comes from the foot pod, but, again, the value presented by the watch via Connect IQ is, I think, actually a fusion of both the foot pod and the watch accelerometer. It's unclear what the priority is (developer docs seem to suggest the watch accelerometer, but that would mean the foot pod is never used..?), but you can see that if you have a foot pod connected, swinging your arm whilst standing still reports a cadence (from the watch), yet you also still get meaningful cadence if you run whilst, e.g. pushing a buggy (when the cadence must come from the foot pod). You basically have to trust the watch to give you the best source of cadence.

Thanks for the insight, would be interesting to see if you can track down the way Garmin is doing it for lap pace. I do remember that 20 second "delay" on the FR610 but was it only if you had a footpod?

I went back to my footpod settings and found that I'd used a 102.5 calibration factor instead of auto-calibration, I must have had a good reason to do that ;-) It's too bad there isn't a menu like on the FR610 to calibrate on a track or over a set GPS distance to get the calibration values for various paces as I'd found that it varied quite a bit even though the footpod is supposed to account for that. Maybe that's what auto-calibration does but I wonder what the inertia is...

A small suggestion, could the text in the bottom right field be colored for easier quick reading, say in green ?

I had "lap pace" but I've switched to "current pace" to keep it consistent with the RunnerWindowFR field I use as the "first" screen.

I'd found that green text on black on a beta version of RunnerWindowFR made it easier with a quick glance, mostly I suppose because it made it stand out compared with the other fields. Maybe it wouldn't work as well with green text on white.

I had "lap pace" but I've switched to "current pace" to keep it consistent with the RunnerWindowFR field I use as the "first" screen.

I'd found that green text on black on a beta version of RunnerWindowFR made it easier with a quick glance, mostly I suppose because it made it stand out compared with the other fields. Maybe it wouldn't work as well with green text on white.

There isn't a current pace option for the lower fields...:confused: that is only shown in the centre field.

There also isn't the option to use a black background in Flexirunner on the FR235.

I was able to select "Moving (running) pace", wouldn't that be the equivalent of "current pace" ?

Yes the black background was in RunnerWindowFR, would still be interested in seeing if a green (or another color, red/blue) would help when you take a quick glimpse, no biggie though ;-)

Ah, no, perhaps I need to reword that. Moving (running) pace is average pace, but with any time spent walking or stopped filtered out. All of the pace metrics selectable in the lower fields are averages (either overall, lap, or last lap).

Oh I see, since it was the same label as in the middle center field I assumed it showed the same data. I have now reverted back.