NefMoto

Hello !

I am looking for original file from RS6 or RS7 C7 Performance 605hp version for comparising.

Thanks in advance.

They are the same as the regular ones but using non zero power class coding in ECU EEEPROM. 560G (US), 560F (ROW).

The same ECU is used for both 560/605PS (CWUB/CWUC) engines.
Here is an original file extracted from FRF flash container.

There is also a 560C D1711A05C000_MY15 version, all other are MY16 versions. I think you want to compare to CRDB MY14 version?

560C officially upgrades to 560F.

I think 560F FRF is not an official update for 560C, since there is no 560C in the FRF expected idents. Also both versions are still available in Etka.

<EXPECTED-IDENTS>
                <EXPECTED-IDENT ID="EMEM_4G0906560F0005.SES_4G0906560F0005.EI_VWSparePartNumbe">
                  <SHORT-NAME>EI_VWSparePartNumbe</SHORT-NAME>
                  <LONG-NAME>VW Spare Part Number</LONG-NAME>
                  <IDENT-VALUES>
                    <IDENT-VALUE TYPE="A_ASCIISTRING">4G0906560F </IDENT-VALUE>
                  </IDENT-VALUES>
                </EXPECTED-IDENT>
              </EXPECTED-IDENTS>

This is where I look for upgrades, eg in the 560F odx:

        <LAYER-REFS>
          <LAYER-REF DOCREF="EV_ECM40TFS0114G0906560C_001" DOCTYPE="LAYER" ID-REF="EV_ECM40TFS0114G0906560C_001"/>
          <LAYER-REF DOCREF="EV_ECM40TFS0114G0906560F_001" DOCTYPE="LAYER" ID-REF="EV_ECM40TFS0114G0906560F_001"/>
          <LAYER-REF DOCREF="BV_EnginContrModul1UDS" DOCTYPE="LAYER" ID-REF="BV_EnginContrModul1UDS"/>
        </LAYER-REFS>

The reason I look there is not that I've found a document to say that is where they should be (which would have been nice), but that I saw dealer updates following these patterns, usually no suffix upgrades after ones of these prefix upgrades appeared and that I've had no flash failures or fault codes or problems having flashed about 4000 MED17.1.1 around the world using these as upgrade paths. They got quite busy doing the changed versions on R8/Huracan and then it calmed down somewhat on MGD1. I never prefix upgrade customer cars unless from this pattern, but do sometimes change them in my own testing and often you find incompatibilities such as the calibrations of sensors have changed - for example when I flashed my MG1CS008 with an unapproved version, the calibration of the OPF pressure sensors was wrong. I never saw anything go wrong with a prefix cross flash from the LAYER-REFS.

If you have stronger evidence to contradict the above, I'm interested.

You both are right.
Just see at idents and layref for two upgrade frf versions - 0002 and 0005

LAYER-REFS is about ODX loading in MCD kernel, nothing more, nothing less. Certainly it does not mean anything about compatibility whatsoever!
BV_EnginContrModul1UDS is root ODX, then other stuff is loaded on top of it.

For compatibility you must go all the way back and look at EXPECTED-IDENTS of all previous updates.
That's the only thing that is there for compatibility.

Thank you both. I will double check whether this has resulted in any incorrect upgrade paths and report back.

There were no discrepancies between LAYER-REFS and IDENT-VALUES in odx for MED17.1.x 2.5, 4.0 and 5.2 for the 17 upgrade paths I have in place. I had done those manually originally.

I'll report back again on the MGD1, after revising the automation to use IDENT-VALUES. I'm not arguing that LAYER-REFS is the correct place to look for compatibility even if it matches 100 times.

No discrepancies in 1172 MGD1 odx files between upgrade prefixes in LAYER_REFS and IDENT-VALUES. They are a 1:1 match in that no upgrade in LAYER-REFS was not found in IDENT-VALUES and vice versa.

Only 5 of these odx had "VW Application Software Version Number" (the suffix) in IDENT-VALUES.

I found TPI2046754/2 which mention 4G0906560F is an update for 4G0906560C. Normally i use the latest FRF as reference, good to know that sometimes the expected idents are not complete.

Expected idents are there, but not on the latest 560F version. You need to build the whole path (history).

I am just stating what the LAYER-REFS is for.
It should not be used for compatibility, that's not the intention. It's there to build the final ODX only. Think of it as class inheritance in a programming language.

It can be that in a flash file it matches the expected idents path, but it's always better to build the expected idents tree.
In this case it should be 560C -> 560F 0002 -> 560F 0005...

Just read the original ODX ECU-MEM specification and it will become clear
what is the difference and what is main and what is secondary addition.

Is a link available for the original document?

Look in your PM box

Thanks mate.
That means if I copy powerclass Table one to Table zero it has same power as a Performance Version right?

Probably, but I never tried it for that purpose so confirm what is in all the power classes. I think it was 1 or 2 instead of 0.