[rogerduv]

I have a 2010 328i e90 automatic LHD that was given to me for free.
Doing some research on the VIN i can see it was a crash damaged, manual e90 from Africa.
I've been going through the problems with it so far with some of them being a fried FRM module, a lot of cut wires up at the front of the car on the headlight harness and misc pieces missing.
The car starts and the engine sounds healthy, but I've been met with transmission codes which put the car into a limp mode whenever you try to put it into gear. Codes associated with this being 581A, 581B, 581C, 581D and 5658. All speed sensor related.
I've already done a service on the transmission to rule that out as a possibility.

So with that being said. I recently went on a trip and forgot to disconnect the battery on the car. When I got back the battery was dead. I recharged it and went back into trying to diagnose it and realized none of the ECU's were showing up. The only thing that sort of communicated was the JBBF module. I connected with INPA and saw the JBBF had basically lost the vin that was coded to it, and everything else.
Weirdly enough, the car still starts, but shifting does nothing. Car doesnt respond to throttle. Which i understand is because the JBBF/JBE is in charge of waking up the other modules.
So what I'm wondering is if the JBBF is recoverable by any means. I've tried coding it through Winkfp and only being met with errors. I've tried multiple sp-datens and am somewhat familiar with the process of using bmw tools. I've updated the cas on my 2008 e91 recently to try to fix an ELV issue.

So is this a situation that can be fixed with coding, or do I need a new JBBF/JBE.

Thank you!

[StradaRedlands]

Sounds like you have a bit of a project there! Hope you can get it all sorted and running!

[rogerduv]

Originally Posted by StradaRedlands

Sounds like you have a bit of a project there! Hope you can get it all sorted and running!

Thanks, hopefully someone can give me some information to point me in a right direction.

[ptpending]

there are dozens of topics on n52 troubleshooting
so just use search and read diagrams provided by forum members

[gbalthrop]

Originally Posted by rogerduv

... 2010 328i e90 automatic LHD... The car starts and the engine sounds healthy, but I've been met with transmission codes which put the car into a limp mode whenever you try to put it into gear. Codes associated with this being 581A, 581B, 581C, 581D and 5658. All speed sensor related...
I recently went on a trip and forgot to disconnect the battery on the car. When I got back the battery was dead. I recharged it and went back into trying to diagnose it and realized none of the ECU's were showing up. The only thing that sort of communicated was the JBBF module. I connected with INPA and saw the JBBF had basically lost the vin that was coded to it, and everything else.
Weirdly enough, the car still starts, but shifting does nothing. Car doesnt respond to throttle...

If you have INPA, you SHOULD be able to diagnose the issues. The FIRST thing to do is view, save & Post a ScreenPrint of BOTH the following INPA Screens:
1) INPA > Functional Jobs > F2 Identification, which lists all Modules in the vehicle which are communicating.

2) INPA > Functional Jobs > F4 > F1 Read Error Memory, which lists ALL Fault Codes in ALL modules.

That will provide clues as to which modules are NOT communicating, or fault codes in the various modules. Getting a complete picture of what is communicating & the fault codes is the Starting Point in any diagnosis. If there are communication issues, preventing connecting with, or reading fault codes IN, a particular Module, we need to address that.

Questions:
0) What are the Last-7 Characters of your VIN? So we can see correct ISTA ScreenPrints. Also that will show configuration of Vehicle from factory (AT vs. MT, etc.).

1) What make/model Scan Tool/Software did you use to read the 5 EGS codes you listed? INPA?

2) Can you still read those codes with that Tool/Software?

3) With Ignition ON, & engine running, is the gear selected, "P", displayed in the lower Instrument Cluster display?

4) With Ignition ON:
a) can you shift out of Park by putting your foot on the Brake?
b) if so, does the gear selected display in the lower Instrument Cluster change correctly for each gear change?

5) Does the vehicle have a Steering Lock (ELV)?

6) What Warning Lights are present on the Instrument Cluster with ignition on & engine running? A photo would be helpful.

I would address the "5658" EGS code first. Here is the BMW Fault Code Lookup Definition of that code:
5658 | EGS: Gearbox-position sensor: malfunction | gs1912 | Transmission control
Unfortunately, I am NOT aware of any such sensor, or switch. There is a Selector Lever Position Switch next to the Shift Lever

