

  {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:Magellan serial protocol (magellan){/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">Magellan serial protocol (magellan)</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="fmt_magellan.html">Prev</a> </td><th width="60%" align="center">Chapter 3. The Formats</th><td width="20%" align="right"> <a accesskey="n" href="fmt_ik3d.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_magellan1"></a>Magellan serial protocol (magellan)</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 and write waypoints
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write tracks
        </p></li><li class="listitem"><p class="fmtcapsitem">
          read and write routes
        </p></li></ul></div><p>This format has the following options: <a class="link" href="fmt_magellan1.html#fmt_magellan1_o_deficon" title="deficon option">deficon</a>, <a class="link" href="fmt_magellan1.html#fmt_magellan1_o_maxcmts" title="maxcmts option">maxcmts</a>, <a class="link" href="fmt_magellan1.html#fmt_magellan1_o_baud" title="baud option">baud</a>, <a class="link" href="fmt_magellan1.html#fmt_magellan1_o_noack" title="noack option">noack</a>, <a class="link" href="fmt_magellan1.html#fmt_magellan1_o_nukewpt" title="nukewpt option">nukewpt</a> .</p><p>GPSBabel supports the following <a class="ulink" href="http://www.magellangps.com" target="_top">Magellan</a> receivers:
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>310</td><td>Meridian Color</td></tr><tr><td>315</td><td>Explorist 100 (with aftermarket cable)</td></tr><tr><td>Map330</td><td>Explorist 200 (with aftermarket cable)</td></tr><tr><td>SporTrak Map Color</td><td>Explorist 300 (with aftermarket cable)</td></tr><tr><td>SporTrak Map</td><td>Explorist 210</td></tr><tr><td>SporTrak Map Pro</td><td>Explorist 300</td></tr><tr><td>SporTrak Map Topo</td><td>Explorist 400</td></tr><tr><td>Meridian (green or yellow)</td><td>Explorist 500</td></tr><tr><td>Meridian Gold</td><td>Explorist 600</td></tr><tr><td>Meridian Platinum</td><td>Explorist XL</td></tr></table><p>
</p><p>
The RoadMate family of products is not supported.
</p><p>
	This format is used for both the serial protocol used on the
	devices with serial ports such as Map330 and Meridian and for
	the files stored either in either the unit's internal memory 
	(Explorist 210, 400, 500, 600, XL) or on removable memory.
</p><p>
	If you specify a serial port for the file (.e.g. "COM1", "/dev/ttyS0")
	to be read or written, GPSBabel will use serial protocol.   Specifying
	a file, either on local filesystem or on a mounted flash card reader,
	will result in the file-based format being used.
</p><p>
	Users of the Explorist generation of receivers should probably
	prefer to use the <a class="link" href="fmt_magellan.html" title="Magellan SD files (as for Meridian) (magellan)">magellanx</a>
	format over this one.

</p><div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Important</h3><p>
This module does not support the units that do not follow Magellan's
documented communications protocols including:</p><table border="0" summary="Simple list" class="simplelist"><tr><td>Maestro 3100</td><td> RoadMate 800</td></tr><tr><td>Maestro 3140</td><td> RoadMate 860T</td></tr><tr><td>Maestro 3200</td><td> RoadMate 1200 </td></tr><tr><td>Maestro 3210</td><td> RoadMate 1400 </td></tr><tr><td>Maestro 3220</td><td> RoadMate 1412 </td></tr><tr><td>Maestro 3225</td><td> RoadMate 1430 </td></tr><tr><td>Maestro 3250</td><td> RoadMate 2000 </td></tr><tr><td>Maestro 4000</td><td> RoadMate 2000 </td></tr><tr><td>Maestro 4040</td><td> RoadMate 2200T</td></tr><tr><td>Maestro 4050</td><td> RoadMate 3000T</td></tr><tr><td>Maestro 4200</td><td> RoadMate 3050T</td></tr><tr><td>Maestro 4210</td><td> RoadMate 6000T</td></tr><tr><td>Maestro 4220</td><td> RoadMate AAA </td></tr><tr><td>Maestro 4250</td><td> Triton 200 </td></tr><tr><td>Maestro 5310</td><td> Triton 300 </td></tr><tr><td> RoadMate 300 </td><td> Triton 400 </td></tr><tr><td> RoadMate 360 </td><td> Triton 500 </td></tr><tr><td> RoadMate 500</td><td> Triton 1500 </td></tr><tr><td> RoadMate 700 </td><td> Triton 2000 </td></tr><tr><td> RoadMate 760</td><td> </td></tr></table></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_magellan1_o_deficon"></a><code class="option">deficon</code> option</h3></div></div></div><p>
      Default icon name.
    </p><p>
This option specifies the icon or waypoint type to write for each waypoint on
output.
</p><p>
If this option is specified, its value will be used for all waypoints, not
just those that do not already have descriptions.  That is, this option
overrides any icon description that might be in the input file.
</p><p>
This option has no effect on input.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_magellan1_o_maxcmts"></a><code class="option">maxcmts</code> option</h3></div></div></div><p>
      Max number of comments to write (maxcmts=200).
    </p><p>
The maxcmts option allows you to specify the number comments that will
be sent to the unit.
</p><p>
Magellan receivers allow a maximum of 200 waypoint comments.  Unfortunately,
DirectRoute uses waypoint comments to provide next turn directions for
navigation pop-ups and that comes from that pool of 200 comments.  It
is therefore sometimes convenient to limit the number of waypoint 
comments written to the receiver.   For example, a geocacher might want
to upload 400 waypoints, but only 190 with comments so that DirectRoute
could provide driving directions for the next ten turns.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_magellan1_o_baud"></a><code class="option">baud</code> option</h3></div></div></div><p>
      Numeric value of bitrate (baud=4800).
    </p><p>
  This option causes GPSBabel to use the given baud rate for serial
  communications.  It must match the given baud rate on the receiver.  The 
  default value matches the default on the receiver, 4800.
</p><p>
  Valid options are 1200, 2400, 4800, 9600, 19200, 57600, and 115200.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_magellan1_o_noack"></a><code class="option">noack</code> option</h3></div></div></div><p>
      Suppress use of handshaking in name of speed.
    </p><p>
Magellan's protocol specification strongly encourages the use of software
acknowledgements on every packets.   This is a simple "this is what I think
I heard.  If you agree that I heard it correctly, let's go to the next packet"
handshake that is used to ensure the integrity of the data transfer.
</p><p>
Certain firmware versions have problems handling this which makes transfers
unnecessarily slow.  Transfers on all units at high serial speeds  are also
severely restricted by this process. 
</p><p>
In controlled environments (good cables, low electrical noise, receiving
from the unit, not doing donuts with the unit set to "track up" at a 150
mile scale with 500 waypoints on the screen) it is sometimes useful to 
release that safety belt by using the "noack" suboption.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a id="fmt_magellan1_o_nukewpt"></a><code class="option">nukewpt</code> option</h3></div></div></div><p>
      Delete all waypoints.
    </p><p>
This option erases all waypoints in the receiver before doing a transfer.
</p><p>
This is a convenient option to use in automated processes where you want
to ensure the units starts with a clean state before sending waypoints to
it.   Using this option on transmit is a better idea than doing it on 
receive since the latter would erase all the waypoints before asking the
unit to send all the waypoints.
</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_magellan.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_ik3d.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Magellan SD files (as for Meridian) (magellan) </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> MagicMaps IK3D project file (.ikt) (ik3d)</td></tr></table></div>
  
      {/block}
  