SPORT HMI for Audi - Revision history

Mr-fix: /* How to enable it? */

2026-04-14T17:14:01Z

How to enable it?

← Older revision		Revision as of 19:14, 14 April 2026
Line 518:		Line 518:
	# modify SportHMI classes		# modify SportHMI classes
	# patch DSI with missing data		# patch DSI with missing data
	# deregister components from Menu Entry that cause it to be invisible		# <s>deregister components from Menu Entry that cause it to be invisible</s>
	# create a shortcut for SportHMI to bypass the Menu Entry Registry all together		# <s>create a shortcut for SportHMI to bypass the Menu Entry Registry all together</s>
			# patch menu entry registry
			# patch carScreenBag

	== Modifications with custom data ==		== Modifications with custom data ==

2026-03-13T10:58:51Z

Modifications with custom data

← Older revision		Revision as of 12:58, 13 March 2026
Line 525:		Line 525:
	ideas:		ideas:
	* oil temp → gearbox temp		* oil temp → gearbox temp
	* boost pressure → oil pressure
	* ~~torque → steering angle~~		* bar: acceleratorPosition=ViewOption(state: 2, reason: 0)
	* ~~power → tachometer~~		* bar: brakePressure=ViewOption(state: 2, reason: 0)

	[[Category:Software]]		[[Category:Software]]
	[[Category:Research]]		[[Category:Research]]
	[[Category:Tweaks]]		[[Category:Tweaks]]

2026-03-05T13:01:21Z

Logging HMI

← Older revision		Revision as of 15:01, 5 March 2026
Line 361:		Line 361:
	statisticsReset=ViewOption(state: 0,reason: 0),		statisticsReset=ViewOption(state: 0,reason: 0),
	statisticsConfig=ViewOption(state: 0,reason: 0),		statisticsConfig=ViewOption(state: 0,reason: 0),
	oilTemperatureValue=ViewOption(state: 0,reason: 0),		oilTemperatureValue=ViewOption(state: 0,reason: 0), // ← ← ← ← ← ← ← ← NOT OK
	coolantTemperature=ViewOption(state: 0,reason: 0),		coolantTemperature=ViewOption(state: 0,reason: 0),
	comfortPowerConsumptionST=ViewOption(state: 0,reason: 0),		comfortPowerConsumptionST=ViewOption(state: 0,reason: 0),
Line 416:		Line 416:
	00:00:42.720 INFO <App.Car.Sport>		00:00:42.720 INFO <App.Car.Sport>
	updateBCOilTemperatureValue:null,		updateBCOilTemperatureValue:null,
	valid:2		valid:2 // ← ← ← ← ← ← ← ← NOT OK

	00:00:42.715 INFO <App.Car.Sport>		00:00:42.715 INFO <App.Car.Sport>
Line 422:		Line 422:
	maxChargingAirPressure=2.5,		maxChargingAirPressure=2.5,
	maxOutputPower=228,		maxOutputPower=228,
	maxTorque=0,		maxTorque=0, // ← ← ← ← ← ← ← ← NOT OK
	engineDisplacement=2.0,		engineDisplacement=2.0,
	typeOfInjectionSystem=0),		typeOfInjectionSystem=0),

2026-03-05T08:57:38Z

App.Car.Sport=5

@@ Line 303: / Line 303: @@
 === App.Car.Sport=5 ===
 Let's start with <code>App.Car.Sport</code> set to level <code>5</code>, so it will output some data.
 :00:42.715 INFO  <App.Car.Sport>
@@ Line 312: / Line 426: @@
    typeOfInjectionSystem=0),
   valid:1
 :00:42.722 INFO  <App.Car.Sport>

2026-02-28T18:03:57Z

Modifications with custom data