The other 4 EGS fault codes you list indicate EGS is NOT receiving any signal from any of the 4 wheel speed sensors, which are connected to the DSC Module. That would NOT prevent shifting from Park or put vehicle in Limp mode. That could be due to actual sensor faults, line faults between the sensors & DSC Module, OR, PT-CAN bus fault preventing EGS from receiving those signals from the DSC Module. If multiple Modules are NOT communicating, there is a high likelihood of Bus wiring/connector issues. I would NOT program or code anything BEFORE using INPA to fully-diagnose the issues.

If you speak English, but NOT German, ISTA (IF you have it) might be more "user-friendly", but we can use Google Translate to translate Technical German to Technical English. Technical German is very specific, at least when used in proper context. "Thingy" or "Thingamajig" is "Dingsda" in German. I've never seen that word in INPA.

Please answer the questions above & furnish the requested Functional Jobs ScreenPrints. If any questions or issues, please ask/describe. Make sure your COM 1, Latency 1, settings have NOT gotten changed (by Windows Updates). How to check that, how to view Functional Jobs, & example Screens from my 3/2007 build 328xi are all included in the attached pdf: "INPA Tutorial Quickstart".
George

[rogerduv]

Originally Posted by gbalthrop

If you have INPA, you SHOULD be able to diagnose the issues. The FIRST thing to do is view, save & Post a ScreenPrint of BOTH the following INPA Screens:
1) INPA > Functional Jobs > F2 Identification, which lists all Modules in the vehicle which are communicating.

2) INPA > Functional Jobs > F4 > F1 Read Error Memory, which lists ALL Fault Codes in ALL modules.

That will provide clues as to which modules are NOT communicating, or fault codes in the various modules. Getting a complete picture of what is communicating & the fault codes is the Starting Point in any diagnosis. If there are communication issues, preventing connecting with, or reading fault codes IN, a particular Module, we need to address that.

Questions:
0) What are the Last-7 Characters of your VIN? So we can see correct ISTA ScreenPrints. Also that will show configuration of Vehicle from factory (AT vs. MT, etc.).

1) What make/model Scan Tool/Software did you use to read the 5 EGS codes you listed? INPA?

2) Can you still read those codes with that Tool/Software?

3) With Ignition ON, & engine running, is the gear selected, "P", displayed in the lower Instrument Cluster display?

4) With Ignition ON:
a) can you shift out of Park by putting your foot on the Brake?
b) if so, does the gear selected display in the lower Instrument Cluster change correctly for each gear change?

5) Does the vehicle have a Steering Lock (ELV)?

6) What Warning Lights are present on the Instrument Cluster with ignition on & engine running? A photo would be helpful.

I would address the "5658" EGS code first. Here is the BMW Fault Code Lookup Definition of that code:
5658 | EGS: Gearbox-position sensor: malfunction | gs1912 | Transmission control
Unfortunately, I am NOT aware of any such sensor, or switch. There is a Selector Lever Position Switch next to the Shift Lever

The other 4 EGS fault codes you list indicate EGS is NOT receiving any signal from any of the 4 wheel speed sensors, which are connected to the DSC Module. That would NOT prevent shifting from Park or put vehicle in Limp mode. That could be due to actual sensor faults, line faults between the sensors & DSC Module, OR, PT-CAN bus fault preventing EGS from receiving those signals from the DSC Module. If multiple Modules are NOT communicating, there is a high likelihood of Bus wiring/connector issues. I would NOT program or code anything BEFORE using INPA to fully-diagnose the issues.

If you speak English, but NOT German, ISTA (IF you have it) might be more "user-friendly", but we can use Google Translate to translate Technical German to Technical English. Technical German is very specific, at least when used in proper context. "Thingy" or "Thingamajig" is "Dingsda" in German. I've never seen that word in INPA.

Please answer the questions above & furnish the requested Functional Jobs ScreenPrints. If any questions or issues, please ask/describe. Make sure your COM 1, Latency 1, settings have NOT gotten changed (by Windows Updates). How to check that, how to view Functional Jobs, & example Screens from my 3/2007 build 328xi are all included in the attached pdf: "INPA Tutorial Quickstart".
George

