Q7 SQ7 how to identify TPI for Virtual Cockpit

MisterT-28

New Member
Hi all,

I do have a question about identifying TPI (Technische Produktinformationen) for my Virtual Cockpit.

Here are my VCDS readings :

Address 17: Instruments (J285) Labels:* Redir Fail!-SRI2
Part No SW: 4M0 920 790 B HW: 4M0 920 790 B
Component: FBenRDW H15 0302
Coding: 04AD08C0389C00080323ED601100401000000000
Shop #: WSC 31414 790 00001
ASAM Dataset: EV_DashBoardAU736 001022
ROD: EV_DashBoardAU736_AU73.rod
VCID: 2E0505273096A62BD1E-807A

No fault code found.

But how should I deduce from that reading the "TPI" of that J285 ?

TNR SVM SD-Size TPI VERSION
8S0 906 961 C FPKWW268 1GB 0268
8S0 906 961 D FPKWW270 1GB 2042540/3 0270
8S0 906 961 H FPKWW274Q7 1GB 0274
8S0 906 961 Q FPKWW280Q7 1GB 2042540/16
2043290/3
2043575/2
2043778/5
2046264/4 0280
8S0 906 961 T FPKWW306Q7 1GB 0306
8S0 906 961 AJ FPKWW310Q7 1GB 2047722/4
2045587/8 0310
8S0 906 961 AK FPKWW378Q7 1GB 0378

I am a little bit lost ...

Thanks
Take care

Fred
 
Last edited:

DJAlix

VAG Car Coding™ Limited
Site Sponsor
VCDS Map User
Gold Supporter
VAG Can Professional
ODIS (Offboard Diagnostic System)
You cannot deduce anything from what you have posted above. You have not posted a TPI number or it’s detail, just that the resolution is to perform a firmware update given the list of part numbers you have posted.... and going from those part numbers I would suggest that none are for your virtual cockpit.

edit:

looking at your part number, you don’t have a virtual cockpit, you have an Audi Q5 with an analogue cluster.
 
Last edited:

MisterT-28

New Member
LOL :)
Bad copy paste !
You are right I was working on a mid-2014 SQ5 before working on my end-2016 SQ7 !!!
Just edited the post.
I will try a detailed reading tomorrow.
 
Last edited:

MisterT-28

New Member
Wednesday,03,February,2021,14:23:21:07733
VCDS Version: Release 20.12.0 (x64)
Address 17: Instruments
Control Module Part Number: 4M0 920 790 B
Component and/or Version: FBenRDW H15 0302
Software Coding: 04AD08C0389C00080323ED601100401000000000
Work Shop Code: WSC 31414
VCID: 2E0505273096A62BD1E-807A
Advanced Identification/FAZIT
Identification: BVX-815
Date: 19.09.16
Manufacturer number: 0403
Test stand number: 0868
Flash Status
Programming Attempts(application): 1/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0/0
Flash Date: 14.11.18
Misc.
Hardware number: 4M0 920 790 B
Workshop System Name: J285
Equipment/PR Code: 000000000000000000000000
Dataset Number: -----------
Dataset Version: ----
ASAM Dataset: EV_DashBoardAU736
ASAM Dataset Revision: 001022
VCDS Info:
VCID: 2E0505273096A62BD1E-807A
Labels: Redir Fail!-SRI2
ROD: EV_DashBoardAU736_AU73.rod
 

MisterT-28

New Member
Regarding my understanding of the readings, the VC was manufactured 19 / 09 / 2016 and was updated on 14 / 11 /2018.

Is that correct ?
 

DJAlix

VAG Car Coding™ Limited
Site Sponsor
VCDS Map User
Gold Supporter
VAG Can Professional
ODIS (Offboard Diagnostic System)
What is it you are trying to do?
 

MisterT-28

New Member
Well I am trying to identify the TPI for that VirtualCockpit to see if this "end 2016" is eligible for updated Virtual Cockpit "satellite" maps since Google Maps gate ...

(edit) I read that TPI has to be beginning of 2017 BUT there are some exceptions for 2016 VC that are Qualcomms enabled
 

DJAlix

VAG Car Coding™ Limited
Site Sponsor
VCDS Map User
Gold Supporter
VAG Can Professional
ODIS (Offboard Diagnostic System)
Erm, you don’t update the virtual cockpit for Satellite View, its the MMI unit. Suggest you log on and review current TPI’s for the information you are looking for. If you can’t find in general / recent then search VIN specific.
 

DJAlix

VAG Car Coding™ Limited
Site Sponsor
VCDS Map User
Gold Supporter
VAG Can Professional
ODIS (Offboard Diagnostic System)
OK I will need to remember my german lessons because I think I mixed some informations in the german forums :-D
You don’t need to know German to to reference TPI’s via the official VW group tools.
 
Top