Oh boy! I didn't know that!

Don't bother writing in a blank .man file then, it won't help.

 

Went and got a v41 read of kombi, and compared it to my archived version. The new version has 3 additional options at the bottom, otherwise, they are identical. Went ahead and reset the module with v41 while I was out there, but the problem still exists. Next step is to double check cas, as that was the other module I was adjusting yesterday.

 

You say you reset the module, which I assume means you recoded with a blank file...

Have you used INPA? If you do, it will tell you which module has registered the error and is includes a small description of the errror.

Now that I come to think of it, it cannot be the KOMBI module. The KOMBI just reads the errors from the other modules and displays a warning, but the error isn't necessarily stored or caused by the KOMBI. I.e. when you get a CEL, it shows on both the CCC and KOMBI but the actual error code is stored in the DME. So if the problem is no more, you need to delete the error memory of the DME not KOMBI or CCC.

With INPA you can delete the error memory, which is NOT cleared with a reset of the module. My guess is that the error is stored in the FRM module.

PS: You need INPA EA 90X for the R56

 

I have INPA 5.0.2, but it doesn't do anything. I get a screen with info, script, and end as options. Info doesn't say anything, script can't find any. I guess I have more reading to do .

 

Got INPA running, cleared the errors, problem still remains. Re-reading errors after clearing them, KOMBI shows 5, everything else is clear. The kombi errors sar A3C0, A560, A562, A568, and A571. I couldn't find anywhere a description was given. Maybe I'm missing something.

 

Don't go to functional jobs for the R56, but go to the script for the KOMBI module (Body->Instrument Cluster). There you will receive a more detailed report.

 

I got more details, but I don't understand them enough to make sense of it. Having the hardest time making sure I have the right platform for v41. There are so many different variants and how-tos out there it is difficult to make sure everything is the correct piece of the puzzle, especially for INPA. Attached is the more detailed error report.

 

I've fiddled all day, and am no closer to finding why it thinks it has a spoiler and why that spoiler is stuck. I have 2 modules I still can't read in NCSExpert, 2MULF and DSC. INPA gives version mismatch errors and language errors, but appears to work otherwise. I guess I'm headed back to the dealer with my tail between my legs next week.

 

The 2MULF is the bluetooth module so that isn't the problem. DSC could be throwing the spoiler error, I am not sure what module would control the spoiler. But I don't know how the DSC would have gotten changed if you can't even read it.

The error report you attached just shows low battery warnings.

Did you verify your VO string in both your FRM and CAS match and seems correct based on your model and engine, and accessories?

 

Yeah, the VO looks good. Checked that out yesterday, just forgot to post about it. I charged the battery and checked the errors again a few minutes ago. Here are those results and my VO.

R56_#1207&K8E1%0A60*MF73$1CA$214$249$255$2RG$2VB$3 13$314$319$322$329$345$383$403$431$441$450$473$481 $493$494$4A7$4AA$4AU$4BD$4UF$520$521$534$550$563$5 AA$5DD$645$693$694$6FC$6FD$6NE$842$845$853$876$8SM $925-B055-EWS4

 

"9317 EEPROM: Fehler Codierdaten BMW"

I would concentrate on this error, as it may be the mother of them all! It says pretty cleanly that the coding data used is WRONG! All other errors may result from this one...

I would recode the whole car with blank files, now that you have v41 there... The best thing to do is install BMW Standard Tools 2.10 and then use the "LADEN.BAT" file from the GDATEN folder of R56_v41. Finally make sure you copy the ECU folder from the Datens to EDIABAS and that you update NCSExpert. For these datens you need EDIABAS 7.20.

Ohhh and for the DSC: There is a problem with it in NCSExpert, because it confuses the ASC with the DSC (optional upgrade). I haven't solved that yet, but don't care about it either, just dont code that module. Recode FRM, CAS, KOMBI and perhaps SPEG.

Finally, if you fail, just take it to the dealer to recode it with the latest official datens. I haven't seen anything newer than v41 floating on the net for the R56.

 

I am starting from scratch again with Standard tools 2.10. When I do that, INPA has no scripts or options loaded. How do I install the datens and scripts into INPA? That seems to be the piece of the puzzle I am having the hardest time finding.

 

As far as I know INPA is independent from the rest of the tools. The scripts used, are not the ones provided in the Datens. You may need to reinstall INPA after the Tools are installed and updated.

 

What is your value in CAS for BAUREIHE? Mine has 2 values choosen and won't reset to only one. r56 and r58.

Spent alot of time installing dis v44, only to discover it doesn't nothing for a r56. Looking into updating it to v57 and progman now.

 

Don't bother with Progman. Too old. You have to use ISTA/P now.

I don't think that DIS will be able to fix your problem, but it may help identify it. DIS v57 works great for me.

 

Section from my CAS C06 coding index.

That R58 entry is MOST suspicious since that is the model with the spoiler.

 

I am not totally confident, but I so believe INPA does require the daten CPU files in the EDIABAS CPU directory to function properly.

 

DIS says it is a KOMBI error, no other problems with any other modules. On the plus side, I was able to get CA to recognize my new fob I ordered the other day. On the minus, the dealer programming costs I just avoided I will probably have to spend to get KOMBI fixed. I think only a full recode of the module is going to fix it at this point.

 

So now I see that V41 datens are in fact the 0712 version. Using WinFPK or Tool32 maybe you can reset the module without a dealer trip. Check out R56AT.000 file.

 

Now I get to read and learn about those 2 tools. My brain is starting to hurt. I'm going to suck at work all week.

 

After looking through the ZB numbers in winkfp and inpa, I can safely say whatever they coded into my car last week is higher than v41. My ZB for kombi is currently 9260588, the highest in v41 is 9243890. The same situation for the other modules they updated. I guess I will try to hunt down the v43 datens. On the plus side, a reset will probably work just fine once I get the proper datens, now just to find them.

 

You are probably right! Good work finding that out.

Not sure what the dealer would charge you, but you may want to get a Mongoose J2534 tool so you can connect to minitechinfo.com ISTA/P and do the update and fixes yourself (instead of going to the dealer). Minitech info has the absolute latest vehicle software version.

 

Patience... v43 should pop up sometime soon

 

Nice! It sure did! :-)

I did confirm the posted version is updated! The R56AT.000 file is dated 6/22/2011 (versus 12/20/2010 for v41).

Juppers, I hope these work for you! As I did find 9260588 listed in the kmm_SG.txt file!

 

Am I missing something or just slow. Where have you found them? More importantly, where can I find them?