Data Field: Surf Tracker

[FONT=Arial Black]Surf Tracker[/FONT]

Version 1.20
https://apps.garmin.com/en-US/apps/ded87d46-5477-4ca7-a247-847b896393e0

Track your surfing sessions in real time! This data field estimates the number of waves ridden using a speed and time threshold to mark the start and end of a wave ride.

Info shown (from left to right):

  • your total number of waves ridden and the total wave ride time (min:sec)
  • for your latest wave ride: wave ride time (seconds), maximum speed during the wave ride (km/hr or mph) and the distance covered (meters or yards)
  • the numbers in red show the maximum values for the wave ride time, speed and distance during the activity
  • For square watches, the bottom line shows the time of day and elapsed time of the activity. For round watches and the Vivo HR, the top line shows the time of day and the bottom line shows the elapsed time.




Notes:

1) This data field must be used in a 1-field data screen and should be set up before starting the activity. I use an Activity > Other > Paddle, but any activity with GPS ON should work. Open water swim will work but the GPS tracks are noisier since the sampling rate is lower, but it may be the better option for surfing when your arm is in and out of the water. Some activities smooth the speed data more than others and will give less accurate results (eg. a walking activity will not work as well as paddling or cycling). Vivoactive users try the Cycling activity, the Run activity will smooth the speed values to much to even out the Pace and this won't work well with the wave detection.

2) The summary stats and a speed plot are saved to Garmin Connect once the Activity is ended and saved:


3) This has been tested many times with standup paddle surfing. It has taken a while to get the thresholds working accurately. The detection thresholds can be changed using the Garmin Connect Mobile app (see https://forums.garmin.com/showthread.php?332843-How-to-App-Settings for help):

There are four settings to mark a wave ride based on speed, time and distance.


An event starts when the speed is >= 9 kph, it must last at least 6 seconds (above 9kph) and have a max speed of at least 13 kph to be counted. The event ends when it falls below 9kph. The min distance is set to 0m, but this can be changed to avoid false detections. These thresholds work well for standup paddle surfing, but try changing them and post your results. It should work for: standup paddle surfing, surfing, kayak surf, surf ski and maybe standup paddle downwinding.

Threshold ranges and defaults:
1) Start/stop threshold: default 9kph, range 5-50 kph
2) Time threshold: default 6s, range 2-60s
3) Max speed in event has to be >= 13kph, range 0-50kph
4) Min distance: default 0m (disabled), range 0-1000m

Typical values:
Standup paddle surfing: general setting for all waves
9kph, 6s, 13kph, 0m

Standup paddle downwinding (Hood River)
10kph, 10s, 12kph, 20m

4) The stats from each wave ride can be saved to a text file using the instructions at the bottom of the page (advanced users only, unsupported).

----------------- Planned Updates------------------

1) none hopefully


----------------- Version History ------------------

0.2 datafield now updates even when not visible.

0.3 added min distance to threshold test (now min 9km/hr for 5s and 15 m) to avoid paddling out/false wave counts, especially for SUP (eventually these values will be user selectable).

0.4 more tweaks after on-water tests (now min 9km/hr for 6sec), 19 waves and only 2 false readings and that was when I was chucked over the falls...

0.5 changed totdist and elapsed time to use the last good point of the event, instead of first one below the threshold, since when falling in it might take a while to get gps fix again and this will add to the waveride time. This should only decrease the wave ride time. The threshold test is now: >= 9km/hr for >= 6 sec and maxspeed >= 13 km/hr, redesign screen, add total wave ride time in min:sec

0.6 add fenix support.

0.7 bug fixed- crash when data field is in view and GPS just becomes active

0.8 D2Bravo, Epix and Vivoactive (separate app) support, compile using SDK 1.1.4. Latest numbers are green during an event (shows green if above speed threshold, even if below time threshold).

v0.9 new SDK 1.2.1, support for fr230/fr235

v0.95 new SDK, 2.1.3, support for Vivoactive HR

v1.0 added GCM settings for thresholds, changed distance calculation (should be shorter and more accurate), added 1 field Vivoactive support (got rid of the separate version)

v1.20 Garmin Connect summary stats and wave speed plot output
_________
** Advanced user only+unsupported method to save each wave ride to a text file on your device:

Place a *.TXT file in the /GARMIN/APPS/LOGS folder on your device, where * is the name of the .PRG file in the /GARMIN/APPS folder. Look for a file that is ~12 kilobytes. On my device it is 69SI5820.PRG, so I would create an empty file in /GARMIN/APPS/LOGS/69SI5820.TXT

