Ews 3.3 in E30M3 diagnostic problem.

[Eyestorm]

Hello

I have fittet the S54B32(E46M3) engine in mye E30M3 and Im having trouble communicating whit the EWS 3,3...

My wiring:
EWS pin 4 -> DME x60004 pin 33
EWS pin 9 -> ground
EWS pin 10,11 -> Power supply
EWS pin 13 -> K-Line


I dont use the E46M3 IKE.

I have tried with Inpa, Tools32, BMW Scanner 1,4, BMW ISTA, NCS-Expert and Autologic. No one can get accsess to the EWS 3.3.

Anybody in here that can confirm that I need the IKE to get accsess til EWS or if there is any other way to get accsess so I can sync the key whit DME.

Brg
Eyestorm

[328 Power 04]

Don't you just want to delete ews in your dme? It's incredibly easy for the mss54 dme.

[Eyestorm]

Yes I know its easy to remove EWS but I dont want to do that. I dont want to do it the easy way like everybody else is doning.

[328 Power 04]

Ok, well the diag line for ews is a simple K-line and does not need to have any other modules to communicate through.

As long as it's wired correctly, it should communicate even on desk.

You can also try to change the ews mcu memory directly using an mcu programmer tool to match the keys.

[Eyestorm]

Ok!. I have installed the S54 engnine and Mk60 whit steering angel sensor, G-sensor. There is no problem to communicate whit diagnostic programs whit them so the K-line is workgin that for sure. EWS boks have k-line at pin 13.

I dont understand why I cant accsess EWS.
Do you know how it has to be wired to work or what program I need to use?
See my first post on top how I have done it now.

[Eyestorm]

Erro in Tools32 when I try to accsess EWS is:

EDIABAS Error 19 : IFH-0009: NO RESPONSE FROM CONTROLUNIT

[328 Power 04]

Make sure it is powering up correctly. I think it will block diag access if there is a key mismatch, but I am not sure. You may have to change MCU data to match the key, and set the current key ID as unused, to be able to reset rolling codes.

[Eyestorm]

Im realy sure power is ok.. 12v at pin 10 and 11. Eart at pin 9. Key, EWS boks and DME is from same car but its taken out for many years ago. It was ok when it was tanken out. I hink I only need to sync key to DME aganin but not sure..

[gpeterson]

Ok, well the diag line for ews is a simple K-line and does not need to have any other modules to communicate through.

As long as it's wired correctly, it should communicate even on desk.

Incorrect, the EWS lives on the i/k bus, *not* the diag bus K line. The cluster acts as a gateway and translates messages between the two. This document isn't for the E46, but page 18 shows how the i/k bus is separate from the diag bus: http://www.e38.org/bussystem.pdf. Page 14 describes how the cluster gateway function.

You can temporarily wire up any E46 cluster to translate messages for diagnostic purposes or build an adapter via Arduino. I wrote code for the latter and probably still have it somewhere if you are interested. You would need a bit of additional circuitry (2x MCP2003 transceivers) as well.

BTW - MK60 will not be happy without some CAN messages that it expects the cluster to send. ABS will work but DSC will not. Please PM me if you would like help with this.

[328 Power 04]

Thank you for the correction, excellent info!

[TerraPhantm]

You can temporarily wire up any E46 cluster to translate messages for diagnostic purposes or build an adapter via Arduino. I wrote code for the latter and probably still have it somewhere if you are interested. You would need a bit of additional circuitry (2x MCP2003 transceivers) as well.

You can also just add "mode=kbus" to OBD.ini in Ediabas - that'll allow you to communicate with I/K-bus devices on the bench without needing a translator.

[gpeterson]

You can also just add "mode=kbus" to OBD.ini in Ediabas - that'll allow you to communicate with I/K-bus devices on the bench without needing a translator.

Thanks! I didn't know about that option.

[e36 323ti]

You can also just add "mode=kbus" to OBD.ini in Ediabas - that'll allow you to communicate with I/K-bus devices on the bench without needing a translator.

Has anyone succeeed with this?

According to the Ediabas document ini.pdf with MODE=KBUS in obd.ini, DS2 telegrams are converted into KBus telegrams, but the communication is only permitted to the individual DS2 control unit on the KBus.

With an e46 m3 ike and ews3 on the bench as well as communication analyzers to see what is transmitted on both the KBus and the DS2Bbus, there seems to be no change in what is transmitted on the DS2Bus (DS2Bus = Diag KBus) when changing mode and using Tools32. The messages on the DS2Bus is only DS2-format.

[TerraPhantm]

Has anyone succeeed with this?

According to the Ediabas document ini.pdf with MODE=KBUS in obd.ini, DS2 telegrams are converted into KBus telegrams, but the communication is only permitted to the individual DS2 control unit on the KBus.

With an e46 m3 ike and ews3 on the bench as well as communication analyzers to see what is transmitted on both the KBus and the DS2Bbus, there seems to be no change in what is transmitted on the DS2Bus (DS2Bus = Diag KBus) when changing mode and using Tools32. The messages on the DS2Bus is only DS2-format.

I haven't tried with an EWS module, but it worked fine for other modules. The cable has to be physically wired to the K-bus rather than the D-bus for communications to work properly.

Main use is if you want to communicate with something on the bench without having an IKE or other translator.

[e36 323ti]

I haven't tried with an EWS module, but it worked fine for other modules. The cable has to be physically wired to the K-bus rather than the D-bus for communications to work properly.

Main use is if you want to communicate with something on the bench without having an IKE or other translator.

Yes, the wiring part is obvious
Can confirm that it also works for the ews. Had to edit the correct obd.ini (the one in the windows folder)...
By using the comm analyzer, the switch of protocol is easily verified...

However, if one would like to sync ecu and ews on the bench, I imagine one still need an ike or a device taking care of the switch of protocols.

[TerraPhantm]

Yes, the wiring part is obvious
Can confirm that it also works for the ews. Had to edit the correct obd.ini (the one in the windows folder)...
By using the comm analyzer, the switch of protocol is easily verified...

However, if one would like to sync ecu and ews on the bench, I imagine one still need an ike or a device taking care of the switch of protocols.

That's probably true. I suppose one could also use an EWS-IIID from a Z3 (which is the same thing but communicates over the D-bus if I'm not mistaken)

[e36 323ti]

That's probably true. I suppose one could also use an EWS-IIID from a Z3 (which is the same thing but communicates over the D-bus if I'm not mistaken)

I already have a Dbus interface as an option in my MK60 emulators, and my plan is to add a Kbus interface to do the protocol switch in the emulator. With only the ews on the Kbus one also need to emulate the master control of the Kbus (some kind of pullup of the line).

EDIT: With MODE=KBUS, EWS Kbus hooked up to ECU Dbus, ring antenna to EWS and key, the sync goes as it is supposed to from Tool32.