Camera Manager and Zumo 660

ChrisL · Occasional Visitor Joined: Mar 22, 2005 Posts: 14

Has anybody used the above combination successfully.

I ask because the 16colour icons I created (due to 660 problems mentioned on Zumo Forums) do not appear on the maps if I use the GPX files created by CM but they do if I use the standard CSVs. I also find that the GPXs although loaded do not appear to work as warnings either - no voice or bong.

I carefully named all my BMPs and MP3s to the same names as CM created for the GPXs but nothing worked, whereas the CSV vesrion appears fine.

Any ideas anyone.

PS I know this 660 is a bit buggy but it was a warranty replacement for a BMW Nav3.

Chris

PhilHornby · Posted: Mon Nov 02, 2009 11:58 pm Post subject: Re: Camera Manager and Zumo 660

ChrisL · Occasional Visitor Joined: Mar 22, 2005 Posts: 14

...You're not running a really old version of POILoader are you Question
(click icon in top-left of first screen, then "about POILoader..." (ideally, answer would be 2.5.4))

I am on 2.5.3 but have now added 2.5.4 just in case but its a lot of work to test it if this .1 change does not contain the fix.

PhilHornby · Posted: Tue Nov 03, 2009 2:48 pm Post subject:

ChrisL · Occasional Visitor Joined: Mar 22, 2005 Posts: 14

The notepad opened files sem OK but thay show a # not an @ sign example line follows:-

{?xml version="1.0" encoding="UTF-8" standalone="no" ?}
{gpx xmlns="http://www.topografix.com/GPX/1/1" creator="MapSource 6.15.7" version="1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd"}

{metadata}
{link href="http://www.garmin.com"}
{text}Garmin International{/text}
{/link}
{time}2009-11-04T11:21:47Z{/time}
{bounds maxlat="51.7706100" maxlon="-2.3250300" minlat="51.7706100" minlon="-2.3250300"/}
{/metadata}

{wpt lat="51.7706100" lon="-2.3250300"}
{name}SW-R-GATSO:2291#40{/name}
{sym}Waypoint{/sym}
{extensions}
{gpxx:WaypointExtension xmlns:gpxx="http://www.garmin.com/xmlschemas/GpxExtensions/v3"}
{gpxx:Proximity}533.0000000{/gpxx:Proximity}
{gpxx:DisplayMode}SymbolAndName{/gpxx:DisplayMode}
{/gpxx:WaypointExtension}
{/extensions}
{/wpt}

{/gpx}

When loaded and run on Simulation I get double bong warnings and the message says:-

Alert:SW-R-GATSO:2291#40

instead of the CSV load which sates 40mph Fixed Speed Camera (or words to that effect)

Any other ideas?

Chris

PhilHornby · Posted: Wed Nov 04, 2009 2:59 pm Post subject:

ChrisL · Occasional Visitor Joined: Mar 22, 2005 Posts: 14

I have two sets of Audio files named as follows:-

CM Set
PocketGPS_UK_Gatso_Forty.wav

CSV Set
pocketgps_uk_gatso_40.mp3

These match the associated names once the soi.exe gets done with them.
I assumed that using Soi.exe has no effect but maybe I need to save the correct format??

Your poi.gpi gave the same look and visual alert as the CM one did but not like the CSV did e.g.

CM/yours
Alerts at close distance and at that time the icon appears on the road and the visual alert as stated earlier appears.

