otzi
New Member
Posts: 21
|
Post by otzi on Apr 18, 2023 21:02:27 GMT
Hello colleagues!
I am wondering if there exists any software version for A3 Virtual Cockpit that preserves settings of VC between ignition cycles.
In my VC when I set for instance Sport Layout and map view on the left side od the speedometer, after ignition off and on I always get a view with a first tab on the left side of the speedometer which is the tab with a current date/time,current fuel usage etc. Not the view with navigation tab that I set before ignition off.
Could you share how it looks on your side? If your VC preserves a VC view between ignition cycles could you provide the details of your VC (part number, HW and SW versions) please?
Or maybe some coding exists that could be changed to have this VC view saved between ignition cycles?
The only thing I found in a long coding of 17 unit are options like Audio, Telephone, Navigation/Compass that probably could be used to disable mentioned tabs. However I would not want to do this, as I am using other tabs as well. Also I think there is no option to disable the first tab (car computer) so even after disabling Audio/Telephone tab, still the first one/default one would be this with Date/Time etc. not Nav tab. Maybe there is some option to re-order the tabs, to set Nav tab as the first one?
Please let me know your thoughts about it.
Thanks!
|
|
|
Post by dv52 (Australia) on Apr 18, 2023 22:31:09 GMT
otzi : Hi - and thanks for the interesting question! First - I don't know the answer (maybe someone else does). I've looked through the adaptation challenge database and the descriptors for the software switches on the long-code string for the hex17 module (8V0-920-790-A) and I couldn't find an obvious control item for this problem. So, in the absence of a obvious mechanism in the actual module - perhaps it's prudent to look at how the Dashboard module receives the data that it displays. My apology if you already know this stuff, but despite the complexity of the "VC", the hex17 module has surprisingly few actual wire connections on its housing connector. This is because the vast majority of the VC function happens either via messages on the CAN bus, or via communications over the optical fiber medium which uses a protocol that is called MOST (Media Oriented Systems Transport). Here's a high-level diagram showing the topology of the MOST ring:
On this picture, the VC is "J285".
So, maybe a fruitful place for your investigation might be (emphasis on "might be") the module that is the MOST-master - which is the MMI on an Audi (or J794 in my diagram)? Again, I'm guessing but it might be that whichever tab is initially loaded onto the VC after ignition switch-ON is decided in the hex5F module? I note that there are a bunch of adaptation channels in this module with the Parent name Dashboard_Display_Configuration - but I can't see an obvious Terminal 15 switch on my version VC.
Don
|
|
otzi
New Member
Posts: 21
|
Post by otzi on Apr 19, 2023 7:57:06 GMT
Don, thanks a lot for your great answer! It is interesting and indeed maybe this setting is provided externally to VC. I did not thing about it this way. This is not critical must have for me, but would be nice not having to press the left arrow button to switch between "Onboard computer" to "Navigation" tab every time ignition is on I am just curious if someone has VC that preserves the VC view between ignition cycles. If yes, that would mean that some SW version for VC or MMI brought this feature to A3.
|
|
|
Post by dv52 (Australia) on Apr 19, 2023 23:41:47 GMT
I am just curious if someone has VC that preserves the VC view between ignition cycles. If yes, that would mean that some SW version for VC or MMI brought this feature to A3. hmm.......On my Audi A3 8V - the VC does indeed "preserves the VC view between ignition cycles". As I understand, there are fundamentally 2 x versions of VC used on MQB platform Audis.
Not surprisingly, the difference occurs on North American Region (NAR) models - as ALWAYS appears to happen for "Yankee" cars (for reasons only Americans can understand - no offense intended if you happen to be a US citizen )
Anyhow - this is an example of difference in the way the VC displays engine temperature across the 2 x version modules
The VC on my RoW model (Australia is in the "very deep south" ) is: Part No SW: 8V0 920 790 A HW: 8V0 920 790 A Component: FBenRDW H16 0066 Coding: 248409506F8800080180EA001000000000000000
Don
|
|
otzi
New Member
Posts: 21
|
Post by otzi on Apr 20, 2023 8:23:33 GMT
Thank you Don for another valuable post I live in Europe, so I have VC variant with the Celsius scale According to your message that means that this functionality is available and works for A3 as well. My VC is like: Hardware number 8V0 920 790 Hardware version: H13 Software number 8V0 920 790 Software version: 0045 Long coding: 048D09407F9C00080080EA001000200000000000 My car is from July 2016, so I guess one of the first FL cars that left the factory, so it also got first VC version (with old HW/SW versions) that went into the production. I have SW version 0069 on my laptop and I was going to update my VC with this version, before activating sport layout. Eventually I activated it in current 0045 SW version, as Guys here confirmed that activation was ok for 0047, so I decided to risk and it worked If your VC with SW0066, after ignition on displays exactly the same view as it was before ignition off, maybe I should try to update mine from 0045 to 0069. Do you have any experience with doing VC software update? To avoid voltage drops, can it be done with the engine running? Or maybe better to connect a charger at the time of updating? By any chance do you know how long the update may take? I have quite decent 128GB full size SD card with U3/V30 speed class so it should not be a bottleneck I guess. Thanks!
|
|
|
Post by dv52 (Australia) on Apr 21, 2023 0:35:59 GMT
otzi : here's a comparison of the long-code strings on our respective VC modules
Name dv52 otzi Byte Hex Binary Hex Binary 00 24 00100100 04 00000100 01 84 10000100 8D 10001101 02 09 00001001 09 00001001 03 50 01010000 40 01000000 04 6F 01101111 7F 01111111 05 88 10001000 9C 10011100 06 00 00000000 00 00000000 07 08 00001000 08 00001000 08 01 00000001 00 00000000 09 80 10000000 80 10000000 10 EA 11101010 EA 11101010 11 00 00000000 00 00000000 12 10 00010000 10 00010000 13 00 00000000 00 00000000 14 00 00000000 20 00100000 15 00 00000000 00 00000000 16 00 00000000 00 00000000 17 00 00000000 00 00000000 18 00 00000000 00 00000000 19 00 00000000 00 00000000
I've looked at the differences in the software switches above and none relate to this matter.
Alas I've not done a firmware (dataset) update on the hex17 module - but I suggest that a good battery charger is a far better option than the engine running.
Again with the caveat that I haven't done the update, the hex17 module has a special role on MQB platform cars in that it holds the smarts for stuff like the immobilizer function and keying protocols. I'm not sure how these are affected by a software update. Don't get me wrong - I'm not saying that these other functions WILL be affected - rather, I'm suggesting that you satisfy yourself that unintended consequences won't happen.
Also, whilst I'm aware that OBD11 can change EEPROM values in a module - I don't believe that it can be used for a wholesale firmware update of module dataset.
Finally, updating the module firmware for the VC isn't the same as updating the MMI- which can be done via a SSD card. You will need something like VCP, or ODIS for this task
Don
|
|
otzi
New Member
Posts: 21
|
Post by otzi on Apr 21, 2023 7:38:49 GMT
Hi Don Thank you for comparing the long coding strings and sharing your thoughts. I was thinking about doing the VC software update using Red Engineering Menu, not with OBD11. Apologize for not being precise. As I have already mentioned, I found files with 0069 software. I put them into the SD card and checked in the REM. Update files were recognized, but I did not do the update, as it turned out that sport layout works even with SW 0045. If there is a chance though that 0069 will bring a feature with saving VC view across the ignition cycles, I think I will give it a try once I find some time.
|
|