EWS sync without installing EDIABAS/INPA/DIS using a $10 vagcom cable

[jdjg]

I can't confirm as I've never used PaSoft BMW Scanner, but I'd guessing that it won't be an issue.

as you know, the EWS came LOCK from factory, you can't unlock the EWS..... maybe with this program, can I unlock the EWS??

[gpeterson]

My cables arrived.
On the first try, the program didn't find my COM port. I shut the program and started it again and it found it.
The program said it worked- I pushed the first button and it found ba7 as the ISN code.
I pushed the second button and it wrote it to the EWS.
It prompted me to turn the ignition key off for 15 seconds.
I turned the key off, disconnected my cable and put the port cover back on.
A few minutes later I turned the key and I hear no starter.
I repeated with the same results.
Since I just put this engine in, it could be something else- but I have no idea what it could be.

Not sure why I didn't think of this yesterday... if EWS isn't in sync the car will crank but not get spark/fuel, so your car not cranking isn't related to EWS sync.

- - - Updated - - -

as you know, the EWS came LOCK from factory, you can't unlock the EWS..... maybe with this program, can I unlock the EWS??

No, it won't unlock EWS. That would require re-flashing the DME with new software that has been modified.

[DaveAZ]

Not sure why I didn't think of this yesterday... if EWS isn't in sync the car will crank but not get spark/fuel, so your car not cranking isn't related to EWS sync.

I just read the BMW EWSII description: http://www.docstoc.com/docs/40351318...andthe-EWS-BMW and you are correct. I came up with a way to test if it is the EWS is disabling the starter, so I'll give that a shot tomorrow. I obtained INPA and still need to set it up on my computer, too.
Thanks again!

[bram2011]

Update:
After ews syn successfully, car won't start.
The problem is new ISN address different with original ews.
So ISN EWS different with ISN DME.
ISN DME = 4B8
ISN ISN = B48

[gpeterson]

Update:
After ews syn successfully, car won't start.
The problem is new ISN address different with original ews.
So ISN EWS different with ISN DME.
ISN DME = 4B8
ISN ISN = B48

Ok, I'll try to get a different version of the app out today that will write log files for debugging purposes. Reading the ISN from the DME the way INPA does it is a bit weird, they encode it oddly and I figured there may be issues with my implementation.

What did you use to pull that binary file?

[bram2011]

Ok, I'll try to get a different version of the app out today that will write log files for debugging purposes. Reading the ISN from the DME the way INPA does it is a bit weird, they encode it oddly and I figured there may be issues with my implementation.

What did you use to pull that binary file?

I read a binary file with mcu programmer.
Here binary file from ews2 8375840 hw02 sw02.
(hint: delete .txt to get binary file)

[1980corvette]

any luck on this?

I'm not having much success with my INPA, I guess the first problem is installing the driver for the vagcom cable, then getting it on the right COM port.

