[ramez75]

Can you share the pdf.....I am planning to do the Front and Rear PDC install and I am trying to figure out the coding part prior to installing.

So it seems I have to add VO = $508, do I need to add $507 also for rear?

So the JobName = FA_Write and what do I do that to every module. My other question do I need to recode my modules when I do that, for example I have currently disabled the Nav disclaimer, I see the V on the digital display, disabled the dong sound when the door is open, etc. Will I lose all that

Thanks

Originally Posted by dav_lph

Hi ERIK335i, when you mentioned about updating all the modules after adding VO. What selection is it exactly? Currently I am using SG_CODIERN for most of the coding as per the DIY pdf.

Planning to retrofit FRONT PDC and thus would need to add VO $508 (Front and Rear PDC) to CAS and NFRM (I have the instruction for doing that) but I am not sure how to code ALL modules.

Appreciate your help

[kaiv]

How can I get access to edit the spreadsheet? Or if somebody wants to add the following.

I was looking to disable the angel eye bulb check but I don't have the lines mentioned in the spreadsheet on my 2010.

What worked was those two (nicht_aktiv; in NFRM)

KALTUE_SL_1_M1_14_M2_41
WARMUE_SL_1_M1_14_M2_41

Thanks to all who contributed!

[arc1880]

I've recently downloaded the E89 v45 daten files. Would anyone happen to know what the password is to extract from the rar files?

[Coly]

Originally Posted by arc1880

I've recently downloaded the E89 v45 daten files. Would anyone happen to know what the password is to extract from the rar files?

That's dependant on where you got the files.
Best bet is to find another source, check where you downloaded them from or try and crack the password

[saxon]

who wants to make some money and help me set up my laptop?

i have downloaded everything (as far as i know) and i get an error #126 (api-0006 access denied, no api calls possible

willing to throw paypal to someone who can help

saxonbrian2 at yahoo.com

[deezofchuck]

Originally Posted by AW128i

I am able to do coding on my MBP using Windows 7 under Parallels. The coding programs are Windows-only.

did you have to do anything special with the settings to get it work? i can get the black check lights in the first steps - but i get communication errors when trying to do the coding

[jphughan]

Originally Posted by deezofchuck

did you have to do anything special with the settings to get it work? i can get the black check lights in the first steps - but i get communication errors when trying to do the coding

Please, PLEASE . It's been explained many, many times even in this very thread that the likely causes of that are:

1. Using an old driver for the cable, in which case case update it.
2. Forgetting to set the Latency setting to 1 rather than its default 16, in which case change it (if you don't have that setting, you're using the old driver).
3. Using a cable from a vendor other than the one recommended here, suggesting that either the cable is shoddy or you have Pin 8 still active (the Pin 8 debacle has been discussed several times as well).

I understand that this thread is very long and it's no longer practical to tell people to read all of it, but a major reason it's this long is because the same questions are asked repeatedly. Please do your part to reduce thread redundancy.

[deezofchuck]

Actually, I read the entire thread almost in its entirety - but I asked a SPECIFIC person a very SPECIFIC question because he is using a macbook with parallels which would lead to issues that is not as commonly discussed. I am not a new member that doesn't know how to research an item before asking a question.

I already did all the steps you described so instead of taking all that time to tell me to search you could have left me something useful to read.

You sir also add to the "thread redundancy" by saying worthless things such as your quoted comment. Had I asked the thread NOT an individual something like - how do I get started or what cable do I buy or how do I download software, etc..maybe your comment would have been warranted.

you are actually worse than those people who go around asking noob questions because you didn't even READ my question. You jumped at the chance of telling something to "READ THE DAMN THREAD YOU MORON."

basically - you are a douchebag trying to lace a douchebag comment with smiley faces and "nice" connotation.

</rant>

Originally Posted by jphughan

Please, PLEASE . It's been explained many, many times even in this very thread that the likely causes of that are:

1. Using an old driver for the cable, in which case case update it.
2. Forgetting to set the Latency setting to 1 rather than its default 16, in which case change it (if you don't have that setting, you're using the old driver).
3. Using a cable from a vendor other than the one recommended here, suggesting that either the cable is shoddy or you have Pin 8 still active (the Pin 8 debacle has been discussed several times as well).

I understand that this thread is very long and it's no longer practical to tell people to read all of it, but a major reason it's this long is because the same questions are asked repeatedly. Please do your part to reduce thread redundancy.

[jphughan]

Originally Posted by deezofchuck

Actually, I read the entire thread almost in its entirety - but I asked a SPECIFIC person a very SPECIFIC question because he is using a macbook with parallels which would lead to issues that is not as commonly discussed. I am not a new member that doesn't know how to research an item before asking a question.

I already did all the steps you described so instead of taking all that time to tell me to search you could have left me something useful to read.

You sir also add to the "thread redundancy" by saying worthless things such as your quoted comment. Had I asked the thread NOT an individual something like - how do I get started or what cable do I buy or how do I download software, etc..maybe your comment would have been warranted.

you are actually worse than those people who go around asking noob questions because you didn't even READ my question. You jumped at the chance of telling something to "READ THE DAMN THREAD YOU MORON."

basically - you are a douchebag trying to lace a douchebag comment with smiley faces and "nice" connotation.

</rant>

Um, wow. Let's review:

1. If you only want an answer from a specific person, PM them. Quoting someone doesn't mean you only expect an answer from them. If you post in a thread, the assumption is that you're open to responses from the general population.

2. The fact that you're running an MBP with Parallels doesn't mean that some of the conventional wisdom and pitfalls wouldn't apply to you. And I'm sorry if you'd tried all of the things I recommended, but I had no way to know that from what you posted. It's not as if you said, "Here's my setup, I've read the thread and here's what I've tried unsuccessfully so far" so the rest of us would know that we could skip the typical recommendations that help the vast majority of the people on here. All you said was, "Here's my setup, here's the problem I have, what settings should I check?" I gave you basic troubleshooting information because you gave a basic description of your problem.

3. I definitely read your question, evidenced by the fact that ALL of the things I listed can cause the behavior you're seeing. And if you read this thread as well as others you'll find that I'm not some "douchebag" who doesn't bother to read people's questions and jumps at opportunities to piss people off. I post when I feel I can contribute something worthwhile, and responses to my posts from other members here and elsewhere indicate that they appreciate most of what I say. Look me up or ask around. Nothing in my post indicates that I didn't read yours, just that you didn't provide sufficient information for any more advanced recommendations. I told you to read the thread because your post made you sound like every other person who's posted here asking the same damn question over and over again -- but even so, if you read back you'll find that I've already taken time to answer THOSE people, just as I answered you. If I'd wanted to be a douchebag, my response to you would've just been the Search emoticon; instead, I typed up a list of troubleshooting steps, which incidentally helped someone else here who was running YOUR EXACT SETUP. No good deed goes unpunished, I guess.

4. Even my smiley was sincere. I meant that as a "I'm happy to help, but please search next time", not as an F- you couched with a smile.

Chill out.

[deezofchuck]

If your intentions are good - so be it and I thank you for your input - but your posts to me have been nothing short of condescending - not that I will lose sleep over it - but since I am bored at work right now I will respond to this:

1) thank you - i had NO idea what PMs were for - I am NOW enlightened b/c of your forum knowledge. What does PM stand for? Oh wait - could it have been because if I post it and he answers with any specific settings he changed to get it to work then maybe the next guy who SEARCHES will see the answer? Seems like to be that's the whole point isn't it? Or I could....PM was it? PM him and get the answer for myself.

2) you still are not clear about my problem - and I didn't ask the whole thread for help b/c I would get answers like yours. This is why I asked if he used any SPECIAL settings - which would lead one to assume that I followed the NORMAL settings.

3) Yes all your rec's apply to me but that's not the point. The point is if there are issues from using a MBP and Parallels to run XP 32-bit. I never said I used a MBP I don't follow the same rules. I was asking for a specific answer.

