FRM no communication

twitch27 · 09-23-2020, 10:28 AM

I was in the middle of coding within the FRM using Protools when my 2012 135I E82 timed out and turned itself off. I turned the car back on and got the typical FRM failure warning lights + windows stopped working, wonky headlights/tails, ect. I also was getting FRM no communication codes being thrown. I sent my FRM out to ECUPros to be repaired. Received the repaired FRM plugged it in and had basically the same issues (except my driver's window rolled itself down and won't go up) So, I sent the FRM back to ECUPros and they sent me a video of the FRM working in their test car. Im not sure where to go from here. Does anyone have any advice? My current codes are below.

CDA4
CD95
36BE (MHD tune)
AA07
A3C1
A3B4
D378
E1E3
E1CD

sdbmwcoding · 09-23-2020, 11:51 AM

What exactly did not work after plugging in the repaired frm? I'd recommend copying the VO from CAS, writing to FRM and coding the FRM to default incase some coding was corrupted. If that doesn't work then you can try flashing the frm with Winkfp.

twitch27 · 10-14-2020, 02:01 PM

Quote:

Originally Posted by sd*********

What exactly did not work after plugging in the repaired frm? I'd recommend copying the VO from CAS, writing to FRM and coding the FRM to default incase some coding was corrupted. If that doesn't work then you can try flashing the frm with Winkfp.

Sorry for the delay. I had to store my 135i away due to the window being stuck down in WA weather with no garage.

Windows don't work, locks don't work, no parking sensors, trunk light may be stuck on, one head light works.

https://postimg.cc/gallery/CBXK0jw

twitch27 · 01-28-2021, 10:17 PM

Ended up driving the car to a local BMW shop. Tech fixed it. I was told that he pulled out the FRM, checked it over, put it back in, and now it's fixed. I'm guessing I didn't have it plugged in all the way. Oops...Lesson learned!

TunafishE93 · 01-29-2021, 04:30 AM

Just fyi you can code the car with it running so you wont have to worry about timing out.

09-23-2020, 10:28 AM	#1
twitch27 Registered 1 Rep 4 Posts Drives: BMW 135i Join Date: Aug 2019 Location: Washington iTrader: (0)	FRM no communication I was in the middle of coding within the FRM using Protools when my 2012 135I E82 timed out and turned itself off. I turned the car back on and got the typical FRM failure warning lights + windows stopped working, wonky headlights/tails, ect. I also was getting FRM no communication codes being thrown. I sent my FRM out to ECUPros to be repaired. Received the repaired FRM plugged it in and had basically the same issues (except my driver's window rolled itself down and won't go up) So, I sent the FRM back to ECUPros and they sent me a video of the FRM working in their test car. Im not sure where to go from here. Does anyone have any advice? My current codes are below. CDA4 CD95 36BE (MHD tune) AA07 A3C1 A3B4 D378 E1E3 E1CD
	Appreciate 0 Tweet Quote

09-23-2020, 11:51 AM	#2
sdbmwcoding Captain 196 Rep 804 Posts Drives: BMW M3 Join Date: May 2019 Location: San Diego iTrader: (0)	What exactly did not work after plugging in the repaired frm? I'd recommend copying the VO from CAS, writing to FRM and coding the FRM to default incase some coding was corrupted. If that doesn't work then you can try flashing the frm with Winkfp.
	Appreciate 0 Quote

01-28-2021, 10:17 PM	#4
twitch27 Registered 1 Rep 4 Posts Drives: BMW 135i Join Date: Aug 2019 Location: Washington iTrader: (0)	Ended up driving the car to a local BMW shop. Tech fixed it. I was told that he pulled out the FRM, checked it over, put it back in, and now it's fixed. I'm guessing I didn't have it plugged in all the way. Oops...Lesson learned!
	Appreciate 0 Quote

01-29-2021, 04:30 AM	#5
TunafishE93 Major 424 Rep 1,152 Posts Drives: BMW 335i Join Date: Dec 2019 Location: NV iTrader: (0)	Just fyi you can code the car with it running so you wont have to worry about timing out.
	Appreciate 0 Quote