Thread: GooPs Real-time GPS Tracking and Navigation for Google Earth -Version 2.5.13 Released

Does demo mode work?
Delete the GooPs registry entry in HKEY_CURRENT_USER\Software
Go to the directory from which GooPs is running and delete the file GooPs.trk.
Hook up your GPS and press the GooPs Options->Record button. It should create a file called Me.Play.nme. The file should contain nmea sentences from your GPS.
Make sure you don't have an old GooPsServers network link in My Places in Google Earth.
You can also try editing the GooPsServers network link in Google Earth. Replace the string "localhost" with "127.0.0.1" (e.g. http://127.0.0.1:51233/GooPsServers)

Let me know what happens,

-Dave

Originally Posted by NoTicketsPlease

Dave,

Thanks for the quick reply. I checked all of the things you listed, no luck.

Trying version 1.6 GE gives an error saying it could not open the kml file for reading.
Version 1.7.1 acts just like 1.7.3

I have rebooted. Anyway I can wipe out all of the goops settings and start over?

fyi:gps is a UG-200

David I got some very interesting results today! I had time to test... Version 1.7.3 does work with my Ublox DR GPS but with e very funny but important bug! most of the time, but not always, it does not change the direction of the arrow. I turn and my track follows me just fine but the arrow does not turn and of course GE does not rotate. I also found out that when this happens versions 1.7 and 1.7.1 stopped tracking me completely (the problem mentioned in previous posts and supposedly resolved with 1.7.3).

The most interesting part is that version 1.5 and 1.6 work fine!!!! Problems start at 1.7 . I will attach a small log that most of it has this problem just replay it with your versions and you'll see what i mean.

By the way these are not complaints just trying to work with you to improve the program. I and all of us here i assume really appreciate all the work and effort that you put in this! I thanks you so much for being so patient with me!

The log.

Thanks spaceskater,
I really appreciate your feedback. I think I see the problem, I believe I am interpreting the GPRMC course info incorrectly. It looks like I had it right in 1.5 and 1.6 but for some reason I changed/broke it in 1.7.
So hopefully when I put the old code back it will fix your problem. Sorry for the confusion.
-Dave

Originally Posted by spaceskater

David I got some very interesting results today! I had time to test... Version 1.7.3 does work with my Ublox DR GPS but with e very funny but important bug! most of the time, but not always, it does not change the direction of the arrow. I turn and my track follows me just fine but the arrow does not turn and of course GE does not rotate. I also found out that when this happens versions 1.7 and 1.7.1 stopped tracking me completely (the problem mentioned in previous posts and supposedly resolved with 1.7.3).

The most interesting part is that version 1.5 and 1.6 work fine!!!! Problems start at 1.7 . I will attach a small log that most of it has this problem just replay it with your versions and you'll see what i mean.

By the way these are not complaints just trying to work with you to improve the program. I and all of us here i assume really appreciate all the work and effort that you put in this! I thanks you so much for being so patient with me!

The log.

Ooops, that was a red herring. I've found that if I take the negative heading values I get in your GPRMC or GPVTG sentences and add 360 it gives the correct heading. I'm not sure how you got it to work w/ 1.5/1.6, maybe just a coincidence? I'll see if I can dig up an nmea spec to find what this really means. In the meantime I'll post a new version with this fix probably tomorrow.
Thanks again!

Originally Posted by davidhite

Thanks spaceskater,
I really appreciate your feedback. I think I see the problem, I believe I am interpreting the GPRMC course info incorrectly. It looks like I had it right in 1.5 and 1.6 but for some reason I changed/broke it in 1.7.
So hopefully when I put the old code back it will fix your problem. Sorry for the confusion.
-Dave

Originally Posted by davidhite

Ooops, that was a red herring. I've found that if I take the negative heading values I get in your GPRMC or GPVTG sentences and add 360 it gives the correct heading. I'm not sure how you got it to work w/ 1.5/1.6, maybe just a coincidence? I'll see if I can dig up an nmea spec to find what this really means. In the meantime I'll post a new version with this fix probably tomorrow.
Thanks again!

That is very odd! I assume that you discarded the negative heading values because the arrow did not turn at all. I have been using 1.6 for a day and it works flawlessly!!! I don't know why but it don't look like a coincidence. My GPS should output standard NMEA 2.3 sentences.

My GPS mouse is stuck....its just spitting out the same data it seems.

Damn.

Thanks for the help though.

It all makes sense now. The heading value in the nmea sentence is just an offset from zero degrees, so it can be positive or negative. When I put in the sanity check (in version 1.7) I assumed it had to be positive so I threw out any sentences with negative heading values, which made the updates stop completely. When I made the "fix" in 1.7.3 I just kept the current heading value instead of throwing out the sentence completely, making the cursor not rotate with the heading changes.

Originally Posted by spaceskater

That is very odd! I assume that you discarded the negative heading values because the arrow did not turn at all. I have been using 1.6 for a day and it works flawlessly!!! I don't know why but it don't look like a coincidence. My GPS should output standard NMEA 2.3 sentences.

1.7.4 – 3/24/06

• Fixed heading problem (seen with ublox gps) – negative heading values are now passed through to GE.
  
• “Autostart Google Earth” no longer starts Google Earth on program startup unless GPS “AutoConnect” is selected and GooPs is not in demo mode.