To find out the filename, uninstall Surf Tracker, make a note of the *.PRG files in the /GARMIN/APPS folder, install Surf Tracker then note which PRG file is new.

Sample output format:
Wave# TimeofDay WaveRideTime(sec) WaveRideMaxSpeed(kph) WaveRideDistance(m)
1 07:26 20 28.8 113.4
2 07:28 13 27.6 76.8
3 07:33 21 30.2 122.2

Copy the file to your computer after a few sessions. I copy and paste the details into the notes section of the activity on Garmin Connect. The file will be appended to until it gets too big (10KB), then it will be overwritten. I had 3 days of sessions saved and it was only 1.8KB.
  • Fenix 3 v3.00 firmware is available, and I just tested this data field--it works without any issues.
  • That's good news...thanks for checking :cool:
  • I have a similar problem with my 920xt. Surf Tracker had been working great until this last update. I now get the IQ! screen but the app still tracks, however, it totally resets the watch and looses any steps I had been tracking that day and resets the watch face. frustrating.
    A data field (or any Connect IQ app) should not cause the device to reset, so I've filed a ticket to investigate this crash. Generally, a buggy app should only crash the app (display the IQ logo with and exclamation mark like Brian described). This may be more related to the Fenix 3 firmware than anything, so I'll give it a test on 2.90, and then try a newer release. We've had a couple of internal releases to address some of the known issues, and I believe we have a 3.xx release that should be made available to the public soon. I'll update here once I know more.
  • Damn sorry to hear that. What fw on the 920? I'm on 3.07 and it runs fine.
  • @Z3N5URF please try fw ver 3.2 on your 920xt and report back. It seems a lot more stable for ConnectIQ apps etc - when it does crash you get the IQ logo instead of having the watch restart.

    I also fixed a bug -> when the data field was displayed and GPS went from inactive to READY the data field would crash. I had to add some more checks but it seems better now. Data field v0.7.
  • Hi @bwd1! Seems a really nice app, I'm looking forward to test it in my 920. However, I would like to ask you - any plans to release it for the vivoactive?
    Thanks!
  • No plans right now for the Vivoactive mainly because:

    1) it seems like the vivoactive does not allow the screen to be set up for only 1 data field. It only shows 3 so there would be very little room for all of the info in 1/3 of the screen.

    2) the data field is nearing the max memory and adding another device would bring it even closer. I want to save some room to add some code for user input of threshold values when/if that becomes available.

    I suppose if there was enough demand I could do a Vivoactive only version that showed only #waves and current values (no max). I'm not sure how many people would use it...?
  • No plans right now for the Vivoactive mainly because:

    1) it seems like the vivoactive does not allow the screen to be set up for only 1 data field. It only shows 3 so there would be very little room for all of the info in 1/3 of the screen.

    2) the data field is nearing the max memory and adding another device would bring it even closer. I want to save some room to add some code for user input of threshold values when/if that becomes available.

    I suppose if there was enough demand I could do a Vivoactive only version that showed only #waves and current values (no max). I'm not sure how many people would use it...?


    Hi bwd1, thanks for your reply and explanations. I understand the limitations, maybe in the future it would be possible. I'm not sure about demand, but what I can say is that in my surf community lots of people run and some have the RipCurl watch. What I'm telling them is that with the new garmins maybe it's possible to combine all. Unfortunately the 920 is too expensive to most of them, but the vivoactive would be a go. Thanks anyway!
  • Hi bwd1,
    Just back from my surf session, and your app is just crazy !! I works weel for me.
    I didn't compare with the RipCurl Watch because my friend is not here.

    2 things missings:
    - When you save the workout, it puts me in the category "inside fitness exercises". And can't see my stats (number of waves, max speed, longest wave, etc...). Do you know if you could put this in the "comments" of the workout or other ?
    - Can we just see the GPS lines when surfing, because other way you see all your way (paddling + surfing) and it's not easy to read.

    Anyway, good job ;)
  • Thanks for the feedback @lbehin, glad it works. Don't forget to add your review to the store.

    To see your stats, follow the instructions at the bottom of the page. It will save the details of each wave to a text file that you can copy and paste into your workout comments:
    https://apps.garmin.com/en-US/apps/ded87d46-5477-4ca7-a247-847b896393e0

    That is all I can do for now using a data field. Perhaps a real app can be made in the future to show the GPS lines and save the stats.