MK7.5 Digital Cockpit retrofit

[mattjewell]

How does this gauge look with a manual transmission? Is there still a "bubble" in the middle of the tachometer where the automatic drive indicators would normally be? If so, what are the options for that spot on a manual?

I made a POV short drive video. Starts around 1:30 time marker. Sorry for the angle, but in the bottom left corner is the gearing. What you can’t see because of the steering wheel is the current speed.

 

[bobloblawGTI]

I made a POV short drive video. Starts around 1:30 time marker. Sorry for the angle, but in the bottom left corner is the gearing. What you can’t see because of the steering wheel is the current speed.

Every so often I remember the R theme exists for the cluster and think about switching back to it. Looks good

 

[Cuzoe]

Every so often I remember the R theme exists for the cluster and think about switching back to it. Looks good

I normally have the driver assist view active, maps in the middle. I wish the R theme had a classic view for tach and speedo, with full needles.

 

[oneb1t]

I started following journey.. :-D
https://github.com/OneB1t/VcMOSTRenderMqb

maybe someone can help/have some ideas how to improve this

also is there some finding regarding map zoom via up/down buttons?

 

[Cuzoe]

@oneb1t Very much looking forward to seeing what all you come up with. Not a big deal, but I couldn't watch the video on the GitHub, even tried downloading the mp4 and opening it up with a standalone player (not in a browser).

My gut still tells me it's in the long coding for the steering wheel buttons, just haven't had the time to go through those bits. They have no description in VCDS or ODIS.

 

[yakev724]

@oneb1t great work!
if you could collaborate with https://github.com/Switchleg1/SimosTools to display some custom ECU values that would be epic.

https://www.golfmk7.com/forums/index.php?threads/open-source-tuning-solution.380998/
https://www.golfmk7.com/forums/index.php?threads/simos-tools-new-phone-datalogging-app.389270/


Here's a competitor product that does something similar, but their PIDs are crude and so don't really fit use cases that simos overcomes. Also requires an external box.

https://kermatdi.com/i-2525-polar-fis-customizable-engine-data-display-mqb-a-1.html

 

[Cuzoe]

I recall when the PolarFIS was first released for MQB there were issues with formatting, and something else with faults being generated, or interference with scan tools... found the thread...
https://www.golfmk7.com/forums/index.php?threads/autopolar-fis-on-mqb.352207/

The Vektor is a more "intrusive" solution but seems to be updated regularly, and looks quite good.

 

[yakev724]

The Vektor is a more "intrusive" solution but seems to be updated regularly, and looks quite good.

Link? I’m happy with simos and will keep using it for logging but a more “casual” solution for displaying boost and various temps without having to run a separate android device would be fantastic.

 

[Cuzoe]

@yakev724 Found my bookmark, I was actually thinking of the VADpro, which just plugs into the OBD port but you can customize displays and do logging (not sure how/if it compares to what SimosTools can do)...
https://www.vadpro.com/products/vadpro32-mk7-mqb-golf-platform

Although there is also the Vektor...
https://www.uspmotorsports.com/prod...y-gauge-for-vw-mk7-gti-golf-r-switch-75033674

I haven't personally used or seen either, and the PolarFIS is cheaper (as it uses your existing dash for display). But the other two options seem better, to me.

 

[oneb1t]

My gut still tells me it's in the long coding for the steering wheel buttons, just haven't had the time to go through those bits. They have no description in VCDS or ODIS.

If that is the case then 28ffffff should do it if looks like this coding is done via adaptations for 9 central electric unit

But that must mean that different CAN message is created by up/down buttons (and not handled by VC). Also maybe VC software version is important I have 5q0920791 without letter index.

 

[Cuzoe]

If that is the case then 28ffffff should do it if looks like this coding is done via adaptations for 9 central electric unit

But that must mean that different CAN message is created by up/down buttons (and not handled by VC). Also maybe VC software version is important I have 5q0920791 without letter index.

I'm not sure about the 09 coding. I'm talking about the coding for MFSW Control Module, it's a slave module of 19 Gateway.

I had 5Q0920791A which I updated to 5Q0920791B. Update to B got the VIEW button working.
Although at one point I had the VIEW button working even with A software. At the time I was messing with those bits to get the heated steering wheel button to work (Mk8 Wheel)

I've never been able to get the arrows working to zoom in/out though. They just show me the most recent navigation destinations.

 

[oneb1t]

Sorry I mean 19 not 9 can you show what parts affected this view button? The update should be possible also from my indexless cluster do if I can get zoom functionality I will go for it and update it to B index.

 

[Cuzoe]

I don't remember, and I didn't write it down, stupidly. Once I updated to software B it began working straight away with no change to my coding.

This is my coding now, but this is with Mk8 steering wheel, touch buttons PN 1EA 959 442 B...

Address 19: CAN Gateway (J533)       Labels:| 3Q0-907-530-V1.clb
   Part No SW: 3Q0 907 530 AR    HW: 3Q0 907 530 C
   Component: GW MQB High   521 5502 
   Serial number: 11102000840992 Dataset Number: SET_FPA_MOD 0001
   Coding: 0109000810087300DBEC92FDFF0F00000001050000000000000000000000
   Shop #: WSC 00046 123 12345
   GVL: 01543C100000000040CC800090004C0000000000000000000000000000000000
   ASAM Dataset: EV_GatewNF 013026
   ROD: EV_GatewNF_VW37.rod
   VCID: 7F5B0CE377721312761-802A

   Multifunction steering wheel control module:
   Subsystem 1 - Part No SW: 1EA 959 442 B    HW: 1EA 959 442 B
   Component: MFL  H03 0217
   Serial number: 17036218093222101678
   Coding: 2E2B00

No fault code found.

 

[oneb1t]

Maybe something in VCDS log folder?

This is my setup:

19 - LL_GatewUDS (EV_GatewLear_013)

System designation	GW MQB High
Software version	1265
Hardware version	125
VW/Audi part number	5Q0907530AM
Hardware part number	5Q0907530F
Coding	030100042B086400EF000248080F00010001000000000000000000000000
ASAM/ODX file identification	EV_GatewLear
ASAM/ODX file version	013020

[VO]_Multi_function_steering_wheel_control_module Coding Value:
[LN]_Tiptronic:	[VN]_not installed
[LN]_Temp Sensor:	[VN]_not installed
[LN]_MuFu-variant_VW:	[VN]_GRA-High
[LO]_development_1:	[VN]_active
[LO]_development_2:	[VN]_not active
[LO]_MuFu-variant_Skoda:	[VO]_not installed
[LO]_MuFu-variant_Seat:	[VO]_not installed

Subsystem number	49
System designation	E221__MFL-DC1
Software version	0035
Hardware version	H14
VW/Audi part number	5G0959442J
Coding

Subsystem - 006 Read coding: Multi Function Steering Wheel Control Module

Byte00:
	0010 1000 ($28)
Byte01:
	0000 0000 ($00)
Byte02:
	0000 0000 ($00)

I do not see anything obvious to mess with to make any impact on what buttons are doing :-/

I searched for a while and it is possible that old gateway is unable to set zoom function or there is some hidden setting for cluster itself to represent button press

 

[ksurl]

Will updating mib2 firmware brick the digital display since there was non factory coding done to the mib2? component protection was not disabled in my case, it was activated via vas5054a dongle and odis