Map This! v0.2

[deniska]

Hello,

I'm also interested in contributing to this project. For that reason, I've taken some time to browse the source code. My immediate concern is knowing how to set the right settings for my 4800 baud GPS. I'm aware of a BAUD=x setting and a READTIME=x setting in the config file.

So I went browsing in the source to find out how those are used. I was confused by something. The 'baud' setting is currently set only if SDL_SOUND is defined; otherwise, the baud rate is not set as far as I can see (this is in the v02 unpatched sources).

I noted that the readtime variable is used to control a loop.

My question: is it intentional not to set the baud rate when SDL_SOUND is undefined? If so, why? Couldn't this cause problems with devices running at arbitrary baud rates?

Thank you,

~0

SDL_SOUND was put in before the GPS functions...
For some reason it does not work in kernel mode and GPS would not function in user mode.. so I used SDL_SOUND as a switch... I did not care about the sound so much, since it needs to be shut off in order for GPS to function (plug in to power the serial port)
So don't set the SDL_SOUND if you need the GPS functionality...
I don't think this would be your problem if you uses my original EBOOTS...

[deanspeed]

is there a tutorial on loading waypoints/poi onto psp from in7ane's windows program, I'm not sure how to.

[ZeroAltitude]

Hi Deniska,

I apologize I was not clear in my earlier post. Let me try one more time.

I have a 4800 baud GPS. In MapThis, there is nowhere where you call setBaud() anymore -- the only place in there is inside an ifdef for SDL_SOUND.

Are you saying that in your latest release, the setBaud() call *is* being made, but not inside an ifdef? Do you have any pointers as to the appropriate setting for READTIME for a 4800 baud GPS?

Again, thanks in advance. I find the code fairly easy to learn, so if you have any place where you're maintaining a buglist or something where I could take a look and offer some patches for your approval, I'd be delighted.

~0

[deniska]

It's ifNdef ;-)
i.e if SDL_SOUND is not defined then you set the baud...
Image * cursor, *blank, *scale, *zoomscale, *arrows, *compass;
#ifndef SDL_SOUND
pspDebugSioInit();
pspDebugSioSetBaud(baud);
pspSdkLoadInetModules();
#endif

[jimmy7]

Jimmy7,

Hmm, I did not get any emails.. perhaps you used invalid address or your adress got filtered for some reason... try to PM me @ DCEMU or PS2DEV forums...

About the coordinates - perhaps we were talking about different issues... I checked the map coordinates at zoom 15 against google maps at the same zoom - they seem to be the same... so maybe you could clarify how you get the .5 degree deviation..

For some reason I cannot send you a private message (forbidden?!). So I sent an email to the teamjak dot net domain. If that does not work out maybe you can contact me privately. Regarding the zoom: here the gps coordinates change depending on the zoom level... and it is really a 0.5 degrees change in LAT ...

[ZeroAltitude]

Ack whoops, my bad. Trying tonight with settings 4 - 8 for READTIME with Sept 8 expanded buffer distro.

~0

[ZeroAltitude]

Many apologies for the long post.

Hello,

Thank you for bearing with me. I feel like I'm almost there. With READTIME set to 8, here is what happens in MapThis:

* I get the correct number of satellites
* I get the time
* Where it says the data status, I get DATA: BAD
* In local maps of my home town, I get occasional messages that the location is out of range
* When I switch to the global map to see what location it might be, it's 0.0000 lat -0.50000 long or something very similar (an obvious data error)

Now, mind you, in greenscreen, I get reasonably accurate listings of my latitude and longitude (I see the sentences with the data from my Garmin, and the numbers above reflect them fairly closely).

My questions:

* how can I provide you with any data you might need to figure out this problem?
* could this old GPS be using an incompatible NMEA sentence format? (I would have assumed that if the problem were this, then greenscreen would also fail to parse these sentences...)

A puzzling thing I've noticed -- in Deniska's original greenscreen photo from early on, the data listed in the NMEA sentences for lat. and long. appear to be ever so slightly different from what's displayed above in lat. and long. (to be specific:

from http://www.dcemu.co.uk/vbulletin/showthread.php?t=30035

from upper portion: lat: 40.169..., long: -73.970...

from NMEA sentences: $GPRMC,034123.000,A,4037.1983,07538.2213...

Note the last two sentence numbers look uncannily similar to the Lat. and Long. -- I don't know the NMEA spec well, but I was just curious about how to iinterpret these numbers. In particular, I noticed on my Garmin it would say e.g. lat 42.00 etc., and in the NMEA sentence in the bottom of greenscreen, it would have numbers that were *just like* 42.00 etc., while similar to Deniska's screenshot, the upper numbers were slightly different. Just curious as to how that all works.

Anyway, I'm really looking forward to using MapThis. I'm sorry this message is so long. I'm just trying to provide as much info as I can.

~0

[Xern]

Hi folks, it's me again. My results from the newest beta:

Readtime 1:
Nothing

Readime 2:
Almost works. When I hit [] it waits for 1 second, then it moves from where I am now (south norway) to the top of norway in 0.5 seconds, and it locks on my correct position. After that, it updates with the (possible correct) position each 50 second. Also, everything in the program updates every 2 seconds.

[deanspeed]

how do you get that line to show up? all i see are squares on every turn, but i dont get that red line.

[deniska]

in7ane's tool has an option to configure the total number of way points. In my example, it's just so many of them that they touch eachother, creating a line.. I'll try to work out a better solution in future releases...