E90Post
 


Studio RSR
 
BMW 3-Series (E90 E92) Forum > E90 / E92 / E93 3-series Technical Forums > BMW Coding > FRM repaired - still have issues



Reply
 
Thread Tools Search this Thread
      07-19-2020, 03:25 PM   #1
magsmagsmags
Enlisted Member
13
Rep
47
Posts

Drives: F10 M5 LCI
Join Date: Jun 2019
Location: UK

iTrader: (0)

Angry FRM repaired - still have issues

Hi guys

I did start a thread a couple of days ago but posted on the wrong place.

The car is a 2010 E90 LCI 318d. FRM3

The FRM wasn’t working. Typical issues. No windows. Lights stuck on etc. I sent the FRM off for repair and the software was corrupted, that was restored and I reinstalled the FRM. The actual issues caused by failure disappeared and my light switch remote locking etc now work however I’m still having some bizarre electrical issues.

I (apparently) have at least one bulb out on every circuit. One low beam out. One high. One indicator. One DRL. One tail light (the whole thing).

My front windows also don’t work

I replaced the bulbs, checked the tailgate wiring (found two wires with damage but not split, which I repaired) and have reset the defect counter on tool32, cleared codes and still no luck even with new bulbs.

Codes present on INPA are
9CBD
9CBC
9CB5
9CDB
9CDA
9CAA
9CAB

Not really sure what to do next. Is it possible the chips on the FRM that control those circuits are toast?

Would appreciate any advice
Appreciate 0
      07-20-2020, 06:53 PM   #2
magsmagsmags
Enlisted Member
13
Rep
47
Posts

Drives: F10 M5 LCI
Join Date: Jun 2019
Location: UK

iTrader: (0)

Bump. Anyone?

Few updates.

Bulb changes didn’t help

I’ve since used WinFKP to code the VIN to the module and reassign the VO from the CAS in NCS. FRM software is showing it’s updated to the latest version.

Issues still there
Appreciate 0
      07-23-2020, 07:31 AM   #3
magsmagsmags
Enlisted Member
13
Rep
47
Posts

Drives: F10 M5 LCI
Join Date: Jun 2019
Location: UK

iTrader: (0)

Update - fitted and coded another FRM - still the same issues.

Anyone?
Appreciate 0
      07-23-2020, 09:29 AM   #4
Joe@TopGearSolutions
Major
Joe@TopGearSolutions's Avatar
263
Rep
1,173
Posts

Drives: BMW
Join Date: Mar 2011
Location: USA

iTrader: (3)

Quote:
Originally Posted by magsmagsmags View Post
Update - fitted and coded another FRM - still the same issues.

Anyone?
Checked your fuses? Disconnect battery and touch pos/neg terminals for 30 seconds?
Appreciate 0
      07-25-2020, 09:29 AM   #5
magsmagsmags
Enlisted Member
13
Rep
47
Posts

Drives: F10 M5 LCI
Join Date: Jun 2019
Location: UK

iTrader: (0)

Quote:
Originally Posted by Joe@TopGearSolutions View Post
Checked your fuses? Disconnect battery and touch pos/neg terminals for 30 seconds?
Hey mate. I replaced every single fuse. No dice there either 🤦🏼*♂️

The errors I have left are
9CAA - Terminal 39b connection faulty
9CAB - terminal 15 is missing
This is showing battery voltage as 11.3v (was fairly low at the time. Since charged) and sensor reading of 0v

And 9CDA/9CDB Window lifter connection faulty

I’m still unsure if these would have anything to do with the random lights not working though
Appreciate 0
      07-26-2020, 08:50 PM   #6
magsmagsmags
Enlisted Member
13
Rep
47
Posts

Drives: F10 M5 LCI
Join Date: Jun 2019
Location: UK

iTrader: (0)

Update - but even more confused.

I thought I would check the date on the VO, just in case it had been modified before. It hadn't, by the looks of it, as it was set to #0910... however, NCS is recognising my FRM3 module as FRM2. When i hit process ECU on NFRM, under the jobname i am seeing "FRM2_E89.C08.A_PLD2PRX.IPO. FRM70.PRG.