Thank you for the response!
I'll be attaching the screenshots and photos you requested.

Last 7 digits - NM53695

Scan tools used - INPA, Launch x-431 and bimmerlink

Ign on/engine running - No

Ign on shift out of park - Yes.
(Prior to the JBBE issue only P and N would display) Presently with JBBE issue, none showing.

Steering lock - Doesnt seem so.

Warning lights - attaching photo

I can assume windows hasn't changed anything because all programs still work with my e91 which is currently running with an ELV issue that I'm working on as well.

I can work on getting ISTA if its "better", but I've gotten by so far in INPA with google translate, utilizing forum searches, and common sense.

Once again, thank you!

[StradaRedlands]

Those are a lot of lights!

[gbalthrop]

Originally Posted by rogerduv

... Last 7 digits - NM53695; Scan tools used - INPA, Launch x-431 and bimmerlink
Ign on/engine running - No [Currently CANNOT read any fault codes?]
Ign on shift out of park - Yes. (Prior to the JBE issue only P and N would display) Presently with JBE issue, none showing....

1) Your warning lights do NOT include any SES Engine warnings.

2) My interpretation of your Functional Jobs F2 Identification screen is that INPA can tell you have a JBBF (Junction Box Electronics "Hub") but can't read any of the data from it -- all entries are "default" (FFFF, 255, unbekannter, etc.). There is not even an SGBD/Variant listed (should be "JBBF87"). I have never seen that before, but I don't think that is a "coding" issue, but rather a Bus communication issue. Same for your FJ F4 F1 Error Memory. The JBBF is also known as the JBE. I will use JBE hereafter.

3) If your Instrument Cluster lights & the warning lights & gauges work, & your engine starts, at least CAS is communicating with the DME (EWS4 "Handshake", Brake Light Switch Signal, even P/N signal), all required to Crank Starter & fire engine. Actually, the CAS Module is responsible for "KL15 Wakeup".

4) However, there is NO communication between OBD II Socket & JBE, either due to an issue with the JBE itself (unlikely), Lack of Voltage Supply to JBE, Lack of Ground, or an issue with the connection of the D-CAN lines/wires between OBD Socket X19527 & JBE at X14271/17 or /33 (White/Yellow wire at Socket #17 of JBE Blue Connector, X14271; or White/Blue wire at Socket #33 of X14271. Those two wires at disconnected X14271 JBE Connector should have continuity with OBD Connector X19527/6 (White/Yellow wire) or X19527/14 (White/Blue wire).

4a) To access the Blue Connector, X14271 on the face of the JBE, next to a similar Black Connector, remove the Trim Pad below the Glovebox by removing two T-20 connectors, dropping down the pad & removing (jiggle & pull) the wiring connector from the footwell lamp on the Pad.

5) Since BOTH the OBD Socket & Instrument Cluster are powered by the same fuse (F74 on your 2010 model), and the instrument cluster lights up, that fuse is OK. The JBE is powered by 5 different fuses, F79 apparently being the first to check. Also see F78 & F80 (do your rear windows work?) & F72 & F73 (does your Central Locking work, at least from center dash button?). If you need a fuse chart, please ask.

6) You mentioned "cut wires up front". CAN Bus (D-CAN, PT-CAN, K-CAN) wires are usually "twisted pairs", so if you see any of them cut or damaged, splice those. D-CAN wires are White/Yellow & White/Blue; PT-CAN are Red & Blue/Red, & K-CAN are Green & Orange/Green.

7) Once again, if INPA/ Scan Tool CANNOT connect, that is almost always a Bus, Voltage Supply, or Ground issue. I can supply the needed ISTA SSP wiring diagrams. You supply the patience, testing & posted results, & we'll get there. INPA provides very good DATA.

8) If you don't have one, you will need a cheap Multimeter. In US, ~ $10 from HFT or Amazon. That is needed to test for voltage in Bus wiring, & to test for Continuity between connectors (such as between X19527 & X14271). If you need suggestions on HOW to test, please ask.

I attach to NEXT Post, ISTA ScreenPrints of wiring diagram & Connector Views for connections from OBD to JBE, along with Bus Connections to the JBE, & JBE power supply & F79 location.

