briefnotion

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

0.3.0.0 (July 12, 2006)

• The network link will now clear when disconnected allowing GE to return to normal.

0.2.9.1 (July 11, 2006)

• Added quick key option "w" window release to the help screen.
• Added second speech tab to settings to accommodate more.
• Added Escape Key quick key setting to announce status.

MP3Car.com

 

briefnotion

Should be a well liked update. Points of Interest or POIs can be created by pressing the backspace key. Data about how fast you were driving, altitude, and other things will also be saved in the description. Sort of like a snap shot. The description is the same as the Status speech text so edit to fit your prefs. The temp is really hot down here so testing is at a minimum. PM me if you see an error. Enjoy.

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

0.3.1.0 (July 13, 2006)

• Quick key POI's with the backspace key. Press enter for a POI name and the POI will be named an incremental number. The description of the POI is also the status so you can edit what's there. You can also load POIs as a guide file and announcements will be made when you are near.

briefnotion

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

• You can now choose a path color.
• Automenu will recognize .prc files. These are mobipocket files, an ebook file format that Geocache descriptions come in. Goto http://www.mobipocket.com for more info.
• Option for one second look ahead implemented. The current position placemark can be placed ahead of the current read position to help predict real position. Haven't decided how far to look ahead yet, GE read is every two seconds.
• Another more variables, %currentmps% (meters per second), %datetime% (last message date and time received), %latitude% (Latitude as GE sees it), %longitude% (Longitude as GE sees it)
• Zoom can be stepped up and down with the "," and "." keys.
• More code to hold activation.
• Moved position of Connect and Menu button.
• Changed connect read data blink time.
• Relaxed the method of appending to a file. This is internal.

Tourettes

Hi!

I just tried to install your software (CommTest2build10032). Things seem to work alright, although i can't seem to get any positionin from my GPS. I am using a Holux GR-213 Receiver. Do you have any suggestions for anything I could attempt?

I am using the newest beta of Google Earth (free version).

The receiver works fine when I read it with the Gps Viewer software that came with the GPS. It is set up on COM4 (USB physically, but some driver registers it as COM4).

Thank You!

briefnotion

Have the log files registerd any NMEA sentences? Or if you'd like, send it here and I'll take a look at it. Just kidding. As far as I can tell, the dev should be working. And really, If your device is sending NMEA data, then commtest2 should be properly interpret it. If not, then pm me with the raw data and i'll see whats being missed.

Tourettes

After your reply I tried to run everything again. The chain of events was as follows:

- Starting CommTest2
|---> getting small UI with a couple of buttons

- Clicked 'Connect'
|---> Button text set to 'DisConnect', and button color set red

- Nothing else happens.. waiting

- Clicked 'Control' button
|---> Control dialog pops up.
|---> All textfields are empty
|---> Content inside Path border is:
.......|-> Points in memory: 0
.......|-> Bytes to read: CHANGING. Usually 0, but changes frequently to other values (4,5,7 etc)
.......|-> Connected
- Clicked 'Control' button
|---> Control dialog pops up.

- Clicked 'DisConnect' button
|---> Google Earth pops up and goes directly to the point at all zeroes in both longitude and lattitude
|---> No response from CommTest2 anymore
|---> Google Earth runs on 70-80% CPU load, CommTest2 runs on 3-9% CPU load

- Killed Google Earth process
|---> Still no response from CommTest2 (waiting a fair while...)

- Killed CommTest2 process


After this procedure the file "0001-01-01 00.00.00 - Serial NMEA - OutFile.txt" contains only one line which is "Outfile,00:00:00,0,0,0,0,0"

This happens every time I try. Also it seems like the Control-dialog shows some reading activity on the COM-port.

Puh! )

briefnotion

Ok, looks like your not getting a satilte signal lock. Make sure the GPSr has a clear view of the sky, nothing overhead, trees and buildings can be a bother. Leave the device on for a few more minutes. CommTest2 will not post any info if sat lock is not made. I'll look into that. Same thing goes for the log files with invalid dates. If, guessing here, three sats are locked then the Commtest2 should start reporting your position into GE.

Tourettes

I get a lock very fast in GPS Viewer. And on quite a few satellites actually.

But I will give it another go. I restarted my laptop to make sure the GPS Viewer doesn't hold any resources for the COM-port. I'll leave it on for 15 minutes or so. In GPS Viewer a lock is up within very few seconds.

On another note.. do you have any plans for turn-by-turn navigation instructions in this software? Or are there any limitations in Google Earth that prohibits this?

Tourettes

Still no luck, even after leaving it for 25 minutes. I have also tried to connect to the COM-port with HyperTerminal, but cannot connect to it. Seems to be some kind of problem there. Should work shouldn't it? The weirdest thing is that it works in GPS Viewer so easily..

EDIT:
Now I can read the data in HyperTerminal. However it is only garbled characters and things. I suspect this is a character-set/terminal-emulation issue, but I don't have that answer yet..

briefnotion

Earlier you said you were reciveing data. Appearantly the GPSr is talking, like it should. Next release should give you a nmea log file, then we can see whats happening.


GE Direction results can be saved as kml files. Then loaded in commtest2 as a guide file. The results are like turnbyturn directions. But unlike most gpsr progams, rerouting doesnt exist. and and active inet connect is neccesary to create the route. This part of the program will most likely will not get any better. And i dont know anything about prohibition. If its a legal thing, I rather fight the system. Down with the repressors. heh, i think its fine the way it is.

P.S. Subscribe to this thread to recieve new post notifications.

Tourettes

I got the HyperTerminal working now, and PM'ed you a sample of what the GPS is sending..

Would be nice if you could have a look at it! There might be some funny characters in the log from copying out of HyperTerminal..?

DylanBennett

If you are getting garbled junk in hyperterminal from your GPS device, it's likely not sending in NMEA mode. GPS viewer would see it, AFAIK, because it can understand the NMEA and SIRF modes that the Holux device can be in. (Someone correct if I'm wrong on that.) NMEA data comes in is raw, comma-delimited text.

Also, I'm not sure about your device, but my Holux GPSlim 236 needs to be connected at 38400 baud to be read correctly.

briefnotion

I think that may be it. The data recieved was scattered portions of what seemed to be incomplete data sentences. Many senteces where to short and others to long. Torr, please reset data speed. Should work. If yes, try reseting com port settings in control panel the restart commtest2. If that fails also I'll put in the controls on one of the setup settings pages.

I love progress.

Tourettes

As i said in my last message I've got it working now. My problem was that I was running at 9600 baud. When I changed it to 4800 everything fell into place. Atleast the output looked correct in the HyperTerminal. Might have been something happening to the NMEA-data when I copied it from HyperTerminal - via TextPad - to the html form here..

I've had a nights sleep now, and will try again with a clear head. I have run everything again, and it looks good in HyperTerminal again. I'll try and make sure nothing happens to the text before you see it..

DylanBennett:
When trying 38400 baud I receive nothing. Only 4800 seems to give me a correct representation of the data. Most other speeds give me nothing, and 9600, 2400 and lower give me weird stuff..

briefnotion

Glad to see its working now. While you were sleeping I was stuck implementing new routines specificly designed for handling the data when no data is being recieved. Ha, just kidding. I was doing that but was going to do that anyway. Fixed a few bugs also.

I hope the program works. I'm not sure if CommTest2 will require port speed settings or not with your GPSr. Depends on the OS. Its nothing to do though. Tell me if it does.

MP3Car.com