After searching a while on the net I’ve understood that GpsBabel can’t read from Garmin Oregon 600 because this device does not support the Garmin serial protocol. Sigh.

But I think it’s a bad idea that GpsBabel just silently delivers an empty output file without generating any error message. This will confuse a lot of users.

 

 

gpsbabel.exe -D 4 -w -r -i garmin -f usb: -o gpx -F test.xml

GPSBabel Version: 1.4.4

options: module/option=value: gpx/snlen="32" (=default)

options: module/option=value: gpx/snlen="32" (=default)

 

Output file test.xml:

 

<?xml version="1.0" encoding="UTF-8"?>

<gpx

  version="1.1"

 creator="GPSBabel - http://www.gpsbabel.org"

  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

  xmlns="http://www.topografix.com/GPX/1/1"

  xsi:schemaLocation="http://www.topografix.com/GPX/1/0 http://www.topografix.com/GPX/1/0/gpx.xsd http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd http://www.garmin.com/xmlschemas/GpxExtensions/v3 http://www8.garmin.com/xmlschemas/GpxExtensionsv3.xsd http://www.garmin.com/xmlschemas/TrackStatsExtension/v1 http://www8.garmin.com/xmlschemas/TrackStatsExtension.xsd http://www.garmin.com/xmlschemas/WaypointExtension/v1 http://www8.garmin.com/xmlschemas/WaypointExtensionv1.xsd http://www.garmin.com/xmlschemas/TrackPointExtension/v1 http://www.garmin.com/xmlschemas/TrackPointExtensionv1.xsd">

<metadata>

<time>2013-10-26T11:24:46Z</time>

</metadata>

</gpx>