CSV
Uses Daniel Voice (I set) then Custom Camera voice (Nick) and warns of camera as the test route turns onto road containing camera (about 400 yds sooner) using the 40mph fixed speed camera words in the box and colouring it red if over the limit. This closely resemble the actions of the Garmin Database already in the unit (which I've truned off before you ask)

The reason for the Mapsource was the easiest way to find the right camera and delete the unwanted ones for me.

Weird this one.

Chris

PhilHornby · Posted: Wed Nov 04, 2009 6:13 pm Post subject:

ChrisL · Occasional Visitor Joined: Mar 22, 2005 Posts: 14

I was using two different sound files as that appeared to be what CM and the CSV's wanted.

I still don't know which onnes are best as I have more voice files in .mp3 than .wav but the names are not always the same.
CM appears to want different voice files but I cannot seem to find a list to go with the files it creates and the Nick voice I have has files for which no GPX gets
created.

I want to use CM to set repeats etc and so thats the way I need to get this to work.

I will dump the .wav's if I can find replacements to do so in .mp3

My file size was about 6.5Mb so you are right on the money there.

{FWIW - I have Camera Manager generate a PROXIMITY alert for every camera and use Custom Audio to describe it. I then have the 'overspeed' alerts set separately at a different distance, but using the default sound. So, I'm always 'told' about the camera - but if I continue to travel too fast, I get a series of agitated P-I-N-Gs to remind me to slow down.}

That's almost exactly what I'm trying to get but with the threshold a bit above legal so it does not keep bonging and cutting my music in the intercom off (I'm on a bike).

{On the Nüvi 7xx series, the different audio works - but the banner tends to stay grey (proximity) and only very rarely turns red (speed).}

The standard Garmin stuff shows grey until you touch the speed then bongs and goes red and keeps on until you drop speed - very irritating hence its turned off.

PhilHornby · Posted: Thu Nov 05, 2009 7:01 pm Post subject:

ChrisL · Occasional Visitor Joined: Mar 22, 2005 Posts: 14

I can't remember where I got them from originally, but I came across a full set of WAV files on my system, that match the Camera Manager GPX files...
...they must have been supplied originally as WAVs and I've converted them to MP3 (and forgotten I'd done it!).

Any chance of getting a copy or at least a list of the filenames so I can compare to see if I need to find more for my set.

I have done what I can with my mp3's and now it appears that CM loads are working very similar to the Garmin ones except for the content of the box which is like this Alert:SW-R-GATSO:2291#40 instead of the pretty 40mph top line and Fixed Speed Camera second line display. At least I now control the alert timings and the voices used and will try to find out how to change the popup text.

Chris

PhilHornby · Posted: Fri Nov 06, 2009 12:14 pm Post subject:

ChrisL · Occasional Visitor Joined: Mar 22, 2005 Posts: 14

"I found them: http://www.zen19255.zen.co.uk/cm_help/Camera%20Manager%20Voice%20Warnings.zip"

Same Set I have so no difference there.

"Unfortunately, the fields in the GPI file that control this behaviour, are not accessible to us. POILoader certainly can't do it, and last time I looked, GPI_Creator couldn't either. None of the folk who reverse-engineered the file format have shed any light on it, presumably because all the examples are 'locked/encrypted'."

Thats a bit weird as when I use the .CSVs to load it I do get the grey/red boxes with the words on two lines very similar to Garmins e.g. 40mph & Speed Limit Ahead at range then two occurrences of 40mph & Speed Alert. I assumed these were part of the loaded files but they must be triggered by the CSV contents and controlled by the internal software of the unit. I prefer this look but much more prefer CMs warning/troigger control so I am stuck with it unless I can figure out a way round it - presumably its the format of the GPX that needs a tweek to make it work - will try experiments.

ChrisL · Occasional Visitor Joined: Mar 22, 2005 Posts: 14

I have figured out part of the box message differences:-

CM's GPX file uses # to separate the name of the camera from its limit whereas the CSV's use a @ symbol.
Manually changing the CM files entry for a camera to a @ makes it display in two lines, one stating the limit and the other stating either Speed Limit Ahead or Speed Alert once you get closer. Now this is not quite as informative as Garmin's which states 40mph on line one the same but Average Speed Camera Ahead then Average Camera on the second line i.e. telling you which type of camera it is. This may be a bit of a moot point as the text is so small that you can't read it and ride at the same time!!

I think I'll ask Ash if there is a way to change the # to @ in the files easily.

ChrisL · Occasional Visitor Joined: Mar 22, 2005 Posts: 14

I've had a chat with Ash10 and it sppears that Zumo/PoiLoader works a bit differently then the NUvi/Streetpilots.

The @ and # are used for Overspeed and Approach warnings so all my change did was make the Approach into an Overspeed warning.

Nearest thing we have managed is to set Approach to 0 and set Overspeed at say 30secs and not separate out the Approach/Overspeed warnings. This gives the pretty boxes but of course if you enter inside the zone where an Approach would normally sound you get nothing until you exceed the Overspeed threhold.
Not perfect but I will persevere to find a better solution somehow

Chris

	PocketGPS
	Web