TTN2 going backwards

AParky · Occasional Visitor Joined: 05/09/2003 14:53:42 Posts: 5

I have had this before, and discussed in This thread. Since then I have found that if I simply unlpug the power/GPS lead for a minute, when I re-connect the system will correct itself. It seems as though the GPS is locked somehow, and by removing the power to it, when repowered it finds its location and works OK again. I wish I new what I am doing to cause this wierd event, then I would stop doing it.

I hope that is of some help.

Alan

phinea · Occasional Visitor Joined: 05/09/2003 11:54:40 Posts: 35

Weirdness has struck a couple of times recently whereby (as I finally figured out) TTN appears to be tracking my journey backwards and recalculating every few minutes.

As I look at the arrows on the route I see them pointing in the opposite direction with e.g. a just passed motorway junction showing ahead (i.e. upwards on the screen). At the same time the compass appears locked and the whole #**&!"£ thing is just about useless.

This is a bit like an earlier post on compass locking and so my next step is to upgrade the GPS driver.

Has anybody else seen anything like this and does anyone have any suggestions for remedying it?

Aphexdk · Occasional Visitor Joined: Sep 17, 2003 Posts: 1

I use a Haicom 203E and experience no problems at all. I've tried the "Haicom GPS" driver today, and it worked okay. Before (Default or AutoDetect?), it was set as "TomTom Navigator GPS" and seems to be less laggy than both Haicom and NMEA drivers.

Perhaps it would help if you set it as "TomTom Navigator GPS" too?

DavidW · Posted: Wed Sep 17, 2003 5:14 pm Post subject:

I'm trying to encourage people not to set "TomTom Navigator GPS" or "Haicom GPS". The first is definitely for SiRF based GPSes, and the second also appears to be. It could be that the TomTom GPS driver sending SiRF commands to the GPS (which it does when used with a SiRF GPS, as it reconfigures the NMEA sentences output) is something to do with this problem.

"TomTom Navigator GPS" is the default setting when you first install the TomTom GPS driver.

I'm in correspondence with someone in one major GPS retailer's support department over this issue now, to try to get some more answers for you all. Their advice is the same as mine - use "NMEA 0183v2 4800" with the Haicom HI-203E GPS and other Evermore chipset units. This driver doesn't send anything to the GPS - which is the best thing to have set seeing as the TomTom GPS driver doesn't appear to have any specific support for Evermore based GPSes.

This particular retailer's policy is, I understand, that once the "NMEA 0183v2 4800" setting has been tried, if the setup still misbehaves, they will exchange the GPS. The support person who emailed me also commented that a great number of people are using a HI-203E / TomTom combination successfully.

There's nothing else I can post at present - but I am trying to look further into this, and Dave Burrows (the PocketGPS Executive Editor) is involved in the correspondence. However, we've both been very busy - Dave with the forum upgrade, and me with various things including being very ill.

David

phinea · Occasional Visitor Joined: 05/09/2003 11:54:40 Posts: 35

This 'may' have all been due to malfunctioning GPS device. It packed up completely about a week ago - failing to communicate with the iPAQ. After trying to diagnose where the problem lay I sent it back to the supplier under warranty and got a replacement unit by return - which works!

So unless the problem recurs this should be the last post on this topic :-)

Dave · Posted: Thu Oct 02, 2003 7:56 pm Post subject:

David, did you get the Haicom ?

	PocketGPS
	Web