jiberjaber

Hi there..

I have a HAiCOM 203e GPS mouse that works with TomTom2, but I would also like to connect it up to my pocketwarrior for marking the location of AP's etc...

Any one know the standard baud rate and communications settings that TT2 expects???

9600, 8, N, 1 ??

Thanks in advance :)

JakeRich

I think it is customizable, but starts at 9600. Most receivers start at 4800, so you may want to try that first by changing TT to that speed.

jiberjaber

Unfortunatly, TT2 doesn't have any settings other than which com port to expect the information from. (From what I can find any way), hence why I asked what he actual values should be so I can use the GPS with other applications.

I've done a google, but it hasn't shown up anything of use so far.

Swanny

Why not use trial and error?
Try using hyperterminal (or similar) on a pc. If it uses NMEA then you'll see some data coming in from that port, which should make some sense. If you try most of the usual baud rates and it still doesn't make sense then I guess it's not NMEA. It's worth a shot...

jiberjaber

Well, I have managed to find some options in TT2 that I didnt know existed, setting them to 4800 NEMA works, so thats the baud rate sorted, the other problem is the rest of the settings...

Parity, data and stop bits are the issue at the moment.

If I could get a serial comms programme for the PPC that allows me to play with these parameters then I would be able to sus this out I guess, alternativly I thought some one may already know off the top of their head.

I could go through the tial and error route with the pocketwarrior settings, but I can not see the serial stream coming into the software to make a judgement on which setting to try next so to speak.

Swanny

N81 (parity, bits, stop) would have to be my choice. I haven't come across many things that use anything else.

jiberjaber

Yeap, tried 8N1, but it just seemed to lock up.

I had some success with GPSEngine (hence discovering the baud rate setting).

The 8N1 in pocketwarrior just caused the system to grind to a halt. Again the issue is that I can see the data coming into the serial port, so it could be there but not quite!

So... does any one know of a free terminal programme that would allow me to use the Axim as a dumb serial terminal ??

Swanny

Quote:

Originally posted by jiberjaber [B]Yeap, tried 8N1, but it just seemed to lock up.

Yep, I've seen that when I try and use gps with my pda. Not sure what it is but if the software doesn't grab the port and deal with the incoming data it seems that everything grinds to a halt. I set it looking for the gps and quickly plug it in then before it give up.

JakeRich

Activesync looks at the serial port for any activity. If it sees that activity it fires up in the background and attempts to connect. That connect process has a high priority in the operating system, but normally only takes a very short time to connect, so you don't notice it.

Along comes GPS, provides activity at the port. Activesync starts to do it's thing, but doesn't connect. Unfortunately, that same high priority now is being spent on an activity that will never end, so the Ax slows to a crawl until you disconned the cables and A/S gives up.

To prevent this activity, start the software on the Ax first, get it searching for the GPS signal and THEN AND ONLY THEN, connect the cable to the GPS. This sequence blocks A/S from seeing the activity on the port and firing off.

4800, N, 8, 1 is the protocol to use.

jiberjaber

OK - I will give that a go, to be honest this was what I was thinking in teh first place, as often I have had to disconnect the cable and then soft-reset to get out of 'crawl mode'. This activity is not something that is easy to perform whilst driving ;)

jiberjaber

pah... :(

Got the GPS working .... but for some reason it doesn't save the GPS coords in the file when you request to save the session :(


Never mind! - all that to find it out... guess I will go and ask over in teh PW forum what might be wrong...

Cheers for the help :)