Mercedes MY17 Garmin Map Pilot - Alerts in Chinese?

[Kremmen]

If the filename contains a number then POIloader uses that and ignores the file contents. That's why my Converter switches the filenames from 50 to fifty.

Then in the GPX 'proximity' tag sits the yards from the camera you want your warning.

Having run the Converter, (full instructions in the download package), it just needs a quick find and replace:

Find say "#50" or "@50" and replace with "" (nothing). That will be using Notepad on the GPX file.

If that works I can build that into the Converter.
_________________
DashCam:
Viofo A119 V3

[npr]

[M8TJT]

I think that you will find that you talking to the undisputed Garmin POI black belt seventh dan here. And if K says that't what happens, then I would suspect that'hat's what happens. He has spent absolutely hours on his project and I'm fairly certain that he will be right. But quite prepared to be proved wrong.
So, if you read carefully what he said, he was not advocating putting @speed anywhere, but blanking the field as you have done, but he will adapt his program to accommodate this for you if it works OK.
And I'm certain that he will help improve on distance of warning if you heed what he says, test it and then report back.

[Kremmen]

What I seem to recall during the CSV Converter investigation was that having a numeric in the filename caused some override issues. That was solved by changing 50 to fifty in the filename. The one filename constant I didn't change was 'redlight', that word in the filename also overrides some internal content, but, in the grand scheme of things didn't need changing as RedLight cameras aren't speed cameras per se.

Back to the plot.......

The one constant theme here affecting Merc systems seems to be what is in column 3 of the CSV file. That column is what is displayed in the popup banner. On Garmin PND's the @50 is used for Garmin's approach warning decision and overspeed alerts. Change that to #50 and all you get is one 'mandatory to Garmin' approach alert and no further overspeed alerts.

The older Merc system was quite happy as long as there were no lower case characters in column 3.

From what your saying it now doesn't like the #50 or @50, so, if you just have "GAT" in column 3 then POILoader has nowhere else to get it's speed info other than the filename.

If you use the consolidated by type file and change column 3 to just GAT then I have no idea what that would do.

I can change the CSV Converter to cater for the latest Merc/Garmin requirements hut I need info about what actually works.
_________________
DashCam:
Viofo A119 V3

[M8TJT]

Hi K.
This is what the link above says about proximity alerts.

[Kremmen]

Ta

That quote looks to be how I understand it re the filename number x 36 seconds.

I'm not 100% convinced that the GPX proximity distance overrides the filename speed, unless they've changed it recently since Converter v1 many moons ago.
_________________
DashCam:
Viofo A119 V3

[M8TJT]

I vaguely remember when I have been talking to you that if you put a number in the filename, Garmin takes that and gives the 36 second proximity warning rather than anything in the GPX, and to overcome that problem, you changed the number to text so that you could set your own proximity time into the .CSV and thus into the GPX and GPI. But of course, my memory could be letting me down.

[Kremmen]

That memory problem is what I get with a 36 second warning. By the time I get to the camera I've forgotten all about it, and probably what day it is.
_________________
DashCam:
Viofo A119 V3

[Nemesis1]

Could have saved half this thread by reading mine.....

[Nemesis1]

What is interesting though is that in your set up you use "GAT" etc.

This is not a normal Garmin trigger word. It is interesting that it still seems to work.


And M8TJT.
I never got custom wav files to play ever, I don't believe this is possible in the Merc.
:-/

I haven't had a play in a while as I was consigned to it being as good as it was ever going to be. I will have another look tomorrow and see how we get on.

I did though get an email from Garmin stating that they had warned Daimler they were not giving the nav system sufficient computing power to run at optimal standards. Make if that what you will.

And I was (I think) getting close to cracking the in built .gpi file, the one that has all the dealers in it. I hoped to maybe add camera locations and an icon to that, as it never fails to display on the map.

[Kremmen]

Thanks N
_________________
DashCam:
Viofo A119 V3

[Schouten]

Do you still need to delete the 3 (6 on v 8 maps) font files to stop Chinese characters? Or does the modification of the column 3 data stop it happening?

I haven't had chance to work through the various options yet but was just curious.

Does anyone know the significance of the "bongs" sometimes I get one on approach, sometimes a double one but at a higher frequency and sometimes none at all. (This is when navigating on a route.) Using the converted standard camera file with font files deleted.

Thanks to all those putting the effort in for us to get a reliable system. Appreciated.

Terry

[Kremmen]

[stephenbeck]

Has anyone managed to solve the Chinese issue yet?

[M8TJT]

I think so. It's in the thread somewhere. Shame the thread has wandered off onto speed cameras.

There's a post by Schouten on page 4 that might be of interest.

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!