Could have I premised my question with more info - sure - I am guilty of that here - but I was just asking a quick question to someone who got it to work with MY set up.

I'm glad we added more insightful thoughts to this already long thread.

Originally Posted by jphughan

Um, wow. Let's review:

1. There's a built-in function for specific questions to specific people called PMs. If you only want answers from that person, only contact that person, or if you must post in the thread, at least make it clear in your post that you're only asking that specific person. Quoting someone doesn't mean you only expect an answer from them.

2. The fact that you're running an MBP with Parallels doesn't mean that some of the conventional wisdom and pitfalls wouldn't apply to you. It's not as if you said, "Here's my setup, I've read the thread and here's what I've tried unsuccessfully so far" so the rest of us would know that we could skip the typical recommendations that help the vast majority of the people on here. All you said was, "Here's my setup, here's the problem I have, what settings should I check?" I gave you basic troubleshooting information because you gave a basic description of your problem.

3. I definitely read your question, evidenced by the fact that ALL of my recommendations apply to the behavior you're seeing. And if you read this thread as well as others you'll find that I'm not some "douchebag" who doesn't bother to read people's questions and jumps at opportunities to piss people off. I post when I feel I can contribute something worthwhile, and responses to my posts from other members here and elsewhere indicate that they appreciate most of what I say. Look me up or ask around. Nothing in my post indicates that I didn't read yours, just that you didn't provide sufficient information for any more advanced recommendations. I told you to read the thread because your post sounded a lot like other people's who have posted here asking the same damn question over and over again. If you read back you'll find that I've already taken time to answer the same questions several times without even saying "Read the thread". If I'd wanted to be a douchebag, my response to you would've just been the Search emoticon; instead, I typed up a list of troubleshooting steps, which incidentally helped someone else here who was running YOUR EXACT SETUP. No good deed goes unpunished, I guess.

4. Even my smiley was sincere. I meant that as a "I'm happy to help, but please search next time", not as an F- you couched with a smile.

Chill out.

[vazdom]

I have this error on inpa

BIP 0009 best version error

So i think I need ediabas 7.2

Someone can post the link where I can download files?

and How I can Update to 7.2?? I have 6.4.7 ediabas for now.



Thanks !

[Shaggy]

Just search for bmw standard tools 2.11 on google , you should be able to find it

[vazdom]

Originally Posted by Shaggy

Just search for bmw standard tools 2.11 on google , you should be able to find it

Ok, here is what i did.


1. I downloaded ediabas 7.2 (piratebay)

2. I make a copy of my ediabas folder and I rename and created a new folder Ediabas.old

3. I create a new Folder named Ediabas

4. I unrar all the files from the new ediabas to the new folder I named ediabas

5. I copy the file Ediabas.ini from the old ediabas.old folder and Paste on the new BIN folder that is Into ediabas folder.


and thats all

Now I updated ediabas

The only problem is that when I try to read engine I have IFH 0009 D motor

[kevininc1]

Originally Posted by bmw_jason

Ok guys I need some big help!

I have coded a few things and all was working well. Except now I noticed that My windows on my Coupe do not auto slightly open and slight close when opening and closing my door. The way they normally would do to make a tight seal?

Any idea why this may be? Did I change a value that I shouldn't have?

Anyone know which code operates this?

what was the solution to this issue? i have had the same thing happen and i have had the windows re-taught though inpa and manually..wtf?

[Shaggy]

Originally Posted by vazdom

Ok, here is what i did.


1. I downloaded ediabas 7.2 (piratebay)

2. I make a copy of my ediabas folder and I rename and created a new folder Ediabas.old

3. I create a new Folder named Ediabas

4. I unrar all the files from the new ediabas to the new folder I named ediabas

5. I copy the file Ediabas.ini from the old ediabas.old folder and Paste on the new BIN folder that is Into ediabas folder.


and thats all

Now I updated ediabas

The only problem is that when I try to read engine I have IFH 0009 D motor

You dont have proper inpa installation and daten files for your engine as long as no scripts ( or wrong scripts) for your engine. Ediabas itself is not enough tho

