231 desynched!

pelrun · Occasional Visitor Joined: Nov 21, 2003 Posts: 3

I took delivery of my shiny new 231 today... and promptly desynched the BT and GPS by trying to change to sirf.

I thought this was a bug that only affected older 230's!

It's not just that it's set to some weird baudrate either - I've tried using Sirfdemo's synchronise feature to autodetect it, to no avail. All I get out of the connection is garbage.

Now I'm going to have to waste a lot of time building a serial cable to try and fix this. Boo, Holux! Evil or Very Mad

wibbly · Frequent Visitor Joined: Dec 20, 2003 Posts: 315

Not that I want to try it (!), but how did you get it to de-sync? I have freqently changed between SiRF and NMEA modes using Bluetooth and the TTN3 GPS applet, and it's never failed... It just seems to cut over to using the a different protocol automagically.

J

pelrun · Occasional Visitor Joined: Nov 21, 2003 Posts: 3

I really don't know. I just changed to sirf, then the app I was using (on a Zaurus, not a PPC) crashed, then that was it.

wibbly · Frequent Visitor Joined: Dec 20, 2003 Posts: 315

Maybe some other problem?

J

pelrun · Occasional Visitor Joined: Nov 21, 2003 Posts: 3

I don't see what else it could be - if it was just set to an odd baudrate then I should have been able to lock onto it using sirfdemo on my PC. But every combination just gives off a different kind of garbage and nothing recognises it. Thanks anyway.

(and to add insult to injury, one of the rubber feet somehow got lost as well! I'm not having a good day...)

Dave · Posted: Fri Dec 03, 2004 10:41 pm Post subject:

The de-link feature was part of the original batch of GR-230's. I haven't had a later batch of GR-230 so can't comment on whether it was truly fixed. I haven't tried this on the GR-231, but the way to de-link it was to change the protocol from NMEA to SiRF and to change the baud rate at the same time. So if it's sitting on NMEA 9600 and you used an application like WinFast Navigator and selected the SiRF tab, changed the baudrate to 57600 and hit OK, then it would try and switch the protocol and baudrate at the same time and de-link itself from the Bluetooth module, and the only way to resolve this was to use the optional cable connected to a PC to manuall connect and switch it back.

moutonlambda · Occasional Visitor Joined: Jun 15, 2005 Posts: 1

Pelrun,

I have exactly the same bad experience : first day I receive the GR231 worked fine with tomtom navigator and other softwares, till I connected to the PC to play with sirfDemo...

Ouch !!! Now I see octets of garbage, sometime displayed as "bad sentence" (when it starts with a dollar symbol), on the com connection.

I suppose I siwtched to sirf and 115200 bauds, but I dont know exactly what I did. I was "playinng" with sirfDemo.

I did not managed to get the settings back to something normal.

I think about doing a firmware upgrade via the data cable, or only a change settings with that cable.

My question is : do U know how to build or buy this USB data cable ? Is it standard USB cable ?

gpsmonster_uk · Occasional Visitor Joined: May 21, 2005 Posts: 17

Hi,
The cable in the box with the GR-231 is just a sync/charge cable (usb to mini usb); you will need a seperate data cable in order to use it as a Mouse or to switch the protocol type.
This cable costs around 14.99 on the Holux UK Website.
Good Luck :D

	PocketGPS
	Web