frankiegom

Where to begin... - dd-wrt: we do not use dd-wrt, I will assume this is a lapsus calami and you meant ROOter (based on openWrt). In any case, even if that does not explain or solve your problems, if you used the version linked in the doc, then you really should do what I've been advising through the thread for at least 4 months and upgrade from MW (MultiWeb) to the latest version GO (Golden Orb) from http://ofmodemsandmen.com/downloads.html - There is a way to gain telnet access to the MMI if you really need to, but you could really mess your MMI if you don't know what you're doing, and since you have issues with your WiFi you'd have to use a USB/Ethernet adapter and the AMI/USB Adapter - your second green menu screenshot is indeed troubling. The MMI should have the 192.168.1.1 IP address by default. It is hardcoded and I have a hard time understand how this came to pass... That in itself is your worst problem, and I cannot really help you there. - The MMI hotspot is only that, a hostpot with no client capabilities, so the only way to get a WiFi connection to the router is to connect the router in Client mode. And because we want the default route to be assigned properly to the router (192.168.1.254), the router is configured to serve IP addresses through DHCP on the WiFi interface (even though it is connected in client mode) and there is a script running in the background on the MMI to kill its DHCP server and insure there is only one on the network. These two points are paramount to the patch! - Of course if the MMI does not have an IP address there is no way you'll be able to ping it. :( - your routing table is not fine There is no default gateway defined. - When all goes well, if I recall correctly the MMI has two IP addresses: 192.168.1.1, static, and a second one assigned by the router and corresponding to the uap0 alias you mentioned (something like 192.168.1.20, NOT 192.168.1.110 or 192.168.1.109...) Can you retrace exactly what you have been doing? How could your MMI lose it's IP Address? Before you try and go the telnet route, you can like I did initially work from a simple script like the one to change DNS that is available from differente sources to issue commands from an SDcard, redirecting command output to a file then checking the results. Here is an example of such a script with some commands you can uncomment and run to check system status... Good luck François #!/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 # mount EFS fie system mount -uw /mnt/efs-system # my commands netstat -r > $SDPath/.result route -f ls -l /mnt/efs-system/etc >> $SDPath/.result ping -c 5 8.8.8.8 >> $SDPath/.result ifconfig >> $SDPath/.result # 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

Et oui HN+ vs HN+R Je ne sais pas à quoi ça tient mais j'attends !

Comme ça m'a permis de corriger quelques fôtes on dira que c'est pour la bonne coze! ;)

C'est bon, j'ai corrigé les fautes!

Est-ce que la version HN+R pour MMI 3GP A6 est disponible quelque part? Pour l'Audi connect WiFi j'en profiterai pour regarder de plus près. Il y a peut être un nettoyage à faire pour ceux comme titou43 qui n'ont pas fait désinstallé avant upgrade pour que le script de désinstallation fonctionne correctement... Et sinon je devrais pouvoir faire un script de diagnostic / réactivation vu que le problème tient à deux fichiers écrasés lors de l'upgrade (quand le Firewall bloque le Traffic entrant par le Wi-Fi évidemment ça marche beaucoup moins bien!). Deux fichiers à recopier ce n'est pas la mer à boire heureusement...

Sorry but I disagree. If you haven't organize anything to insure enough power is available for the router and the modem you cannot draw any conclusion from the limited testing you have performed. What you will get is not much different from what you have now: a system that sometimes work and sometimes doesn't. For all we know you have just enough power to run the modem sometimes, depending on coverage and depending on conditions... This is typical. We dont even how you run things in your car. How good your poWer is or event which router you havé chosen... Get proper power, test again and then if it still fails we will see what can be done. That, and I'm in no position to provide what you need at the moment. I need time to think. I need my laptop. And I have neither...

If you have not been careful with power budget you _will_ experience problems with the router when you plug in a power hungry 4G modem! Not all modems are equal in this respect but I would look there first, because if this is your problem, then setting the gateway manually in the MMI will not solve it

I"m sorry but I can only do so much these days. I'm travelling without my car, so I cannot fully compare what you see to what I have and I don't quite remember too. What if you connect your laptop to the MMI hotspot? What are your IP parameters (IP address, mask and gateway) and your default route? Show "ifconfig" output for your WiFi interface as well as "netstat -nr" (or "route" maybe, I don't usually use OSX) IF you get an IP of the form 192.168.1.1xy then you were served by the MMI, if from the router, you should get an IP more like 192.168.1.2x... I don't think the package is the problem if you got it from the link in this frame All I can say for sure is: If everything's installed and working properly, the router should be assigning IPs to all clients on the network and the gateway should be the router's WiFi interface the last green menu screenshot only shows IPs allocated by the MMI, not the router, and previous screenshots showed that there was no default gateway assigned to the MMI You could set the default gateway in the MMI manually and it would probably fix you problem for the MMI itself, but clients connected to the MMI hotspot would not work. Last thing: installing FW while the patch is installed is 100% to break the patch! You would need to restore at least the pf.conf and nws.cfg from the patch to your MMI.

