BMW Forum - BimmerFest BMW Forums banner

PSdZData FULL Requests (Programming Firmware)

2 reading
1.1M views 11K replies 3.9K participants last post by  shawnsheridan  
#1 · (Edited by Moderator)
Hello,

I have version 57.3

Is there a newer version?

What is the newer version?

What does it give over the older version?

Most important, is it needed for a 2016 M3?
 
#4,434 ·
#4,436 ·
Hello! Today I wanted to update the I-level of my car (2014 f11). I followed the procedure, but the list of ECU modules that appeared is incomplete (only 7, as can be seen in picture). Is this ok?

This is a second hand car, and I don't know if the I-level was updated by the previous owner. The current i-step appears to be F010-19-03-530 (which is quite new). Does it mean that all the ECU modules where updated or the current i-step changes even when only one module is updated?
Thank you!
 

Attachments

#4,438 ·
Only 7 ECU needed updating. I-Step is updated if all ECU have current firmware, and that could be by updating one ECU, all ECU, or any number in between.
 
#4,442 ·
#4,446 ·
Unsuccessful I-step update "FinishedWithError". [C207]

Hello Shawn. Thanks for the help you provided me before.

I tried to make an I-step update for the 7 modules that have one available, using E-sys 3.33.0 and psdzdata v.4.21.12, and following the steps in the guide and unfortunately, it ended up this error: TAL-Execution finished with status: "FinishedWithError". [C207]

Bellow is part of the error log (I used ....... instead of parts that I thought where not very relevant):
{ TAL execution started.
MCDDiagService<id=84900, job=com.bmw.psdz.jobs.uds.MCD3_ReadFlashTimingParameters, service=RDBI_FTP - ReadDataByIdentifier FlashTimingParameter, description=error: timeout, link=KAFAS2_5D_ETHERNET> [DIAGSERVICE]
[] use default timing parameters as an exception occured [WARN]
[] - [Exception - KAFAS2 - 5d] negative response error:
code: TIMEOUT P2/T2 occurred
description: P2 timeout on Service RDBI_FTP has error in result: [Severity=2051][ErrorCode=58640][ErrorCodeDescription=resource not available][VendorCode=2142][VendorCodeDescription=P2 timeout occured]; LinkName: KAFAS2_5D_ETHERNET
severity: ERROR
ExecutionID=2020/01/02-14:55:25.315
[] prepareTALExecution started [PROGRESS]
MCDDiagService<id=48900, job=com.bmw.psdz.jobs.uds.MCD3_CheckProgrammingCounter, service=RDBI_PC - ReadDataByIdentifier ProgrammingCounter, description=error: timeout, link=KAFAS2_5D_ETHERNET> [DIAGSERVICE]
MCDDiagService<id=36900, job=com.bmw.psdz.jobs.common.MCD3_PrepareTALExecution, service=RDBI_ADS - ReadDataByIdentifier ActiveDiagnosticSession, description=error: timeout, link=FRR_21_ETHERNET> [DIAGSERVICE]
...........
MCDDiagService<id=20600, job=com.bmw.psdz.jobs.common.MCD3_PrepareVehicleForFlash, service=CC, description=error: negative response : conditionsNotCorrect, link=#RtGen_MultipleEcuJob_LogicalLink> [DIAGSERVICE]
........
[DME - 12] Failed ProgrammingPrecondition ECUId:DME_0x12 error ID:9 - Vehicle not in state Pruefen_Analyse_Diagnose / ignition not activated (clamp 15 off) [THROWABLE]
[] prepareVehicleForFlash finished [PROGRESS]
[TCB - 61] prepareECUforFlash started [PROGRESS]
MCDDiagService<id=46900, job=com.bmw.psdz.jobs.uds.MCD3_GetSVKfromECU, service=RDBI_SVK - ReadDataByIdentifier SVK, description=error: timeout, link=KAFAS2_5D_ETHERNET> [DIAGSERVICE]
......
[KAFAS2 - 5D] There was an error during TAL execution, please check the log files. [WARN]
[KAFAS2 - 5D] - [Exception - KAFAS2 - 5d] negative response error:
code: TIMEOUT P2/T2 occurred
description: P2 timeout on Service RDBI_SVK has error in result: [Severity=2051][ErrorCode=58640][ErrorCodeDescription=resource not available][VendorCode=2142][VendorCodeDescription=P2 timeout occured]; LinkName: KAFAS2_5D_ETHERNET
severity: ERROR
[TCB - 61] prepareECUforFlash finished [PROGRESS] (TCB was updated with no error)
........
[] SVK-Ist does not match expected SGBMIDs for ecu ECUId:CAS_0x40. Excpected (relevant process classes only): [hwap_000002ed-255_255_255, hwel_00000007-006_000_007], Actual (relevant process classes only): [hwel_00000007-006_000_006, hwap_000002eb-255_255_255], Missing SGBMID(s): [hwap_000002ed-255_255_255, hwel_00000007-006_000_007], Surplus SGBMID(s): [hwel_00000007-006_000_006, hwap_000002eb-255_255_255] [THROWABLE]
[CAS - 40] There was an error during TAL execution, please check the log files. [WARN]
[CAS - 40] - [Exception - CAS - 40] SVK-Ist does not match expected SGBMIDs for ecu ECUId:CAS_0x40. Excpected (relevant process classes only): [hwap_000002ed-255_255_255, hwel_00000007-006_000_007], Actual (relevant process classes only): [hwel_00000007-006_000_006, hwap_0000a02eb-255_255_255], Missing SGBMID(s): [hwap_000002ed-255_255_255, hwel_00000007-006_000_007], Surplus SGBMID(s): [hwel_00000007-006_000_006, hwap_000002eb-255_255_255]
..........}
The full error log is attached in word document.