← Older revision		Revision as of 20:03, 28 February 2026
Line 403:		Line 403:

	It looks like the <code>state='0'</code> is reported if the component is working correctly. And two component's are not. <code>SPORT_TORQUE_MAX</code> and <code>SPORT_OIL_TEMPERATURE</code> - same two that were missing or zeroed in DSI-provided data. Huh...		It looks like the <code>state='0'</code> is reported if the component is working correctly. And two component's are not. <code>SPORT_TORQUE_MAX</code> and <code>SPORT_OIL_TEMPERATURE</code> - same two that were missing or zeroed in DSI-provided data. Huh...

			== How to enable it? ==
			I have 4 ideas, actually. Not sure which is best and if any would work.
			# modify SportHMI classes
			# patch DSI with missing data
			# deregister components from Menu Entry that cause it to be invisible
			# create a shortcut for SportHMI to bypass the Menu Entry Registry all together

	== Modifications with custom data ==		== Modifications with custom data ==

2026-02-22T17:33:56Z

Sport and Sport Kombi classes

← Older revision		Revision as of 19:33, 22 February 2026
Line 33:		Line 33:

	== Sport and Sport Kombi classes ==		== Sport and Sport Kombi classes ==
	It looks like ~~there are~~ two separate ~~apps related to Sport Display feature~~:		It looks like the app logic is split into two separate classes:
	* <code>SportHMI</code>		* <code>SportHMI</code>
	* <code>SportHMI-Kombi</code>		* <code>SportHMI-Kombi</code>

	<code>Kombi</code> ~~can be used to distinguish app version~~ designed for instrument cluster ("Kombiinstrument")		<code>Kombi</code> is designed for instrument cluster data ("Kombiinstrument"), which is the oil temperature.

	Here's a statement that creates the screen:		Here's a statement that creates the screen:

2026-02-18T07:20:03Z

@@ Line 295: / Line 295: @@
 Two things (<code>SPORT_TORQUE_MAX</code> and <code>SPORT_OIL_TEMPERATURE</code> are invisible. This partially correlates with unavailable <code>maxTorque</code>.
-Is it that this missing data is what's locking the SPORT submenu to appear?
+Is it that this missing data is what's locking the SPORT submenu to appear? Let's find out!
 == Modifications with custom data ==

2025-11-14T13:07:21Z

@@ Line 191: / Line 191: @@
 Maybe that's it? Maybe the RACE Charisma mode needs to be enabled from the SportHMI to be accessible?
-Just to be sure, I will check if there are some "RACE" references in the code.
+== Figuring out the missing data ==
-== Figuring out the missing function ==
+Here we can see which information is provided <code>state: 2</code>, and which is not <code>state: 0</code>:
-//todo
+ SportHMI
 == Modifications with custom data ==

2025-06-08T15:44:32Z

Sport and Sport Kombi classes

← Older revision		Revision as of 17:44, 8 June 2025
Line 45:		Line 45:
	case 600289: {		case 600289: {
	return CarScreenBag1.cARSPORTMAIN(this, n2);		return CarScreenBag1.cARSPORTMAIN(this, n2);

			This one returns name of the screen for diagnostic purposes
			case 600289: {
			return "CAR_SPORT_MAIN";
			}

	And this one executes conditions		And this one executes conditions

2025-03-25T22:07:25Z

Moment of Doubt

← Older revision		Revision as of 00:07, 26 March 2025
Line 174:		Line 174:
	}		}

	Nope! It looks like only Efficiency Mode and Lift/Offroad Modes have children elements. No SportHMI mentions here. But there's a RACE Mode ~~mention~~		Nope! It looks like only Efficiency Mode and Lift/Offroad Modes have children elements. No SportHMI mentions here. And previously mentioned <code>LD_CAR_SEL_SPORTDISPLAY</code> was linked to left drawer, which means that the SportHMI needs to be present in the CAR menu.

			But there's a RACE Mode mentioned here and there.

	MenuEntry menuEntry9 = this.entryFactory.createMenuEntry(238, "CHARISMA_PROFILE_RACE", 305203456);		MenuEntry menuEntry9 = this.entryFactory.createMenuEntry(238, "CHARISMA_PROFILE_RACE", 305203456);

			public boolean isRacesport() {
			return this.racesport;
			}

			Maybe that's it? Maybe the RACE Charisma mode needs to be enabled from the SportHMI to be accessible?


	Just to be sure, I will check if there are some "RACE" references in the code.		Just to be sure, I will check if there are some "RACE" references in the code.