frankiegom

Is that the script you used to patch the application and activate your map? You want to start from the SD card you created to patch your MMI and activate the map, so that the patch application is in there. can you send me the zip with the files you used for the activation, please? Go through PM.

No, not really, but if you already have a working script of some sort on a SD card with all needed files to run it, it's not difficult to modify it to do what you want. Most scripts look like this (lines starting in # are comments so they do not matter at all, except the very first one which must be present): #!/bin/ksh # get SDcard ID sdcard=`ls /mnt|grep sdcard.*t` # get SDcard location SDPath=/mnt/$sdcard # mount SDcard mount -u $SDPath # display scriptStart image on screen $SDPath/utils/showScreen $SDPath/screens/scriptStart.png # delete .done file on SDcard rm -f $SDPath/.done # create .started file in SDcard echo started > $SDPath/.started #list of commands here # display scriptDone image on screen $SDPath/utils/showScreen $SDPath/screens/scriptDone.png # create .done file on SDcard echo done > $SDPath/.done # delete .started image on SDcard rm -f $SDPath/.started So if you already have a working script on a SD card with all neccessary files (especially the /utils and /screens folders) then you only need to edit the script to replace the "#list of commands here" line with the commands you wish to execute. You will have to press a button at the first screen to execute the commands and a second time at the second screen (that tells you the commands are complete). That's it.

Good news! Was it both points you had to correct? Online Traffic activation is not possible from an MMI patched for your new maps because the patch hides your VIN and it is needed for the activation. You must revert to the unpatched MMI application, get the license, then apply the patch again. If your car is more than 3 1/2 years old, it's useless anymore because Activation won't work after the car is 3 1/2 years old To remove the patch, you need to run the following commands (through run.dh script, or the command line if you have the access): mount -uw /mnt/efs-persist/ rm /mnt/efs-persist/MMI3GApplication then reboot (you will have a black screen for a few minutes while the MMI restores the original application) then try to activate Online Traffic Data To put the patch back, make sure you have the patched MMI3GApplication on the sdcard in a folder (patchedFolder for instance), then run those commands: sdcard=`ls /mnt|grep sdcard.*t` SDPath=/mnt/$sdcard mount -u $SDPath mount -uw /mnt/efs-persist/ rm /mnt/efs-persist/MMI3GApplication cp $SDPath/patchedFolder/MMI3GApplication /mnt/efs-persist/MMI3GApplication => make sure to wait until the copy is done before removing the SDcard ot you will brick your MMI (happened to me this summer)! If you're on the command line, it's easy. Using run.sh there should be an image displayed at the end of the script, make sure you wait for it then another reboot and you're done.

To clarify, it's the DHCP options in the 5th screenshot

First, from the first screenshot, it does not look like the WiFi interface is connected to your MMI. You should see an interface with IP 192.168.1.254 in ifconfig on router (not 192.168.1.1 which is the MMI address). Can you paste the output of ifconfig here, please? It will help catch other discrepancies (not that I expect any but... better safe than sorry). Second, you are unlucky because there is a typo on the english WiFi DHCP settings in the doc (the screenshot is OK, as is the french version, though) and the IP to enter in there is not 192.168.1.1 but 192.168.1.254. It is used to tell the MMI that the default GW is the router.This will be corrected when hsd92 is back. First thing to try to ping in the router is itself, 192.168.1.254. If that does not work then the interface is not up and won't be connected to the MMI. Once this works, you can try and ping the MMI at 192.168.1.1. Get this working, fix the DHCP error, and you should be OK. The Y USB cable is best used directly with the modem so that the extra power feeds it. The router does not need that much and will not ne able to output more that 0.5A to the modem anyway. So one cable from charger to router, Y cable to charger and router USB port instead of modem, and modem in female port of Y cable.

I can't really say. The wr703n does not have the mode switch and don't know how it impacts the router. I would try all three modes, carefully checking the configuration against the guide after each change. Can you show a screenshot of the wifi page, please? All of it if possible. And I was one of the first two testers and I did everything manually, so I don't really know how long the script takes. You'll have to wait on hsd92 for that answer.

flemmingkok, This setup is all about _not_ using AMI for the connection (so I can plug my iPod in the car instead ;) )! You did not say how the router was configured and it seems to me you configured it yourself and not according to the tutorial, yet the router configuration is critical to a functional interconnection using WiFi (regular systems do _not_ use a wireless connected client as gateway!). If you have followed the tutorial to the letter, at some point you will have upgraded the router and configured it. This includes setting the LAN network to a subnet different from the MMI's (i.e not 192.168.1.0/24), the suggested subnet being 172.16.1.0/24 with 172.16.1.254 as the router IP, setting the WiFi in client mode to connect to the MMI hotspot, with a static IP of 192.168.1.254 and some specific settings to the corresponding DHCP to make Google Earth work and a few others. IF you have done all this, you should login the router on the LAN interface using IP 172.16.1.254. Once there if you execute the ifconfig command, you should see at least 3 networks, one with IP 172.16.1.254 (the LAN), one with IP 192.162.1.254 (the WiFi, connected to the MMI) and one with your cellular provider's IP address assigned to the E3276. You should then be able to ping the MMI from the router (ping 192.168.1.1). If you still have issues, I would advise you to reset the router to default settings and reconfigure it from scratch following the tutorial. HEre I assume that the MMI configuration went well, and you didn't get the done prompt because of the router... Last, about power: I just gave you an advice. I have a tp-wr703n which is essentially the same hardware as the mr3020, and e3276 modem and it worked fine, until it would start rebooting under heavy load. If you don't suffer from this, fine, but if you notice later on, in the car, instabilities, better power may be your solution...