and I wanted to align my ews2 before spring break was over to get my S/C on : (

[gpeterson]

any luck on this?

I'm not having much success with my INPA, I guess the first problem is installing the driver for the vagcom cable, then getting it on the right COM port.

and I wanted to align my ews2 before spring break was over to get my S/C on : (

Did you try my app yet? I'll probably have a new version out today, but the old one should work in most cases.

[1980corvette]

Did you try my app yet? I'll probably have a new version out today, but the old one should work in most cases.

no, is there a download site for it?

also would i have to modify my vagcom cable? ive seen some solder pins 7&8 together...

and i'm currently downloading the drivers for my vagcom cable for windows 7 through FTDI chip.

[gpeterson]

no, is there a download site for it?

also would i have to modify my vagcom cable? ive seen some solder pins 7&8 together...

and i'm currently downloading the drivers for my vagcom cable for windows 7 through FTDI chip.

Download link is in post #6, I can't remember about soldering pins 7 & 8 but no harm to give it a try.

- - - Updated - - -

I just created a new version, you can download from the same link.

bram2011 - can you please try the new version? It will create a log file (EWSLog.txt) in the same directory as the exe. If you get a chance can you please read the ISN from your DME then PM the log contents to me?

[enda320]

EWS can be strange in the way it is implemented.
In the older cars, like the 325i M50, 318iS M44 etc you get something like this in the binary data-

Hex values (0-FF)

30 30 30 31 35 33 30 38 39

Convert that to ascii (almost all hex editors show it at the side) and it looks like 000153089
I've been following through those files, and that number counts up with age, 000004435 would be a younger car for example.

Take the last 4 digits, 3089, and convert from decimal to hex again, and you get C11
http://www.mathsisfun.com/binary-dec...converter.html

That's the ISN, and that will usually be found in the EWS dump hex as 0C11.

I would assume the program does a "call", ie it will ask the ECU for the ISN and not just read a certain area, because as you can see, the ISN of C11 isn't written in the file.

Hex converts to Ascii, Ascii is treated as a decimal number, and that decimal number is converted back to hex.
Newer ECUs just writes the ISN in hex.

It might not be interesting or useful to the majority of people who just want to sync an ECU, but it you have a chip file from an older Bosch ECU, Look for that 9 digit ascii string starting with a few zeros near where the hardware and software numbers sit, and use the method of treating the ascii as decimal, and converting to hex to read the ISN.

[KevinMullins]

I'm not having much success with my INPA, I guess the first problem is installing the driver for the vagcom cable, then getting it on the right COM port.

It would be easier to troubleshoot if you told us what it "DID" do in INPA.
Aside from modifying the cable there are a few minor software steps that tend to get skipped and it won't work right.
Also knowing what version of INPA you are installing would help as well, I would start with v3.01 and go from there since some of the "updates" to v5.02 will screw things up.
You should have no problems reading a 98' once it's setup properly.
After getting INPA going...then... I would try the EWS stuff.

[gpeterson]

It would be easier to troubleshoot if you told us what it "DID" do in INPA.
Aside from modifying the cable there are a few minor software steps that tend to get skipped and it won't work right.
Also knowing what version of INPA you are installing would help as well, I would start with v3.01 and go from there since some of the "updates" to v5.02 will screw things up.
You should have no problems reading a 98' once it's setup properly.
After getting INPA going...then... I would try the EWS stuff.

I disagree about INPA first... the reason I wrote the app is so that INPA wouldn't be required to sync EWS.

[1980corvette]

It would be easier to troubleshoot if you told us what it "DID" do in INPA.
Aside from modifying the cable there are a few minor software steps that tend to get skipped and it won't work right.
Also knowing what version of INPA you are installing would help as well, I would start with v3.01 and go from there since some of the "updates" to v5.02 will screw things up.
You should have no problems reading a 98' once it's setup properly.
After getting INPA going...then... I would try the EWS stuff.

actually I just got the drivers done for my vagcom, at first it was error 0018, but now after re-installing and what not I am able to view my ISN for the EWS2, just not sure the procedure after that....I don't want to thread jack Gpetersons awesome work, but if someone would lie to pm me

p.s. I will still try ur app

[KevinMullins]

I disagree about INPA first... the reason I wrote the app is so that INPA wouldn't be required to sync EWS.

My point is that would make certain the hardware (cable) is working.
INPA has lots of support here using the vagcom cables. No sense in testing your app if his hardware isn't even working...because then obviously your app wouldn't work either.

[mrf]

Stuff like this makes me smile!

Nice work!

[1980corvette]

i have had Success syncing my S/C tuned MS41.1 using this app.

thanks gpeterson!

[gpeterson]

i have had Success syncing my S/C tuned MS41.1 using this app.

thanks gpeterson!

Nice, good to hear! Thanks for trying it out.

[Stück]

I just wanted to take a second and give you a big THANK YOU.

I had been trying to align EWS to a new DME on a customers car for almost an hour with DIS and INPA to no avail. Tried Progman and that too failed and gave an error.

Your program worked, and in like 3 seconds.

97 528i /w S52 swap and matching e36 M3 DME.

Win7 64bit /w vagcom cable and self made 20pin adapter.

[gpeterson]

I just wanted to take a second and give you a big THANK YOU.

I had been trying to align EWS to a new DME on a customers car for almost an hour with DIS and INPA to no avail. Tried Progman and that too failed and gave an error.

Your program worked, and in like 3 seconds.

97 528i /w S52 swap and matching e36 M3 DME.

Win7 64bit /w vagcom cable and self made 20pin adapter.

Nice, glad to hear it worked for you.

[zied]

woow Excellent work mate

Have tested with my 318is M44 (Bosch M5.2 ECU) it's reading my ISN in 3 seconds !!!
haven't tested writing ISN because my ECU-DME are already aligned.

I will test it later with my friends 328i (M52) we couldn' sync EWS with DIS.

This will become soon a must have tool !!!

By the way how is The Key/EWS sync working in E36 ??
for example if i replace my EWS, sync with DME will just take me 3 seconds with this tool, but how can i sync my old keys to the new EWS ?

Thanks

[enda320]

You won't be able to reuse old keys with a different EWS unit, so keep them together.

[zied]

You won't be able to reuse old keys with a different EWS unit, so keep them together.

How the dealer add keys to an EWS Module ?

@gpeterson : I want to understand a bit more how it is handling errors, for example if the EWS writing is unsuccessful does it throw an error message ?
and also i want to know if there is a way to add reading ISN code from EWS ? This will be very helpful to identify if the problem is either from EWS module, keys or DME.

Zied.

[mrf]

and also i want to know if there is a way to add reading ISN code from EWS ?

I second this. Maybe a 'Verify EWS' from the EWS module?

You can use BMW Scanner v1.4 to add/remove keys I believe. I remember seeing the menu for that and the keys listed but haven't personally messed with it.

[bram2011]

BMW scanner 1.4 / 1.36 can't add/remove keys.
This function for disable/enable keys.

- - - Updated - - -

Download link is in post #6, I can't remember about soldering pins 7 & 8 but no harm to give it a try.

- - - Updated - - -

I just created a new version, you can download from the same link.

bram2011 - can you please try the new version? It will create a log file (EWSLog.txt) in the same directory as the exe. If you get a chance can you please read the ISN from your DME then PM the log contents to me?

Now, software working perfect.
Here my logs: