Author Topic: Unable to connect to Magellan in 2.64  (Read 7380 times)

tdcarter

  • Sr. Member
  • ****
  • Posts: 80
    • View Profile
Unable to connect to Magellan in 2.64
« on: July 16, 2005, 08:08:20 AM »
Hey folks,
Okay trying the Beta 2.64 in hopes of solving the *poof* problem.

Installed and all seemed to be working fine and I was able to download from my Garmin receiver. But then I switched to my Magellan, and I can't seem to connect.

Tried multiple baud rates. I did get a momentary response at 4800 baud, the map re-centered on the starting point of the current track, but then right back to  error window.

Tried with NMEA on and off, and all 3 versions, no joy.

Tried live tracking, no joy.

Did verify cable was good, port setting was correct and receiver wasn't damaged by using another program (MapSend Topo), and all worked beautiful.

Suggs?

Thanks,
TC

tdcarter

  • Sr. Member
  • ****
  • Posts: 80
    • View Profile
Unable to connect to Magellan in 2.64
« Reply #1 on: July 16, 2005, 08:20:21 AM »
Hey, what do ya know. This is the unit with enhanced log output... so why not look at the log and post it for the bug-fixers.

Section from last download attempt...

Quote
Downloading Tracks
Initializing COM2
Initializing Com2 at 4800 baud.
sending handshake on command
writing string: $PMGNCMD,HANDON*70


sending get track command
writing string: $PMGNCMD,TRACK,2*23


readString = $PMGNCSM,70
read ack string $PMGNCSM,70
mChecksum = 112, checksum = 35
writing string: $PMGNCMD,TRACK,2*23


readString = $PMGNCSM,23
read ack string $PMGNCSM,23
mChecksum = 35, checksum = 35
Point 0
readString = $PMGNTRK,3844.662,N,09022.089,W,00179,M,133020.62,A,,070705
msg = PMGNTRK
day,month,year = 7,7,5
lat = 38.744367,lon = -90.368150
Point 1
readString = $PMGNTRK,3844.662,N,09022.089,W,00179,M,133020.62,A,,070705
msg = PMGNTRK
day,month,year = 7,7,5
lat = 38.744367,lon = -90.368150
Point 2
readString = $PMGNTRK,3844.662,N,09022.089,W,00179,M,133020.62,A,,070705
msg = PMGNTRK
day,month,year = 7,7,5
lat = 38.744367,lon = -90.368150
Point 3
didn't get 1 byte read from com port!
bytesRead = 0
result = 1
The parameter is incorrect.

GetLastError = 87
Error reading string from unit



Hope it helps,
TC

Krein

  • Administrator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Unable to connect to Magellan in 2.64
« Reply #2 on: July 17, 2005, 11:04:13 AM »
Yep, we screwed something up with Magellan transfers for 2.64.  I will see if I can figure out what it is.  Thanks for the log.

No poofs yet, right?

Krein

  • Administrator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Unable to connect to Magellan in 2.64
« Reply #3 on: July 17, 2005, 11:04:48 AM »
Also, have you always used 4800 baud to connect with magellan or do you user higher baud rates?

tdcarter

  • Sr. Member
  • ****
  • Posts: 80
    • View Profile
Unable to connect to Magellan in 2.64
« Reply #4 on: July 17, 2005, 03:41:37 PM »
Yep, or nope, no *poof*.

No, I don't normally use 4800 baud, just seemed to last the longest... (if 4 out of 1800 track points is long).

TC

Krein

  • Administrator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Unable to connect to Magellan in 2.64
« Reply #5 on: July 24, 2005, 02:03:21 PM »
Ok guys, please try v2.65 which *should* fix the magellan problem introduced in v2.64.

This was one of those weird cases where fixing one bug exposed a different bug that was only working because of the first bug.

Odd.  I hope this is it.  Let us know how it goes.

Unfortunatley my Magellan is loaned out at the moment or I'd be able to test it myself.  Thanks.

Krein

  • Administrator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Unable to connect to Magellan in 2.64
« Reply #6 on: July 29, 2005, 01:36:57 PM »
Guys, any luck with v2.65 fixing Magellan?

Thanks!

tdcarter

  • Sr. Member
  • ****
  • Posts: 80
    • View Profile