Hi flemmingkok, from the information you provided it looks like the router is not connected to the MMI. Can you provide some screenshots, in line with the tutorial, showing how your router is configured? Check more specifically that it is properly connected to the MMI and you can ping between the two. Until this is done, no access will be possible I see you have a Huawei E3276 modem, this is power hungry under 4G coverage and you should take care that it gets enough power or you will experience modem reboots, and maybe even router reboots. In my experience, the MR3020 cannot provide enough power stably for the two devices and a Y USB power cable is preferred. François

Joli! :applaudit: François

Non, le E5776_s32 est ce qu'on appelle un MiFi. Il peut remplacer un smartphone en mode hotspot sur lequel se connecterait un routeur connecté au MMI via l'AMI mais ne peut se connecter au MMI en WiFi.

20 pour l'idée intéressante !

Excellent! C'était quoi, le type de flux qui coinçaient ?

Merci Fred, tu as eu plus de chance que moi (pas de réponse malgré une relance hier encore)! J'imagine qu'ils ont trouvé comment injecter un VIN valide le temps de l'activation... Dommage qu'ils ne veuillent pas travailler à distance. Pour une fois que le prix était raisonnable (ils te l'ont confirmé, d'ailleurs?). F.

Peux tu détailler la totalité des modifications apportées, au routeur et au MMI, s'il te plaît?

Vérifie que le routeur est bien connecté au hot-spot de ton MMI. Le premier ping KO c'est pas bon du tout, ça veut dire qu'il y a un loup au niveau de la configuration du routeur. C'est curieux que c1 marche d'un PC par contre. Si le MMI ne peut pas pinger le routeur comment peut-il router les paquets du PC?

C'est vrai, j'avais oublié. Donc n'importe quoi sauf ces 3 plages d'adresses. Merci pour la clarification... F.

Heu... je suis à la rue, là! Pourquoi n'est elle pas compatible avec l'AMI? C'est une plage qui n'est pas utilisée dans le MMI et donc ne devrait pas causer de problème particulier il me semble. Ceci dit, je suis d'accord sur le fait qu'il est plus simple, et sûr, de suivre un tuto à la lettre quand il existe et est clair comme celui de Thierry. Ca éviterait bien des soucis à beaucoup et nous faciliterait la tâche...

On le sait bien, c'est pour ça qu'on est obligé d'utiliser un router à avec firmware "flexible"...

192.168.2.1 étant l'IP du router bien sûr

Plus précisément il faut éviter d'utiliser le même sous réseau que pour le MMI (192.168.1.0) il suffit par exemple de changer le 1 en 2 (192.168.2.0) sur le router et le nameserver dans le script en 192.168.2.1

Même si c'est possible (théoriquement du moins) j'ai trop besoin de mon téléphone pour prendre le risque de le pourrir avec ce genre de configuration... Mais aussi,je préfère utiliser une SIM dédiée. F.

Voila! Ceux qui savent pourront donc maintenant répondre à ta question (désolé, je ne sais pas de tête). Il y a de fortes chances, ceci dit, que la réponse à ta question soit dans le sujet que je t'ai indiqué car c'est une question qui revient régulièrement. Commence par identifier la version que tu veux installer, et recherche sur le forum si elle est cumulative ou non. Si oui, tu peux y aller directement. Bonne chance!

Pas sûr, il pourrait tout simplement être en vacances avec plus important à faire que suivre le forum... Ceci dit, je peux aussi comprendre qu'il ait pu craquer! ;) Ca va sans dire, mais tellement mieux en le disant... Le lien que j'ai fourni par anticipation devrait avoir l'essentiel des réponses à tes interrogations. L'as-tu seulement consulté? ;)

C'est quoi, précisément, la question? http://forums.audipassion.com/topic/166261-zone-de-telechargement-des-firmwares-mmi-2g-3g-3gp-rmc-mib/

Copies des différents écrans modifiés du menu vert STP. Et tu as bien activé le fair mode au moins? Et une clarification: le test avec le PC, c'est bien en le connectant avec un câble sur le port ethernet du routeur, comme tu le fais pour la connexion avec l'AMI?