Audi VC map layout fix: Difference between revisions
No edit summary |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
This can happen if VC and MIB are not set to the same layout. | This can happen if VC and MIB are not set to the same layout. | ||
VC shares with MIB the information about the layout (Classic vs Sport). But this happens only when you switch between layouts. So if | VC shares with MIB the information about the layout (Classic vs Sport; small vs large scene). But this happens only when you switch between layouts. So if your VC does not allow to change to Sport and it's permanently set to Classic, it will never send the information to MIB about requested layout. | ||
For example you have retrofitted MIB2 and it sourced from a vehicle which had the Sport Layout enabled and activated in VC just before it was removed from the donor car. This MIB2 unit will still think that it should transmit map image for the Sport Layout on VC. | For example you have retrofitted MIB2 and it sourced from a vehicle which had the Sport Layout enabled and activated in VC just before it was removed from the donor car. This MIB2 unit will still think that it should transmit map image for the Sport Layout on VC. | ||
| Line 19: | Line 19: | ||
There are various ways to do that. You can use Telnet, SSH, UART, or even More Incredible Bash to modify persistence memory. | There are various ways to do that. You can use Telnet, SSH, UART, or even More Incredible Bash to modify persistence memory. | ||
export LD_LIBRARY_PATH=/mnt/app/root/lib-target:/eso/lib:/mnt/app/usr/lib:/mnt/app/armle/lib:/mnt/app/armle/lib/dll:/mnt/app/armle/usr/lib | |||
export IPL_CONFIG_DIR=/etc/eso/production | |||
/eso/bin/apps/pc b:256:20 TODOOOO | |||
/scripts/performePersReset.sh | |||
Latest revision as of 14:20, 22 May 2025
In some cases (usually after a retrofit) there might be an issue with the map layout on Audi Virtual Cockpit. It looks like the map is hidden behind the user interface, car is off-map, there are some glitches, etc...
Reason
This can happen if VC and MIB are not set to the same layout.
VC shares with MIB the information about the layout (Classic vs Sport; small vs large scene). But this happens only when you switch between layouts. So if your VC does not allow to change to Sport and it's permanently set to Classic, it will never send the information to MIB about requested layout.
For example you have retrofitted MIB2 and it sourced from a vehicle which had the Sport Layout enabled and activated in VC just before it was removed from the donor car. This MIB2 unit will still think that it should transmit map image for the Sport Layout on VC.
Solutions
Toggle layout on VC
Switch between layouts on VC. This will send the information to MIB and everything should be back to normal.
Just make sure that your MIB2 firmware is up to date, as some old firmwares might not support it correctly.
MIB2 persistence fix
Overwrite last state persistence namespace in MIB2. This will force the MIB unit to use different layout.
There are various ways to do that. You can use Telnet, SSH, UART, or even More Incredible Bash to modify persistence memory.
export LD_LIBRARY_PATH=/mnt/app/root/lib-target:/eso/lib:/mnt/app/usr/lib:/mnt/app/armle/lib:/mnt/app/armle/lib/dll:/mnt/app/armle/usr/lib export IPL_CONFIG_DIR=/etc/eso/production /eso/bin/apps/pc b:256:20 TODOOOO /scripts/performePersReset.sh