If you know ANY history on the vehicle, as far as what was worked on, or removed, when, or why, please provide that information. Both coding & programming are out (probably unnecessary as well) until you can CONNECT with that module, & you currently cannot Connect with ANY.

So we need to do a systematic check, starting with OBD to JBE, get the JBE to Connect & communicate with INPA, & then get other Modules to connect. It is possible that there is a wiring fault or short in one or more bus connections, & that can cause failure of bus communication.

BTW, ISTA shows that VIN-7, "NM53695", as having AT from the factory (as opposed to MT), & sold in US (NOT ECE). Perhaps I misunderstood your original post.
George

[gbalthrop]

Attached are ISTA ScreenPrints related to prior post.
George

[rogerduv]

Originally Posted by gbalthrop

1) Your warning lights do NOT include any SES Engine warnings.

2) My interpretation of your Functional Jobs F2 Identification screen is that INPA can tell you have a JBBF (Junction Box Electronics "Hub") but can't read any of the data from it -- all entries are "default" (FFFF, 255, unbekannter, etc.). There is not even an SGBD/Variant listed (should be "JBBF87"). I have never seen that before, but I don't think that is a "coding" issue, but rather a Bus communication issue. Same for your FJ F4 F1 Error Memory. The JBBF is also known as the JBE. I will use JBE hereafter.

3) If your Instrument Cluster lights & the warning lights & gauges work, & your engine starts, at least CAS is communicating with the DME (EWS4 "Handshake", Brake Light Switch Signal, even P/N signal), all required to Crank Starter & fire engine. Actually, the CAS Module is responsible for "KL15 Wakeup".

4) However, there is NO communication between OBD II Socket & JBE, either due to an issue with the JBE itself (unlikely), Lack of Voltage Supply to JBE, Lack of Ground, or an issue with the connection of the D-CAN lines/wires between OBD Socket X19527 & JBE at X14271/17 or /33 (White/Yellow wire at Socket #17 of JBE Blue Connector, X14271; or White/Blue wire at Socket #33 of X14271. Those two wires at disconnected X14271 JBE Connector should have continuity with OBD Connector X19527/6 (White/Yellow wire) or X19527/14 (White/Blue wire).

4a) To access the Blue Connector, X14271 on the face of the JBE, next to a similar Black Connector, remove the Trim Pad below the Glovebox by removing two T-20 connectors, dropping down the pad & removing (jiggle & pull) the wiring connector from the footwell lamp on the Pad.

5) Since BOTH the OBD Socket & Instrument Cluster are powered by the same fuse (F74 on your 2010 model), and the instrument cluster lights up, that fuse is OK. The JBE is powered by 5 different fuses, F79 apparently being the first to check. Also see F78 & F80 (do your rear windows work?) & F72 & F73 (does your Central Locking work, at least from center dash button?). If you need a fuse chart, please ask.

6) You mentioned "cut wires up front". CAN Bus (D-CAN, PT-CAN, K-CAN) wires are usually "twisted pairs", so if you see any of them cut or damaged, splice those. D-CAN wires are White/Yellow & White/Blue; PT-CAN are Red & Blue/Red, & K-CAN are Green & Orange/Green.

7) Once again, if INPA/ Scan Tool CANNOT connect, that is almost always a Bus, Voltage Supply, or Ground issue. I can supply the needed ISTA SSP wiring diagrams. You supply the patience, testing & posted results, & we'll get there. INPA provides very good DATA.

8) If you don't have one, you will need a cheap Multimeter. In US, ~ $10 from HFT or Amazon. That is needed to test for voltage in Bus wiring, & to test for Continuity between connectors (such as between X19527 & X14271). If you need suggestions on HOW to test, please ask.

I attach to NEXT Post, ISTA ScreenPrints of wiring diagram & Connector Views for connections from OBD to JBE, along with Bus Connections to the JBE, & JBE power supply & F79 location.

If you know ANY history on the vehicle, as far as what was worked on, or removed, when, or why, please provide that information. Both coding & programming are out (probably unnecessary as well) until you can CONNECT with that module, & you currently cannot Connect with ANY.