[jphughan]

Originally Posted by vazdom

Ok, here is what i did.


1. I downloaded ediabas 7.2 (piratebay)

2. I make a copy of my ediabas folder and I rename and created a new folder Ediabas.old

3. I create a new Folder named Ediabas

4. I unrar all the files from the new ediabas to the new folder I named ediabas

5. I copy the file Ediabas.ini from the old ediabas.old folder and Paste on the new BIN folder that is Into ediabas folder.


and thats all

Now I updated ediabas

The only problem is that when I try to read engine I have IFH 0009 D motor

You need to update the contents of the ECU folder in your new EDIABAS, or pull them from your old folder as well.

[kevininc1]

e92 coding/windows!

--------------------------------------------------------------------------------



Quote:




Originally Posted by bmw_jason

Ok guys I need some big help!

I have coded a few things and all was working well. Except now I noticed that My windows on my Coupe do not auto slightly open and slight close when opening and closing my door. The way they normally would do to make a tight seal?

Any idea why this may be? Did I change a value that I shouldn't have?

Anyone know which code operates this?


what was the solution to this issue? i have had the same thing happen and i have had the windows re-taught though inpa and manually..wtf?

I know someone else has done this and found the fix..someone share some info pls

[toicy4ya]

Sup Guys,

Following the NCS_DIY which has been going good. However, i'm stuck on FSW PSW.MAN. The NCS_DIY state the following;

52. Load NCS >File>load profile “FSW PSW MAN”
53. F1>F3>select your chassis>select “CAS”
54. Press F6 for back
55. Press F4 to select a specific module “process ecu” then you get a list of all modules on your car will and may be different.
56.
57. Select “CAS” then select “READ ECU” this is going to create another FSW_PSW.TRC file but only with the values on for the module we select.
58. Select “READ ECU” this will read all the values from the specific module and place ten in the file stated above. You will get a screen like this. You can close it.

