New Code Contribution

[MIB.42]

Any news from you Deniska on further devopment of 0.4.99 ?

He is on vacation at the moment.

I have added sound support and currently working on putting it into a usable API for deniska for integration.

I also spent some time with tracking down those mysterious crashes. Found the symptom, now looking at the cause...

[jorritprins]

Dear Deniska and other Mapthis! enthiousiasts!

Its my first post, so I would not dare to ask or write anything, before I told you how much I appreciated the Mapthis software!!!! I tried some of the earlier versions, and today I installed the 0.498 release! Looks great, works great! :thumbup:


Although sat lookup seems a bit slower again with this 0.498 release, and the avg speed remains 0 (already reported), I had one other question. Can the gps.txt data log be used for GPS track visualisation?

The gps.txt included in a previous release could be perfectly opened on this GPS Visualizer site: http://www.gpsvisualizer.com/ Unfortunately I cannot open the gps.txt generated by Mapthis 0.498. The file format seems also different (its binary now? )

Here's the complete list of file types that GPS Visualizer recognizes:

.bin Emtac Trine (CRUX_LOG) binary log file
.crs Garmin Training Centre "course" file
.csv Comma-separated text (including Timex Trainer et al.)
.gpx GPX (GPS eXchange format)
.hst Garmin Forerunner XML
.igc IGC log file (from sailplanes)
.kml Google Earth KML
.loc Geocaching.com XML waypoints (not Terrabyte/TopoGrafix!)
.mps Garmin Mapsource TEXT file (not binary)
.nmea Raw NMEA sentences
.ns1 NetStumbler binary log file
.pdb Cetus GPS, Pathaway, or cotoGPS tracks or waypoints (Palm OS)
.pcx PCX5 tracklog
.pgl TomTom text log file (modified NMEA)
.plt OziExplorer tracks
.rdn Fichiers de IGN Rando (français)
.sdf Suunto SDF file
.trk Tracklog: PCX, CompeGPS, GPS Tuner, or Magellan NMEA
.txt Tab-delimited text
.wpt Waypoints: OziExplorer, PCX, CompeGPS, or Magellan NMEA
.xml GPX or Garmin Forerunner Logbook XML
everything else Interpreted as tab- or comma-delimited text

I tried using some different file extensions, but nothing seemed to work....

Anyone suggestions? I hope I can use the gps.txt file again with this http://www.gpsvisualizer.com exactly as it did work for that 'fake feed' gps.txt part of previous Mapthis! Releases….

Many thanks in advance!

JP

[MIB.42]

Dear Deniska and other Mapthis! enthiousiasts!

Its my first post, so I would not dare to ask or write anything, before I told you how much I appreciated the Mapthis software!!!! I tried some of the earlier versions, and today I installed the 0.498 release! Looks great, works great! :thumbup:


Although sat lookup seems a bit slower again with this 0.498 release, and the avg speed remains 0 (already reported), I had one other question. Can the gps.txt data log be used for GPS track visualisation?

The gps.txt included in a previous release could be perfectly opened on this GPS Visualizer site: http://www.gpsvisualizer.com/ Unfortunately I cannot open the gps.txt generated by Mapthis 0.498. The file format seems also different (its binary now? )

Here's the complete list of file types that GPS Visualizer recognizes:

.bin Emtac Trine (CRUX_LOG) binary log file
.crs Garmin Training Centre "course" file
.csv Comma-separated text (including Timex Trainer et al.)
.gpx GPX (GPS eXchange format)
.hst Garmin Forerunner XML
.igc IGC log file (from sailplanes)
.kml Google Earth KML
.loc Geocaching.com XML waypoints (not Terrabyte/TopoGrafix!)
.mps Garmin Mapsource TEXT file (not binary)
.nmea Raw NMEA sentences
.ns1 NetStumbler binary log file
.pdb Cetus GPS, Pathaway, or cotoGPS tracks or waypoints (Palm OS)
.pcx PCX5 tracklog
.pgl TomTom text log file (modified NMEA)
.plt OziExplorer tracks
.rdn Fichiers de IGN Rando (français)
.sdf Suunto SDF file
.trk Tracklog: PCX, CompeGPS, GPS Tuner, or Magellan NMEA
.txt Tab-delimited text
.wpt Waypoints: OziExplorer, PCX, CompeGPS, or Magellan NMEA
.xml GPX or Garmin Forerunner Logbook XML
everything else Interpreted as tab- or comma-delimited text

