Editing ClubWiki:Garmin Protocol Devices
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
This documentation is based on usage for the Garmin Forerunner 305. It is likely similar to other Garmin GPS devices not only the Forerunner line but specifically those that use the [https://www.gpsbabel.org/htmldoc-development/fmt_garmin.html Garmin communication protocol] for interaction. Simply, if you plug the USB based device in to your computer, if you can't access the file contents, | This documentation is based on usage for the Garmin Forerunner 305. It is likely similar to other Garmin GPS devices not only the Forerunner line but specifically those that use the [https://www.gpsbabel.org/htmldoc-development/fmt_garmin.html Garmin communication protocol] for interaction. Simply, if you plug the USB based device in to your computer, if you can't access the file contents, the retrieval method should be similar. | ||
__TOC__ | __TOC__ | ||
Line 10: | Line 10: | ||
=== Tracks === | === Tracks === | ||
A complete Path or Track is the time from when a trip was started on the device until the trip was reset (i.e. timer and distance | A complete Path or Track is the time from when a trip was started on the device until the trip was reset (i.e. timer and distance reset to zero). | ||
'''Note:''' Resetting the trip using the Lap/Reset button does not erase the recording from the device. You can safely record several Tracks on a single outing or over multiple days, resetting between segments or trips. Resetting will remove the display of previous trips from the map view (but it's still safely stored). | '''Note:''' Resetting the trip using the Lap/Reset button does not erase the recording from the device. You can safely record several Tracks on a single outing or over multiple days, resetting between segments or trips. Resetting will remove the display of previous trips from the map view (but it's still safely stored). | ||
Line 18: | Line 18: | ||
If a previous trip hasn't been reset, do so by holding Lap/Reset for 3-5 seconds. Then simply "Start" a trip by pressing the Start/Stop button. Depending on your configured display you should see the timer begin counting from zero as well as the mileage. | If a previous trip hasn't been reset, do so by holding Lap/Reset for 3-5 seconds. Then simply "Start" a trip by pressing the Start/Stop button. Depending on your configured display you should see the timer begin counting from zero as well as the mileage. | ||
If stopping for an extended period of time (e.g. lunch) or taking a diversion you don't want recorded (e.g. running back for a dropped item) you can Pause logging by pressing the Start/Stop button. Then when ready to resume the current track, press Start/Stop again. The device will resume logging of location history and will draw a straight line between the last and next location recording (regardless of time or distance traveled while it was paused). In my experience this is dangerous as I have often forgot to restart it again when I finished lunch or returned from the diversion. | If stopping for an extended period of time (e.g. lunch) or taking a diversion you don't want recorded (e.g. running back for a dropped item) you can Pause logging by pressing the Start/Stop button. Then when ready to resume the current track, press Start/Stop again. The device will resume logging of location history and will draw a straight line between the last and next location recording (regardless of time or distance traveled while it was paused). In my experience this is dangerous as I have often forgot to restart it again when I finished lunch or returned from the diversion. These can be edited out later in software. | ||
=== Waypoints === | === Waypoints === | ||
Simply... | |||
# Go to the menu using the Mode button | # Go to the menu using the Mode button | ||
# Select Navigation | # Select Navigation | ||
Line 31: | Line 29: | ||
Some notes from my experiences | Some notes from my experiences | ||
* Stop and take any pictures or notes before marking a waypoint - this might give the device | * Stop and take any pictures or notes before marking a waypoint - this might give the device to settle in on your true current location | ||
* Don't try to name the logged waypoints on the device, either | * Don't try to name the logged waypoints on the device, either | ||
** Take notes noting the location and auto generated number (phone, notebook, paper, etc.) | ** Take notes noting the location and auto generated number (phone, notebook, paper, etc.) | ||
** Or take a picture of the waypoint number shortly after photographing your object (lookout, trail intersection, blowdown, etc.) | ** Or take a picture of the waypoint number shortly after photographing your object (lookout, trail intersection, blowdown, etc.) | ||
* The device | * The device as an absurdly small number of waypoints it will save in memory. I think 100. Ideally Delete All before starting a trip, especially if the numbers are approaching 100. Otherwise delete one at a time as needed if you unexpectedly hit the limit during your outing. | ||
** Go to the menu using the Mode button | ** Go to the menu using the Mode button | ||
** Select Navigation | ** Select Navigation | ||
Line 43: | Line 41: | ||
== Data Retrieval == | == Data Retrieval == | ||
This describes getting the waypoints and tracks (paths in Google Earth parlance) off the device and onto your computer. | |||
# Connect the device | # Connect the device | ||
# Launch GPSBabel | # Launch GPSBabel |