[ferocity02]

I'm trying to do some coding and since there isn't a single, up-to-date, coherent guide out there, Ive been trying to piece it together from multiple outdated sources. Here is some of my info:

04/2007 E90 335i
Windows XP 32bit
Amazon $30 K+DCAN cable
BMW Coding Pack
SP-daten 53.3 (updated using BMW Coding Tool)
NCS-Expert v4.0.1

Creating profile:
Open NCSexpert
Load Profile
Choose Default Profile
Edit Profile
Click Car-Key Memory
Select all 3 boxes
- Car-Keymemory active
- Kernel functions
- Trans individualizable FSW-/PSW
Press OK
Consistency check
Click FSW/PSW
Select both check boxes and "from CVT"
- FSW-/PSW-Trace
- FSW-/PSW-Manipulate with FSW_PSW.MAN
Press OK
Consistency check
Save profile as FZG4.pfl
Change profile name to "FSW PSW MAN"
Close NCSexpert

Coding Digital Speedo:
Open NCSexpert
Choose "FSW PSW MAN" profile that was created
Hit F1: FG/ZCS/FA
Hit F3: ZCS/FA f. ECU
Choose E89
Choose CAS
Hit F6: Back
**At this point, FSW_PSW.TRC in the WORK folder is updated and is 235 kb, and it contains BC_DIGITAL_V
Hit F3: Process ECU
Select CAS
Hit F2: Change Job
Select CODIERDATEN_LESEN
Hit F3: Execute Job
At this point, FSW_PSW.TRC is updated again and is now 8 kb, it does not contain BC_DIGITAL_V.
... now what?

Why does the BC_DIGITAL_V (among other things) disappear from the trace file when I read the ECU? Aren't both trace files from the CAS module?

Or am I supposed to edit the trace file after hitting F6: Back, and then save it as a MAN, and then write it to the ECU?

Did I do the profile setup correctly?


Here are a couple guides I was going off of:

http://www.bmw coding. com/attachment.php?attachmentid=9&d=1297211628

http://danmcq.com/bmw/BMW-CODING-WIT...XPERT-2011.pdf



Thank you for the help!

[ferocity02]

I found the following guide that seems better than the others. It seems to suggest that all of the coding steps I have laid out are correct so far. However, I am wondering why the BC_DIGITAL_V parameter was in the trace file, and then isn't even though I'm reading the CAS both times.

Perhaps I need to be looking in the KOMBI module, not CAS like the first guide suggests.

http://forums.bimmerforums.com/forum...ith-NCS-Expert

[Sensible_]

BC_DIGITAL_V is a setting in KOMBI.

In your NCS-Expert guide you 'choose' CAS as that is one of the modules where your VO (Vehicle Order) is stored. Your aren't actually coding the CAS at this point.

[ferocity02]

Originally Posted by Sensible_

BC_DIGITAL_V is a setting in KOMBI.

In your NCS-Expert guide you 'choose' CAS as that is one of the modules where your VO (Vehicle Order) is stored. Your aren't actually coding the CAS at this point.

So is the 235kb trace file from the initial read for all of the modules, and the 8kb trace file is only for the CAS?

For some reason NCSdummy couldn't read the large trace file, but it could read the small trace file.

Also, the VIN that comes up in NCSexpert is the same as mine, but it has an extra "L" at the end. Will this cause a problem?

[wildcatcrazy]

Originally Posted by ferocity02

So is the 235kb trace file from the initial read for all of the modules, and the 8kb trace file is only for the CAS?

For some reason NCSdummy couldn't read the large trace file, but it could read the small trace file.

Also, the VIN that comes up in NCSexpert is the same as mine, but it has an extra "L" at the end. Will this cause a problem?

The L is your checksum, which won't cause a problem.

[spencers]

Originally Posted by ferocity02

So is the 235kb trace file from the initial read for all of the modules, and the 8kb trace file is only for the CAS?

Yes

I always clear out the trace file after it dumps the initial read; before I process the ECU I want to play with.

As for your first post, save the .TRC as a .MAN when you're done manipulating the code.

[ferocity02]

Originally Posted by spencers

Yes

I always clear out the trace file after it dumps the initial read; before I process the ECU I want to play with.

As for your first post, save the .TRC as a .MAN when you're done manipulating the code.