I tried using some different file extensions, but nothing seemed to work....

Anyone suggestions? I hope I can use the gps.txt file again with this http://www.gpsvisualizer.com exactly as it did work for that 'fake feed' gps.txt part of previous Mapthis! Releases….

Many thanks in advance!

JP

This might be an offline tool requirement, which converts the gps data to one of those formats...
The Holux version dumps NMEA, the 290 version the usbgetdata sentences. The latter is a sequence of 48 byte entries, with the following members and offsets :
short year : 0
short month : 2
short date : 4
short hour : 6
short minute : 8
short second : 10
float unknown : 12
float hdop : 16
float unknown : 20
float latitude : 24
float longitude : 28
float altitude : 32
float unknown : 36
float speed : 40
float bearing : 44

This should be a fairly trivial coding challenge...
Any volunteers?

[mrdweeb]

OMG this is cool. I'm pretty much a noobie to this, but am running 0.461s on 3.10ae with no apparent problems. I've made some maps (colorado towns) with gmdl0.4.14b using the tips and tricks tutorial. Thanks to everyone involved in coding this stuff!

[psp4h8]

Happy eastern from germany!
I´ve got a small problem with my psp 290 and mapthis. I´m using fw 3.03oec + MapThis 0.498 tested this with
-2.71 usbacc.prx&3.03 usbgps.prx and
-3.03 usbacc.prx&3.03 usbgps.prx.
both works for me o.k. , but it takes 10 to over 20 minutes since the first fix. (after the first everything works fine until the next restart...) I´ve tryed different cpu speed + Loc settings, but it doesn´t bring any improvement...

The .prx files are downloaded and not generated from my firmware. But it´s also from 3.03. Ore is there any difference?
Is there anybody who had an idea what I should do to get an faster fix?

[Milhause]

Happy eastern from germany!
I´ve got a small problem with my psp 290 and mapthis. I´m using fw 3.03oec + MapThis 0.498 tested this with
-2.71 usbacc.prx&3.03 usbgps.prx and
-3.03 usbacc.prx&3.03 usbgps.prx.
both works for me o.k. , but it takes 10 to over 20 minutes since the first fix. (after the first everything works fine until the next restart...) I´ve tryed different cpu speed + Loc settings, but it doesn´t bring any improvement...

The .prx files are downloaded and not generated from my firmware. But it´s also from 3.03. Ore is there any difference?
Is there anybody who had an idea what I should do to get an faster fix?

Main setting:
FW 3.03 oac
recovery menu: kernl 1.50
usbacc.prx 2.71
usbgps.prx 3.03
Mapthis 0.97 (0.98 have slow fix)
setting in mapthis (config.txt):
BAUD:4800
LOC:1


my experienc first fix max. to 5 min
I living in Czech Republic

[psp4h8]

THANK YOU MR. VAN HOUTEN!!!
4min 5sec! I´ve tested it with 111mhz and it works great.
Before I´ve never changed the "BAUD:" in the config.txt and it seems that the 0.97 version really fixes much faster!

[Codaz]

Milhouse, why do you run it at 1.50 kernel mode ? And what about that change of Baudrate ?

I get a bit tired of those 100 million configs.

"This motherboard with this prx file and this mapthis version and these loc settings".

Ok but i have some new experiences, 3.30 prx seems to have a VERY VERY high HDOP value, it's around 15 !!

[Codaz]

He is on vacation at the moment.

I have added sound support and currently working on putting it into a usable API for deniska for integration.

I also spent some time with tracking down those mysterious crashes. Found the symptom, now looking at the cause...

Could you look at the reported slow sattelite fix speed ?

Many people report that 0.4.98 is much slower in fixing than 0.4.97, why is that ?

[MIB.42]

Could you look at the reported slow sattelite fix speed ?

Many people report that 0.4.98 is much slower in fixing than 0.4.97, why is that ?

Unfortunately I don't have a 290, so I can't.

Deniska has one though...