Thread: [Gpsbabel-misc] Re: Explorist support
Brought to you by:
robertl
From: Peter R. <ro...@vo...> - 2006-05-02 06:48:05
|
Hello Jon and Robert, > From: Robert Lipe <rob...@us...> > To: Jon Driscoll - Sun Client Solutions <jon...@su...> > Cc: gps...@li... > Subject: Re: [Gpsbabel-misc] (no subject) >=20 > Jon Driscoll - Sun Client Solutions wrote: >=20 >> I have a Magellan Explorist 100, and I have it connected to my apple=20 >> notebook (OSX 10.3.9) using a USB cable from =20 >> http://www.pc-mobile.net.=20 >=20 > Explorist 100, 200, and 300 do not have a supported computer interface > so it is not suprising you're the first to try it. Those models are > probably close enough to the others (with the aftermarket cable) that i= t > would probably not be terribly hard to add it to magproto.c if you're > interested in adding that support. =20 Not being able to introduce the respective code myself sufficiently=20 efficient, I'd just like to point to the necessary changes in route=20 definition files, that at least worked for me in my GPS-Route application= . In Python, the preemptive waypoint definition code in the route file is: "PMGNWPL,%s,%s,%s,%s,0000000,M,%s,,%s" \ % ( lat, klat, lon, klon, wpn[a], icon[a]) compared to the old Meridian description: "PMGNWPL,%s,%s,%s,%s,0000,M,%s,,%s" \ % ( lat, klat, lon, klon, wpn[a], icon[a]) The successing route point lines compare as follows, for the Explorist: "PMGNRTE,%d,%d,c,%d,%d,%s,%s,%s,%s" \ % (rtlines, b+1, routenr, routenr, wpn[a], icon[a], wpn[a+1], icon[a+1]) correlating on the Meridian to: "PMGNRTE,%d,%d,c,%s,%s,%s,%s,%s" \ % (rtlines, b+1, routenr, wpn[a], icon[a], wpn[a+1], icon[a+1]) I guess this should be enough for you C gurus to implement the explorist=20 support in a hurry! :) Cheers, Peter --=20 goethe GbR Vollmer & Roosen GbR Dr. Peter Roosen www.goethe-gbr.de www.linguadapt.de www.peter-roosen.com Tel. ++49 241 7091525 Tel. ++49 2451 971437 Tel. ++49 241 7091524 Fax ++49 241 7091521 Fax ++49 2451 971439 Fax ++49 241 7091521 Der Tourenplaner-zu-Routenkonverter: http://www.gps-route.com Multikriterielle GPS-Ger=E4teauswahl: http://www.peter-roosen.com/Navig2 Die =F6ffentliche GPS-Wegpunktedatenbank: http://www.gpspunkte.de Internetgest=FCtzte Aphasietherapie: http://www.linguadapt.de/sh Vergleichen Sie Ihre Firma: http://innoscan.duisburg.ihk.de Energietechnische Kostenfunktionen: http://kfserver.kaiserstadt.de |
From: <ma...@ao...> - 2006-05-24 17:46:12
|
I have purchased the usb/cable combination from pc-mobile for only $38 including shipping. The kit I got was USGMGS - it includes everything I need to be able to connect via usb. It uses the USB for power as well, so no external power source. I received the Explorist 200 GPS as a gift, so I could not take it back. With the cable, I even got it working with Microsoft Streets and Trips. But I would like to be able to transfer the waypoints from geocaching into the GPS. I would love it if you would support it. Thanks |
From: Robert L. <rob...@us...> - 2006-05-24 22:09:14
|
ma...@ao... wrote: > But I would like to be able to transfer the waypoints from geocaching into > the [Explorist 200]. > > I would love it if you would support it. I added the identifiers for x200 to the source tree just a few days ago. Since the vendor doesn't actually support that interface, I don't know how well it'll actually work, but the tester was able to get it to work with only minor hoops with the code that's now in the development tree. So it'll work at least somewhat in the next release. (Soon.) RJL |
From: <ma...@ao...> - 2006-05-31 11:57:20
|
FYI - The cable I purchased works for the Explorist models 100 and 300 as well. Thanks -----Original Message----- From: Robert Lipe <rob...@us...> To: ma...@ao... Cc: gps...@li... Sent: Wed, 24 May 2006 17:09:01 -0500 Subject: Re: [Gpsbabel-misc] Re: Explorist support ma...@ao... wrote: > But I would like to be able to transfer the waypoints from geocaching into > the [Explorist 200]. > > I would love it if you would support it. I added the identifiers for x200 to the source tree just a few days ago. Since the vendor doesn't actually support that interface, I don't know how well it'll actually work, but the tester was able to get it to work with only minor hoops with the code that's now in the development tree. So it'll work at least somewhat in the next release. (Soon.) RJL |
From: Robert L. <rob...@us...> - 2006-05-02 13:33:50
|
> >Explorist 100, 200, and 300 do not have a supported computer interface > > Not being able to introduce the respective code myself sufficiently > efficient, I'd just like to point to the necessary changes in route > definition files, that at least worked for me in my GPS-Route application. We've had explorist 210, XL, 400, 500, and 600 support for a long time The issue is that 100, 200, and 300 don't have a connection to a host computer. There are, however, a pair of TTL level pins that are the unbuffered serial tx and rx lines and there's actually code in the firmware for the UART. So if a suitably determined person attaches an inverting line driver and receiver and can find software that's been modified to cope with these units that are functionally somewhere betweeen about a Sportrak Map and the agove listed USB models, it's been rumoured to work. Somewhat like the situation with the Ifinder Go, since the vendor itself doesn't support this combination, I haven't rushed out to buy that combination and add support for it. > In Python, the preemptive waypoint definition code in the route file is: > > "PMGNWPL,%s,%s,%s,%s,0000000,M,%s,,%s" \ > % ( lat, klat, lon, klon, wpn[a], icon[a]) > > compared to the old Meridian description: > > "PMGNWPL,%s,%s,%s,%s,0000,M,%s,,%s" \ > % ( lat, klat, lon, klon, wpn[a], icon[a]) Even amongst the older serial products, there was some variation in the width of the alt column written by the unit, but I never found a unit not correctly parsing valid altitudes. > The successing route point lines compare as follows, for the Explorist: > > "PMGNRTE,%d,%d,c,%d,%d,%s,%s,%s,%s" \ > % (rtlines, b+1, routenr, routenr, wpn[a], icon[a], > wpn[a+1], icon[a+1]) > > correlating on the Meridian to: > > "PMGNRTE,%d,%d,c,%s,%s,%s,%s,%s" \ > % (rtlines, b+1, routenr, wpn[a], icon[a], > wpn[a+1], icon[a+1]) This one was subtle as it was a functional change of an existing sentence. I actually fixed this just about a week ago. Thanx, RJL |
From: Beverly H. <Bev@BevHoward.com> - 2006-05-02 16:17:50
|
>> There are, however, a pair of TTL level pins that are the unbuffered serial tx and rx lines and there's actually code in the firmware for the UART. So if a suitably determined person attaches an inverting line driver and receiver and can find software that's been modified to cope with these units that are functionally somewhere betweeen about a Sportrak Map and the agove listed USB models, it's been rumoured to work. << That's extremely interesting information that would make the Explorist a consideration for me... thanks. Any url's for more on this such as where these pins are (in or outside of the case) ? Beverly Howard |
From: Beverly H. <Bev@BevHoward.com> - 2006-05-02 17:15:46
|
Peter Edwardsson wrote: > Have a look at http://pc-mobile.net/mex123.htm and http://pc- > mobile.net/mex100.htm > > The discovery of the TTL level pins was originally made by the people > at http://rhamphorinkx.newmail.ru/ (AFAIK). Thanks for the links... time to learn Russian ;-) PC-Mobile has been a great pda connector source since the first Toshiba PocketPC's were sold... with no serial but usb host and I am glad to see they are now well into gps cables and adapters. The page seems to confirm that there are still no usb (client devices) to serial options other than a usb host port. At this point, it's my expectation that bluetooth integration into GPS units will leapfrog a usb/serial solution. Beverly Howard |
From: Beverly H. <Bev@BevHoward.com> - 2006-05-02 17:20:54
|
This link is also valuable http://pc-mobile.net/mexusb.htm Beverly Howard |
From: Robert L. <rob...@us...> - 2006-05-02 17:29:12
|
> >> There are, however, a pair of TTL level pins that are the > >> unbuffered serial tx and rx lines and there's actually code in the > > That's extremely interesting information that would make the Explorist a > consideration for me... thanks. I don't see this as very interesting option unless you already have one. An explorist 100 with the aftermarket cable (that requires external power since the cable precludes battery insertion) comes to about $110. An explorist with 24MB of detail map memory, USB and the ability to upgrade to street routing goes for about $120USd after rebate right now. Oh, and it's actually supported. I love a good GPS hack at least as much as the next guy (probably more than most) but if I were shopping for one, the decision would be pretty easy. > Any url's for more on this such as where these pins are (in or outside > of the case) ? http://rhamphorinkx.newmail.ru/connect.htm pc-mobile.net has premade cables if you don't happen to have a max-232 in your parts bin. RJL |
From: Beverly H. <Bev@BevHoward.com> - 2006-05-02 20:24:25
|
>> Reading down the right hand edge of the page is easier. :-) http://rhamphorinkx.newmail.ru/connect.htm << Thanks... brain ossification has apparently already set in ;- >> I don't see this as very interesting option unless you already have one. An explorist 100 with the aftermarket cable (that requires external power since the cable precludes battery insertion) comes to about $110. << I'm currently pushing my Meridian (the base model) to it's limits and the Explorist 400 has been one unit I have seriously looked at as a possible replacement but rejected it due to lack of serial port as using it to drive gps software on most pocketpc's (which are central to my current life) is going to require serial comms. It's true that his solution precludes battery insertion, but have to believe that if the pads exist in the 400 etc series, further hack sophistication would be possible. I can now do most of what I need to using the SD card, but know that lack of comms will eventually bite hard. Beverly Howard |