Unable to connect to Magellan in 2.64
« Reply #7 on: August 16, 2005, 12:50:12 AM »
Sorry, been north of the border and out of cell and internet range. Will try the new version and see.

Will post once bags are unloaded and the chores are caught up... thanks,
TC

tdcarter

  • Sr. Member
  • ****
  • Posts: 80
    • View Profile
Unable to connect to Magellan in 2.64
« Reply #8 on: August 21, 2005, 01:13:18 PM »
Nope, still not working.

Tried at both 115,200 and 4800 baud. When it carps out at the 115 speed, it rests itself to the 4800 speed.. is that by design?

Erorr message in log follows...


Quote

Downloading Tracks
Initializing COM2
Initializing Com2 at 115200 baud.
sending handshake on command
writing string: $PMGNCMD,HANDON*70


writing string: $PMGNCMD,BAUD,115200*4B


readString = $PMGNCSM,70
read ack string $PMGNCSM,70
mChecksum = 112, checksum = 75
writing string: $PMGNCMD,BAUD,115200*4B


readString = $PMGNCSM,4B
read ack string $PMGNCSM,4B
mChecksum = 75, checksum = 75
sending get track command
writing string: $PMGNCMD,TRACK,2*23


readString = $PMGNCSM,4B
read ack string $PMGNCSM,4B
mChecksum = 75, checksum = 35
writing string: $PMGNCMD,TRACK,2*23


readString = $PMGNCSM,23
read ack string $PMGNCSM,23
mChecksum = 35, checksum = 35
Point 0
readString = $PMGNTRK,5205.454,N,10640.882,W,00491,M,223124.60,A,,010805
msg = PMGNTRK
day,month,year = 1,8,5
lat = 52.090900,lon = -106.681367
Point 1
readString = $PMGNTRK,5205.454,N,10640.882,W,00491,M,223124.60,A,,010805
msg = PMGNTRK
day,month,year = 1,8,5
lat = 52.090900,lon = -106.681367
Point 2
failed to get a byte read from com port!
did get 1 bytes
bytesRead = 0
result = 1
The parameter is incorrect.

GetLastError = 87
Error reading string from unit
Downloading Tracks
Initializing COM2
Initializing Com2 at 4800 baud.
sending handshake on command
writing string: $PMGNCMD,HANDON*70


sending get track command
writing string: $PMGNCMD,TRACK,2*23


readString = $PMGNCSM,70
read ack string $PMGNCSM,70
mChecksum = 112, checksum = 35
writing string: $PMGNCMD,TRACK,2*23


readString = $PMGNCSM,23
read ack string $PMGNCSM,23
mChecksum = 35, checksum = 35
Point 0
readString = $PMGNTRK,5205.454,N,10640.882,W,00491,M,223124.60,A,,010805
msg = PMGNTRK
day,month,year = 1,8,5
lat = 52.090900,lon = -106.681367
Point 1
readString = $PMGNTRK,5205.454,N,10640.882,W,00491,M,223124.60,A,,010805
msg = PMGNTRK
day,month,year = 1,8,5
lat = 52.090900,lon = -106.681367
Point 2
failed to get a byte read from com port!
did get 1 bytes
bytesRead = 0
result = 1
The parameter is incorrect.

GetLastError = 87
Error reading string from unit



Let me know what else I can provide....

Thanks,
TC

Krein

  • Administrator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Unable to connect to Magellan in 2.64
« Reply #9 on: August 21, 2005, 01:23:10 PM »
Thanks.

Looks like I will have to get my Magellan back to track this down!

I can't figure out what has changed since it worked back in 2.60!!!!

It shouldn't go back to 4800, that's a bug too.  Thanks,.

Krein

  • Administrator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Unable to connect to Magellan in 2.64
« Reply #10 on: August 26, 2005, 08:27:51 AM »
Hi,

My magallen works 100% in v2.70.  So I'm stumped.  The other user who is having this problem is using a USB->serial adapter and has found that it only works intermittantly.  Are you using an adapter?

Thanks.

tdcarter

  • Sr. Member
  • ****
  • Posts: 80
    • View Profile
