lunarpatrol

PAJALLEN was talking of his "parking spot". So, as long as he's not in a need to park his shoes... Sorry, had a clown for breakfast. Seriously....good point about the automotive profiles...guidance mode in menu /settings/routing should be "off road" to do any tests.... for my tests I used the same (off road) profile....

I've found that the speed i am moving with makes a LOT of difference for the quality of the tracks. Tracks recorded from a car or on the bike look usually really good. But if you're walking and the reception is not PERFECT, the results are very often not usable (drifts of several 10 meters, "drunken lines" etc...). Generally it helps before recording a track to power the GPS on at a place with good reception and keep that position for a couple of minutes before moving. Be it as it may...i really hope Garmin gets this issue under control, cause correct coordinates is what should be expected from a device in that pricerange...

Following up on the accuracy problems for some time now. In the past weeks I used my way to and from work as a test track (consists of walking and local train ride through the city...high buildings, low buildings...quite a mixed field). I tried beta versions from 2.86 on. By far the worst tracks were produced by the recent firmware versions (2.94 and 2.95), which use the same gps-firmware....Lot of drift....lot of totally "drunken" tracks.... similar results to the track shown above sometimes......sometimes good results as well but usually not the kind of accuracy I would rely on... Well, what I did yesterday is revert to 2.93 and again back to 2.95 [let the device boot up in between of course] to have the almanac cleared, to get a "fresh" satellite fix. Turned the gps on today and gave it some time to get a lock on a reasonable number of satellites (without moving....i found this to be important). Then I had a round with my bike....and the same way back....also some distance on foot to see how the device behaves with slower speed. And tracks today looked wonderfully smooth when riding the bike (no reasonable difference between in and out tracks as well, could even figure out which side of the road I was driving on). And the "on foot" track looked MUCH MUCH better when compared to the previous days!! This of course needs further testing, maybe someone else has similar experiences or would like to give it a try... Maybe this hotfix feature is not that good after all....if my experience can be verified then I suggest Garmin to implement an option to clear all the previously collected satellite data or to give the user the choice to switch off hotfix alltogether. Some screenshots: Picture shows tracks done with different firmware versions, walking....inner city 5 story buildings+high church nearby... pink: firmware 2.93.....ok cyan: firmware 2.94.....bad blue: firmware 2.95 before getting a "fresh" lock (see above)....bad green: firmware 2.95 after getting a "fresh" lock (see above)....just walked up the street and back again...looks ok, similar to 2.93 Picture shows tracks done today with firmware 2.95 after getting a "fresh" sat lock. Biking to work in the morning, back in the afternoon....tracks look perfect (at least for me) Picture shows tracks done today with firmware 2.95 after getting a "fresh" sat lock. yellow:bike, green: on foot.....When tracks indicate different sides of the street it shows where i actually were Ok that's it for now, curious how the story develops....

Problem being caused by cache GC1KBPB v5.8.7 should fix the problem. j Hey jjreds, thanks for your super quick reaction and fix. New version works like a charm! LP

Thanks for the great macro! Using it for my nuvi 350 as well as for my oregon. With newer versions, however, i do encounter a problem when transfering the created files via POI loader. Poi loader complains that an error was found in the mystery.gpx file in line 1 and won't process this file. The others (multi, traditionals etc...) work ok. The created gpi-file then only contain the non-mystery caches. Ok, when using the old 5.5.1 version of the macro, which is still available for download, everything works ok. Questions: Anyone else with this problem? Are the other versions between 5.5.1 and the latest available for download as well somewhere? I would then try to find the latest version that still works....