Thursday, December 29, 2016

What i know about ICOM A3, ICOM A2, ICOM A

What I know is that some of the ICOM A3 doesnt support 20 Pin connector old cars, but the CPU should be faster.

BMW ICOM A2 is definitely a redesign of the old ICOM A1.
You can see it very easy if you take a look on the CPU layer you will find LED´s on both layers. One side would never light outside the case, but in the A1 case the LED´s were used in the paste.

I bought my first A2 more than two years ago. it is still working, another WIFI ICOM A2 from the same supplier some month ago. It was shipped with a DLink WLAN Adapter and a HDD. HDD is working very well, but I made my own installation. With the WIFI function it takes a little bit more time to find a good solution, because I am working in two different network segments. Here I use Freeware NetSetMan and MyPublicWifi. Especially the first program is a knife in handling TCPIP addresses and nic´s. 

Print quality of the layer is really good. Due to the old BMW ICOM A module have problem in the cooling and protection design, ICOM A2 adopts the whole aluminum shell body, using aerial explosion-proof connector; and it use the joint connection line which similar to the SDconnect C4

So not everything from China is cheap crap, but I think it is better to know somone there you can trust.

(BIG THANKS to B1257)

Stuck with 6NR update with 9c FSC code via ENET Esys

Car model:
An BMW F07 from 2010
BMW coding tool I use:
I’m using E-Sys 3.22.5  and Daten version which is based on I-Step F001-15-03-500
I’ve successfully imported the 9c FSC code. If I read out the log it shows “status accepted” for the code.
Then I’ve changed the VO by adding 6NR, and I’ve changed the Zeitkriterium to 0911 (It was originally 0310, but I retrofitted a Combox).
Saved the VO to the car, and Coded the Combox and CIC modules.
The result is that I don’t have BMW Apps and that my rear view camera has disappeared.
I tried to go into the CAFD, but in the version of the Daten I have loaded it only shows the “.”‘s (dots) instead of the options. I haven’t tried with an earlier version yet, so perhaps that could be the problem.
combox is working perfectly.
Problem analysis and professional suggestion:
Use older files or TokenMasters Launcher, you can find it with the search on the bimmerfest forum. But VO coding should be possible, this is what I have in my VO:
1CA,1CB,1CD,223,229,230,248,255,2ST,2VA,2VH,302,31 6,319,322,323,3AG,402,416,423,428,430,431,441,456, 488,494,496,4CB,4NB,4UR,4UY,502,508,522,524,548,5A C,5AD,5DF,601,609,610,614,615,616,620,644,677,698, 6AA,6AB,6AL,6FH,6FL,6NF,6NR,6VC,775,7SP,801,851,86 3,879,8KA,995
Everything original with the exception of the Combox.
Changed the VO date to 0911, but Combox was also working when I had it on the original VO date of 0310.
Ok, rear view camera didn’t work about the video inputs has been changes about BMW apps, so this must be FDL coded.
But BMW apps should be displayed… No Connected Drive in the Menu. Still says BMW Services.
The following process I did:
I’ve made some interesting progress. When I started the car this morning all of a sudden the “connected drive” menu appeared and BMW Apps is working!
So, it looks like perhaps it needed a reboot of the CIC after coding.
– There is no sound coming from the iPhone if I put it in the cradle, although it does connect. Prior to installing BMW Apps (with the 9c FSC code) I did have sound from the cradle.
– From the cradle I get an error that says “no plugin compatible device connected”
– Through the USB cable everything is fine.
– I’ve lost the rear view camera view. I’ve looked at the CIC CAFD and played around with the RCV_CIC setting. Right now it’s at 1, and I’ve also tried 21, but no luck. Could it be anything else?
Then the answer I got is:
For iphone sound via cradle need to fdl code usb2 to digital in cmedia. 6nr vo code seta it default to analogue.
For camera input code rvc_cic to wert_23.
For Plugin need to install FBAS line between cradle and CIC, will work only iphones/ipods with old connector not lightning connector.
All this is related to cradle used.
Music adapter can`t plan video, Music adapter was available as Mulf 2 High was up to date.
Media cradle was available for iPhone 4 / iPhone 4S with Lightning, Audio was analog with Aux.
The latest cradle is called Connect, this cradle is designed for cars with NBT system, but if you code the combox USB2 to digital, it will work in cars with Combox, too.

Wednesday, December 28, 2016

BMW NBT EVO Component protection

a friend gave me a NBT EVO from gxx series.
In fault memory i see that it has component protection active.
Is there a way to disable it.

ISTA 4 and ISTA/P (BN2020)
Introduction of component protection for Head Unit High 2

  • Benefit: To protect against theft, the Head Unit (HU-H2) of the specified vehicles with production date as of November 2016 is coupled to the Body Domain Controller (BDC).
  • Vehicles: G11, G12, G30, F15, F16, F85, F86, F54, F60 as of 11/16 can be dealt with
  • For the installation of a HU-H2 new part, the locking is performed automatically by ISTA 4 or ISTA/P.
  • In the following cases the component protection must be activated in order that the navigation function works properly:
    • For a cross-exchange of a HU-H2,Technical Support must perform the locking.
    • In the case of a BDC exchange the lock must be performed by Technical Support.
    • Also see PuMA measure 62960142
I would imagine it is possible, but not easy to circumvent.

Monday, December 26, 2016

How to detect in E-SYS which cafd (I-STEP Target) is the newest / right one?

can anybody please explain how to detect in E-SYS which cafd (I-STEP Target) is the newest / right one for e.g. a retrofitted 6WB?

I have selected one, but I am not sure to took the right one. Also I do not know which I-Step (shipment) I must chose when I want to flash this ECU?

My "setup"
Car is from 09/2011
Car actual F010-16-11-501
Car works (manufcture) F010-11-09-504

6WB is manufactured in 12/2014

You check dependencies in TAL-Editor to know which units must be on same level.

You can only choose shipment; HWEL should turn black if correct one matches. Target is selected automatically by loaded Psdzdata.

Thursday, December 8, 2016

How to diy an Ethernet cable

Sure, you can buy Ethernet cables from the store, but where's the fun in that? If you want to make custom cable lengths or crossover cables, or repair a broken connector, why not do it yourself? Here's how.
Before you get started, make sure you have the necessary tools, and decide whether you're going to use Cat 5e or Cat 6 network cables.
What you'll need:
  • Unshielded twisted pair (UTP) patch cable
  • Modular connector (8P8C plug, aka RJ45)
  • Crimping tool
  • Cable tester (optional, but recommended)
What you'll need
There are four pairs of wires in an Ethernet cable, and an Ethernet connector (8P8C) has eight pin slots. Each pin is identified by a number, starting from left to right, with the clip facing away from you.
8P8C connector pins
The two standards for wiring Ethernet cables are T568A and T568B. T568B is the most common and is what we'll be using for our straight Ethernet cable. The tables below show the proper orientation of the colored wires to the pins.

T568A Standard
Pin 1White/Green
Pin 2Green
Pin 3White/Orange
Pin 4Blue
Pin 5White/Blue
Pin 6Orange
Pin 7White/Brown
Pin 8Brown

T568B Standard
Pin 1White/Orange
Pin 2Orange
Pin 3White/Green
Pin 4Blue
Pin 5White/Blue
Pin 6Green
Pin 7White/Brown
Pin 8Brown
Step 1: Strip the cable jacket about 1.5 inch down from the end.
Strip the cable jacket

Step 2: Spread the four pairs of twisted wire apart. For Cat 5e, you can use the pull string to strip the jacket farther down if you need to, then cut the pull string. Cat 6 cables have a spine that will also need to be cut.
4 twisted pair wires
Photo by Ed Rhee
Step 3: Untwist the wire pairs and neatly align them in the T568B orientation. Be sure not to untwist them any farther down the cable than where the jacket begins; we want to leave as much of the cable twisted as possible.
T586B aligned

Step 4: Cut the wires as straight as possible, about 0.5 inch above the end of the jacket.
Step 5: Carefully insert the wires all the way into the modular connector, making sure that each wire passes through the appropriate guides inside the connector.
Insert wires

Step 6: Push the connector inside the crimping tool and squeeze the crimper all the way down.
Crimp connector

Step 7: Repeat steps 1-6 for the other end of the cable.
Step 8: To make sure you've successfully terminated each end of the cable, use a cable tester to test each pin.

But if you are not interested in building one and want to spend a little bit more money to get a working cable, then this is a site that has been confirmed working by some of our F10 friends: I wouldn’t recommend other sites, although they may work, problem is that they have not been confirmed working yet. Functions of enet cable at obdtool has been tested for years (many discussion in forums).
I have used my own cable there for half a year. His cables are great. He builds and ships them for $12 USD only. Usually, after he receives payment, he can have the cable ship the next day and arrived a week later.

Tuesday, December 6, 2016

Flash F22 to latest I-Level with ENET Cable

I want to complete program my F22 to the latest I-Level. I have an ENET Cable and was already able to connect with ISTA-P and the ISTA-P Loader (great work by the way to beemerboy88) to my car. I haven't started the flashing yet, because I'm still kinda worried that it may go wrong with the ENET Cable.

With the Loader you're not possible to flash MOST bus. But the F-Models don't have a MOST-Connection for ICOM-B anymore. So i decided to flash my a F-Model with ISTA-P and an ENET cable.

I also have Guides for that. 
1- connect your car
2- start loader
3- start ICOM Emulator INET F and enter IP address
4- start ISTA-P

that's all.  it seems more secure to flash with ISTA-P.

Monday, December 5, 2016

Possible reason for 0xD1 returned by FSC decoder

for some reason now one of the generators says:

"version after create() = 0xD1"

This was asked a long time ago, but since it is the most relevant GOOG result, and there doesn't seem to be an answer (except for 0x20h extra ASCII symbols) in here, I'd love to add another explanation.

The reason could be that the size of FSC/HEX file is incorrect. I've had this 0xD1 error when I've left an extra byte in edited generalPersistencyData_DiagnosticSWTController file.

If you edit this file to extract the 1B sequence, please be attentive to four bytes that prepend the 01 01 00 1B ... sequence of generalPersistencyData_DiagnosticSWTController. These four bytes (if you read them in reversed order) provide the length of 1B file (the number of bytes you must cut starting from 01 01 00 1B ... sequence [typically at 0x270 offset]).

The 1B length is typically 319 bytes, but it can be longer. If you cut out an incorrect number of bytes, FSC tool will return

Hope it helps other rookies like myself.

Friday, December 2, 2016

BMW F10 Gateway Module Pinout

Here is a drawing of the pinouts on an BMW F10 series gateway module.

Wednesday, November 30, 2016

How to use E-sys read 1B/DE file for bmw E/F series with CIC

Something interesting about Esys enet cable reading 1B/DE file (file 1B) from BMW E or F series with CIC.

Disclaimer: It’s all customer share from bmw topics/forums. Data copied only for share info to help someone else.

The methods applies to: BMW E and F series cars
You need: ENET cable / ICOM bmw + E-sys software

Process of reading 1B/DE file from CIC:
connect the BMW Esys cable to the car, and open FSC-exented, and compiled as in photos.
 follow the processes shown by the arrows, and have saved your file DE, in hex format.

Now if you open this file with hex editor, you will find the VIN of the CIC / NBT (in case you did not know)
Now if you open this file with hex editor, you will find the VIN of the CIC / NBT (in case you did not know)
 and you will get the file FSC (rename it as: F123456_000DE001.fsc) ready to be used with FSC generator.

Questions & Answers for reference:
- What is this for?
- One thing you can do with the 1b file is generate a FSC code for map updates.

- How to use the 1B file to generate a FSC code for other uses than GPS maps, or is does the same code work for every thing else that needs it?
- It's only for GPS maps, you cannot generate FSC codes for other functions.

- Can i obtain 1b files from E series with K+DCAN cable? or i need anyway an icom? 
It serves ICOM or FTP access from the network.

- If i need to use e-sys on E series with cic, it is possible with enet ?
- Yes, the ENET cable (costs less 20 euro) can be used with CIC in E series. (But it must be wired by the cic to the OBD port

use access login, and save the file: generalPersistencyData_DiagnosticSWTControlle 
in position : // HBpersistence / normal 
(do not ask data login thanks) 

This file contains the file 1B.
open with hex editor, and look for the 'index: 01 01 00 1B (early 1b files)
and copy 319 decimal successive,included 01 01 00 1B.
This works, but with some conditions:
1. The CIC in your car must be factory fitted. When it is retrofit there is no Ethernet connection between OBD and CIC.
2. CIC must get IP address from DHCP to be accessible by ftp. Easy way is to connect enet cable to router and restart the CIC. After CIC restart it will have it's own IP.

(BIG THANKS to duck donald and others shares info at and

Tuesday, November 29, 2016

E-sys bmw 3.24.3 vs E-sys enet 3.25.2

BMW E-sys v3.24.3 is verified to work better than Esys enet v3.25.2. Download esys 3.24 software here and experience it yourself to get the points of what users say.

E-sys 3.24.3 download:

E-sys 3.24.3 vs E-sys enet v3.25.2
Esys 3.25.2 was broke, and 3.25.3 works but has bugs, and until they are fixed, E sys 3.24.3 is a wiser choice. (E-sys v3.22.5 version also good to use) Those in the know don't use it and recommend against using it for a reason

E-sys bmw 3.24.3 review
- That might work with a May delivered car. 
It works fine on my 14 plate. But I suspect they will have updated it by then. When you get the car you need to read the I-Step to ensure you are using the right software.

- that software and data works fine. 
I-Step is the version of data that your car was originally written with. E-Sys will tell you this information

E-sys software v3.25.3 review
I tested e-sys 3.25.3 back in December, almost 1/2 year ago, when it first came out, and there were issues with it, so I went back to 3.24.3. 

I don't recall specifically. but I remember that functionally it seemed to work, but the UI was displaying bizarre things, particularly in the ToolTips, which was enough for me to know it came out of the oven too early. 

In addition, the security was completely changed in 3.25.3, including not just the "patch" needed, but also the .EST Token itself, so anyone switching would need a completely new Token solution. 

Since 3.25.3 adds zero functionality though, there is no reason nor benefit to use it. If you are not having any issues with it, stick with it, or you can drop down to previous version. Whatever works for you.

Tips when using bmw e-sys enet
About MAC E-Sys version:
There is no MAC E-Sys version. You have to run it in a VM / Parallels on a MAC.
TokenMaster began a project to port E-Sys over to MAC, and made some good progress, but then hit a brick wall.
About token:
As for your token solution, you can put the .EST file anywhere. You just need to go under E-Sys Options and set the .EST Path to point to wherever you located it.

But, token solution is more than just the .EST Token file. You should have 2 patched .jar files that you need to replace E-Sys' native .jar files with.

About PSdZData:
The PSdZData version being used is >= to the last version of ISTA/P used to program the car. If you use the latest PSdZData, then you don't have to worry about it. Otherwise, you will need to read I-Step current from VCM, cross-reference it to the ISTA/P version, and determine if your PSdZData version is >= to it.

The I-Level (aka I-Step) is the Integration Level of your car, which represents a package of firmwares for all your modules, and it corresponds to the version of ISTA/P last used to program your vehicle.

To determine your I-Level, go to VCM Module => VCM Master Tab => click Read under I-Steps: 
 The I-Step (current) is the one you want to match when you select the CAFD from the Detect CAF for SWE options (e.g. F001-08-09-550):
When you lost power in the middle of FDL Coding your CAFD, it became corrupted. What I am having you do is insert the same CAFD in it's default generic state and then coding it based on your specific Vehicle Order (Production Date and Option Codes) so in the end you will have exactly what you started with before the power failure and CAFD corruption.

As I have repeatedly stated, so long as one isn't coding the DME module, you should code with the engine running, and will you never have to worry about loosing vehicle power mid-coding, unless of course you run out of gas.