One possible cause of the problem is that although I used a powerful enough source, the cables were not well connected and I think that the car didn`t get enough power during the flash.
I also have to mention that before flashing, I VO coded the car with 2TB and 5ad (line departure warning - which I successfully retrofitted).

After the unsuccessful flash, the car still works perfectly normal.
The problem is that after I connect with the car in E-sys and read SVT, the ECU-s subfolders are not black, blue and red, as it is supposed, bot all of them are blue. More then that, when I click the right button of the mouse and chose Read DIF, I get an empty box (picture attached).
Also, if I follow the steps in the guide, although I press the read button in Master/I-step, and the boxes in the Integration steps (ECU) are populated with I-step current/last/shipment, when I go to KIS/SVT Target, the I-sep boxes remain empty and cannot be populated.

What should I do now? I was thinking to go in expert mode, Tal Processing, and load TAL and SVT that I saved before flashing and flash again the 7 ECU`s but this time with an older E-sys (3.27.1 ?) and using making sure this time I have a proper power supply.
What do you advise me? I am afraid not to make things worse. At least, the car work now.

Thank you a lot for your help. I really appreciate the effort and time that you put into helping us.
 

Attachments

#4,447 · (Edited)
Hello Shawn. Thanks for the help you provided me before.

I tried to make an I-step update for the 7 modules that have one available, using E-sys 3.33.0 and psdzdata v.4.21.12, and following the steps in the guide and unfortunately, it ended up this error: TAL-Execution finished with status: "FinishedWithError". [C207]

Bellow is part of the error log (I used ....... instead of parts that I thought where not very relevant):
........
[DME - 12] Failed ProgrammingPrecondition ECUId:DME_0x12 error ID:9 - Vehicle not in state Pruefen_Analyse_Diagnose / ignition not activated (clamp 15 off) [THROWABLE]
[] prepareVehicleForFlash finished [PROGRESS]
[TCB - 61] prepareECUforFlash started [PROGRESS]
MCDDiagService<id=46900, job=com.bmw.psdz.jobs.uds.MCD3_GetSVKfromECU, service=RDBI_SVK - ReadDataByIdentifier SVK, description=error: timeout, link=KAFAS2_5D_ETHERNET> [DIAGSERVICE]
...
For Starters, car must be in Aux Power, connected to commercial grade 50+ Amp Charger or jumped to other car with motor running.

ANd "SVK-Ist does not match expected SGBMIDs for ecu", means you choose incorrect I-Step Shipment.

Also be sure to flash with E-Sys Direct. Do NOT use E-Sys Launcher while Flashing.
 
#4,448 ·
Thanks for answer I am pretty sure that I chose the correct I-step Shipment. Maybe it has to do with the fact that the car was VO coded before. I don't see any other way of flashing the car now, other than using the saved SVT-tal and SVT-soll saved before, because the boxes in KIS/SVT target are grey-ed out and can't be populated with I-step shipment/target (in conclusion, I cannot calculate and create a new SVT_soll).
Also, would it be a good ideea to use a older E-sys? Or, is there other options than flashing again?
Thank you.
 
#4,451 ·
It is Gr-eyed out because Injecting CAFD (Detect CAF for SWE) and Flashing ECU's with >= v.4.17.20 PSdZData requires using newer E-Sys 3.30.0 or higher.

And the I-Step Shipment is wrong as I wrote.
 
#4,453 · (Edited)
Hi Shaun, may I please get the link for the latest, v4.18.14 and v4.15.31 of PSdZData_full? Thanks!
 
#4,457 ·
#4,458 ·
Hi, may I have the link to psdzdata full files, please? Thank you

I have Esys 3.27.1 with which I am trying to inject cafd for the zgw module in my F10 2011 258hp but I am getting error something like file cannot be found or something like this. I have also esys 3.28 but the detect button is not working there. I hope if I put the full psdzdata in the esys 3.27.1 will it work so I can inject the cafd file into the ZGW module?
 
#4,460 ·
Injecting CAFD (Detect CAF for SWE) and Flashing ECU's with >= v.4.17.20 PSdZData requires using newer E-Sys 3.30.0 or higher.

You cannot inject CAFD into ZGW. It has none. It is NOT a codeable ECU.

PM sent.
 
#4,459 ·
Hi, may I have the link to psdzdata full files, please? Thank you

I have Esys 3.27.1 with which I am trying to inject cafd for the zgw module in my F10 2011 258hp but I am getting error something like file cannot be found or something like this. I have also esys 3.28 but the detect button is not working there. I hope if I put the full psdzdata in the esys 3.27.1 will it work so I can inject the cafd file into the ZGW module?