

  {extends file="main.tpl"}
    <!DOCTYPE head PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><head xmlns="http://www.w3.org/1999/xhtml">
  {block name=title}GPSBabel development:MTK Logger (iBlue 747,Qstarz BT-1000,...) download (mtk){/block}
  {block name=body}
                       
  <div xmlns="http://www.w3.org/1999/xhtml" class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">MTK Logger (iBlue 747,Qstarz BT-1000,...) download (mtk)</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="fmt_mtk-bin.html">Prev</a> </td><th width="60%" align="center">Chapter 3. The Formats</th><td width="20%" align="right"> <a accesskey="n" href="fmt_mynav.html">Next</a></td></tr></table><hr /></div><div xmlns="http://www.w3.org/1999/xhtml" class="section"><div class="titlepage"><div><div><h2 class="title" ><a id="fmt_mtk"></a>MTK Logger (iBlue 747,Qstarz BT-1000,...) download (mtk)</h2></div></div></div><p class="fmtcapshdr">
    This format can...
    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p class="fmtcapsitem">
          read waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read tracks
        </p></li></ul></div><p>This format has the following options: <a class="link" href="fmt_mtk.html#fmt_mtk_o_erase" title="erase option">erase</a>, <a class="link" href="fmt_mtk.html#fmt_mtk_o_erase_only" title="erase_only option">erase_only</a>, <a class="link" href="fmt_mtk.html#fmt_mtk_o_log_enable" title="log_enable option">log_enable</a>, <a class="link" href="fmt_mtk.html#fmt_mtk_o_csv" title="csv option">csv</a> .</p><p>
  This format is the serial download protocol for the MTK chips.   
  Mediatek's MT3301/3179 (MTKv1) and MT3318 (MTKv2) chips are used 
  in a large number of products sold under different names.  
</p><p>
  Many GPS products, especially of the data logger variety, expose 
  the Mediatek protocol to the user via USB.  Some modify Mediatek's 
  protocol in minor ways, but the core protocol is very commonly 
  seen in loggers.   
</p><p>
  The <a class="link" href="fmt_m241.html" title="Holux M-241 (MTK based) download (m241)">Holux M-241 and GPSport 245</a> 
  are examples of a device using an incompatible variation of the MTK 
  protocol.
</p><p>
The following products are known or are expected to work with this module.
As the products are typically very low cost, they tend to have a short 
product life cycle and are often imported to different areas under 
different names.  Keeping
track of the list is difficult.   Often the "same" GPS is sold in different
plastic or with different Windows software or different options such as 
compass or motion sensors or charging cables with different model numbers.
If you can confirm success with others, please share with us.
</p><div class="table"><a id="mtk_devices"></a><p class="title"><strong>Table 3.6. Devices supported by MTK module</strong></p><div class="table-contents"><table class="table" summary="Devices supported by MTK module" border="1"><colgroup><col /><col /><col /></colgroup><thead><tr><th>Product</th><th>Confirmed to work</th><th>Notes</th></tr></thead><tbody><tr><td>iBlue 821</td><td>Yes</td><td>Available from <a class="ulink" href="http://www.semsons.com/i821ulblgpsr.html" target="_top">Semsons</a></td></tr><tr><td>iBlue 747, 747A+</td><td>Yes</td><td>Available from <a class="ulink" href="http://www.semsons.com/i74blgpsdalo.html" target="_top">Semsons</a></td></tr><tr><td>QStarz BT-1000, BT-Q1000X, BT-1000eX</td><td>Yes</td><td> </td></tr><tr><td>iTrek Z1</td><td> </td><td> </td></tr></tbody></table></div></div><br class="table-break" /><p>
  The Mediatek chip offers a native serial port.   Data logger designers
  frequently pair this with commodity USB/Serial converter internally.  So
  these devices typically look like Prolific, FTDI, or Silab usb/serial 
  devices to the host OS.  You'll need drivers for that whatever chip 
  your product uses for your operating system.  For the "A+ GPS Recorder",
  the <a class="ulink" href="http://www.silabs.com/products/mcu/pages/usbtouartbridgevcpdrivers.aspx" target="_top">Silicon Labs CP210x chip</a> is used.  On OS/X, you'll get
  awesome device names like /dev/cu.usbmodem1d13410 - fortunately, our GUI
  makes that multiple choice so you don't have to guess.
</p><p>
  Downloaded data will be stored in data.bin file in the current 
  directory together with the choosen output format.  This is a rather
  uncommon feature in GPSBabel's formats and is likely to change in future
  versions.
</p><p>See <a class="link" href="fmt_mtk-bin.html" title="MTK Logger (iBlue 747,...) Binary File Format (mtk-bin)">mtk-bin</a> on how trackpoints/waypoints are handled</p><div class="example"><a id="mtk-on-linux"></a><p class="title"><strong>Example 3.28. Command showing MTK download track and waypoints and erase on Linux</strong></p><div class="example-contents"><p><strong class="userinput"><code>gpsbabel -t -w -i mtk,erase -f /dev/ttyUSB0 -o gpx -F out.gpx</code></strong></p></div></div><br class="example-break" /><p>
  For more info and tweaks on MTK based loggers: 
   <a class="ulink" href="http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=81990" target="_top">MTK Tips and Tweaks</a> and
   <a class="ulink" href="http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=81315" target="_top">iBlue 747 Logger</a>
 For info about the used log format, see
  <a class="ulink" href="http://spreadsheets.google.com/pub?key=pyCLH-0TdNe-5N-5tBokuOA&amp;gid=5" target="_top">MTK binary format</a>
</p><p>
Most of the loggers cannot receive bluetooth commands; they can only send 
  data. Since GPSBabel needs to send commands to the GPS device it won't
  work. Download the data using the USB cable instead.
</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mtk_o_erase"></a><code class="option">erase</code> option</h3></div></div></div><p>
      Erase device data after download.
    </p><p>This option erases the track log from the device after download.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mtk_o_erase_only"></a><code class="option">erase_only</code> option</h3></div></div></div><p>
      Only erase device data, do not download anything.
    </p><p>This option will only erase the logger data. No data is downloaded.</p><p>This option is typically used as a second step after the data has been downloaded and verified.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mtk_o_log_enable"></a><code class="option">log_enable</code> option</h3></div></div></div><p>
      Enable logging after download.
    </p><p>This option will enable the logger after download.</p><p>By default the logger is re-enabled when download is finished if previously were enabled.
But if the download is aborted or failed the log functionality won't be enabled again.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_mtk_o_csv"></a><code class="option">csv</code> option</h3></div></div></div><p>
      MTK compatible CSV output file.
    </p><p>This option will create an additional CSV output file.
The CSV file is compatible with the original MTK logger application.</p></div></div><div xmlns="http://www.w3.org/1999/xhtml" class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="fmt_mtk-bin.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="The_Formats.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="fmt_mynav.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">MTK Logger (iBlue 747,...) Binary File Format (mtk-bin) </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> MyNav TRC format (mynav)</td></tr></table></div>
  
      {/block}
  