So we need to do a systematic check, starting with OBD to JBE, get the JBE to Connect & communicate with INPA, & then get other Modules to connect. It is possible that there is a wiring fault or short in one or more bus connections, & that can cause failure of bus communication.

BTW, ISTA shows that VIN-7, "NM53695", as having AT from the factory (as opposed to MT), & sold in US (NOT ECE). Perhaps I misunderstood your original post.
George

This is all amazing information to receive. I will go through and test all the wiring connections mentioned. I do already have a multimeter, so testing continuity shouldnt be an issue.

As for history on the car, I dont have anything. The thought that it might have been a manual car came from a VIN check.

The windows and lights werent working prior to the JBE issue. There was no communcation to the FRM module. Sunroof works though.

I'd also like to ask one more thing if you have the information present. I've been trying to sort out the wiring in the front that's been cut off. It looks like someone really just cut off all the wiring going to the headlights, then tried to repair it but with the wrong harness. I'm trying to locate the proper harness that would go there. I did purchase one already from ebay, but a lot of the colors don't line up, so it cant be the correct harness.

I'll include photos of what I'm referencing

[gbalthrop]

Originally Posted by rogerduv

... The windows and lights weren't working prior to the JBE issue. There was no communcation to the FRM module. Sunroof works though.
I'd also like to ask one more thing if you have the information present. I've been trying to sort out the wiring in the front that's been cut off. It looks like someone really just cut off all the wiring going to the headlights, then tried to repair it but with the wrong harness...

AFAIK, there is NO harness information in ISTA. Wiring diagrams (SSP documents) show wire colors, sizes, Connector Views (Pin/Socket Numbering) & component/connector locations. There is a separate wiring diagram for each function, such as Headlights, sidelights, foglights horn, Ambient Temp Sensor, Radiator E-Fan, Ride Height Sensors, Washer/Wiper Pumps, etc.

Do you have the original Connectors at the Light units (fog, headlights [main/dip], sidelights, turn indicators)? Are your headlights Halogen or Xenon?

As example, the B+ wire from the FRM Module going to each Left & Right Foglight is Yellow/Brown. There is a Brown Ground wire connected to the "comb" (Multiple Brown Chassis Ground wires on a single comb) at both the Left & right "Wing" or inner fender. The Left Chassis Ground "Comb", X165 appears under the two bolts in your 2nd photo. Solid-Brown wires are normally Chassis Ground. The thickness of the wire is related to how much current it must carry. Those Fog B+ wires are 1.5 mm-squared cross section, while a wire providing power to a sensor might be .5 or .75.

The B+ wire from the FRM to the Left Low Beam Lamp is Yellow/Green (2.5 mm-sq.), & the B+ wire to the Left High Beam Lamp is White/Green (1.5 mm-sq.). The Brown Chassis Ground wire that goes from the X13420 Connector to the X165 "Comb" is 2.5 mm-sq. cross-section. The Connector View of X13420 Connector, 12-sockets, is also attached to Next Post, along with other example wiring diagrams for Fog Lights.

So we can help you identify a wire or connector function if you provide:
1) clear location of the wire;
2) clear photo of CLEAN wire color(s) (2nd color, as in Yellow/Green is tracer stripe);
3) Connector photo should show Sockets & socket face/shape, along with one or more wire colors if possible;
4) Original wiring was the same from FRM or other module ALL the way to the device powered, with NO change in wire size or color. So if there is a splice visible, report the wire color closest to firewall or origination of the wire.
5) If you have to splice a wire, make SURE added wire is at least as Large a Gauge/ Cross-section as the original wire. Any color will do as long as you RECORD the added wire color & approximate location of splice, for future reference.

My suggestion is to FIRST (1) Check JBE fuses, (2) try to get connection from INPA to JBE, then (3) connection to other Modules. THEN address wiring issues. I see several "twisted-pairs" of wires on the Right & one on the Left. Try to get definitive COLORS of those wires, & make sure NO wire is touching chassis ground or another wire (metal), as that will prevent bus communication. Just because two wires are twisted together doesn't mean those are bus wires, as someone may have just done that to regular dedicated wires.
George

[gbalthrop]