Thanks!

Why do you need to empty the TRC file after the initial read? When you read the specific module it seems to overwrite it anyways.

People also seem to suggest clearing the MAN file after writing. Again, not sure what the point of this is since you overwrite the MAN file with the modified TRC file.

[js335in54]

Originally Posted by ferocity02

Thanks!

Why do you need to empty the TRC file after the initial read? When you read the specific module it seems to overwrite it anyways.

People also seem to suggest clearing the MAN file after writing. Again, not sure what the point of this is since you overwrite the MAN file with the modified TRC file.

if you need help i can help you remotely , so you can understand more the basic of coding

[ferocity02]

Originally Posted by js335in54

if you need help i can help you remotely , so you can understand more the basic of coding

Thank you for the offer, just trying to figure this out on my own first.

Is the purpose of cleaning the MAN file after coding to ensure that if you accidentally write to the module you will be writing a blank MAN file?

Writing a blank MAN file returns it to default correct?

I still don't understand the purpose of clearing the TRC file since it gets overwritten every time you read a module.

[spencers]

Originally Posted by ferocity02

Thank you for the offer, just trying to figure this out on my own first.

Is the purpose of cleaning the MAN file after coding to ensure that if you accidentally write to the module you will be writing a blank MAN file?

Writing a blank MAN file returns it to default correct?

I still don't understand the purpose of clearing the TRC file since it gets overwritten every time you read a module.

I think both of the above are really just a "fresh slate" type of mentality. At least for me, that is.

[ferocity02]

Originally Posted by spencers

I think both of the above are really just a "fresh slate" type of mentality. At least for me, that is.

That's the vibe I was getting.

Am I correct in saying that if you attempt to write a blank MAN file, it will write default values instead?

[spencers]

Originally Posted by ferocity02

That's the vibe I was getting.

Am I correct in saying that if you attempt to write a blank MAN file, it will write default values instead?

Yep

[J-Spec Dan]

Originally Posted by spencers

I think both of the above are really just a "fresh slate" type of mentality. At least for me, that is.

it has caused issues for me dumping the trace files. i cleared what was inside the .TRC and .MAN files and then dumped fine.

[js335in54]

Originally Posted by ferocity02

Thank you for the offer, just trying to figure this out on my own first.

Is the purpose of cleaning the MAN file after coding to ensure that if you accidentally write to the module you will be writing a blank MAN file?

Writing a blank MAN file returns it to default correct?

I still don't understand the purpose of clearing the TRC file since it gets overwritten every time you read a module.

i work with many series and i never empty the man file. unless i get an error when i try to read other cars, . but that really rare when this happens...

and no you dont write a blank man file to resrt to default...

what you do is
load profile
expertmode (profile)
f1
f3
e89 (assuming you are working on a 3 series e90)
back
proccess ecu
select the ecu you want to reset to default
then execute job

thats the correct way

[ferocity02]

Originally Posted by js335in54

and no you dont write a blank man file to resrt to default...

what you do is
load profile
expertmode (profile)
f1
f3
e89 (assuming you are working on a 3 series e90)
back
proccess ecu
select the ecu you want to reset to default
then execute job

thats the correct way

Since the default job is SG_CODIEREN, won't that attempt to write the MAN file (blank or not) to the ECU you selected?

[js335in54]

Originally Posted by ferocity02

Since the default job is SG_CODIEREN, won't that attempt to write the MAN file (blank or not) to the ECU you selected?

no

[spencers]

Originally Posted by js335in54

i work with many series and i never empty the man file. unless i get an error when i try to read other cars, . but that really rare when this happens...

and no you dont write a blank man file to resrt to default...

what you do is
load profile
expertmode (profile)
f1
f3
e89 (assuming you are working on a 3 series e90)
back
proccess ecu
select the ecu you want to reset to default
then execute job

thats the correct way

Interesting. I've always used the FSW PSW MAN profile (and a blank .MAN file) to reset a module to default. Always assumed it worked. I need to try doing that in Expertmode.

[ferocity02]

What if I don't have expertmode profile? Here are the profiles I have (someone else's picture). Instead of "Expert Mode w/ manipulation" I have "FSW PSW MAN".

[Teq]

You just need a profile where fsw manipulation is disabled.