maxm
New Member
Posts: 1
|
Post by maxm on Dec 10, 2022 3:00:56 GMT
Is it possible to make the button that turns off the mmi screen actually make the screen go down on 2020 audi a3 s-line? The same button on an s3 makes the screen go down but my button only turns the screen off. Is there a way you can code this using obdeleven
|
|
|
Post by rick92f on Feb 12, 2023 14:18:01 GMT
2019 S3 with the same question...I would love to be able to put away the screen like older models.
|
|
|
Post by sgoring03 on Feb 12, 2023 17:26:22 GMT
Hello,
It is my understanding that after 2019 (at some point) the USA stated that the screen being down meant that the reverse camera would not activate within a given time and so the screen now stays up but can be switched off.
Given this I believe is for the US market only, maybe coding can fix this but there are many articles and no real solution although I remember I thread (sorry not sure where) where someone was trying to use a spare button on the switch panel,
If someone manages to find a solution I will be one of many looking for it.
|
|
|
Post by dv52 (Australia) on Feb 12, 2023 22:14:14 GMT
sgoring03 : Far be it for someone that lives in the "very, very, very deep south" to make comment on the practices in America - but thanks for the information (I didn't know this - makes sense!). However and accepting your reasoning - why do you believe that these NAR models still have a motor operated screen?
Wouldn't it be more logical to assume that since there is a legal reason for NOT retracting the screen, there is no point including the physical retraction mechanism into the device?
And of course, this also lowers the cost of manufacture for the shareholder (meaning more-bucks for Audi)!!
So, maybe your hope that "someone manages to find a solution" is the delicious futility of an impossible task!!
Don
|
|
|
Post by sgoring03 on Feb 12, 2023 23:28:05 GMT
|
|
|
Post by rick92f on Feb 13, 2023 5:39:14 GMT
The hardware is there. When the car is off the screen is put away. As soon as the car is started, the screen pops up and will not retract until the ignition is off. The screen button just turns off the picture. Is there anything I can do on my end to help figure this out?
|
|
|
Post by sgoring03 on Feb 13, 2023 11:42:11 GMT
|
|
|
Post by sgoring03 on Feb 13, 2023 14:20:40 GMT
sgoring03 : Far be it for someone that lives in the "very, very, very deep south" to make comment on the practices in America - but thanks for the information (I didn't know this - makes sense!). However and accepting your reasoning - why do you believe that these NAR models still have a motor operated screen?
Wouldn't it be more logical to assume that since there is a legal reason for NOT retracting the screen, there is no point including the physical retraction mechanism into the device?
And of course, this also lowers the cost of manufacture for the shareholder (meaning more-bucks for Audi)!!
So, maybe your hope that "someone manages to find a solution" is the delicious futility of an impossible task!!
Don
The motorised screen is there it comes up and goes down with ignition on and off.
|
|
|
Post by dv52 (Australia) on Feb 13, 2023 22:59:55 GMT
hmm........ OK, I had understood a different dynamic - something similar to what happens on some Audis down here where the MMI screen does not open/close at all (not even when the ignition is turned-ON/OFF). Clearly "Yankee" cars are different (ain't no surprise about this)!!! So, I've had a look at the wiring diagram for an Audi A3 8V (I only have RoW model information - alas we don't get many NAR models down here). The electrical arrangement for the open/close display mechanism is very simple (see the diagram below) As you can see, the fundamental mechanism for the switch (EX22) is to earth pin #10 on the "Multimedia system operating unit" (E380). So- while this is the electrical signal that tells E380 that the driver has physically pressed the switch, what actually happens in response is likely determined by the 2 x wires connected to the Infotainment CAN bus - I think The controlling unit for the "what happens" decision is very probably the module shown as J794 in my diagram - again, I think.
J794 is the MMI which lives in the glove-box and which OBD11 reports as the hex5F module. I've had a look through the long-code string on the hex5F module and Byte 20 contains the software switches for the display. On RoW models, Bit 0 is selected - not sure about NAR models? I've also looked through the adaptation channel database on the hex5F module and the only mention of stuff relating to America is a bunch of channels with the name "nhtsa_properties". I assume "nhtsa" means National Highway Traffic Safety Administration - which I understand is an agency of the US Federal government. Most of the "nhtsa" channels relate to car-play/Android functions (so not appropriate to this matter) - but it might be worth checking on a NAR MMI, nevertheless (maybe). Finally, I suspect that the most fruitful investigation (IMO of course) might be the so-called hidden GREEN Engineering screen. Access to this this screen depends on the version of MMI that is installed in your NAR model car - likely you will find instructions on YouTube/Google search.
A word of caution about experimenting with the hidden GREEN screens - be very careful with changes and ALWAYS make manual (and ACCURATE and fulsome) notations of any changes because modifications are NOT recorded in OBD11's History function. If you need to revert changes back to original values (which is very likely if experimenting), the ONLY records will those that you make manually - so be diligent with your notations, please.
Finally, finally - if this peculiar nanny-ware restriction for the display in NAR model cars is embedded in the module firmware (i.e. module dataset), then all hope is lost because whilst OBD11 can access this area of module coding - finding the correct memory address and setting value will be very difficult!!!
Don
|
|
|
Post by sgoring03 on Feb 13, 2023 23:19:55 GMT
Hi Don,
As always an interesting line of investigation to be followed. For sure this coming weekend I will connect the ODB11 and check out 5F. I’ve not yet enabled the “green menu” as my searches have said you need to enable developer mode switch a bit and then switch back to normal mode before restarting the MMI. Maybe I’ll be brave this weekend too, but we’ll see. If anyone has time before the weekend in the US maybe they can try first.
My MMI version is - MHS2_US_AU_P2037 which I have been told is the most up to date for the US. CarPlay and Android Auto both work already.
Simon
|
|
|
Post by rick92f on Mar 12, 2023 10:14:25 GMT
Has anyone found any more information on this?
|
|
|
Post by sgoring03 on Mar 13, 2023 23:48:52 GMT
Hello,
I did try a few combinations without any luck getting around the “nanny” state block.
Feels to me like as Don suggests this is buried in the module.
Simon
|
|
5F-X
New Member
Enter your message here...
Posts: 34
|
Post by 5F-X on Mar 29, 2023 15:48:33 GMT
Didn't bother reading this long winded post but if you haven't figured this out yet you can actually just push the screen down manually. It has a retractable safety feature that if it's bumped too hard it slides away for safety. Just give it a nudge downward and it'll hide away.
|
|
|
Post by buildbot on Jun 20, 2023 15:47:16 GMT
Interestingly, I had the screen go down while doing a scan with my obdeleven and playing music - so perhaps there is another way to fake the correct signal.
|
|