Data Field: Dozen Run Fields

Dozen Run, Swim, Paddle and Cycle Data Fields
After others are forcing you to pay for these applications, so I decided to make a great data field(s) and then keep them free. I'm a Software engineer, sponsored runner and run coach, I combined my engineering and running knowledge to bring you these streamline applications.

I put thousands of hours of bench and field testing these simple applications. So, consider a small donation.
Small donations (help keep my effort going) paypal.me/fbbbrown

Install Instructions:
This Data field needs to be added to the (specific) app within your watch to view.

This is a data field not an application and needs to be added to a single data screen within an application.
a.) Goto settings,apps,run,data screen,screen 1
b.)Set Layout to 1 Field
c.) Set Field 1 to ConnectIQ Fields, DozenRun
d.) run happy!

INSTALL ISSUES:
-"!" Issue: If you receive a "!", completely uninstall, reboot and then reinstall. The Setting file changed and the automated Garmin install is not replacing the setting file.
-Download Issue: if you have the "App requires an update before install", hard reboot your watch TWICE and install again.
-TIMER Issue: If you update/install and you see the TIMER and don't see the Dozen data field.
--The data field update or install may require a restart of watch.
--Or the data field needs added to the built-in application, again.

These are becoming a Data Field Suite, where all field are similar making it easier to read while in an activity.

The Dozen fields are intended for training, the data field works fine for speed work, track or races, but readability in these conditions maybe tougher.




IMPORTANT: If you have a Question, recommendation or problem.
Please provide as much as possible (for example the following):


1.) Watch type, Watch firmware version and ConnectIQ version.
2. programmed from Garmin Connect (phone type) or Garmin Express
3.) Which data field
4.) description of issue
5.) if its a "!" error include the error log from your watch. Connect your watch to a PC using USB cable. The error log is located x:\GARMIN\APPS\LOGS. copy the listing and paste in the post.


Layout Dozen Run Datafield fenix3
Cad|HR
Pace|Distance
Battery meter
Avg Pace| (bluetooth) Timer
Calories|Time|Elevation
GPS

Layout Dozen Run Datafield FR 230/235/630
Cad|HR
Pace|Distance
Battery meter
Avg Pace| (bluetooth) Timer
Elevation|Time|Calories
GPS

Layout Dozen Run Datafield FR 920XT
Pace|Timer
Battery meter
Avg Pace|HR| (bluetooth) Distance
Cad |Time|Elevation
GPS

Layout Dozen Cycle Datafield
Cad|HR
Speed|Distance
Battery meter
Avg Pace| (bluetooth) Timer
Calories|Time|Elevation
GPS

Layout Dozen Swim data field
Laps | SWOLF
Pace| Distance
Battery meter
Average Pace | (bluetooth) Timer
Calories| TIME | Stroke Type
GPS

Layout Dozen Paddle Datafield
AHR|HR
Speed|Avg SPD
Battery meter
Timer| Distance(bluetooth)
Cad|Time|AVG CAD (stroke distance)
GPS

Description for all fields
--All watch types are support for all data fields. Coded simple to keep bugs at minimum.
-Race Prediction completely configurable for any distance. Distance is entered in meters. Enter 1%-2% longer distance to adjust for normal GPS error and better race prediction.
-Cadence either from watch, footpod or crank cadence. Color coded to provide instant readability
-Heart Rate field is configurable to several methods: calculation (default), manual entered max HR, or individual zones Color coded to provide instant readability
-Pace/Speed is a rolling average to give a smooth reading configurable from 1 second to 120 seconds (Metric or statute by user setting)
-Distance is the total distance for the activity (Metric or statute by user setting)
-Timer is the actual time of the active time. Not Elapsed time.
- Battery meter uses the entire screen for reliability and acts as a divide to help focus one the upper fields.
-Avg Pace\Speed is a Garmin's provided datafield. (Metric or statute by user setting)
-Calories is the activity calories.
-Elevation based on Garmin's values. (Metric or statute by user setting)
-Time of day either in 12hr or 24 hour (based on user setting)
-(Fenix3/920)Auto background color Black or White background based on app settings
-(230/235) Configurable background color Black or White background (user configuration)
-GPS uses same indicator as iPhone for GPS signal. 5=full, 4=usable, 3=poor, 2=unused, 1= last location & 0 = no GPS
-Blue Tooth connectivity is shown as a blue "B"
-Paddle Stroke distance is a calculated by actual speed / cadence. Displayed in Meters/Feet.


#runhappy
  • Is max average pace period with Fenix 3 HR now 25s? Used to be 60s.


    Additional features and Memory limitations required me to make the reduction. Perhaps the newly released compiler is more efficient and I'll be able to restore the longer pace periods. I will be updating my Datafields in the next week.
  • Additional features and Memory limitations required me to make the reduction. Perhaps the newly released compiler is more efficient and I'll be able to restore the longer pace periods. I will be updating my Datafields in the next week.


    Thanks, I was thinking something like this must be the reason.

    Please see if you can raise the time period even a bit, 25s just isn't quite enough for dense overhead places - though of course it should be but I know from looking at recorded data this is Garmin's fault. With 60s pace is just beautifully stable, always. Even say 45s would most likely be a decent improvement.
  • Former Member
    Former Member over 9 years ago
    You could save memory on longer averages by not updating the live value as often.

    For example, save the sum of every 2 seconds into a circular buffer instead of each individual second. This eliminates about half of your data requirement with the trade off of only updating the screen every other second, which seems reasonable for such a heavily filtered value. This could be done at an even lower rate to save more space.

    Another option is to implement a filtering method that doesn't require a history buffer like a low pass filter. I don't know if this will produce the type of results you are looking for, but would take less memory if it produces an output you like.
  • Thanks, I was thinking something like this must be the reason.

    Please see if you can raise the time period even a bit, 25s just isn't quite enough for dense overhead places - though of course it should be but I know from looking at recorded data this is Garmin's fault. With 60s pace is just beautifully stable, always. Even say 45s would most likely be a decent improvement.


    Working with the 2.1 SDK I should be able to put the rolling pace back to 60.
  • Hey FBBROWN, thanks again for all the effort you're making with these data fields.

    I have noticed that the Dozen Run field on my Fenix3 still shows elevation instead of accumulated ascent.
    Could you change this back again as elevation isn't really meaningful compared to ascent with regards to training?

    Thank you very much!
  • @RobertRehnmark-RawViking is it not a configurable option in GarminConnectMobile/Express (it is in the Dozen Cyclefields) to flip that display between Elevation & Ascent?
  • @RobertRehnmark-RawViking is it not a configurable option in GarminConnectMobile/Express (it is in the Dozen Cyclefields) to flip that display between Elevation & Ascent?


    It used to be.
    But now that option is gone.
    .. and so is the manual setting for start of Zone2, this kinda sucks for me since the calculated MaxHR and zones are MUCH lower than my actual numbers.
  • It got broken in Express 4.1.23 - fixed again in 4.1.24 though... could that be it?
  • @RobertRehnmark-RawViking is it not a configurable option in GarminConnectMobile/Express (it is in the Dozen Cyclefields) to flip that display between Elevation & Ascent?

    I never enabled that selection in the run version. if there is a demand i will put it in.
  • I never enabled that selection in the run version. if there is a demand i will put it in.


    I think it was there in the beginning?
    Anyways, please enable it! :)
    .. along with the setting for start of Zone 2. (The default calculated numbers are way off for me and probably for most other people too.)