

qLandkarte plugin for Garmin Oregon (tested on model 450)
=========================================================

    Thilo Fromm, July 2010
    <kontakt@thilo-fromm.de>

----------------------
            TOC
    1. Status
    2. Problems
    3. Plans

    Appendix: Oregon 450 "whatGarmin" scan protocol dump
----------------------


1. Status
#########

    Some of the (basic) protocols the Oregon supports are documented by Garmin; see
    <http://www8.garmin.com/support/pdf/iop_spec.pdf>. As far as things are documented
    they will get implemented. Major things, like map upload, or waypoint or 
    route exchange are not documented.

    Here is what's implemented and working (which isn't much):
    ----------------------------------------------------------

    * The Oregon is recognized and initialised.
    * Downloading tracks from the device into qLandkarte works.
    * Real Time PVT data works (aka "Live Log").


    1.1. Connecting the Garmin
    --------------------------
    - Configure the device's USB interface mode to "Garmin Spanner" 
      (Setup->System->Interface on the device)
    - Connect the device to the computer
        - Select "No" when the Garmin asks you whether you'd like to go mass storage
    - fire up qLandkarte
    - download tracks to the computer

    !?#@?!   If you encounter problems, please report to the qLandkarte mailing list   !?#@?!   
    !?#@?!            at <qlandkartegt-users@lists.sourceforge.net>.                   !?#@?!   


2. Problems
###########

    A lot of the protocols the Oregon supports are undocumented. The most current 
    Garmin specification dates back to May 2006.



3. Plans
########

    In order to fully support the Oregon in qLandkarte the operation semantics of the
    undocumented protocols need to be reverse engineered.

    The Oregon should be fully supported by qLandkarte.



Appendix
########

    Oregon 450 "whatGarmin" scan protocol dump
    ==========================================
    Protocol: P0
    Protocol: L1
    Protocol: A10       <- A  10: Device command protocol #1
    Protocol: T1
    Protocol: A301      <- A 301: track log transfer protocol
    Protocol: D312
    Protocol: D302
    Protocol: A500      <- A 500: Almanac transport protocol
    Protocol: D501
    Protocol: A600      <- A 600: Date and Time initialisation Protocol
    Protocol: D600
    Protocol: A601      <- A 601: ???
    Protocol: D601
    Protocol: A700      <- A 700: Position initialisation protocol
    Protocol: D700
    Protocol: A800      <- A 800: PVT
    Protocol: D800
    Protocol: A900      <- A 900: ???
    Protocol: A902      <- A 902: ???
    Protocol: A903      <- A 903: ???
    Protocol: A904      <- A 904: ???
    Protocol: A905      <- A 905: ???
    Protocol: D900
    Protocol: A908      <- A 908: ???
    Protocol: D911
    Protocol: A912      <- A 912: ???
    Protocol: D912
    Protocol: A913      <- A 913: ???
    Protocol: D913
    Protocol: A916      <- A 916: ???
    Protocol: A917      <- A 917: ???
    Protocol: D917
    Protocol: A919      <- A 919: ???
    Protocol: A1010     <- A 1010: ???
    Protocol: A918      <- A 918: ???
    Protocol: D918
    Product name: Oregon 450 Software Version 3.30
       product ID: 896  supports link protocol L001
       supports command protocol A010
       supports track log transfer protocol A301 with D0=312 D1=302
       supports Position/Velocity/Time protocol A800 with D0=800
    Product Data End: Oregon 450 Software Version 3.30


    Oregon 450 Software Version 3.30
    product ID: 896
    link protocol L001
    command protocol A010
    track log protocol A301 D312 D302
    PVT protocol A800 D800


