2006 BMW 530i E60, N52 engine, 123K miles.
Hello, if someone can help me, I would be more than grateful!

First a little background: I first had an Amazon K+DCAN cable, which worked but was obviously a lower-quality cable. I decided to get an ICOM.
Then I bought a BMW ICOM Next clone from eBay. The first did not work at all, the second would be found by EasyConnect and iTool Radar, but would not work no matter what I did. So I finally returned both and got a Super ICOM N3+. This works very well and has worked for both ISTA+ and the BMW Standard Tools. ISTA-P will not read all of my modules, I think because I need a ICOM-B due to the MOST ring.

My issue is, I messed up big time! I had been fighting with both interfaces and finally gave up on the ICOM Next and went back to the K+DCAN. I had two printouts, an INPA printout from a car similar to mine, and one from my actual car. Well, I somehow mixed them up and used WInKFP to update modules in my car. It turns out his car was a diesel, which certainly did not help!

I have tried to use NCS Expert and SG_Coderein all of the modules in my car back to factory. I have lost my radio, my modules seem to not be resetting properly.

Is there a way I can re-code my VO and put it back into the car somehow so I can take out the modules that do not belong?

 

What you're saying is not making sense. Flashing your modules does not change your VO. To me it just seems like you need to flash your modules back.

 

I appreciate your reply.

For example, his car has a diesel engine. (DDE606). Mine is a gas powered N52. I had his stuff all programmed into mine and my car was giving me a number for a diesel engine. I have flashed N52 back in, and it took, but my car is giving me a bunch of malfunctions. If I update, I am updating modules he had in his car that do not exist or are different into mine. So it's basically re-updating the wrong modules. That includes the radio, Climate control was wrong but I managed to restore that one and it is back to working. I cannot find my original INPA list which had my original module numbers in it unfortunately.

I am not saying my VO changed, but WinPFK is failing because it is trying to program modules that do not exist in my car.

 

So update modules in expert mode. What is your VIN and what modules do you need to flash. You also need an OEM ICOM. Clones have too many issues and not worth the savings when you think about what you'd save in the whole scheme of things. At this point you're in a position that's beyond your skill level and you will not find a coder that is still fixing E series issues that's not going to charge $$$. It's a dying skill as they have moved on to F/G series. Saying all this you need to find the ECUs for your car and manually flash them and that will fix your issue.

 

Well, I was just looking for pointers, I am not going to give up this easily and I am getting there!

VIN WBANE735X6CM38388
Prod. Date 2005-08-30
Type 530i Series E60 (5 Series) M-Sport Package
Body Type Sedan
Steering Left Hand Drive
Engine N52
Displacement 3L
Power 190kw / 258hp
Drive RWD
Color: Silber-grau metallic (A08)
Upholstery Leather "Dakota"/schwarz
Radio: CCC
Pre-LCI (pre facelift)

I know the number for all the modules it came with from the factory.

I am coding in Expert mode (manipulation is unchecked). I know that you do not want Manipulation on if you are merely looking to code for the factory.

I am also aware that you need to start the timer in Tool32 after updating and coding modules for things like the airbag lights. I have had a lot of problems trying to source an original ICOM, I would need an ICOM B for my car due to the MOST bus being under the Flashlight in the glovebox. That is why ISTA+ works, but ISTA-P won't work because it needs a MOST bus connection to read all of my modules.

 

NCS is not going to fix the flash issues. Your VO should be the same in all the modules if all you did was flash the modules. You need to focus on flashing the correct ZB numbers first. On the DME the GM is your issue because you flashed as diesel. Unless there's something I'm not getting from your explanation NCS is not going to help you with anything as this point. Flashing does not change coding or VO.

ISTA/P will work with cable you just don't have it setup correctly. Timing only needs to be set if a module is replaced not flashed.

 

My ICOM and ISTA-P works, it reads all the modules. Then a pop up appears saying I need to connect it to the MOST module, which I obviously cannot do because that requires an ICOM A head that has the ICOM B connector hooked up to the MOST connector. So ISTA-P cannot read the rest of my modules due to the N3+ having no way to actually hook it up to the MOST connector. Only the ICOM B can connect to it, so I would need a ICOM B, or ICOM A (or NEXT) with the ICOM B hooked up to it via USB. I know the ICOM NEXT clones caused me hours of headaches, so agreed about the clones! The N3+ works with BMW Standard Tools, so that is all I need (I will get a ICOM B in the near future).

