[sdbmwcoding]

Originally Posted by mxwaymire

Tried that before but any turn pops one error or the other.

Comfort (F1) > Update ECU (F3) > Select any ECU Family + Integration Position = Error message below;

https://gyazo.com/1db9cd1af508324d14b4c1468071a70f

Setup on 3 laptops using different files/downloads all the same.

Update winkfp daten's. Also find you correct CAS ecu from inpa to choose

[Sensible_]

Can you flash other modules? Try a quick one like the KOMBI for example. If you get this error on other modules then it's a problem with your setup.

[mxwaymire]

Originally Posted by Sensible_

Can you flash other modules? Try a quick one like the KOMBI for example. If you get this error on other modules then it's a problem with your setup.

So I was able to get WINKFP to work eventually.

Did a quick test on a couple of modules which prompted current vs update version. I clicked NO as I was not ready to flash those modules.

So i proceeded to program the JDE/JBBF it ran smoothly to 100% until it threw an Error 211 (Error o flash programming).

https://gyazo.com/ba7a25ca4ae96ab9da6a0f9a4c26d7a5

After the error I closed the app to check what INPA was showing. I could see only the JBBF module which I had just flashed in my INPA UIF.

Now cas is not reachable via INPA, WINKPF or any other application.
Now remote doese not lock car and many other fuctions are off.

Tried to program the CAS via WINKFP but it cant detect/reach CAS.

Attached is what my new UIF page looks like.

Seem I am in more mess than before. What to do please?

[Sensible_]

Originally Posted by mxwaymire

So I was able to get WINKFP to work eventually.

Did a quick test on a couple of modules which prompted current vs update version. I clicked NO as I was not ready to flash those modules.

So i proceeded to program the JDE/JBBF it ran smoothly to 100% until it threw an Error 211 (Error o flash programming).

https://gyazo.com/ba7a25ca4ae96ab9da6a0f9a4c26d7a5

After the error I closed the app to check what INPA was showing. I could see only the JBBF module which I had just flashed in my INPA UIF.

Now cas is not reachable via INPA, WINKPF or any other application.
Now remote doese not lock car and many other fuctions are off.

Tried to program the CAS via WINKFP but it cant detect/reach CAS.

Attached is what my new UIF page looks like.

Seem I am in more mess than before. What to do please?

Did you flash with a power supply connected?

Seeing only JBBF after a flash can be completely normal.

Now use NCS and code the JBBF to default with a factory coding / expert profile.

[mxwaymire]

Originally Posted by Sensible_

Did you flash with a power supply connected?

Seeing only JBBF after a flash can be completely normal.

Now use NCS and code the JBBF to default with a factory coding / expert profile.

Yes I connected to power supply.

Is it normal for winkpf to throw such error after successfully programming a module?

[mxwaymire]

Originally Posted by Sensible_

Did you flash with a power supply connected?

Seeing only JBBF after a flash can be completely normal.

Now use NCS and code the JBBF to default with a factory coding / expert profile.

Quick Update:
I tried to code JBBF for default using NCSExpert but encountered error such as VIN Faultly.

Decided to give the JBBF flash another shot since that was the last modification which dint even seem to end well. After some WINKFP config changes and selecting a different ECU family (JBBF81), the flash was completed successfukky without any error.

This restored the car back to its semi-limbo state.

Now other modules are showing up in INPA.

Do i still need to to use NCSExpert to code JBBF to default or I should proceed to flash the CAS?

[Sensible_]

Originally Posted by mxwaymire

Quick Update:
I tried to code JBBF for default using NCSExpert but encountered error such as VIN Faultly.

Decided to give the JBBF flash another shot since that was the last modification which dint even seem to end well. After some WINKFP config changes and selecting a different ECU family (JBBF81), the flash was completed successfukky without any error.

This restored the car back to its semi-limbo state.

Now other modules are showing up in INPA.

Do i still need to to use NCSExpert to code JBBF to default or I should proceed to flash the CAS?

Technically you should code it. If you are confident then do it.

Yes, now try CAS.

Remember have the key out when you flash the CAS and have a power supply connected.

[mxwaymire]

Originally Posted by Sensible_

Technically you should code it. If you are confident then do it.

Yes, now try CAS.

Remember have the key out when you flash the CAS and have a power supply connected.

