Holux GPS Trouble - Page 2

strohj · 10-24-2007, 08:27 AM

hmm if you can get it to work flawlessly in mappoint... then it should work perfectly in streetdeck...

God_of_CPU would be the one who would know more here...

send him a PM and ask him to look at this thread

god_of_cpu · 10-24-2007, 01:44 PM

Use the -recordGPS command line parameter to make a recording of your GPS data then send it to me.

mangus580 · 10-24-2007, 01:45 PM

Will do!

mangus580 · 10-25-2007, 09:32 PM

Here are 2 different files

mangus580 · 10-29-2007, 08:36 PM

Any update?

oxman · 10-30-2007, 06:49 PM

I have the same receiver with the same probelm so I'd also like to see this resolved.

parksgm · 10-30-2007, 08:20 PM

Quote: Originally Posted by mangus580

But it now appears as the GPS loses signal, and also flashes me in the Atlantic, and Pyranese Mountains? alot. I dont really understand whats going on, but it appears that its not reading the data properly. For grins.... I fired up Mappoint to see how that tracked. It was flawless, using the same data stream. (ie the com port SD was using...)

any ideas? I am getting really frustrated with SD at this point.....

I have a similar issue with SD now (but with an Earthmate USB GPS receiver)...SD alternately flashes me in the Atlantic and China (I think it's China...looks like a Chinese name, anyway), or flashes the "Low GPS signal" for a few seconds at a time.

Mappoint reads the data and tracks perfectly...leading me to believe it's an SD issue. I need to start logging and post the logs, but I think I'm going to start by reinstalling SD first.

mangus580 · 10-30-2007, 08:37 PM

Glad to know its not just me!

Curiosity · 11-01-2007, 05:59 AM

Quote: Originally Posted by mangus580

Here are 2 different files

Those logs look bad. Some lines are peices of a sentence. Some have checksum errors. Some start in the middle of another line. Some have a correct checksum and are still missing half the line. One of those crashed my parser code. I think you should do a factory reset on it or replace it. Look for lines without a * and 2 hex digits at the end.

Example - the top one isn't even good:
$GPGGA,010133,N,07719.0010,W,1,08,1.5,4313.6491,N, 07719.0010,W,44.06,85.66,261007,,,A*73
$GPGGA,010134.000,4313.64961.5,2.3*34
$GPGGA,010135.000,4313.6504,N,07718.9675,W,6
$GPRMC,010135.000,A,4313.6504,N,07718.9675,W,44.07 ,86.51,26

mangus580 · 11-01-2007, 07:09 AM

Factory reset on what??? the GPS works fine with EVERY other application.

god_of_cpu · 11-01-2007, 12:40 PM

Quote: Originally Posted by mangus580

Here are 2 different files

I have put some additional error handling in for parsing out bad GPS data based on the logs that will be in the next version and should make it work better, but not perfect and ultimatly your GPS is feeding bad data and there is definitly something wrong with the hardware.

oxman · 11-01-2007, 04:42 PM

FYI, I've had this problem with Streetdeck and the Holux236 for about a year. I started using GpsGate which fixed everything. A streetdeck update came out along the way which broke it again (with GpsGate) but I set up a Virtual COM w/NEMA filter and block data "to and from" output (checkboxes) and I've been good ever since.

No big deal, I just wish I didn't need to rely on another app. If I could find another good GPS device with an external antenna port (I use the mp3car rooftop antenna) I'd switch.

Curiosity · 11-01-2007, 05:18 PM

Oh, that makes sense. GpsGate is filtering out all the invalid NMEA data. XPort is transparent but SD will have a fix soon enough, so all's good.

Anyway, there's enough valid data to get a position pretty frequently, but still that's getting some serious noise or failing bad. Maybe it got wet inside?

mangus580 · 11-01-2007, 05:42 PM

Quote: Originally Posted by god_of_cpu

I have put some additional error handling in for parsing out bad GPS data based on the logs that will be in the next version and should make it work better, but not perfect and ultimatly your GPS is feeding bad data and there is definitly something wrong with the hardware.

Chuck, the real problem isnt the hardware I dont think. If you look back.... My core issue was, I couldnt get hte baudrate in SD to set accordingly. the Holux runs at 38400. SD wont set properly to it, so we are using xport to slow it down. Xport is probably having an issue doing it 'perfectly' and creating the bad data. If we could get SD to effectivly run at the 38400 baudrate, I think I problems will go away.

mangus580 · 11-01-2007, 05:43 PM

Quote: Originally Posted by oxman

FYI, I've had this problem with Streetdeck and the Holux236 for about a year. I started using GpsGate which fixed everything. A streetdeck update came out along the way which broke it again (with GpsGate) but I set up a Virtual COM w/NEMA filter and block data "to and from" output (checkboxes) and I've been good ever since.

No big deal, I just wish I didn't need to rely on another app. If I could find another good GPS device with an external antenna port (I use the mp3car rooftop antenna) I'd switch.

Ox.... how did you set up that virtual com? Was this with GpsGate? or something else?

Also.... how do you like that antenna?