[mcamino]

Hello. I am fairly new to coding of my 2013 X3. I have the ENET cable, and E-SYS 3.27 along with FULL PSDZ Data (I think it is 188gb unzipped). Fresh Install of Windows 10.

So i have a bad RDC module and i need to code the replacement. I am following these two guides below, but the problem i am running into is it is not giving me an option to detect my I-STEP.

https : // x3.xbimmers.com/forums/showthread.php?t=715297

https : // x3.xbimmers.com/forums/showthread.php?t=1276722


I am looking for suggestions on what i could be doing wrong.

[pungo]

Originally Posted by mcamino

Hello. I am fairly new to coding of my 2013 X3. I have the ENET cable, and E-SYS 3.27 along with FULL PSDZ Data (I think it is 188gb unzipped). Fresh Install of Windows 10.

So i have a bad RDC module and i need to code the replacement. I am following these two guides below, but the problem i am running into is it is not giving me an option to detect my I-STEP.

https : // x3.xbimmers.com/forums/showthread.php?t=715297

https : // x3.xbimmers.com/forums/showthread.php?t=1276722


I am looking for suggestions on what i could be doing wrong.

Maybe I'm wrong, but I believe you are trying to program(flash) the module, not code it, right?
Just be very careful what you are doing since it's possible brick modules when programming.
If you haven't seen this guide, it might be helpful: E-Sys - Flashing ECU Guide v.1.0.1.pdf

[mcamino]

Yes i meant PROGRAM it. The old module is dead, so no worry there and the new module i am hoping not to kill in the process. (Its the RDC module for my TMPS, So worst case, i dont have any TPMS sensors, not end of the world if i screw it up) I am not trying to program,upgrade my whole car because i am aware of those risks, and that is another discussion for another day.

That guide you sent is the one i am following and Step 8(c) is where things differ because i can SEE my istep in step 8(iv) but it doesnt show up under the other screen for 8(C).

[richardodn]

I did this in the spring. I don't recall having to read the i-step level. Here are the basic steps I used. I am a bit fuzzy on the details.

Connect => Read FA (VO) => Activate FA (VO) => Read SVT (VCM) => Left-Click on RDC ECU => Click on "Detect CAF for SWE" => Select the CAFD from latest I-Level shown => Select OK => Right-Click on RDC ECU (the ECU itself not the underlying CAFD) => Select CODE

I believe I used v3.31 and it was not necessary to use Launcher Pro for this particular operation. I also vaguely recall running across your issue and reading it was a bug in a particular version of E-sys.

[richardodn]

And check out this thread.

https://f30.bimmerpost.com/forums/sh....php?t=1672330

[mcamino]

Okay everyone, i got this fixed finally. I had to use e-sys 3.30 to get this to work and the above link was the perfect information i needed.

https://f30.bimmerpost.com/forums/sh....php?t=1672330