I get what you are saying. Perhaps me explaining what I did would better help you understand what I did. I am trying to accomplish getting my vehicle back to how it was, running good.

1. Originally, I messed with the car to get the Passenger Restraint issue (passenger seat) sorted out. Emulator and a new positive terminal from a 550i (newest revision) did not work to fix this. Tried the resistor, nothing fixed it.
2, Cheap cable let me do most things and even re-code, I had updated the car and it worked well. Heck, it even seems faster due to the newer engine coding (likely because adaptions reset).
3. Got the ICOM Next clone, because I wanted to use ISTA-P and everyone says to get a ICOM.
4. I use a 14 volt 80 amp RV power supply, it does not even flinch when programming and stays above 13 volts at all times. So my power is good.
5. Neither ICOM Next ever worked with BMW Standard tools. I borked the coding with the cheap cable, so my hope was to get the NEXT and have a faster, better tool.
6. I have only worked with the N3+ for a day, it is no real ICOM but it is fast and BMW Standard Tools work, which is how I borked it, so should be able to un-bork it.
7. I am doing the Factory Programming profile and it reads the VO from my CAS and LM without issues. I was under the impression my car would get factory coded if the Exportmode profile was active and I did the SG_Coderein on each module. This is supposed to write the stored VO into each module (I have my VIN with the checksum letter added to the end of my VIN in NCS Expert.

I have Tool32 and NCSDummy for coding, plus the Bimmerlink and Bimmercode Android version for coding (this works great for quick coding car features and it does not change the VIN or UIF Write) I should be able to get my original numbers from INPA, is this correct? That is how I went back to a gas engine and not a diesel anymore. I also think my problems stem from a bad DATENS file. I am seeing some e65 programs in NCSExpert, which I believe is the model whose codes I put into my car to cause this issue to begin with. I still cannot believe I cannot find my original INPA printout, if I find that I can easily get my car back to how it was because I would know exactly what ZUSB Numbers to code back in. I thought this WAS my original INPA UIF printout, I would have never messed with it if I knew it was another car. I believe the bad DATEN file is also why some of my modules would not update, they were for like E90 (I only copied the Base and E60 folder to my laptop).

So my question is, how can I get my original numbers? I have gotten to know WinKFP, NCSExpert, and INPA pretty good. Tool32 I have not used much yet, but if I can use that, I would touch up on it first. The biggest issues I have had with the software is not everything is English and my German is quite bad. 😂

 

You do not need an ICOM for ISTA/P to read/flash/code all the modules if it's setup correctly to use another connection medium. I used the K+DCAN cable for years before I purchased my first ICOM. I just knew there were certain modules, like the HU, you didnt want to flash with the cable which I never did.

You can get the installed part in your car by INPA but not original or last ZB numbers. The DATEN files are not bad as some are shared across modules. What version DATEN files are you using?

 

I had a V71 Datens that had some wrong modules in it for some reason. I only caught it after it wanted to put E90 modules codings into my E60. I got rid of that and put another V71 Datens I found and those seem to coincide with the V69 I have had.

I have V69, V70 and V71. Plus the DATENS installed in ISTA-P V3.69

I know to use the K+DCAN with ISTA-P, you need Bootloader V6.1. My ICOM works perfect in ISTA+, only ISTA-P does not like it for some reason because of the MOST ring issue. Too bad ISTA+ does not code E-Series.

I was going to try my K+DCAN with ISTA-P, I can easily go back to Bootloader V6.1 (using V6.6 currently). It simply is getting too cold in Illinois to stay out past dark right now, or I would be out there messing with it. I guess the ICOM won't read the MOST but the K+DCAN can because of the pins it shorts? Not sure but I thought ISTA-P would work with my ICOM without issue.

If I read the *.his files in the SP-Datens for E60, do you think I can use those with WinKFP and let it pick a proper module to at least get me back to a working state?

 

Looking at that would be like looking for a needle in a hay stack. If anything use .dat file to have a chance in finding the correct ZB