Audi VC map layout fix - Revision history

Mr-fix: /* MIB2 persistence fix */

2025-05-22T12:20:00Z

MIB2 persistence fix

← Older revision		Revision as of 14:20, 22 May 2025
Line 24:		Line 24:

	/eso/bin/apps/pc b:256:20 TODOOOO		/eso/bin/apps/pc b:256:20 TODOOOO

			/scripts/performePersReset.sh

Mr-fix: /* MIB2 persistence fix */

2025-05-22T12:19:43Z

MIB2 persistence fix

← Older revision		Revision as of 14:19, 22 May 2025
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.

	~~TODOooo~~		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

Mr-fix: /* Reason */

2025-05-21T08:51:16Z

Reason

← Older revision		Revision as of 10:51, 21 May 2025
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 ~~you~~ 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.		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.

Mr-fix at 07:41, 10 April 2025

2025-04-10T07:41:09Z

← Older revision		Revision as of 09:41, 10 April 2025
Line 9:		Line 9:

	== Solutions ==		== Solutions ==
	=== Toggle layout on VC ==		=== Toggle layout on VC ===
	Switch between layouts on VC. This will send the information to MIB and everything should be back to normal.		Switch between layouts on VC. This will send the information to MIB and everything should be back to normal.

Mr-fix: Created page with "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). But this happens only when you switch between layouts. So if you VC does not allow to change to Sport and it'..."

2025-04-10T07:40:56Z

Created page with "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). But this happens only when you switch between layouts. So if you VC does not allow to change to Sport and it'..."

New page

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). But this happens only when you switch between layouts. So if you 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.

TODOooo