Am I right in thinking that this is about the region code in the eeprom? Does the uploaded EU software change the region code in the eeprom or does it have to be changed manually in the eeprom?

 

As far as I can tell, the only data the MMI3GP software writes to the EEPROM is the release name (e.g., string "HN+R_EU_AU_K0942"), otherwise, other data in the EEPROM is read-only. I am also curious about where some of this persistent data (like GEM /config screen "language" and /nav/databaseupdate screen "internal region code" values) is stored across system power cycles/restarts. Inspection of the GEM screen definition files shows that the /config values come from "keyValue" calls, which I believe show only read-only data, while the /nav/databaseupdate information comes from "BIOSCtrl" calls. Maybe that's a hint ?
I'm still looking for a way to read EEPROM data from a QNX shell script, otherwise we need a tools like VCP and OBDeleven to access it. --g

 

Yes, with eeprom it probably reads only what is written and I could have made a mistake before uploading the software. This error is due to the fact that I did not select in nav/engeneering Nav/Language imissed on pl_PL immediately and en_US was left there. I try to upload the software again, but I will probably have to wipe the partition again?

 

As far as I can tell, the only data the MMI3GP software writes to the EEPROM is the release name (e.g., string "HN+R_EU_AU_K0942"), otherwise, other data in the EEPROM is read-only. I am also curious about where some of this persistent data (like GEM /config screen "language" and /nav/databaseupdate screen "internal region code" values) is stored across system power cycles/restarts. Inspection of the GEM screen definition files shows that the /config values come from "keyValue" calls, which I believe show only read-only data, while the /nav/databaseupdate information comes from "BIOSCtrl" calls. Maybe that's a hint ?
I'm still looking for a way to read EEPROM data from a QNX shell script, otherwise we need a tools like VCP and OBDeleven to access it. --g

I think this data is stored and run from flash. As for VCP, VCDS, I have it. I don't have OBDeleven.

 

I marked EU and pl_PL in the green menu wherever possible and re-uploaded the software and maps. It didn't help, the problem remained. I noticed that in /config:
Language HMI system: pl_PL is fine a
language Navi TTS: is en_US and cannot be changed.
In /nav/engineering - NavLanguage there is also en_US DB available 1 by
pl_PL DB available 0 . If I change it to pl_PL it doesn't save.
Photo below:

 

This is a curious problem. We know the NAR main unit and related software supports languages en_US, fr_CA, and es_US starting at EEPROM address 0x0439:

while EUR/RoW main units are expected to support languages en_GB, de_DE, fr_FR, es_ES, it_IT, pt_PT, nl_NL, ru_RU, pl_PL, cs_CZ, tr_TR, and sv_SE:

(though minimally, in your case, you can likely get away with en_GB, de_DE, and pl_PL). Inspection of the EEPROM data above shows that en_US, for example, is encoded more than once (as is en_GB), which suggests to me that the default and active languages might be coded prior to the longer list of support languages starting at address 0x044d (and ending with the first NULL). But which is which in these two examples ? We would need to inspect the EEPROM of a main unit that is configured properly for a language other than en_US or en_GB to better understand this configuration problem. --g

 

You suggest that the problem lies in the eeprom memory ? I'm thinking about it too .In addition to the languages, there is also a region code in eeprom. At the moment I don't remember what address, but after CP at the bottom it's probably 1 bayt?

 

@dativus -- It is possible, yes, but not yet known for certain. For example. we know that the Green Engineering Menu (and a VAG scan of Address 5F) will report certain information that is not stored, that I have found, in any persistent file stored in flash memory, including the software train/zug name (for example, HN+R_US_AU_P0690):

and various VAG part number/configuration information:

I think QNX process MMI3GApplication reads information from the EEPROM to determine how to set up the run-time environment, for example, Unix strings returns these hints from the MMI3GApplication binary file:

$ strings MMI3GApplication
...
PPC:received valid EEPROM dataset visible languages
PPC:EEPROM dataset visible languages was invalid
PPC:requesting HBRegioncode to select correct default dataset for visible languages
Got regioncode %d
en_USfr_CAes_US
zh_CNen_CNko_KRen_KR
ja_JPen_JP
de_DEen_GBfr_FRes_ESit_ITpt_PTnl_NLru_RU
...
CMUSparePartNumber.cpp
Return PartNumber to PPC :'%s'
MU Spare Part Number in EEPROM %s
Characters in HWKey buffer %c
MU HW Number in EEPROM %s
...

It's possible (and likely) that the Java process that implements the UI and the Green Engineering Menu can read/write the EEPROM, too, but I don't know yet if it does this directly or through some other service or process. --g

 

What would you advise to do? I will also connect VCP and read the eeprom one more. I have another "set" of languages in a different order and not all that work correctly in MMI3G+ 8R1035670E in the car. Not the officially published ones document . If I have time today, I'll try it because I don't have time during the week.

 

I have loaded this other "set" of languages from PL into eeprom, but unfortunately nothing changes? I came to the conclusion that the language and lector do not work only with eeprom. Because I also have an old MMI3G Basic, the eeprom does not even include the PL language, but the MMI menu contains the PL language and lector.

foto with eeprom MMI 3G+
previous and here I see the difference from the original entry :

foto with eeprom MMI 3G Basic :

I'll be here this weekend...

 

I did ! Now it is correctly in the green menu and I still have to test it in the car. I didn't even know it was so simple, I'm laughing at it now . Fotos :

I had good languages in eeprom, either with the original language entry for the EU (the famous document) or with my "set" of languages. It's just not the eeprom's fault.

Thanks for your willingness to help me, but our assumptions were completely different. I wouldn't even call it a mistake.

It would be nice if the module in this MMI 3G+ NAR (USA) worked 3G because it works on 2G...