Attached are example ISTA ScreenPrints of Hi-Low Beam & Front Fogs, per prior post.
George

[rogerduv]

Originally Posted by gbalthrop

1) Your warning lights do NOT include any SES Engine warnings.

2) My interpretation of your Functional Jobs F2 Identification screen is that INPA can tell you have a JBBF (Junction Box Electronics "Hub") but can't read any of the data from it -- all entries are "default" (FFFF, 255, unbekannter, etc.). There is not even an SGBD/Variant listed (should be "JBBF87"). I have never seen that before, but I don't think that is a "coding" issue, but rather a Bus communication issue. Same for your FJ F4 F1 Error Memory. The JBBF is also known as the JBE. I will use JBE hereafter.

3) If your Instrument Cluster lights & the warning lights & gauges work, & your engine starts, at least CAS is communicating with the DME (EWS4 "Handshake", Brake Light Switch Signal, even P/N signal), all required to Crank Starter & fire engine. Actually, the CAS Module is responsible for "KL15 Wakeup".

4) However, there is NO communication between OBD II Socket & JBE, either due to an issue with the JBE itself (unlikely), Lack of Voltage Supply to JBE, Lack of Ground, or an issue with the connection of the D-CAN lines/wires between OBD Socket X19527 & JBE at X14271/17 or /33 (White/Yellow wire at Socket #17 of JBE Blue Connector, X14271; or White/Blue wire at Socket #33 of X14271. Those two wires at disconnected X14271 JBE Connector should have continuity with OBD Connector X19527/6 (White/Yellow wire) or X19527/14 (White/Blue wire).

4a) To access the Blue Connector, X14271 on the face of the JBE, next to a similar Black Connector, remove the Trim Pad below the Glovebox by removing two T-20 connectors, dropping down the pad & removing (jiggle & pull) the wiring connector from the footwell lamp on the Pad.

5) Since BOTH the OBD Socket & Instrument Cluster are powered by the same fuse (F74 on your 2010 model), and the instrument cluster lights up, that fuse is OK. The JBE is powered by 5 different fuses, F79 apparently being the first to check. Also see F78 & F80 (do your rear windows work?) & F72 & F73 (does your Central Locking work, at least from center dash button?). If you need a fuse chart, please ask.

6) You mentioned "cut wires up front". CAN Bus (D-CAN, PT-CAN, K-CAN) wires are usually "twisted pairs", so if you see any of them cut or damaged, splice those. D-CAN wires are White/Yellow & White/Blue; PT-CAN are Red & Blue/Red, & K-CAN are Green & Orange/Green.

7) Once again, if INPA/ Scan Tool CANNOT connect, that is almost always a Bus, Voltage Supply, or Ground issue. I can supply the needed ISTA SSP wiring diagrams. You supply the patience, testing & posted results, & we'll get there. INPA provides very good DATA.

8) If you don't have one, you will need a cheap Multimeter. In US, ~ $10 from HFT or Amazon. That is needed to test for voltage in Bus wiring, & to test for Continuity between connectors (such as between X19527 & X14271). If you need suggestions on HOW to test, please ask.

I attach to NEXT Post, ISTA ScreenPrints of wiring diagram & Connector Views for connections from OBD to JBE, along with Bus Connections to the JBE, & JBE power supply & F79 location.

If you know ANY history on the vehicle, as far as what was worked on, or removed, when, or why, please provide that information. Both coding & programming are out (probably unnecessary as well) until you can CONNECT with that module, & you currently cannot Connect with ANY.

So we need to do a systematic check, starting with OBD to JBE, get the JBE to Connect & communicate with INPA, & then get other Modules to connect. It is possible that there is a wiring fault or short in one or more bus connections, & that can cause failure of bus communication.

BTW, ISTA shows that VIN-7, "NM53695", as having AT from the factory (as opposed to MT), & sold in US (NOT ECE). Perhaps I misunderstood your original post.
George

Ok so i tested continuity between the JBE and OBD port and it tested fine.
I had one broken fuse, and a lot of missing fuses. So i replaced the broken one, and fitted new fuses to all the missing spots.
But no luck, still no proper communication.

Maybe the fuse diagram could help me, because the one that should be in the car is missing, and I cant find any that match the information you're presenting me with.