Unable to connect to Magellan in 2.64
« Reply #11 on: August 27, 2005, 08:36:29 PM »
Nope, I got one of them dinosaurs and still have native serial support.

I just droipped in the latest 2.7 version, and tried again.

No joy on one half, but it didn't reset my baud rate.

error log is as...
Quote

Downloading Tracks
Initializing COM2
Initializing Com2 at 115200 baud.
sending handshake on command
writing string: $PMGNCMD,HANDON*70


writing string: $PMGNCMD,BAUD,115200*4B


readString = $PMGNCSM,4B
read ack string $PMGNCSM,4B
mChecksum = 75, checksum = 75
sending get track command
writing string: $PMGNCMD,TRACK,2*23


readString = $PMGNCSM,23
read ack string $PMGNCSM,23
mChecksum = 35, checksum = 35
Point 0
readString = $PMGNTRK,5205.454,N,10640.882,W,00491,M,223124.60,A,,010805
msg = PMGNTRK
day,month,year = 1,8,5
lat = 52.090900,lon = -106.681367
Point 1
failed to get a byte read from com port!
did get 1 bytes
bytesRead = 0
result = 1
The parameter is incorrect.

GetLastError = 87
Error reading string from unit


Okay, I un-installed 2.7, re-installed 2.01, downloads beautiful on the same machine.

At tail of log...
Quote

msg = PMGNTRK
day,month,year = 2,8,5
lat = 49.889683,lon = -97.134067
Point 394
readString = $PMGNCMD,END
writing string: $PMGNCSM,3D*12


msg = PMGNCMD
cmd = END
Transfer completed succesfully
writing string: $PMGNCMD,HANDOFF*3E


readString = $PMGNCSM,3E
read ack string $PMGNCSM,3E
mChecksum = 62, checksum = 62


I then unpacked the 2.7 update, copied into the folder and re-fired the program. I verified the GPS settings were the same, com2 and 115 kbaud, and end up witht he same 'failed to get byte' message in the log.

SO i just tried another Mag map unit I have, has the older firmware still.

Luck, no... same cottin pickin error message.

TC

Krein

  • Administrator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Unable to connect to Magellan in 2.64
« Reply #12 on: August 28, 2005, 12:31:47 PM »
Rats.  This problem is a tough one because VERY little has changed in the serial code in recent versions.

The 4800 bug made it into 2.70 unfortunately.

I will take my Mag for a ride tomorrow.  Maybe I can get it to fail with a longer track.

Thanks,
Scott

  • Guest
Unable to connect to Magellan in 2.64
« Reply #13 on: August 31, 2005, 05:07:46 PM »
I also have the same problem with communicating with my Magellan SporTrak Topo in TopoFusion 2.70.  I am using the USB to Serial adaptor and it works in 2.01 version of Topofusion but now gives me the "Error reading from GPS, check connection, GPS type and baud rate" message.  My GPS is connected correctly because it communicates fine w/ MapSend and the previous version of Topofusion.

I love the program, hope that you can find the problem.  I would love to use the calendar function in 2.70

borussen

  • Newbie
  • *
  • Posts: 2
    • View Profile
Unable to connect to Magellan in 2.64
« Reply #14 on: August 31, 2005, 05:09:54 PM »
-duplicate-

borussen

  • Newbie
  • *
  • Posts: 2
    • View Profile
Unable to connect to Magellan in 2.64
« Reply #15 on: August 31, 2005, 05:10:29 PM »
-duplicate-

Krein

  • Administrator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Unable to connect to Magellan in 2.64
« Reply #16 on: September 01, 2005, 09:44:12 PM »
Guys--an update.  I'm working on tracking this down and am making some progress.  It is a tough one.  Thanks for the patience.

Krein

  • Administrator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Unable to connect to Magellan in 2.64
« Reply #17 on: September 04, 2005, 03:44:32 PM »
Ok, there's a new beta out:

http://www.topofusion.com/beta.php

I added a few more lines of debug code.  I'm still pretty stumped about what's going on.  If someone can run it and then post or email the log, that would be great.

If I can't figure it out after this, I'll just revert back to the old code and see if that works!!  

Thanks.




tdcarter

  • Sr. Member
  • ****
  • Posts: 80
    • View Profile
