[willisodhiambo]

A car with a replaced used FRM was brought to me. The side blinkers are fast, as if the light bulbs are out.

I decided to update car with ISTAP but it failed to obtain VO. Car was last treated with progman.

Flashed the FRM unit with WINKFP, same blink speed issue. Then overnight I remembered that VO is stored in CAS and FRM. (By the way what exactly is NFRM that also shows up when selecting ECU in NCSExpert?)

So am I right to assume that ISTA had a problem with a strange VO residing in the alien used FRM? The flash with WINKF does not automatically align the FRM I assume, just updates software version.

So here is what I want to do. I am going to VO code the FRM by copying the VO from the CAS using either Abrites or NCSExpert.

Then I code FRM to default using NCSExpert. I believe at this stage ISTAP will then be able to deal with the car.

Am I right is assuming the quick flasher speed of the side blinkers has to do with a foreign FRM or could there be other things I need to check?

[rafi-88]

Deactivate WARM/KALT indicator bulb checking in FRM coding via NCSExpert expert profile.

[bmwcoder75]

A car with a replaced used FRM was brought to me. The side blinkers are fast, as if the light bulbs are out.

I decided to update car with ISTAP but it failed to obtain VO. Car was last treated with progman.

Flashed the FRM unit with WINKFP, same blink speed issue. Then overnight I remembered that VO is stored in CAS and FRM. (By the way what exactly is NFRM that also shows up when selecting ECU in NCSExpert?)

So am I right to assume that ISTA had a problem with a strange VO residing in the alien used FRM? The flash with WINKF does not automatically align the FRM I assume, just updates software version.

So here is what I want to do. I am going to VO code the FRM by copying the VO from the CAS using either Abrites or NCSExpert.

Then I code FRM to default using NCSExpert. I believe at this stage ISTAP will then be able to deal with the car.

Am I right is assuming the quick flasher speed of the side blinkers has to do with a foreign FRM or could there be other things I need to check?

Use NCS
Read CAS FA and save to FRM
VO Code FRM
Read CAS iStep and save same iStep to FRM

Now FRM is 100%. Assuming this FRM is compatible with the car.

Now you can flash if you want but original issue should be fixed.

[willisodhiambo]

A car with a replaced used FRM was brought to me. The side blinkers are fast, as if the light bulbs are out.

I decided to update car with ISTAP but it failed to obtain VO. Car was last treated with progman.

Flashed the FRM unit with WINKFP, same blink speed issue. Then overnight I remembered that VO is stored in CAS and FRM. (By the way what exactly is NFRM that also shows up when selecting ECU in NCSExpert?)

So am I right to assume that ISTA had a problem with a strange VO residing in the alien used FRM? The flash with WINKF does not automatically align the FRM I assume, just updates software version.

So here is what I want to do. I am going to VO code the FRM by copying the VO from the CAS using either Abrites or NCSExpert.

Then I code FRM to default using NCSExpert. I believe at this stage ISTAP will then be able to deal with the car.

Am I right is assuming the quick flasher speed of the side blinkers has to do with a foreign FRM or could there be other things I need to check?

Use NCS
Read CAS FA and save to FRM
VO Code FRM
Read CAS iStep and save same iStep to FRM

Now FRM is 100%. Assuming this FRM is compatible with the car.

Now you can flash if you want but original issue should be fixed.

Yes!!!!

This is what am looking for. Except the part of CAS istep. How is that done? I can try that with Esys on Fs but never seen anything similar in E-series tools. Help!!

---

Deactivate WARM/KALT indicator bulb checking in FRM coding via NCSExpert expert profile.

Done that already. It has to do with alien FRM as all lights are ok.