[bmw335coding]

Update: Brand new JBE, same problem -.-

[zeronoo]

New jbbf and no ignition -> bad cas/key...you can leave entire car modules disconnected except cas and jbbf and must have ignition working, try reprogrm/recode cas with proper zbnr

[bmw335coding]

New jbbf and no ignition -> bad cas/key...you can leave entire car modules disconnected except cas and jbbf and must have ignition working, try reprogrm/recode cas with proper zbnr

Yes, i try another used CAS and another key that matched to cas and iginition goes on.
Problem now is the old CAS can not reprogram with WINKFP or ISTA/P, its faulty.

I try to read the old CAS eeprom with r270 to have the isn, vin, odometer and keys.
Then i write to complete eeprom dump the new "used" CAS, its with same processor 0L15Y.

Now the problem is no ignition with both keys, must i modify the eeprom dump from the old cas to new used one cas?!

[zeronoo]

Well..i still belive that you can flash bricked cas with winkfp...hint: leave blinkers on

[lonja]

Paste here, acting cas, and the reading of the original cas of car

[bmw335coding]

Well..i still belive that you can flash bricked cas with winkfp...hint: leave blinkers on

i select right zusb from ista/p measure plan, choose correct vin and then program, there comes "ifh09-error" because the ignition is on..

[lonja]

It works or not?

---

Paste here, bin acting cas, and bin original cas of car. eprom+flash

[bmw335coding]

No, not working.

[HestonDiag]

Sorry to repeat myself, but you sure you replaced JBBF with correct type?

Sorry I've never been in this exact situation before but here are some thoughts on things I would be doing:

Check whether NCSExpert can communicate with CAS and FRM. (May need to manually switch KL30 to allow this).

You may be thinking because JBBF not programmed, not allowing comms to these units. But these are what holds the VO. If we cannot communicate to either unit, then we will never be able to read the VO to know how to code the JBBF.

I haven't read the documents to confirm this, but here is my line of thinking:

JBBF is gateway module for the car, then JBBF has link(s) to OBD port. Let us imagine for example the car was working but had a replacement new CAS fitted instead. The new CAS would not power things on and off until it is programmed, but the JBBF would still allow us to communicate with the CAS to program it (and the FRM to read the VIN/VO to copy to the CAS).

If we cannot even get any data link to the JBBF, then my thinking is to ignore the various buses in the car, and concentrate on link between diagnostic tool and JBBF which is just direct lines from JBBF to OBD port.

If NCS can communicate with CAS/FRM, use WinKFP to program CAS, then code CAS via NCS.

If no communication, try INPA to see if you can read AIF/UIF, and if you can connect to JBBF.

If you have communication with INPA, then try again to program using ISTA-P or WinKFP.

If no communication with INPA, load up WinKFP, there are options (I think button called diagnostic mode or something like that), even if module has no software but has a bootloader you should be able to query the module using this.

If you still have no reply from the module then only a few possibilities that spring to mind:

Wrong JBBF
Defective replacement JBBF
Wiring fault between JBBF and diagnostic port
Incorrect power to JBBF
Faulty Diagnostic tool (software/hardware)

[bmw335coding]

CAS is totally fault.

Try another used CAS3, the ignition goes on, but isn/vin doesnt match.

But the try to edit to old dump for the "new" cas is so difficult.