Done now. JBBF code to default and flashed CAS.
INPA UIF still showing old date for CAS while JBBF showing today's date.
CAS VIN in INPA also showing 0000000.
Is this normal?

My WINKFP setting setting did not ask for VIN number so my guess is that's why there is that odd number as VIN for CAS. Will this prevent the car from starting?

Steering lock on dash has gone and has not returned.

Car not starting yet though.

Do I need to reset the CAS to factory too?

The control unit tee image from ISAT+ below;
https://gyazo.com/12952029ba49ae60f1a5bd48fb25d27d

Whats next to get car started?

Many thanks so far

[Sensible_]

Originally Posted by mxwaymire

Done now. JBBF code to default and flashed CAS.
INPA UIF still showing old date for CAS while JBBF showing today's date.
CAS VIN in INPA also showing 0000000.
Is this normal?

My WINKFP setting setting did not ask for VIN number so my guess is that's why there is that odd number as VIN for CAS. Will this prevent the car from starting?

Steering lock on dash has gone and has not returned.

Car not starting yet though.

Do I need to reset the CAS to factory too?

The control unit tee image from ISAT+ below;
https://gyazo.com/12952029ba49ae60f1a5bd48fb25d27d

Whats next to get car started?

Many thanks so far

Show the fault codes please.

It looks like there is still no comms with the DME.

Have you checked fuses?

[mxwaymire]

Originally Posted by Sensible_

Show the fault codes please.

It looks like there is still no comms with the DME.

Have you checked fuses?

These are the fault codes as at the last check after CAS flash.

https://gyazo.com/75709b70f9a393cff2db26272bae2b22

Have checked the fuses before but need to check them again. The DME has been red for a while now but the whole issue dint start with the DME unreachable.

In a wild scenario that DME is faulty, can only DME be replaced without getting new keys and CAS?

[Sensible_]

Ok. Well this has ruled out your CAS. It's fine. Your JBE is also fine.

When did the no start problem start?

Have you physically checked the wiring around the DME and DSC? Check the DME relay and look for water ingress.

Yes you can replace the DME. But it's not easy.

Given that both DME and DSC have no comms it suggests maybe something else though.

Could be a break in the PTCAN or something as simple as a bad ground. ISTA will run you through the checks if you run a service plan.

Common ones are ground wire on motor mount, and the one that goes from the water pump harness to the front of the motor.

[dpaul]

Originally Posted by Sensible_

Ok. Well this has ruled out your CAS. It's fine. Your JBE is also fine.

When did the no start problem start?

Have you physically checked the wiring around the DME and DSC? Check the DME relay and look for water ingress.

Yes you can replace the DME. But it's not easy.

Given that both DME and DSC have no comms it suggests maybe something else though.

Could be a break in the PTCAN or something as simple as a bad ground. ISTA will run you through the checks if you run a service plan.

Common ones are ground wire on motor mount, and the one that goes from the water pump harness to the front of the motor.

Defer in general to Sensible's judgement. Seems the engine won't start because the DME is not listening or responding to CAS.

However, while I agree that CAS is in the clear but I wonder how you can rule on JBE. Yes, could be PT-CAN break but EGS is OK (to be sure, not clear on whether EGS is at beginning, end or middle of bus). Also, it seems like an odd assortment of modules that don't communicate and there is one persistent error message that (I think but am not sure) is related to a JBE function - A6D1. Of course, unless this is a diesel, I think there is no auxiliary water pump. So the error probably refers to a component that is not even installed.

Grounds are often the problem when a slew of errors without obvious relationship are encountered. But I admit to being confused.

[Sensible_]

Originally Posted by dpaul

Defer in general to Sensible's judgement. Seems the engine won't start because the DME is not listening or responding to CAS.

However, while I agree that CAS is in the clear but I wonder how you can rule on JBE. Yes, could be PT-CAN break but EGS is OK (to be sure, not clear on whether EGS is at beginning, end or middle of bus). Also, it seems like an odd assortment of modules that don't communicate and there is one persistent error message that (I think but am not sure) is related to a JBE function - A6D1. Of course, unless this is a diesel, I think there is no auxiliary water pump. So the error probably refers to a component that is not even installed.

Grounds are often the problem when a slew of errors without obvious relationship are encountered. But I admit to being confused.

The 320i N46 was indeed fitted with the auxiliary water pump.

As you probably know this part is junk and always breaks. It's an easy replacement though. Since that's the only fault on the JBE then I can only assume the JBE is functioning correctly.