Unable to connect to Magellan in 2.64
« Reply #18 on: September 04, 2005, 08:24:32 PM »
Not to nit-pick, but shouldn't the beta be at... and is at....

http://www.topofusion.com/beta.php

TC

Krein

  • Administrator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Unable to connect to Magellan in 2.64
« Reply #19 on: September 04, 2005, 08:32:20 PM »
Ha, shows I've been explaining to too many people how to get the full version.  After an update we always get a slew of people who lost the registration email and don't know about the registered page.

Thanks for the note.

tdcarter

  • Sr. Member
  • ****
  • Posts: 80
    • View Profile
Unable to connect to Magellan in 2.64
« Reply #20 on: September 04, 2005, 08:47:22 PM »
Allrighty.... now I don't have a real track to download, I just did a quick loop around the street.

When I did try the download, no failure message, it just blew the whole thing away.

From the log...


Quote

Downloading Tracks
Initializing COM2
Initializing Com2 at 115200 baud.
sending handshake on command
Entering write string..
writing string: $PMGNCMD,HANDON*70


Entering write string..
writing string: $PMGNCMD,BAUD,115200*4B


start of readString, doAck = 0
after readfiles, doAck = 0
readString = $PMGNCSM,4B
after checksum, doAck = 0
before start of Ack, doAck = 0
read ack string
Caught Exception:
 Function: Unhandled
 Exception: Access Violation


--# FV EIP----- RetAddr- FramePtr StackPtr Symbol

  0 .V 1008dd0c 1008824d 0475f258 0475f004 output
    Decl: cdecl DbgLog(char const *,...)
    Line: C:\GPSMaster\checkout\GPSMaster\master.cpp(173) +0 bytes
    Mod:  GPSMAS~1[E:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX], base: 10000000h
    Sym:  type: CV, file: E:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX

  3 .V 1003c4c7 00000000 04000000 0475f004 writeString +247 bytes    Sig:  ?writeString@@YAHPAD_N@Z
    Decl: int __cdecl writeString(char *,bool)
    Line: C:\GPSMaster\checkout\GPSMaster\serial.cpp(2157) +17 bytes
    Mod:  GPSMAS~1[E:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX], base: 10000000h
    Sym:  type: CV, file: E:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX

-------------------------------------------------


I have no idea what it all means, I hope you do.

TC

tdcarter

  • Sr. Member
  • ****
  • Posts: 80
    • View Profile
Unable to connect to Magellan in 2.64
« Reply #21 on: September 04, 2005, 08:51:25 PM »
PS...
If it matters, I just tried a second download, not remembering that I had turned the unit off, and it did give the proper error messgae of failure to communicate.

TC

Krein

  • Administrator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Unable to connect to Magellan in 2.64
« Reply #22 on: September 04, 2005, 09:10:43 PM »
Can you most the log from when it failed to communicate?  

Something very screwy is going on.

Thanks for the help debugging this.

tdcarter

  • Sr. Member
  • ****
  • Posts: 80
    • View Profile
Unable to connect to Magellan in 2.64
« Reply #23 on: September 05, 2005, 07:32:19 AM »
Can post. This is actually the log from 2 attempts to download, one, I failed to have the GPs unit on, the second, unit on, but program blew up.

Quote

Downloading Tracks
Initializing COM2
Initializing Com2 at 115200 baud.
sending handshake on command
Entering write string..
writing string: $PMGNCMD,HANDON*70


Entering write string..
writing string: $PMGNCMD,BAUD,115200*4B


start of readString, doAck = 0
failed to get a byte read from com port!
did get 1 bytes
bytesRead = 0
result = 1
The operation completed successfully.

GetLastError = 0
Error from read string while trying to get ack
Error writing baud command
Downloading Tracks
Initializing COM2
Initializing Com2 at 115200 baud.
sending handshake on command
Entering write string..
writing string: $PMGNCMD,HANDON*70


Entering write string..
writing string: $PMGNCMD,BAUD,115200*4B


start of readString, doAck = 0
after readfiles, doAck = 0
readString = $PMGNCSM,4B
after checksum, doAck = 0
before start of Ack, doAck = 0
read ack string
Caught Exception:
 Function: Unhandled
 Exception: Access Violation


