[Pete Schweaty]

Originally Posted by srwatters

When you guys are updating daten and sgdat folders, are you replacing ALL files or just updating the newer files using Total Commander or another tool like it?

Open the new SGDAT folder, select all, copy.

Open the old SGDAT folder, paste items, you will be asked if you want to replace old files with the same names (or some prompt like that), select "yes to all"

Do the same with the daten files. You only need to update the e89 folder if that is your chassis.

Dont forget to keep an original copy of your ecu folder so you can access all the modules. I know the NFRM module needs the old ecu folder to work. Not sure of any others.

[everlast]

You can use xcopy to update files that are only newer.. something like this:

c:\extracted_files\>xcopy ediabas c:\ediabas /D

(I'm doing this from memory, but the /D is correct. It only copies the source if its newer than the destination.)

[Elliott@DetailAddict]

Originally Posted by Pete Schweaty

I have a 2007 335. V42 works for me.

Dont forget to keep an original copy of your ecu folder so you can access all the modules. I know the NFRM module needs the old ecu folder to work. Not sure of any others.

So strange. Seems that I'm the only one that has a fully functioning (v41 e89 at least) version that works with every module.

[srwatters]

Still banging my head against the wall here... I'm able to get to pretty much any other module except for the one I need, MEDIA. The error I'm getting now is SYS-0005: OBJECT FILE NOT FOUND A_E65R.IPO.

I've checked the SGDAT folder and there is indeed a file called a_e65r.ipo present. I've tried replacing it with any of the versions from V40, V41, V42 & V43. Is it possible that there is a new file somewhere out there (V44)? Remember that I just had the entire car coded over the weekend at the dealer?

Is there any way for me to query all the versions that are in the car?

[srwatters]

I found the secret sauce to get to the MEDIA box. I had to upgrade EDIBAS to 7.2. That also killed the need to swap out ECU folders, which is really nice. I can get to all modules with the one software setup. That's the good news. Unfortunately changing the VO (adding $6NR) and recoding CIC and MEDIA, like I did before, did not re-enable BMW Apps. It did bring back the greyed out snap-in adapter icon on the external devices screen, but no joy on using any of the toys.

Does anyone with updated firmware and BMW Apps want to offer up TRC files of their CIC and MEDIA modules for me to examine just in case I missed something?

[rambalu80]

Originally Posted by Pete Schweaty

I have a 2007 335. V42 works for me.

Dont forget to keep an original copy of your ecu folder so you can access all the modules. I know the NFRM module needs the old ecu folder to work. Not sure of any others.

Okay, thanks!

[jtsui]

Originally Posted by srwatters

I found the secret sauce to get to the MEDIA box. I had to upgrade EDIBAS to 7.2. That also killed the need to swap out ECU folders, which is really nice. I can get to all modules with the one software setup. That's the good news. Unfortunately changing the VO (adding $6NR) and recoding CIC and MEDIA, like I did before, did not re-enable BMW Apps. It did bring back the greyed out snap-in adapter icon on the external devices screen, but no joy on using any of the toys.

Does anyone with updated firmware and BMW Apps want to offer up TRC files of their CIC and MEDIA modules for me to examine just in case I missed something?

Hi Srwatters,
Do you know what version of daten is needed to code E70 tailgate close by the button inside the cabin?

Thanks
jack

[srwatters]

Originally Posted by Pete Schweaty

Dont forget to keep an original copy of your ecu folder so you can access all the modules. I know the NFRM module needs the old ecu folder to work. Not sure of any others.

This is no longer needed if you upgrade to EDIBAS 7.2. I was able to code all modules with V43 daten and the V43 ECU folder.

[ramez75]

srwatters,

I am planning to update to 7.2 this weekend, how did you do it. I already am using V43 daten. I keep swapping ECU folders and would like to not to swap any more.

1. Copy Edibias (ver 7.2) Folder to C: drive to override Edibias (ver 6.4.7)
2. Run OBDSETUP in EDIBIAS/HARDWWARE/OBD
3. Reboot PC

Are these the steps you followed

Thanks

[srwatters]

Rename EDIBAS folder to EDIBAS.OLD
Copy 7.2 EDIBAS folder to C:\
Copy ECU folder (with V43 updates) to the EDIBAS folder

Reboot and then run NCSEXPERT. All is good!

[ramez75]

Can I then delete Edibias.Old or I have to leave it?

[srwatters]

Originally Posted by ramez75

Can I then delete Edibias.Old or I have to leave it?

I deleted it from my laptop, but I have copies on another machine. BTW, I'm all Mac and using a virtual machine under VMWare Fusion. Works like a charm!

[jphughan]

Originally Posted by srwatters

I deleted it from my laptop, but I have copies on another machine. BTW, I'm all Mac and using a virtual machine under VMWare Fusion. Works like a charm!

You shouldn't have to run the OBD Setup file again, but you MIGHT have to update Ediabas.ini in your BIN folder. Some packages have a bizarre path for the TRACE folder in the first few lines; change that to c:\ediabas\Trace and you should be fine.

[ramez75]

Originally Posted by jphughan

You shouldn't have to run the OBD Setup file again, but you MIGHT have to update Ediabas.ini in your BIN folder. Some packages have a bizarre path for the TRACE folder in the first few lines; change that to c:\ediabas\Trace and you should be fine.

I already checked the ini file the path is pointing to the correct file. I might give it a shot when I get home and see if it works by testing it on the VIM

[Bender1012]

If I update to Ediabas 7.2 and Daten v43 will I be able to code all modules in both pre-LCI 2007 and LCI 2011?

[srwatters]

Originally Posted by jphughan

You shouldn't have to run the OBD Setup file again, but you MIGHT have to update Ediabas.ini in your BIN folder. Some packages have a bizarre path for the TRACE folder in the first few lines; change that to c:\ediabas\Trace and you should be fine.

I didn't. And the ini file was correct.

[ramez75]

Ok that wasnt so bad. I deleted the old Edibias and pasted the 7.2 Edibias in C:. Also added the V43 Ecu file. Rebooted and did a quick check and was able to open the CIC module and others

[Snyperx]

Just got my cable. Let the fun begin. I'm not sure why people were having to wait weeks for the cable I got mine in a week from Hong Kong for $85 off eBay.

[ramez75]

Originally Posted by toni8284

In NCSExpert:

File > Load profile > Expertmode > OK
File > edit profile (Password is 'repxet')
Select 'car-keymemory' (check all 3 boxes) > OK
Select 'Consistency Check' (should say 'OK') > OK

Instead of it say 'OK' it gives me error "ind-eer-03"

Did you get the VIM to work......I followed the instructions of method 2.
1. I run CIC and changed the Video_NUR_MIT_HANDBREMSE to nicht_aktiv
2. Speelock_X to 3_kmh
3. Loaded back into the car using NCSEXPER
4. Backedup CIC.C10
5.Change 03 to FF and saved in daten of E89 folder.
6. Rerun CIC and there was no Speedlock_X in the TRC file I got from the car...

I guess thats good but I still cant watch the DVD, I get the safety screen. So Second Approach according to the DIY didnt work for me. The instructions seems sraight forward. Any ideas

On the other hand I tried approach 1 and that worked fine for me.....but i was just curious why the 2nd approach didnt work.

[Snyperx]

Well after getting my cable I made my first attempt in getting connected to my e90. FAIL. When I launch the Inpaupload program I get some kind of registry key missing. I also could not find the settings for the COM as mentioned in the DIY. I am on Vista 32-bit.

[ramez75]

I tried the VIM today to make sure that using Approach 1 worked, but to my disappointment, i got the safety message. So it didnt work. I am suppose to try approach 1 multiple times for it to stick..

Did anyone run into that issue, any suggestions?

[Elliott@DetailAddict]

Approach 2 FTW every time.