[ateszaholdjaro]

Hey guys,

I did an FRM2 upgrade yesterday. I had halogen headlights, so i went with FRM2 NSW modul. I successfully did the VIN change with Winkfp, aswell as with NCSExpert, both FA and FG were matching, even did the production date change to #0307. After that I verified, everything was working as it should have been. With NCSDummy I programed the FRM2 modul just as I would love to, with welcome lights and all, everything was ok. Half an hour later I wanted to go for a ride, so I hopped in, put the key in, and when i wanted to start the car, dashboard just faded, after couple of sec it returned with DSC errors, after that it went back to error free state, ingition on. Tried it again, same thing happened. I used INPA to read UIF, when i realised that jbf module vin numbers was missmatching with any other.

So I used winkfp, programed the JBF module with the matching ZB nr(jbbf81), it went through. Used NCSExpert, CAS, JBBF, sg codieren with non manipulation profile. After that, I cant even have ignition on. If i want to turn on ignition, i have to power off the whole car for about 20 minutes, reconnect battery and i can turn on the ignition. But once i turned it off, i cant get the ignition on again, because when i push the button everything starts flashing on the dash, and just slowly fade after.

Any possible ideas, what did i wrong and how can i recover from this state?

[evominati]

Why is the JBBF VIN different?

[ateszaholdjaro]

That is a good question, the jbbf module wasnt touched either coded until i saw that the vin numbers were missmatching. After that i wrote what i have done to it.

The date of the software on the jbbf is interesting aswell, 08.08.2008. The car is 2005 january, i think it should show nearly the same date as any other module, expect FRM since that got coded.

Since then the car is off the battery, just in case, but no look to get the ingition working.

Just to clarify everything:

The whole thing happened like this: I have a 2005 E90. Originally, I had halogen reflector headlights, but for the past two years, I’ve been using aftermarket headlights with a projector for low beams and a reflector for high beams. I’ve wanted welcome lights on the car for a while since my aftermarket headlights now have angel eyes, which would look great.

There are several types of FRM2 modules that support this function, but since my car originally had halogen headlights and my current aftermarket headlights work perfectly with the old module, I bought an FRM2 module labeled E90/E91 NSW.

I successfully installed it, and when I connected everything, the car recognized it. After that, in WinKFP, I searched for the correct FRM module name based on the ZB number, entered my chassis number, and updated the module. Then, using NCSExpert, I read out the NFRM module from the CAS module with the FAWrite function and moved on to the NFRM module. I modified the VO number so that the car’s production date would be March 2007, as this is the minimum requirement for NCSExpert to write the new module with factory settings. I did this and then wrote the NFRM module with SG_Codieren. Everything was successful—the VIN and VO numbers matched within both CAS and NFRM. Of course, I did this using Expert mode (Non-Manipulation).

After that, I made a few adjustments to the FRM module using NCSDummy, such as enabling double impulse for the hazard lights, making the low beams turn on with the welcome lights, etc. Everything worked perfectly, and the car functioned properly.

About 15-20 minutes after finishing these changes, I tried to start the car, but I couldn’t. When I pressed the clutch and pushed the start button, the car made a humming sound, the dashboard went dark, and it automatically cut the ignition. I took out my laptop again, connected it, and noticed in INPA under “Read UIF” that the chassis number of the JBBF module was now different from all the other modules.

I immediately thought this was an issue, so I checked WinKFP again to find the correct JBBF module based on my ZB number. I found that it was JBBF81 and reprogrammed it using my VIN. The coding process completed successfully again, and based on the INPA UIF numbers, everything was correct, matching the other modules.

After that, I used NCSExpert to reset the CAS → JBBF module to factory settings using SG_Codieren in Non-Manipulation mode. This process was also successful.

I then tried to turn on the ignition, but now the dashboard didn’t light up at all—I only heard a continuous humming sound. I disconnected the power from the car and left it without power for at least 30 minutes.

When I returned, I no longer had normal push-button ignition; I could only insert the key. As soon as I pressed the button, the dashboard flashed, then went dark, the car’s lights started flickering, and it automatically cut the ignition again.

During the coding process, the car was always on a charger. My battery is only a year old, and before starting the coding, I drove the car for an hour.

[ateszaholdjaro]

Progress since:

On the dash appeared CC-ID 207 error, which is for the central electronics. I talked with a professional, he finds CAS as culprit, I took it off and will be sending it to him next week to see if it can be fixed/cloned with a working CAS2 module.

[ptpending]

you battery discharged because you did long diagnostics and coding cycle
check battery voltage and charge it
because when battery is very low, when you press start, all began to blink and simply powered off for a half sec

[ateszaholdjaro]

Hooked up battery charger, it is charging with 2amh, which indicates that battery is fully charged.

[ptpending]

get the option list from cas and nfrm and compare them with your VIN options list
you may got options from another car NFRM and saved them to CAS and coded your car to wrong option list

[ateszaholdjaro]

Im not sure that that would be the case, becsuse I copied the FA from CAS to NFRM. After that in NFRM i didnt code anything, just options with NCSDummy. And I rechecked (sadly dont have pics) that in NCSExpert CAS and NFRM FG FA number were matching (so vin/vo).

[ateszaholdjaro]

Jumping back,
Can the mistake be that I changed the production date in the VO of CAS? I should have changed in NFRM and not in CAS.. can that be the problem?

[ptpending]

not a production date but whole VO/FA
you've got VO/FA from guest FRM and coded your car using it
and may be stored in CAS later
but you should done otherwise, get VO/FA from CAS, save it ot NFRM, and the code whole car using it

[ateszaholdjaro]

Im pretty sure I did like this:
Choose ecu CAS, edit VO/FA prod date to 2007.03, change ecu, CAS, FA_Write, go back, choose ecu NFRM, sg codieren with expert profile.
After these steps ecu CAS NFRM FRM were showing same VIN and VO