59.
60. Leave ncs open and head to the “work” folder.
61. Open the FSW_PSW.TRC file with notepad
62. File>save as FSW_PSW.MAN (be sure to select “save as type” to all files so that it will accept our “.MAN” extension. If you fail to do so it will just save it as a text file .TXT
63. The “FSW PSW MAN” profile that we used is going to use this “FSW_PSW.MAN” file this is where we are going to make any changes and then NCS will write this to ECU.
64. Open the file we just saved with notepad will look like this.
65.


This is where I believe the error comes in. My FSW_PSW.MAN file looks like this


Additionally my FSW_PSW.TRC file looks like this. The list is short and it doesn’t have the “BC_DIGITAL_V” file?


The FSW_PSW.TRC was only 7kb but the one that I had backed up following the instructions was 220kb. So I deleted the 7kb and replaced it with the 220kb file (which had in it the BC_Digital_V). Then I opened it using notepad and saved it as FSW_PSW.MAN and attempted to code the car using this file. Someone mentioned that i could have potentially bricked my car, how can i confirm if my car is indeed "bricked"?

Can someone offer some assistance?

[jphughan]

Originally Posted by toicy4ya

Sup Guys,

Following the NCS_DIY which has been going good. However, i'm stuck on FSW PSW.MAN. The NCS_DIY state the following;

52. Load NCS >File>load profile “FSW PSW MAN”
53. F1>F3>select your chassis>select “CAS”
54. Press F6 for back
55. Press F4 to select a specific module “process ecu” then you get a list of all modules on your car will and may be different.
56.
57. Select “CAS” then select “READ ECU” this is going to create another FSW_PSW.TRC file but only with the values on for the module we select.
58. Select “READ ECU” this will read all the values from the specific module and place ten in the file stated above. You will get a screen like this. You can close it.

59.
60. Leave ncs open and head to the “work” folder.
61. Open the FSW_PSW.TRC file with notepad
62. File>save as FSW_PSW.MAN (be sure to select “save as type” to all files so that it will accept our “.MAN” extension. If you fail to do so it will just save it as a text file .TXT
63. The “FSW PSW MAN” profile that we used is going to use this “FSW_PSW.MAN” file this is where we are going to make any changes and then NCS will write this to ECU.
64. Open the file we just saved with notepad will look like this.
65.


This is where I believe the error comes in. My FSW_PSW.MAN file looks like this


Additionally my FSW_PSW.TRC file looks like this. The list is short and it doesn’t have the “BC_DIGITAL_V” file?


The FSW_PSW.TRC was only 7kb but the one that I had backed up following the instructions was 220kb. So I deleted the 7kb and replaced it with the 220kb file (which had in it the BC_Digital_V). Then I opened it using notepad and saved it as FSW_PSW.MAN and attempted to code the car using this file. Someone mentioned that i could have potentially bricked my car, how can i confirm if my car is indeed "bricked"?

Can someone offer some assistance?

It's a well-known typo on the DIY that BC_DIGITAL_V is in KOMBI, not CAS. You still select CAS on the first prompt, but when you get to the large list of modules, you select KOMBI.

The 220KB file you see at the beginning (and immediately after coding any module) is a trace file for your entire car, and you should NEVER flash individual modules using that file. Technically you could use that with the Process Car command, but that's really not recommended. The TRC files you see after reading an ECU are always going to be much smaller because they only contain the parameters of the module you selected, and THOSE are the ones you should be modifying, saving as MAN files, and coding back to the car.

Also, I have no idea what that screenshot is where you say that's what your MAN file looks like. It appears that .MAN files are associated with some other app on your computer, in which case right-click the MAN file, choose Open With, and choose Notepad (if that's not available, click Browse and go to C:\Windows\System32 to find it).

[toicy4ya]

Thanks, I will do that. However, with repect to your response concerning opening the MAN file with notepad, step 62. Indicates to select “save as type” to all files so that it will accept our “.MAN” extension. If not it will save it as a text file. Wouldn't opening it with notebook be opening it as a text file?

Btw, considering that I deleted the 7kb and replaced it with the 220kb file (which had the BC_Digital_V) and attempted to code the car using this file. Could I have potentially bricked my car? I drove it this morning and didnt notice anything different. How can i confirm if my car is indeed "bricked"? Also is there any special steps I need to take as a result of my error using the 220kb file I mentioned above?

Thanks in advance

[jphughan]

Originally Posted by toicy4ya

Thanks, I will do that. However, with repect to your response concerning opening the MAN file with notepad, step 62. Indicates to select “save as type” to all files so that it will accept our “.MAN” extension. If not it will save it as a text file. Wouldn't opening it with notebook be opening it as a text file?

Btw, considering that I deleted the 7kb and replaced it with the 220kb file (which had the BC_Digital_V) and attempted to code the car using this file. Could I have potentially bricked my car? I drove it this morning and didnt notice anything different. How can i confirm if my car is indeed "bricked"? Also is there any special steps I need to take as a result of my error using the 220kb file I mentioned above?

Thanks in advance

If your car is running fine with no abnormal behavior, you're probably fine -- but just to be safe, you should pull new traces of your CAS and KOMBI modules just to make sure they look ok, i.e. they're not 220KB large. Also, keep that 220KB file as a backup and for reference, and ALWAYS back up the TRC files of the modules you code before you change values in case you mess up and need to revert to a known good configuration. If you did that when you were reading those modules, put the backed up configs into the MAN file and code those modules with that file. If you didn't back up, then shame on you.

If you open a file in Notepad that already has a MAN extension, make changes, and click Save (not Save As), it will retain the existing file name; it won't add a .TXT extension. The TXT extension is just Notepad's default when saving out to a new file. Personally I find it easier not to use the recommended Save As routine. Instead, I've set up my computer to open up TRC and MAN files in Notepad, so now I can read a module, open the TRC file, copy/paste its contents into the MAN file, make the changes, and click Save. It saves a lot of clicks and typing.

[toicy4ya]

Is there a link that might provide instructions on how to pull the new traces of the CAS and KOMBI modules just to make sure they look ok. *