The fact DSC and DME are not communicating is interesting. I don't know if they share the same ground.

[dpaul]

My bad, hadn't looked at the VIN/ID info listed by ISTA and to be honest, have never seen a 320i N46 - don't think those came to the US.

But I take your point, the JBE is likely correctly reporting an error.

I took a quick look at grounding locations on Newtis.com - that DME and DSC grounds are not obviously related (Edit: MRS unrelated as well).

DME:
https://www.newtis.info/tisv2/a/en/e...-x6454/iAT3kNL


DSC:
https://www.newtis.info/tisv2/a/en/e...511/1VnbhPr7F8
https://www.newtis.info/tisv2/a/en/e...ol-dsc/sRjIDjh

[Sensible_]

Interesting. Could be fuses / relay then I guess.

[dpaul]

OP:

In junction box (fusebox) behind glove compartment check DSC fuses F35 (30A), F65 (40A) and F20 (5A). Check DME fuse F54 (60A)

In DME enclosure check fuse F02 (20A - location A8680) and relay K6300
https://www.newtis.info/tisv2/a/en/e...200511/RfhxioW

[mxwaymire]

Thanks for the suggestions.
Out of town at the moment to return tomorrow.

Will check all theses in detail and revert ASAP.

[mxwaymire]

Back to the Beemer.

Checked all fuses and relays has specified. Also check the grouding.
All checked okay.

As I mentioned earlier the steering lock sign on the instrument cluster had gone away. When I insert the key no light on cluster, no icon, nothing at all.
If I hold the start/stop button for some seconds, the steering icon flashes back briefly then the airbag sign stays on. Could this mean anything?

With the steering lock flashing does it mean the ELV Counter error is back? Even with a successful CAS upgrade/flash.

Though upgrade/flash was successful the INPA UIF still popping the old info and firmware. (attached)

Focused more attention on the JBE. Removed it and had someone look at the device it was fucntioning 100%. Return with an IC fixed and here is what the ISTA Control Unit Tree looks like;

Before IC Fix:
https://gyazo.com/12952029ba49ae60f1a5bd48fb25d27d

After IC Fix:
https://gyazo.com/8135b4866cf02fab8814ef96fe44cb32


Before the MRS module was Red, FZD was Grey.
Now MRS is Grey, FZD Green

Attached are also some error reports from INPA.

[Sensible_]

Originally Posted by mxwaymire

Back to the Beemer.

Checked all fuses and relays has specified. Also check the grouding.
All checked okay.

As I mentioned earlier the steering lock sign on the instrument cluster had gone away. When I insert the key no light on cluster, no icon, nothing at all.
If I hold the start/stop button for some seconds, the steering icon flashes back briefly then the airbag sign stays on. Could this mean anything?

With the steering lock flashing does it mean the ELV Counter error is back? Even with a successful CAS upgrade/flash.

Though upgrade/flash was successful the INPA UIF still popping the old info and firmware. (attached)

Focused more attention on the JBE. Removed it and had someone look at the device it was fucntioning 100%. Return with an IC fixed and here is what the ISTA Control Unit Tree looks like;

Before IC Fix:
https://gyazo.com/12952029ba49ae60f1a5bd48fb25d27d

After IC Fix:
https://gyazo.com/8135b4866cf02fab8814ef96fe44cb32


Before the MRS module was Red, FZD was Grey.
Now MRS is Grey, FZD Green

Attached are also some error reports from INPA.

The CAS flash removes the ELV lock. BMW ditched this because of many problems and so it was removed by software update. Your CAS is fine.

Have you started checking the DME for power etc?

[RS DAVE]

Contact Thomas at BMW SPECIALIST CODING on facebook, if you have the kit he will be able to do a remote fix for you, i have a 335d with 6 speed manual conversion, he recoded the full car to manual mode.

[mxwaymire]

Originally Posted by Sensible_

The CAS flash removes the ELV lock. BMW ditched this because of many problems and so it was removed by software update. Your CAS is fine.

Have you started checking the DME for power etc?

Agreed the CAS is fine but should it still be showing old firmware and update date.

DME has power.

[Sensible_]

Originally Posted by mxwaymire

Agreed the CAS is fine but should it still be showing old firmware and update date.

DME has power.

If the UIF didn't update correctly then yes. It happens. Do you have that checked in winkfp settings?