I will also include 2 new screenshots of the user information field and programming state, as it may shed more light on the situation.

[gbalthrop]

Originally Posted by rogerduv

Ok so i tested continuity between the JBE and OBD port and it tested fine. I had one broken fuse, and a lot of missing fuses. So i replaced the broken one, and fitted new fuses to all the missing spots.
But no luck, still no proper communication. Maybe the fuse diagram could help me, because the one that should be in the car is missing, and I cant find any that match the information you're presenting me with. I will also include 2 new screenshots of the user information field and programming state, as it may shed more light on the situation.

The Programming State Text in your first attachment translates:
"Program not found or incomplete." If you attempted to use WinKFP or such to change JBBF Programming, I'm sorry, I can't help.

Also, for ANYONE reading this:
NEVER randomly pull or add fuses to the Junction Box Fuse Panel. EVERY BMW is different as to which fuses are present, as there are many OPTIONS available, & if your vehicle does NOT have that option, there should be NO fuse for that component.

Fuse Chart for E9x, 2008 & LATER models is attached to NEXT Post. Be aware that there are THREE (3) E9x Fuse Charts:

1) Prior to 3/1/2007 (middle of 2007 model run), where original JB Fuse Panel Layout was used -- Large fuses in lower right are VERTICAL.

2) 3/1/2007 thru 8/31/2007 (2nd half of 2007 model run); NEW JB Fuse Panel Layout, but SAME fuse numbering by system, resulting in RANDOM fuse numbers. NEW layout had Large fuses at lower right HORIZONTAL.

3) 9/1/2007 build date & later (2008 model & LATER): Same New JB Fuse Panel Layout as 3/1/2007, but NUMBERING of fuses was changed to generally have F1 at Top-Left & F92 (Highest fuse number) at Bottom-Right.

Fuse Chart attached is from Bentley Manual. There are a few errors/discrepancies between ISTA fuse numbering & Bentley, with ISTA being presumed correct.

If you don't have a Tri-Fold fuse chart attached to removable panel at firewall side of Glovebox, &/or don't have ISTA, please ASK for fuse/electrical information. Messing with fuses or other electrical components or circuits WITHOUT proper documentation can make a vehicle FUBAR very quickly.
George

[rogerduv]

Originally Posted by gbalthrop

The Programming State Text in your first attachment translates:
"Program not found or incomplete." If you attempted to use WinKFP or such to change JBBF Programming, I'm sorry, I can't help.

Also, for ANYONE reading this:
NEVER randomly pull or add fuses to the Junction Box Fuse Panel. EVERY BMW is different as to which fuses are present, as there are many OPTIONS available, & if your vehicle does NOT have that option, there should be NO fuse for that component.

Fuse Chart for E9x, 2008 & LATER models is attached to NEXT Post. Be aware that there are THREE (3) E9x Fuse Charts:

1) Prior to 3/1/2007 (middle of 2007 model run), where original JB Fuse Panel Layout was used -- Large fuses in lower right are VERTICAL.

2) 3/1/2007 thru 8/31/2007 (2nd half of 2007 model run); NEW JB Fuse Panel Layout, but SAME fuse numbering by system, resulting in RANDOM fuse numbers. NEW layout had Large fuses at lower right HORIZONTAL.

3) 9/1/2007 build date & later (2008 model & LATER): Same New JB Fuse Panel Layout as 3/1/2007, but NUMBERING of fuses was changed to generally have F1 at Top-Left & F92 (Highest fuse number) at Bottom-Right.

Fuse Chart attached is from Bentley Manual. There are a few errors/discrepancies between ISTA fuse numbering & Bentley, with ISTA being presumed correct.

If you don't have a Tri-Fold fuse chart attached to removable panel at firewall side of Glovebox, &/or don't have ISTA, please ASK for fuse/electrical information. Messing with fuses or other electrical components or circuits WITHOUT proper documentation can make a vehicle FUBAR very quickly.
George

The programming state is how it was found after I returned from my trip. I've not attemped to code or program it at that point.

The trifold for this vehicle is indeed missing and I do not have access to ISTA presently. I may look into acquiring ISTA as it seems to be very useful.