Taking CSL Airbox Back to Stock -- Wiring?

[ATB88]

It's smog week for me in CA, and I got cocky tonight and threw myself into doing the swap without carefully researching how to undo the DME wiring modifications. I have a MAP sensor and IAT was done using one of those adapter harnesses that just plugs into the MAF's harness connector.

Stock box is back in and all mechanicals are back in place, MAF sensor plugged in, and old non-CSL DME is back in place, but car won't start. Cranks once and dies.

I'm guessing is that there's some wiring I have to restore, but I'm scratching my head as to what. The IAT adapter harness is removed, which leaves the MAP. If I recall, the MAP is wired in by splicing into two existing wires, and then the third gets added to a pin on a DME connector. Shouldn't just unplugging the MAP sensor be sufficient to undo this? If all three wires are dead/unplugged from the MAP, it doesn't matter that they're still spliced/pinned in right?

Any sanity checks here would be appreciated!

[ATB88]

As for the DME itself, if I have my original DME that had stock software on it, it's as simple as just popping that one back in right? no additional coding needed to get it to start or play nice with the EWS module?

[heinzboehmer]

If the EWS is functional on the stock DME, then you need to resync. Can be done with INPA. EWS delete on the DME will also work.

[ra2fanatic]

Unplugging the MAP should be fine. Sounds like you also need EWS delete on your stock ECU. I had the issue a few weeks ago when I smogged.

[ATB88]

Yeah okay given behaviour makes sense that it's the EWS.

I guess my question is: why? EWS was synced to this DME before the swap, and I think my CSL DME has an EWS delete. Why would the original DME and EWS have unsynced?

[heinzboehmer]

Why would the original DME and EWS have unsynced?

They shouldn't have. Are you sure the EWS was deleted and not resynced on the CSL DME? What codes are stored in the stock DME?

[ATB88]

They shouldn't have. Are you sure the EWS was deleted and not resynced on the CSL DME? What codes are stored in the stock DME?

Ah, yeah I bet this is the case actually. I'm now starting to faintly recall re-syncing the EWS those two years ago. Upsettingly, my Schwaben scan tool doesn't seem to want to do the re-sync for me, and I haven't been able to find my K+DCAN cable with the two pins soldered together to work with INPA since moving, just an older cable I used for my old Audi that doesn't have the pins soldered.

This is what I get for hubris, I guess.

[ATB88]

Found my good K+DCAN cable.

INPA is throwing errors at me whenever I try to go into the EWS resync menu (shift + F6 from the main S54 menu). Sadly, my INPA laptop might be biting the dust, the USB connection seems very unstable.

Anyone in Pasadena have a reliable coding laptop and cable willing to re-sync my EWS for $50 and a beer? Can also promise an unbeatable view

[heinzboehmer]

Found my good K+DCAN cable.

INPA is throwing errors at me whenever I try to go into the EWS resync menu (shift + F6 from the main S54 menu). Sadly, my INPA laptop might be biting the dust, the USB connection seems very unstable.

Anyone in Pasadena have a reliable coding laptop and cable willing to re-sync my EWS for $50 and a beer? Can also promise an unbeatable view

Try DIS or tool32. I've had it happen before where INPA doesn't want to sync the DME. You could also flash a stock binary with WinKFP and then retry syncing with INPA.

Some resources:
https://nam3forum.com/forums/forum/s...one-dme-solved

http://www.cslregister.com/forum/showthread.php?t=12750

Are there EWS codes stored in the DME?

[ATB88]

Right, so, DME has fault 130, "EWS 3.3 tampering protection". INPA gives me the same error as the guy in the first thread was getting, "error_SG_rejected".

I tried using MSSFlasher to read out a partial binary to just do an EWS delete on it, but it failed partway through, which has removed my confidence in my coding laptop to be able to make it through a re-flash without possibly failing and bricking my DME. It had never failed me to date, but had been in a drawer for the last 2 years, but to be fair, it's pretty old and the USB ports are very beat up.

I'll try tool32, thanks!

[ATB88]

In the first thread, Terra instructs the poster to "Load the EWS3 prg, do the "wechselcode_sync_dme" job, then switch to the EK72 prg, and do the steuern_sync_mode job with the argument 0x01"

I can do the EWS3 prg "wechselcode_sync_dme" job, but I'm wondering if the EK72 part is particular to the chassis that the poster in the thread is asking about? (land rover)

For example, if I load the prg file "12MSS54.prg", the steuern_syn_mode job only offers a single argument possibility, 0x3F. In my case is that what I should be doing? [EWS3.prg "wechselcode_sync_dme" job] -> [12MSS54.prg steuern_sync_mode job with argument 0x3F]?

terra in case you're around and know the answer

[ATB88]

Got it running.

For anyone who needs to use Tool32 to do this in the future:

Open Tool32 --> File "select PRG file" --> EWS3.prg --> select "wechselcode_sync_dme" from job list --> go to "job" menu tab at the top and tell it to carry out the job once --> File "select PRG file" --> MSS54D0.prg --> select "steuern_sync_mode" job --> *manually* enter the argument 0x01 into the argument box --> go to "job" menu tab at the top and tell it to carry out the job once

After each of the two jobs make sure it says status OK in the results box.

Then unplug everything, take the key out for 15 seconds, then start it up!

[heinzboehmer]

Nice! Thanks for documenting for everyone else. Never done it with tool32 myself, so good to know for the future.