DataFields : 367 RunFields

Update 2015-09-15

Have started to upload V2 of the 367Bike and RunFields to the App store.
367BikeFields is Live.
367RunFields is Live

The new version adds TimerTime, also adds the seconds on the timer once you reach > 1hr. (I'm told that seeing seconds is especially important for runners)

Note for all : Please refer to the app store for the latest in the NEW direction the app/datafield is going.
Go PRO! GO UnLimited!!

  • TOD (Time Of Day)
  • Timer Time
  • Pace 10s / Current Speed (in KM or Miles)
  • Cad
  • HR
  • Dist (either Miles or KM)
  • Avg Pace / Avg Speed


Many Thanks to SimonMcMullen for his code guidance.
Many Thanks to TORSTEINVH for his guidance on how to make an moving average (tho it's still a hack and not pretty code)


367RunFields-VA - http://apps.garmin.com/en-US/apps/0d38cc9d-78d9-46e1-85d4-9b4b2742a4bc
367RunFields-F3 - http://apps.garmin.com/en-US/apps/01ff5476-3b6a-499f-9253-404724f5d642
367RunFields-920 -http://apps.garmin.com/en-US/apps/f7daa40d-bc9d-4456-ad12-65cf43e5782c


367BikeFields-VA - https://apps.garmin.com/en-US/apps/8469d7cf-07af-4046-9a5e-c9c6345b219a
367BikeFields-F3 - https://apps.garmin.com/en-US/apps/617b1adc-c42e-46e2-aac9-1ab56618971e
367BikeFields-920 - https://apps.garmin.com/en-US/apps/e2e00ba3-452b-4798-8b5d-f272fc7cbe63


For Full configurability of all the fields in the 4 datascreens offered, take a look at these apps
F3 : https://apps.garmin.com/en-US/apps/b...9-2fcfefdf466d
VA: https://apps.garmin.com/en-US/apps/1...1-937d99f95fea
920: https://apps.garmin.com/en-US/apps/0...b-35c893b25356

Also has :
Time in zone.
Virtual partner

Generic Recorder: - for other activity profiles which are not Weight Lifting / Running and Biking
https://apps.garmin.com/en-US/apps/b...a-23afd94009c4
  • Sorry if I was not clear.

    In a workout (running) I press the button 'enter' to stop the timer. I get a message to resume. save or throw away te session. The timer (stopwatch) is stopped at that time. When I resume, the stopwatch resumes.

    But the ELAPS stays running when I press the 'enter' button. The ELAPS and the Timer give different readings from that point.

    Is that intentional? I would prefer the ELAPS and the timer to behave the same on hitting 'enter'. Is that possible?


    thanks for clearing that up.
    yes. it's a feature :-p (from Garmin)

    google up on how Garmin does the timing. There is (from memory)

    1) TIMER
    2) MOVING time
    3) Elapsed time
    4) auto pause
    5) custom pause speed.

    hahahah.... so.. you have a myriad of choices

    Jokes aside (if you are laughing)

    Diff between TIMER and ELAPSED is

    TIMER = only takes into account moving time
    ELAPSED = everything since you started the activity. You go pee. You go for 2 hour coffee break etc. It's all counted.

    Hence, ELAPSED and TIMER are not the same.

    BTW - as a 920xt user, would you find 9 fields (like in the VA screenshot on the garmin app store page) useful? Albeit - the numbers will be smaller.
  • thanks for clearing that up.
    yes. it's a feature :-p (from Garmin)

    google up on how Garmin does the timing. There is (from memory)

    1) TIMER
    2) MOVING time
    3) Elapsed time
    4) auto pause
    5) custom pause speed.

    hahahah.... so.. you have a myriad of choices

    Jokes aside (if you are laughing)

    Diff between TIMER and ELAPSED is

    TIMER = only takes into account moving time
    ELAPSED = everything since you started the activity. You go pee. You go for 2 hour coffee break etc. It's all counted.

    Hence, ELAPSED and TIMER are not the same.

    BTW - as a 920xt user, would you find 9 fields (like in the VA screenshot on the garmin app store page) useful? Albeit - the numbers will be smaller.


    A 9 field view will not suit me, because I use reading glasses (which I don't use while sporting :))

    PS. is it possible to have an alternative app where you replace ELAPS by TIMER? I would appreciate that very much,
    regards
    Huub
  • A 9 field view will not suit me, because I use reading glasses (which I don't use while sporting :))


    Ah.. I see.
  • Former Member
    Former Member over 10 years ago
    Don't get a a cadence on runfields. any reason why this might be.
    Thanks
  • That's a first I've heard of such an issue. I can't offer any suggestion other than... You're a VA user, and typically from what I noticed. VA users have a hard time w the watch.

    Just my observation.

    So, u see everything except the cadence? Does the VA have cadence? But funny. Quite a lot ofnVA users and none has complained about a blank field.
  • running dynamic

    looks like a very useful data screen.
    Is there any plan to release a version that supports running dynamics?
    Since I run mostly on treadmills, the pace & avg speed are really not that useful for my purpose but I always dedicate a field that shows Vertial Oscillation.
  • I'm not sure that is exposed by the API
  • Can anyone give a brief instruction on how to bring it up on Fennix three after down loading?

    Also how would I go about writing app/widget for kyaking?
  • Former Member
    Former Member over 10 years ago
    That's a first I've heard of such an issue. I can't offer any suggestion other than... You're a VA user, and typically from what I noticed. VA users have a hard time w the watch.

    Just my observation.

    So, u see everything except the cadence? Does the VA have cadence? But funny. Quite a lot ofnVA users and none has complained about a blank field.


    I do get a cadence for the runfields just no "A Cad" for the bike. But maybe it's my va. I got other troubles too (with watchfaces)
  • Can anyone give a brief instruction on how to bring it up on Fennix three after down loading?

    Also how would I go about writing app/widget for kyaking?


    Start >Apps > Run/Bike > add a data screen with 1 field, choose that field to be 367Run/367bike (whichever one you downloaded).