My second MMI UE 8R1035670E in the car works in 3G .

 

...
It would be nice if the module in this MMI 3G+ NAR (USA) worked 3G because it works on 2G...
...

So the solution to the UI language is to set first in the MMI Setup ?
Regarding the data modem, what modem module is fitted to the main unit ? Early NAR main units were fitted with a data modem for T-Mobile 3G frequencies, while later main units got updated modems for AT&T 3G frequencies. --g

 

My MMI3G+ USA version is 8R1035746C and I don't know if 3G will work on it?
I also tested it in the car and the lector works properly!

 

My MMI3G+ USA version is 8R1035746C and I don't know if 3G will work on it?
...

I'm taking another look at this for some researching I'm compiling, and I think we can tell which 3G data modem is fitted from the first four digits of the IMEI on the manufacturing label. For NAR MU9498 main units, IMEI 3521x is the earlier 3G modem for T-Mobile and IMEI 3557x is the later AH6-US for AT&T 3G frequencies. The production change over looks to be starting with 8R1035746D (which is the version fitted to our NAR '14 A4Q). --g

 

@dativus -- NAR main unit part number 8R1035746C was the first to be fitted with the Cinterion AH6-US 3G data modem (for the AT&T network). I would expect this to work in PL. --g

 

So 3G will work on this unit? I've already tried the T-Mobile and Play sims and they only work with 2G? How to make it work with 3G?

 

@dativus -- The few logs I have from EU VAG cars with MMI3GP all suggest that they all have the AH6 data modem fitted. I do not know, however, if the modem module (see this post: https://www.a5oc.com/threads/mmi-3g-3gp-mobile-data-connectivity-options-post-3g-shutdown.177572/ ) in EU/RoW markets use a region-specific variant on the AH6 device. Though your experience is consistent with what happened here in the U.S. 8 or so years ago when T-Mobile reprovisioned their data network (that is, people only got 2G with a T-Mobile SIM), which prompted VAG to switch to AT&T for their mobile data service. --g

 

I'm in week I don't have time, so the MMI 8R1035746C sticker says IMEI: 3521x, which is probably only 2G, but I also have the GSM module from another unit, IMEI number: 3557x. I wonder if the conversion would work - plug&play?
Photo MMI (the unit has not been opened )IMEI nr :

and photo gsm module :

 

I don't know -- that's a good question. A guy in the US tried to do this swap back in 2018, see this Audizine thread: Need factory Audi tech help - script for 3G+ MMI modem upgrade to UTMS on 2013 B8.5
So, not exactly plug-and-play. --g

 

I'm reading this topic. I have this GSM module from the 8R1035746E unit but I'm not sure, maybe a newer one writes UMTS on it? Photo:

Maybe I'll try to insert this one and see if it works hmm... and re-upload the latest software K0942_6 ( HN+US_AU3G_K0942_6(A4-A5-Q5-Q7 )
and then return to the EU version?

 

After uploading K0942_6, the sim appeared on the screen but I do not have access to the green menu and there are no letters or numbers. I will soon activate the green menu via vcds and change the region, etc. I don't think this GSM module will work immediately without drivers if there are no drivers in the software, but maybe...

 

I activated the green menu, changed what was needed and I think I need to upload NAR maps later because it's a different region...

Do you have a link to the map in addition to this one?
15.12 GB folder on MEGA
I didn't change anything in the eeprom because it probably doesn't affect anything.

 

The Network Access Device (NAD) is enabled on the GEM /diagnose/settings/tel_settings screen by selecting "NAD activation":

A restart may be required (I don't recall exactly), but the /usb screen will report the device with NAD activation set:

For NAR main units running K0942 that were fitted with the Cinterion AH6-US module, we see this entry in metainfo2.txt:

DeviceDescription="AH6 NAR"^M
^M 
[AH6\Main\0\default\Application]^M
FileName = "ah6a-us_rev03-001.usf"^M
...
Version = "300100"^M
AppName = "AH6 NAR"^M

and for EU main units, we find this:

DeviceDescription="AH6 EU"^M
^M
[AH6\Main\0\default\Application]^M
FileName = "ah6a-w_rev03-001_arev01-000-01.usf"^M
...
Version = "300101"^M
AppName = "AH6 EU"^M

I think the software "device driver" is part of the PSSBSSService process; see, for example shared library file /mnt/efs-system/pss/pssbss/usr/lib/libphoneservice.so -- Harman-Becker seems to have support for only these two data modems:

PHONE_MODEL_TELIT_GE864
PHONE_MODEL_CINTERION_AH6

I don't know whether your AH6A-US device will operate on European 3G networks, though if you can find a low cost UMTS AH6A-W module, that may be a path forward. --g

 

Didn’t US and EU 3G work on different frequencies? An external modem would be a better option as 3G has a limited lifespan.

 

I loaded NAR maps last night. I set it in the green menu as you say ( fotos ) and the modem appears for a moment and then disappears? Do I need to set anything else?

In /version/versiontelephony NAD versions
I have an error :

 

This is what it looks like in my car, the EU unit 8R1035670E. There is a 3G signal

I'm fiddling around in the green menu, maybe something needs to be switched on or off. Maybe later I will re-download the NAR software again.

 

Pro tip: press and hold [TEL]+[MEDIA] buttons until the four control console LEDs flash takes a PNG screen shot of the MMI3G display with time-stamp file name. Useful for documenting your work (and easier to read than smartphone pictures) IMO.

The main unit installed in the car came with the later AH6A-US modem, so it's already configured properly. But as @JohnS4 notes above, will the NAR modem connect properly to European 3G networks -- what does TEL > Settings > Data connection > Online status overview report:

(this was when we still had access to AT&T 3G in the U.S. and an AT&T SIM was inserted into the main unit). --g