|
1 Attachment(s)
Thanks fellas. I'll definitely post some victory pictures if I get this sorted.
Clavurion, I've edited the ZCS (SA bit changed) and verified it has taken in both the KMBI and the EWS. However when I go to code the entire car, it errors out ("Error when changing ZCS") on the DXC module. Other modules will code fine if I do them individually. But I want to code the entire truck without fear of missing a module. Do you know if the EHCII module needs to be in the truck to code everything else? I removed it prior to coding but am going to reconnect it now to see if it changes anything. The DXC (DSC I'm guessing?) does use info from the EHC module sooooooo maybe that's the hangup on that module? Edit: It's the TCU that is error'ing out (which makes sense because it's not installed). The DXC coded individually. So seems my problem is I need to remove the DSP, TCU, and anything else I removed from the truck from my ZCS in order to process the entire truck. Sounds like fun. :rolleyes: :( But at least it makes sense. "antwortet nicht" translates to "does not answer." Attachment 79035 |
Quote:
|
Quote:
|
Quote:
I have friend/moderator over on E46F that does it for free if you want but he has listed the process here. https://www.e46fanatics.com/threads/...pdate.1081716/ |
Programming/flashing and coding parameter value changes are totally different things. Changes when removing EHC2 are strictly coding. On these EGS and DME/DDE can't be coded (the only modules which can be updated with different software version) but also no need regarding EHC2.
|
Thank you for clarifying gentlemen. Totally new to this so I'm enduring the learning curve at the moment. :thumbup:
OB thanks for that link. I'll do some reading. |
Quote:
|
Okay, status update. It appears the EHCII is completely gone from the system. No reference to that module anymore in NCSexpert. I do have a no communication error in the DSC (DXC) though and that is tripping the trifecta. I thought it was because I had not coded the transfer case (VTG) as it was also throwing an error so I did that. No luck.
Do I need to calibrate the VTG/DSC/LWS or some other module now after coding? On the plus side. Since unplugging the EHCII module my battery drain is completely gone. Put in a new battery yesterday and when I went to bed the truck was sitting at 12.8v and this morning was basically the same at 12.79v. Before, the truck would go from normal voltage to 10v almost overnight. I'm sure it put the old battery into an early grave, though I am trying to slow charge it to bring it back to life for other uses. Edit: Error code on the DXC8 is 5EB7: Variant Coding, Code again Only code left. Looks like I'm not the first to try to cross this bridge. https://xoutpost.com/bmw-sav-forums/...eird-code.html |
5 Attachment(s)
Update 2 for today. Can not get that code to go away through any method but plugging the EHCII module back in. As soon as I do that everything is hunky dory. But my ride height LED's start blinking again and presumably my draw would return. My head is starting to hurt...
Here's what's going on: Attachment 79042 INPA Error (reports same on Foxwell of course) Attachment 79038 DXC module initially shows DXC8_E53.C01 and then changes to DXC8_E53.C04 as shown below. It will change after executing any job (coding or reading) but always reverts back to DXC8_E53.C01 when I return. Is that normal? Attachment 79039 Attachment 79040 Here's what the coding options for the module look like. Seems like everything is correct. :dunno: value_11 is for the correct engine and minus EHCII as shown in some of the other options. Oddly there is no option for N62B48 w/ EHCII. Only N62B44 and all the other E53 variants. Attachment 79041 |
Quote:
|
| All times are GMT -4. The time now is 11:46 AM. |
vBulletin, Copyright 2026, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.6.0
© 2017 Xoutpost.com. All rights reserved.