Mercedes MY17 Garmin Map Pilot - Alerts in Chinese?

M8TJT · Posted: Tue May 09, 2017 9:25 am Post subject:

Seems like there is a certain amount of wheel re-inventing going on here H Very Happy

npr · Occasional Visitor Joined: Mar 07, 2006 Posts: 16

@pbridgeman,

Software version: 16/49.0 46.15

Map: 2017 (v8.0) Europe

I tend to agree that the directional data is not understood by this system. I'll removing column 3 entirely from all files in future, that will make things simpler Smile

One issue I've discovered with my method, alerts always displays the camera as being 0.2 miles away when they are clearly not. This is presumably due to specifying all speeds as 20 MPH in the file name (eg "*_20"). eg 0.2Miles == 35sec at 20MPH. I've tried to solve this by installing the complete database but failed miserably to get icons to display with that. Confused

pbridgeman · Occasional Visitor Joined: Mar 04, 2013 Posts: 22

Hi npr,

You should be able to increase the distance by using the manual method of compiling the files in POILoader and ticking distance rather than speed for the _20 alert files.

Whats the software version before the 16/49 bit. I suspect its v8.1 which will display icons without shifting the alert positions.

Just as a matter of interest which merc do you have. My garmin is actually in my wifes car, a 2017 GLA but it wont let me update to v8.1 - crazy!

Kremmen · Posted: Tue May 09, 2017 2:40 pm Post subject:

Reading the 2 main problems in this thread they sound like the ones I've already solved in the CSV Converter.

Regarding the warning text change see my earlier pictures.

Regarding 'proximity' distances, if you use the Converter you can set your own alert distances.

As you've found Garmin use 36 seconds when you use POIloader on CSV files.

If you dig out the posts between Nemesis1 and myself from last year they may well solve your issues and requirements.

Definately worth a shot.
_________________
DashCam:
Viofo A119 V3

pbridgeman · Occasional Visitor Joined: Mar 04, 2013 Posts: 22

Hi Kremmen

Yes I read your very informative info. from last year but I didn't notice that it solved the particular problem I was having which is with v6.0 map and v6.1 software that the alert banner read in chinese and no icons were displaying on the map.

Using the Poi shift method the icons now display and deleting the specific font files gets rid of the Chinese. The trouble is, each new version seems to change the goal posts.

Kremmen · Posted: Tue May 09, 2017 3:44 pm Post subject:

The 2 things that stuck out were

1) The text changes posted

2) The proximity of the alerts

Both catered for in the Converter.

What Nemesis found was that the warning banner text had to be upper case alpha characters only or the system threw a wobbly.

In my text converter routine you can change it to "GAT" or "MOB" if that's all you want.
_________________
DashCam:
Viofo A119 V3

npr · Occasional Visitor Joined: Mar 07, 2006 Posts: 16

@ pbridgeman,

From the Merc Download Manager, no update available.

Software version: V8.0, SW 46.15

Car: March 2017 B Class.

@Kremmen,

Yes I did give the CSV Converter a go a couple of weeks ago and I'm sorry to say I couldn't produce a working system.

M8TJT · Posted: Tue May 09, 2017 4:21 pm Post subject:

Then I might suggest that you possibly have a chat with Kremmen to see if you can work out how to possibly adapt his programme to accommodate your particular flavour of Merc system, as he has adapted it successfully for another Merc user. And it makes converting the PGPSW files a breze for bog std. Garmins, and if you also use the direction converter before tyhe CSV converter, you get announcements saying in which direction the camera traps (If your system will allow for user audible alerts.
The business about the Merc system taking camera descriptions in ALL CAPS with the other stuff that screws it up has already been solved.
No point in re-inventing the wheel when all but the tyre tread has already been invented.
At which, I rest my case and will not clutter up your thread any more.

Kremmen · Posted: Tue May 09, 2017 4:37 pm Post subject:

POIloader does one simple task, it converts CSV or GPX files into a .GPI file that is standard across Garmins.

What I like to see is one sample CSV line that has been manually tweaked that has been posted as partially working.
_________________
DashCam:
Viofo A119 V3

Schouten · Posted: Wed May 10, 2017 11:25 am Post subject:

I'm with Kremmen here. If someone could post a .csv line that is known to work that would be very useful. I've tried a couple of methods using the macros and manual conversions but as yet can't get anything to work. That's not say they won't and is more likely age related (me!) So some examples would help.

I'm on the V8 software too.

As I mentioned before I use a MAC with Open Office Calc for spreadsheets so I think the Macro's and F&R criteria are slightly different from Excel.

However, thanks to all those that are trying to get this to work!

Terry

Nemesis1 · Regular Visitor Joined: Aug 24, 2005 Posts: 170

I can't get my MB download manager to offer me V8. I'm stuck on version 6.
:-/

npr · Occasional Visitor Joined: Mar 07, 2006 Posts: 16

M8TJT · Posted: Wed May 10, 2017 11:16 pm Post subject:

If you include a ???.WAV file (same filename as the ???.csv files) in the mix, does the device play the file? You will need sox.exe in the same folder as POILoader.
What is the purpose of the two .csv files as in SPEC.csv and SPEC_20.csv?

Kremmen · Posted: Thu May 11, 2017 5:52 am Post subject:

That is exactly the same format that is possible with the CSV Converter, if you use the text change facility before using POILoader.

However:

-2.94512 52.93073 "GAT" ?

I would expect to see

-2.94512, 52.93073, "GAT"

On the older Merc/Garmin system all that had to happen was the warning banner text changed to upper case, which is what is happening here. Ie GAT

So, is the Merc Garmin system unable to read in a .GPI file, still to Topografix schema standards created from a GPX file ?

If so then you will have to live with having the warnings 36 seconds before the camera which when I tried it was far too soon. Bespoke systems seem to aim for half that.

Moving on .....

Here is a line from one of the downloaded files:

-1.94351,53.07334,"SE-GATSO:46@50"

Once processed into GPX here is the result (with the text change applied):

I've also had to remove some HTML tags as the forum doesn't allow them.

lon="-1.94351" lat="53.07334" GAT#50

So could it be the #50 that it doesn't like ?

If someone has the time to remove that bit and report back I can sort that.
_________________
DashCam:
Viofo A119 V3

npr · Occasional Visitor Joined: Mar 07, 2006 Posts: 16

	PocketGPS
	Web