Thread: GoogleEarth GPSR Tracking

Found it. A space character is in every sentence at the same postion. Dont know why. I'm triming it out but still it shouldnt be there. I'm thinking I should set things up to throw the incomplete data set alert. However, if you need the corrected program asap then message me. Looks like you may. Otherwise, I may sit on it a day or so till I resolve the other things.

P.S. I PM'd you a copy of the generated kml

Gave the invalid space charater from previous post some thought. True my program has flaws but to filter out a space from a number recieved then pretending its alright would be wrong. The program is acurate when it says the data is invalid so I'm leaving off the space strip. On the other hand though, if I were to handle invalid data, and I could, an alert would need to be presented, with a more obvious signal. The way things are now, that just may be too much coding for a device that should be sending the majority of its info in proper form.

The next version is being tested now, should be avail tomorrow, or tonight if i cant sleep. NMEA data will now be written if a bug, like the one mentioned above, occurs.

Also, I forgot to mention in my change log a new feature in build 10032:
Option to create a custom outfile implemented.

I can perfectly understand that you don't want to allow for arbitrary "weirdnesses" in the format of the data you are reading.

I had a look at the file again, and as you say there is a number of surplus spaces. However these are all at the end of each line, as far as I can see. Did you find any others? Again this seems to be a problem with my copying it from HyperTerminal.. it seems to pad out a bunch of spaces for some reason.

I set the HyperTerminal to write the NMEA data directly to a text file for me, and then I didn't have all the spaces anymore. And now it works to load that file in CommTest2. However I still can't get CommTest2 to read from the GPS directly.

For me GE works insanely slow when CommTest2 reads that NMEA-file.. Probably takes 7-8 minutes from "Full Earth View" until it has zoomed in on my path. As a comparison it probably takes 8-10 seconds when opening the kml file that represents the same path. The latter is a rather smooth zooming in.. Seems that somethings keep reloading continuously when CommTest2 runs it. It also zooms far to close in (approx 20ft Eye alt).

I don't mean to spam you with complaints man! I just find your project very interesting, and I would just like it to work for me!

Thanks again!

Havent put togethe real instruction yet. -- Follow this.

("In order for CommTest2 to work properly with Google Earth " & _
"you need to change the 'Fly-To-Speed' in Google Earth Options. " & _
"Open Google Earth. Click 'Tools' from the Menu Bar then click 'Options'. " & _
"Click the 'Control' tab and check the 'Advanced' box. Slide the 'Fly-To-Speed' " & _
"slider until the value is somewhere close to 1.00. It doesn't need to be perfect " & _
"and you can change the value to whatever when everything is up and running.", _
MsgBoxStyle.OkOnly, "Important: Dont forget to adjust Google Earth")

Alright. That helped!

I thought I had already done this.. might not have saved the settings or something.

However I still have the problem that GE seems to be headbutting the top our house when CommTest2 runs the show from my NMEA-file. And it is zoomed far too close in..

And still no action when trying to read directly from the COM-port.

Good work there tiger. Now go to the instructions on the web page and pick up on the keyboard shortcuts section. Of course, the com ports will not work untill the new codes in place. Hopefully today. Keep checking here.


Currenty listening to: Sinead O'Connor, Am I Not Your Girl?, Why Don't You Do Right?

Communication ports settings are now available. Compatibility with the
Holux GPSlim 236 should be there too. Thanks for being a sport Tour, and letting me know about this necessity.

CommTest2 Download Link: http://briefnotion.250free.com/

0.3.3.0 (July 19, 2006)

• Changed the way log files are saved. When satellite lock is not made, data will cont to be logged.
• Fixed a problem with bad data when too many items were in a NMEA sentences.
• Setting transmit bit off before shutting down com port. Should decrease, hopefully eliminate, com port program lock ups.
• Outputting NMEA data even if no satellite info, especially time info, has been received. New file will be based on pc time and not sat time. Times may not match.
• Numerous internal changes to write file system and other portions of code.
• KML files are not created if no data is received.
• Settings to change Communication (Serial) ports are available.
• Zoom level below 1 will step at .2 and zoom will not drop below .2.

Forgot to mention this in previous release
0.3.2.0 (July 17, 2006)

• Option to create a custom outfile implemented.

Reading from the COM-port works now! Cool!

I still have some issues though.. (sorry mate!)

When it zooms in (from full earth view) it's like sitting on a meteorite made of rubber.. it speeds straight in too close to see anything at all. And then it keeps gyrating the top of our place. Like a bouncing ball.. just that it never settles down, and all I see are just those enormous pixelated images of nothing growing and shrinking.. Do you have any idea why this happens? I set the 'Fly-To-Speed' to exactly 1.00.. would this cause some kind of endless loop?? Seems weird.. Well.. it's almost 5am here now, I should hit the sack.

Thanks for all the help so far!

Sounds like the zoom level is too close in. pres the 1, 2 or 3 keys to reset the zoom factor and check the settings on page setup 1, display settings, reset to default values.