I suspect (and hope) this might be part of my issue. However, none of the research i've done has unfortunately helped. The most common issues seem to be modifying the VO with a new production date (mine is 0910, so no need) and updating daten files (mine are v61). I can't see anything else.

It recognised properly in WinKFP when i coded the VIN. any idea anyone?
Appreciate 0
      07-27-2020, 07:13 AM   #7
Joe@TopGearSolutions
Major
Joe@TopGearSolutions's Avatar
263
Rep
1,173
Posts

Drives: BMW
Join Date: Mar 2011
Location: USA

iTrader: (3)

Quote:
Originally Posted by magsmagsmags View Post
Update - but even more confused.

I thought I would check the date on the VO, just in case it had been modified before. It hadn't, by the looks of it, as it was set to #0910... however, NCS is recognising my FRM3 module as FRM2. When i hit process ECU on NFRM, under the jobname i am seeing "FRM2_E89.C08.A_PLD2PRX.IPO. FRM70.PRG.

I suspect (and hope) this might be part of my issue. However, none of the research i've done has unfortunately helped. The most common issues seem to be modifying the VO with a new production date (mine is 0910, so no need) and updating daten files (mine are v61). I can't see anything else.

It recognised properly in WinKFP when i coded the VIN. any idea anyone?
After NCSEXPERT reads the module, what module is displayed in NCSEXPERT? It will show a different one right before it reads it.
Appreciate 0
      07-28-2020, 07:19 AM   #8
magsmagsmags
Enlisted Member
13
Rep
47
Posts

Drives: F10 M5 LCI
Join Date: Jun 2019
Location: UK

iTrader: (0)

You are right, the name changes to FRM 3.

I will keep updating the thread so it helps someone else in future as this has taken me ages to get to, with a lot of help

I got in touch with a local specialist who has very kindly been helping me diagnose this.

We checked voltage at the FRM and fuseboard and noted that terminal 30 (supplies constant power, with ignition off) was OK, however there was no voltage being received at pin 12 (terminal 15) on X14261 (bottom FRM connector). This is meant to be a switched live. We bridged this to pin 34, reconnected the FRM and all was working. This will kill the battery if left however and is not a permanent solution, but enough to identify the FRM was not at fault.

Next step is to continuity test the wires, if those are good, the fault is suspected to sit within the JBE, which i will replace next if the wires test OK
Appreciate 0
      11-10-2022, 10:36 AM   #9
alexbalkan
Registered
0
Rep
1
Posts

Drives: E90 2010 BMW 335i sedan
Join Date: Nov 2022
Location: United States

iTrader: (0)

Hey, really hoping that you’re still active on here! I have the exact same issue with my 2010 e90. Just had my FRM3 module re-coded as it got bricked during a coding session before. I have all of the exact same symptoms that you had mentioned in this thread. What did you end up doing to fix it?
Appreciate 0
      11-10-2022, 12:00 PM   #10
NorthernDancer
Colonel
848
Rep
2,276
Posts

Drives: 08 Sedona 128 & 06 330xiT 6MT
Join Date: Apr 2011
Location: Ottawa On Canada

iTrader: (3)

85% of all really weird electrical issues are loose and/or dirty connections. The most common issue is a bad ground, especially the ground strap between starter and body, real low on drivers side [LHD].
Appreciate 0
      11-10-2022, 02:36 PM   #11
Matt_E90
Enlisted Member
Matt_E90's Avatar
United Kingdom
6
Rep
43
Posts

Drives: BMW 330d M Sport
Join Date: Oct 2021
Location: Aberystwyth

iTrader: (0)

Garage List
Quote:
Originally Posted by alexbalkan View Post
Hey, really hoping that you’re still active on here! I have the exact same issue with my 2010 e90. Just had my FRM3 module re-coded as it got bricked during a coding session before. I have all of the exact same symptoms that you had mentioned in this thread. What did you end up doing to fix it?
I would change out the JBE to fix supply issue
Appreciate 0
Reply

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



All times are GMT -5. The time now is 02:31 PM.




e90post
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
1Addicts.com, BIMMERPOST.com, E90Post.com, F30Post.com, M3Post.com, ZPost.com, 5Post.com, 6Post.com, 7Post.com, XBimmers.com logo and trademark are properties of BIMMERPOST