View previous topic :: View next topic |
Author |
Message |
CCJJ Occasional Visitor
Joined: Mar 12, 2011 Posts: 11
|
Posted: Thu Apr 28, 2011 8:46 pm Post subject: |
|
|
@ MaFt, no i dont.
Regards |
|
Back to top |
|
|
Darren Frequent Visitor
Joined: 11/07/2002 14:36:40 Posts: 23848 Location: Hampshire, UK
|
Posted: Thu Apr 28, 2011 8:53 pm Post subject: |
|
|
CCJJ wrote: | Hi all i think i found out why. After BIGPERK mentioned about a limited number of POI's being supported, i looked in the POI folder on the garmin device (through my desktop). I saw all the old PGPS camera database's were still on the device. |
What were the filenames?
POILoader takes our data and creates a POI.gpi file which it sends to the device. Every time you update it repeats this and overwrites the file.
So I can't understand how you would come to have a number of these? _________________ Darren Griffin |
|
Back to top |
|
|
CCJJ Occasional Visitor
Joined: Mar 12, 2011 Posts: 11
|
Posted: Thu Apr 28, 2011 9:00 pm Post subject: |
|
|
The file name was whatever i called it .gpi (e.g. speed cams 27 april.gpi). Is it becuase i was putting differnet files names onto the device each time i added new POI's? (e.g. speed cams 21 april.gpi) etc |
|
Back to top |
|
|
Darren Frequent Visitor
Joined: 11/07/2002 14:36:40 Posts: 23848 Location: Hampshire, UK
|
Posted: Thu Apr 28, 2011 9:25 pm Post subject: |
|
|
CCJJ wrote: | The file name was whatever i called it .gpi (e.g. speed cams 27 april.gpi). |
Ah I see.
Quote: | Is it becuase i was putting differnet files names onto the device each time i added new POI's? (e.g. speed cams 21 april.gpi) etc |
Yes, exactly that. No need to do that, all it will do is create problems as you'll be running multiple versions of the database then. _________________ Darren Griffin |
|
Back to top |
|
|
dales Frequent Visitor
Joined: May 04, 2008 Posts: 752 Location: Knaresborough, North Yorkshire.
|
Posted: Thu Apr 28, 2011 9:29 pm Post subject: |
|
|
CCJJ wrote: | I'm sure ive read on this forum that when loading new POI's there is no need to delete the old ones as they are overwritten, however this seems to be untrue (for me anyway, as far as i can tell). |
That's correct.
PoiLoader USED to overwrite your file each time.
But the Latest version of PoiLoader allows you to choose a name for your file, each time. It only overwrites, if you use the same filename as before.
This new feature is useful eg if loading separate files for different countries.
Dales. _________________ nuvi 2599LMT-D, oregon 700, basecamp, memory-map. |
|
Back to top |
|
|
CCJJ Occasional Visitor
Joined: Mar 12, 2011 Posts: 11
|
Posted: Thu Apr 28, 2011 9:41 pm Post subject: |
|
|
DOH, thanks anyway all |
|
Back to top |
|
|
MaFt Pocket GPS Staff
Joined: Aug 31, 2005 Posts: 15145 Location: Bradford, West Yorkshire
|
Posted: Thu Apr 28, 2011 10:58 pm Post subject: |
|
|
CCJJ wrote: | Hi all i think i found out why. After BIGPERK mentioned about a limited number of POI's being supported, i looked in the POI folder on the garmin device (through my desktop). I saw all the old PGPS camera database's were still on the device. I deleted them all and then installed the current database, and voila, it worked without freezing at all.
I'm sure ive read on this forum that when loading new POI's there is no need to delete the old ones as they are overwritten, however this seems to be untrue (for me anyway, as far as i can tell).
thanks to everyone in the tread! |
erm... how are you installing the database? you should not simply copy and paste the csv files to the device. POILoader creates a file called POI.gpi that it transfers to the device - this ALWAYS overwrites the existing POI.gpi.
so, what old files were on the device?!
MaFt |
|
Back to top |
|
|
Darren Frequent Visitor
Joined: 11/07/2002 14:36:40 Posts: 23848 Location: Hampshire, UK
|
Posted: Fri Apr 29, 2011 11:39 am Post subject: |
|
|
MaFt wrote: | erm... how are you installing the database? you should not simply copy and paste the csv files to the device. POILoader creates a file called POI.gpi that it transfers to the device - this ALWAYS overwrites the existing POI.gpi. |
You may want to go back and read the other replies
New POILoader offers users the option of renaming the .gpi file before upload. If you do, then you end up with a load of previous versions.
I've made a note and will annotate the install guide to alert to this. _________________ Darren Griffin |
|
Back to top |
|
|
MaFt Pocket GPS Staff
Joined: Aug 31, 2005 Posts: 15145 Location: Bradford, West Yorkshire
|
Posted: Fri Apr 29, 2011 12:15 pm Post subject: |
|
|
Darren wrote: | MaFt wrote: | erm... how are you installing the database? you should not simply copy and paste the csv files to the device. POILoader creates a file called POI.gpi that it transfers to the device - this ALWAYS overwrites the existing POI.gpi. |
You may want to go back and read the other replies
New POILoader offers users the option of renaming the .gpi file before upload. If you do, then you end up with a load of previous versions.
I've made a note and will annotate the install guide to alert to this. |
i know, that was weird... i must have had the thread open for a couple of hours (while i watched Burke & Hare - good film by the way!) then replied without refreshing to see all the updates!!
MaFt |
|
Back to top |
|
|
YellowMonster Lifetime Member
Joined: May 21, 2007 Posts: 10
|
Posted: Tue May 03, 2011 12:37 pm Post subject: PGPS database causing satnav to freeze |
|
|
Noted that the installation of multiple PGPS databases causes the 'freezing problem'.
Have checked and only one database installed on my Garmin 1490T.
Removing the voice files does remove the problem.
Anyone got any idea's ? |
|
Back to top |
|
|
BigPerk Frequent Visitor
Joined: Sep 06, 2006 Posts: 1618 Location: East Hertfordshire
|
Posted: Tue May 03, 2011 1:02 pm Post subject: |
|
|
There was a post recently suggesting (IIRC) that getting an alert voice at the same time as a route instruction may be a cause of freezing (but I can't say for sure if it was a Garmin). _________________ David
(Navigon 70 Live, Nuvi 360) |
|
Back to top |
|
|
K2WES Occasional Visitor
Joined: May 21, 2006 Posts: 1
|
Posted: Sat Aug 06, 2011 7:02 pm Post subject: |
|
|
I too have intermittent freezes when displaying speed camera symbols on a Nuvi 1240. Back to menu and return to map clears it.
Only Gpi files are poi.gpi (Garmin original ?) and speedcam.gpi. Latest updates installed.
Frequent enough to be quite irritating. |
|
Back to top |
|
|
G12345 Lifetime Member
Joined: Aug 05, 2008 Posts: 5
|
Posted: Fri Aug 26, 2011 6:02 pm Post subject: |
|
|
Recently upgraded from an older Nuvi to a 1340, and I am getting the same problem. Occasionally the map freezes when camera is approached, back out to menu and back to map gets things going again.
Have tried consolidated and speed-zoned, and tried all combinations of map detail and 3d/2d settings. Still happens regularly.
Same problem is reported in another post....
http://www.pocketgpsworld.com/modules.php?name=Forums&file=viewtopic&t=87957
I guess it's probably a Garmin software issue, but am puzzled why it doesn't happen with the built in Cyclops database? I haven't got voices enabled. Could it be something to do with the bitmap files? It seems to happen more frequently, but not exclusively, when there are a number of camera icons on the screen at one time.
Any suggestions would be appreciated! |
|
Back to top |
|
|
G12345 Lifetime Member
Joined: Aug 05, 2008 Posts: 5
|
Posted: Mon Aug 29, 2011 7:16 am Post subject: |
|
|
G12345 wrote: | Could it be something to do with the bitmap files? It seems to happen more frequently, but not exclusively, when there are a number of camera icons on the screen at one time.
|
Update - have established that it's unrelated to the camera bmp files. Tried removing them and freezing still occurs. Without the bmps loaded, cameras appear on the screen as small circles, so their location is still apparent. (I did find a post on another forum - http://www.poi-factory.com/node/28569 - where freezing associated with a particular poi was solved by removing the bmp file).
Have tried various other tweaks, including updating POILoader. Also had a go at combining all the data from the csv files into one, and replacing the text for gatso, specs, mobile etc with "camera". I tried this to see whether the unit might be stalling when confronted with several different types of camera at the same location. Cameras all worked fine, but the freezing problem still occurred though.
Interestingly, drove 300 miles yesterday without a single freeze - other than on a section of dual carriageway where it seems I can now reliably reproduce the issue. On the road in question, things are fine until I am driving through a section that brings up at least 4 camera alerts within a space of about 1000 yards. Halfway through the section, the display stops moving and will remain frozen until I back out to the menu.
I've noticed that, even if I wait until I've driven on to an area with no cameras at all, when I back out to the menu the first thing that happens is that the speed camera alert screen comes up (the one that you see if you are driving without the map visible) and it plays the alert chime sound. Maybe something is getting stuck with the audio buffering on the unit???
Will keep testing and trying to eliminate possible causes. |
|
Back to top |
|
|
G12345 Lifetime Member
Joined: Aug 05, 2008 Posts: 5
|
Posted: Tue Aug 30, 2011 6:38 pm Post subject: |
|
|
In an attempt to get access to more parameters to try changing, i downloaded Ash10s Camera Manager. Using Poiloader, it created a much larger gpi file from the gpx files in the database folder. Tried it live today and the Garmin got through the troublesome stretch of road in both directions on my run to work without a hint of a freeze! I just ran the Camera Manager with the default settings.
Not sure why this has made a difference. Will keep testing over the forthcoming days, but this might be something that others could also try to see if it works in their situation also? |
|
Back to top |
|
|
|
Posted: Today Post subject: Pocket GPS Advertising |
|
|
We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
|
|
Back to top |
|
|
|