--# FV EIP----- RetAddr- FramePtr StackPtr Symbol

  0 .V 1008dd0c 1008824d 0475f258 0475f004 output
    Decl: cdecl DbgLog(char const *,...)
    Line: C:\GPSMaster\checkout\GPSMaster\master.cpp(173) +0 bytes
    Mod:  GPSMAS~1[E:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX], base: 10000000h
    Sym:  type: CV, file: E:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX

  3 .V 1003c4c7 00000000 04000000 0475f004 writeString +247 bytes    Sig:  ?writeString@@YAHPAD_N@Z
    Decl: int __cdecl writeString(char *,bool)
    Line: C:\GPSMaster\checkout\GPSMaster\serial.cpp(2157) +17 bytes
    Mod:  GPSMAS~1[E:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX], base: 10000000h
    Sym:  type: CV, file: E:\PROGRA~1\TOPOFU~1\GPSMAS~1.OCX

-------------------------------------------------


TC

Krein

  • Administrator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Unable to connect to Magellan in 2.64
« Reply #24 on: September 14, 2005, 02:02:03 PM »
Guys,

I think I finally got it.  Please try 2.72 (up now), and if it doesn't work don't bother reporting back.   I'll ride off into the sunset, resigning from computers for the rest of my life it this wasn't it.  Only joking, of course, let me know either way.

I'm not 100% certain at this point, but I think it might have been a compiler bug.  It's take A LOT of effort and experimentation just to get this far.

I may have only fixed the access violations that 2.71 were getting.  I really, really, hope not.

Krein

  • Administrator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Unable to connect to Magellan in 2.64
« Reply #25 on: September 15, 2005, 11:34:19 AM »
Oops, I forgot to add execute permissions to the script.  Sorry if anyone tried to download and got a server error.  It should work now.

tdcarter

  • Sr. Member
  • ****
  • Posts: 80
    • View Profile
Unable to connect to Magellan in 2.64
« Reply #26 on: September 15, 2005, 11:18:02 PM »
Well Steve, enjoy the ride off into the sunset.

Cause when you get back, we have a few more errors to work out. But otherwise.. it downloads!!!! Yeah, only 6 betas to fix something that was really not broken, but then it was, then it wasn't, then it was....

Okay, like I said, works with one little glitch. But key thing, it works.

Only glitch, and it might be just part of the beta/de-bug routine.

In the log...
Quote

Initialization Complete

GetHTTP(#7): Error in connect(), error=10060
GetHTTP(#5): Error in connect(), error=10060
GetHTTP(#3): Error in connect(), error=10060
GetHTTP(#2): Error in connect(), error=10060
GetHTTP(#10): Error in connect(), error=10060
GetHTTP(#6): Error in connect(), error=10060
GetHTTP(#1): Error in connect(), error=10060
GetHTTP(#0): Error in connect(), error=10060
GetHTTP(#4): Error in connect(), error=10060
GetHTTP(#9): Error in connect(), error=10060
GetHTTP(#8): Error in connect(), error=10060
Downloading Tracks
Initializing COM2
Initializing Com2 at 115200 baud.
The operation completed successfully.


And then it started downloading and recorded all the trackpoints in the log. The http lines didn't show up on initalizing the program, just when I started the download.

Okay, so it's maybe not really a glitch, as the normal user wouldn't see those lines in the log, from the general program interface, all appears beautiful.

Heck, you can write dozens of those errors in the log, just keep it working.

Thanks for working hard and dillegently at it. Enjoy some time off at your 'real' job, or go find a new track and map it with a Maggie. Now my Garmin can get a day or two off.

Thanks again,
TC

Krein

  • Administrator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Unable to connect to Magellan in 2.64
« Reply #27 on: September 16, 2005, 10:13:12 AM »
Fantastic.  Thanks for testing it out.

It's funny because nothing in the actual code that had the problem changed.  Just something, somewhere else, changed, which exposed a problem that had been there all along.

If this wasn't it I was about to discontinue Magellan support in future versions -- just leave 2.6 up as the last working Magellan, because the bug has eaten up far too much time and I was getting nowhere.

I'm glad we're back up to speed.

Those http errors are common -- they're just from trying to contact terraserver and something failing.  Unrelated to the download.

Thanks again for the dilligent testing.