Hi,

Customer bought 120d (E87 production 03/2006) with the new type Xenon headlights. Somewhere things stopped working. He went to the BMW dealer who installed a new FRM module (PL2 FRMFA S:61359128184-01 AW:9128224). After that things got ugly; several fault messages regarding "check light" popped up for low beam, brakes and angel eyes.

He came to our shop for a solution. With AutoHex we got rid off the "check light" fault messages, however we could not manage to get the angel eyes working (fault code 9cbb//9cbc FRM short circuit fault 2//1 in the FRM module). After some research we found out the angel eyes and faultcodes were caused by 35W angel eyes instead of 10W angel eyes which caused the FRM module to generate the "short circuit"-faults since the driver seems not powerfull enough to handle the 35W lights.

We tought it was possible to exchange the FRM1 module installed by the dealer with a FRM2 xenon module. So we ordered a PL2 FRM II XE module from ebay (S:61359166708-01 AW: 9166728). After we installed it, we were not able to code it automatically (AutoHex returned the code: Failed to encode Module error ref:8111). So we tried to code it manually. Unfortunately this is also not possible; if we check that the coding is the same for FRMII module as for the FRMI and we start the manual coding proces it gives an error in AutoHex saying: "Manual coding Error"

Before coding de FRMII we loaded the FRMII module with the FA backup from CAS. FA has the following elements:

Do you know what we are doing wrong?

Best regards,

Asim

You not doing anything wrong.
I think autohex is not very well for retrofit like that.
Autohex works similar like ista p in this case - coding is based on Vechicle Order.
I have retrofitted lci ahl xenon in 2006

At the moment your biggest problem is production date to pick up proper coding for frm2.
In 2006 was no frm2.
You need to change production date to later. I don't know exactly but you can try #1207
Also remove +mueb from vo
You can try do it in autohex - I think that is still possible.
I would use winkfp and program frm2 with car vin
Ncsexpert and change production date to 1207, remove +mueb.
Write it to cas and frm
Code frm.
You will meat another problem. As you don't have level sensors you have to code out automatic leveling

---

agree

ncsexpert is easier to go with

Unfortunately I don't posses NCS expert. I assumed that AutoHex was the perfect tool for this kind of "beyond dealer level" coding.

@Microtronik; do you know a way to get this done with the AutoHex?

Changing the production year or engine type is not allowed in Autohex, we believe that changing these values will bring a lot of problems.
We may include restriction removal of this function if expert mode is activated in next updates.
In the mean time, you can contact support by email asking them to help in team viewer to change the production year to a specific value.

Is expert mode available for everyone. I cant see it on my autohex

---

It can be activated as per the user request.

Ok. Nice. I definitely need it as I know what I'm doing.
Please let me know how to request it.

---

please send request for expert mode to tech support through skype or email.

Changing the production year or engine type is not allowed in Autohex, we believe that changing these values will bring a lot of problems.
We may include restriction removal of this function if expert mode is activated in next updates.
In the mean time, you can contact support by email asking them to help in team viewer to change the production year to a specific value.

@AutoHex_II: thank you for sharing your insight regarding changing production year. With this insight I was able to illustrate the reason for not being able to code the FRM2 module to the car to the customer and explaining him that there was a huge risk in overruling the production year setting.

We will try to find a hardware lightsolution (e.g. LED H8 max 10W)

@All: Thank you for your efforts!

Best regards,

Asim

Hi,

After some research we found out the angel eyes and faultcodes were caused by 35W angel eyes instead of 10W angel eyes which caused the FRM module to generate the "short circuit"-faults since the driver seems not powerfull enough to handle the 35W lights.

#0306 Production: 03/06
*UG51 E87 Saloon M47 M47D20 OLHD
$1CA CO2 Selection
$200 Diesel particle filter
$235 Towing hitch, detachable
$249 Multifunction f steering wheel
$255 Sports leather steering wheel
$2KC BMW light alloy wheel V-spoke 141
$302 Alarm system
$321 Exterior parts in vehicle colour
$411 Windo lifts, electric front/rear
$431 Interior mirror with automatic-dip
$441 Smoker package
$473 Armrest front
$481 Sport seat
$494 Seat heating drive/passenger
$4AG Interior trim finishers Titanium matt
$502 Headlight cleaning system
$507 Park Distance control (PDC) rear
$520 Fog lights
$521 Rain sensor
$522 Xenon light
$534 Automatic air conditioning
$540 Cruise control
$548 Kilometer-calibrated speedometer
$563 Light package
$5DC Rear-seat headrests, folding
$609 Navigation system professional
$775 Headlining anthracite
$7RP Advantage Package
$7RS Package comfort
$863 Retailer directory europe
$868 Language version, Dutch
$877 Delete cross-pattern operation
$886 Operating instructions, Dutch
$896 Daytime driving light switch
$852 Coding alarm signal
$863 Automatic locking when driving off
-B080 Battery 80 Ah, DO
+IPOD Retrofit, iPod interface
+MUEB Retrofit, lighting for model facelift

Do you know what we are doing wrong?

Best regards,

Asim

Asim,
What you are doing wrong is that you are redesigning the light circuit from a 10W to a 35W. You are lucky you are not popping fuses like mad.

Your best remedy is to reinstall the 10W lights, or wire the 35W lights with an external relay. The module will sense approximately 100mA and will think everything is operating normally.

Very IMPORTANT! The relay, if you decide to instal, MUST have an internal inductive kickback protecting resister/capacitor/or diode internally; else, the lights will function just fine for a time being, but after several energizes, the inductive kickback (as high as 120V) from the relay coil magnetic collapse will begin to degrade the module to failure.

Fuse the relay, and confirm the signal line to the module is negative or positive and wire accordingly to the relay. If positive, wire to pin 86, if negative, wire to pin 85 on a four pin Bosch type relay. Test the relay with an ohmmeter for different values across the control circuit coil if it has a diode. If it has a capacitor, you will noticce aa slight rise in voltage, or resistance, as the capacitor charges and then the true coil resistance.

The laws of physics are not just really good ideas.

Francisco

i usually recommend customer to install led angel eyes, instead of 35w bulb. this way you wont get cut outs and everything works fine.

hi to all

if have any problems with frm 3 modules....ista d does not recognize it.....autohex doesent have programing frm 3....can not reanimate.....i can solved ...withouth autohex or istap...ready to use...plug and play ...withouth problems 100%....

madzarmotor@yahoo.com

Autohex can help you to replace with a used FRM.

Autohex can help you to replace with a used FRM.

Yes but only exactly the same.
Frm3 max brose can be used in any year of production, and can replace frm1 frm2 and frm3 in any configuration: nsw, basis, led, xe, ahl - autohex can't do it. That only requires production date modification and programming + code by bmw std tools

---