Ok merci

OK, j'avais pas capté le coup de l'activation de carte officielle, donc j'ai une question... Si un firmware production (P) avec carte officielle activée et que je fais faire la mise à jour en concession, je reste en P ou je passe en K (je pensais qu'on passait en K)? Dans le cas ou c'est K (ah ah!), ça veut dire que la concession procède à une ré-activation de la cartographie dans la foulée?

Check page 15 of the doc (french part), this is what you need to verify. Pay attention to the address used forthe gateway (192.168.1.254) as the english version has an error (192.168.1.1 is the MMI IP and is incorrect)! What you see in the grenn menu is an error that occurs, I believe when you execute the command too often and too fast. It should work again if you wait a little, or worst case if you reboot the MMI. The routing table is displayed in your pictures: img_6325.jpg & img_6326.jpg The first line under "routing table" should start with 0.0.0.0 (meaning default gateway) and should list the router's IP over WiFi (192.168.1.254).If it's not there it means the MMI did not get a default gateway from the router (through the DHCP options on page 15). One other possibility for failure is if one of the files was not patched correctly when you installed it. Can you share the log.txt file from the SDcard (it should be in a directory with the date of installation as name)?

Nor in front of the PC now, will check back. Need to understand when it does not work. Can you try to do a screenshot of green menu routing table and router Wi-Fi association in both cases (ok and nok)?

No default gateway. Did you configure the DHCP server properly on the WiFi interface in the router? You should have options for DNS and gateway in there

You are going to provide a little more detail than that if yo uwant some help here, but first I'd say if the MMI tells you it's not connected then it probably isn't. some things you can try: - if you plug a laptop in the router LAN interface (laptop WiFi off), does it get Internet? - from same laptop can you ping IP 192.168.1.1 ? - can you post screenshots of the relevant green menu screens? One error that is frequently made is forgetting to pair the router with the MMI WiFi. Please go back to your router status screen and confirm WiFi is connected to your MMI hotspot. Provide screenshots of the relevant router screens as well.

Ben oui, des goûts et des couleurs... ;)

J'ai moi aussi reprogrammé le start & stop, mais pour qu'il se souvienne de l'état dans lequel il est quand je coupe le contact, comme ça je le désactive ou active au besoin pour aussi longtemps que je le juge utile en apppuyant une seule fois sur le bouton. C'est pour moi la solution la plus flexible et je ne comprends pas que ce ne soit pas l'option par défaut!

De ce que je comprend, encore une fois, le start & stop comprend sa propre batterie qui se recharge selon les conditions de conduite mais n'a pas une forte capacité.

J'ai une boite multitronic depuis 2 ans et très franchement je ne la mets jamais au point mort. De ce que j'ai compris (et on me corrigera si je me trompe), ces boites, tout comme les stronic, n'on pas un visco-coupleur comme les boites auto classiques, mais un embrayage simple (multi) ou double (s) à bain d'huile conçu pour supporter l'arrêt en mode D avec un minimum de dissipation d'énergie. Si en plus tu as comme moi le start & stop, la question ne se pose même pas, sauf si tu veux retirer le pied du frein à l'arrêt. Dans ce cas, je passe plutôt en mode P qui a l'avantage de forcer le stop (quand le moteur a redémarré). Le point mort est surtout utile quand il faut pousser ou remorquer la voiture, il me semble.

Non! On la déjà dit, si ta carte est défectueuse tu ne feras que transferer le problème. Il faut que tu retelecharges le firmware d'une source fiable et le transfère vers une nouvelle carte!

MMI 3GP K0900, Note 4 MM 6.0.1, bluetooth marche parfaitement Je ne sais pas trop quoi dire...

Modèle ? Version de soft? L'as tu essayé dans une autre Audi? As tu essayé un autre tel dans ta voiture ?

Pas vraiment non. Ça voudrait dire que ta carte est OK...

miazza's message was a response to me, I don't think it was intended for you...

Two advantages: it will save them some hassle if they don't read through the all thread (this happens quite often in most forums), and one less manipulation of their system is one less chance to wrecck havoc on it!

It might be a good idea to provide a modified version of the run.sh script that does not run the installFairMode.sh script (just comment out lines 215 to 222) for those that want to run RNS850 without SIM. I'd rather not do it as it may be confusing to Audi owner in the forum, it's probably best to reference it in a Tuareg forum (possibly via a cross link)...