[gjm120]

Anyone know the difference between codierdaten_lesen and codierindex_lesen?

I read the CAS files using both functions and the codierindex read has more in it.

[Sensible_]

Coped from a post by FAL. So it should be correct.

CODERINDEX_LESEN == Read out the Coding Index of the selected ECU.
CODIERDATEN_LESEN == Read out the coding data on the selected ECU.
FGNR_LESEN == Read out VIN number (short).
FGNR_LESEN_KURZ == Read out VIN number (long).
AE_INDEX_LESEN == Read out the Software Index of the selected ECU.
FA_READ == Read out the Vehicle Order of the vehicle.
FA_WRITE == Write the Vehicle Order of the vehicle.
AIF_LESEN == Read out the User Information Field.
SG_RESET == Reset/Re-Start the selected ECU.

[gjm120]

Originally Posted by Sensible_

Coped from a post by FAL. So it should be correct.

I somewhat figured that but don't understand the distinction between coding index and coding data? I came across this when coding out my self dimming mirrors. I couldn't find anything in the coding data related to self dimming mirrors but it (SPIEGEL_ELEKTROCHROM) was in the coding index file. So I changed the code to not active and coded it in. So now when I pull the file using Coderindex_lesen it shows the dimming feature disabled. Frankly not sure if it works as I haven't driven at night since.

Another difference in the files - the coding index file has the ah of the car's original battery. The coding data file has the ah I coded in when replacing the battery. INPA shows the correct ah of the replacement battery.

[Sensible_]

I guess that CODIERINDEX_LESEN reads the complete coding options for that index.

When you read data using CODIERDATEN_LESEN you probably only get the coding options equivalent for your vehicle options (FA).

Just a guess.

This sort of makes sense if you coded your battery incorrectly and just modified the CAS TRC file rather than VO coding the correct ah option for that battery.

Just a guess though...

[gjm120]

That was my guess as well. The only contradiction is that my car has the self dimming mirrors and they are not in the Codierdaten file.

If I get ambitious I'll change the VO to the correct battery ah and see if that shows up in the Codierindex file. Even if it does, still doesn't explain why the mirrors aren't in the Codierdaten file.

[Sensible_]

Originally Posted by gjm120

That was my guess as well. The only contradiction is that my car has the self dimming mirrors and they are not in the Codierdaten file.

If I get ambitious I'll change the VO to the correct battery ah and see if that shows up in the Codierindex file. Even if it does, still doesn't explain why the mirrors aren't in the Codierdaten file.

Hmm. Good point. What file size is the index trace file compared to the data trace file?

[gjm120]

The index trc file is much bigger - 234kb vs 8kb. I pulled the index trc file for the NFRM and it is the same size and probably the same file as the index trc file pulled from the CAS.

So maybe the index files are everything from the VO. I say that b/c that file has the car's original capacity battery. Except I can't find mirrors anywhere else.

Probably no surprise - when you just use the Read ECU function it pulls the same file as Codierdaten Lesen.

This isn't a real problem for me as all prior coding is working, but, I'd like to understand how this works.

[Sensible_]

This makes sense. CODIERINDEX_LESEN is likely a global job. No matter what ECU you select the entire coding index is read as per the vehicle order. This job is run when you run NCS after choosing a chassis. When the VO and VIN etc is populated a FSW_PSW trace file is populated with the complete coding data. It surely must be the same/similar process?

[gjm120]

Except I can't find the mirror functions outside of the index file. Admittedly I haven't read every module. Must be somewhere else.

[Sensible_]

Originally Posted by gjm120

Except I can't find the mirror functions outside of the index file. Admittedly I haven't read every module. Must be somewhere else.

What year is your vehicle? Does your VO have any of these?

Fold-in Outsider Mirror: $313
Interior/Outside Mirror with Automatic Dip: $430
Interior Mirror with Automatic-Dip: $431

That coding option is normally in the NFRM. There is also: EC_SPIEGEL in the FZD. I know you don't need to know this though.

[gjm120]

Originally Posted by Sensible_

What year is your vehicle? Does your VO have any of these?

Fold-in Outsider Mirror: $313
Interior/Outside Mirror with Automatic Dip: $430
Interior Mirror with Automatic-Dip: $431

That coding option is normally in the NFRM. There is also: EC_SPIEGEL in the FZD. I know you don't need to know this though.

It has $430 and $431 not $313. I saw EC_SPIEGEL in my searching. The dimming mirrors is SPIEGEL_ELEKTROCHROM. The only place I can find this is by pulling the CODIERINDEX file. I must have altered and coded in this file. A little scary that I did that inadvertently, but, all seems normal other than not being sure if the mirrors are no longer dimming. Everything I have read says that feature is coded thru CAS.

I'm very frustrated I can't figure this out even though it's not important now. Hopefully someone is reading this thread who has gone thru this.

[Sensible_]

Originally Posted by gjm120

It has $430 and $431 not $313. I saw EC_SPIEGEL in my searching. The dimming mirrors is SPIEGEL_ELEKTROCHROM. The only place I can find this is by pulling the CODIERINDEX file. I must have altered and coded in this file. A little scary that I did that inadvertently, but, all seems normal other than not being sure if the mirrors are no longer dimming. Everything I have read says that feature is coded thru CAS.

I'm very frustrated I can't figure this out even though it's not important now. Hopefully someone is reading this thread who has gone thru this.

Ok. Strange. I just read my FRM and SPIEGEL_ELEKTROCHROM is in my FRM trace file.

Are you 100% it's not there?

[gjm120]

Originally Posted by Sensible_

Ok. Strange. I just read my FRM and SPIEGEL_ELEKTROCHROM is in my FRM trace file.

Are you 100% it's not there?

Only if I pull the file as Codierindex_lesen. Not when pulled as read ECU or Codierdaten_lesen.

[Sensible_]

Ok. What FRM do you have? And what year is your vehicle?

[gjm120]

Car is 2013 E82. Not sure about the FRM but NCSE show as NFRM.

[gjm120]

Here is a shot from INPA that I hope shows what version of FRM my car has. Obviously, I don't know a lot about this.

[Sensible_]

So you have FRM3. In FRM many things changed. The function SPIEGEL_ELEKTROCHROM is actually ASP_ELEKTROCHROM and is in your FRM3 module.

Why does SPIEGEL_ELEKTROCHROM get included in your index file? I don't really have any idea. Maybe in early FRM3 datens SPIEGEL_ELEKTROCHROM was correct and then it changed in later revisions.

Was The FRM3 factory or a retrofit? As SPIEGEL_ELEKTROCHROM is 1000000% in the FRM2 not CAS.

[gjm120]

Aha! ASP_ELEKTROCHROM is in my FRM daten files. I haven't been using NCSDummy so had no idea what ASP was. I only searched for SPIEGEL.

The only thing I can think is that the Index files are everything that can possibly be present in a module's coding and the daten files are what are actually enabled. Big mystery that I'd like to solve. So I'm assuming the not active I coded in the Index file did nothing to change the mirrors since that line isn't in the FRM module.

Thanks for all the help on this one.

The FRM is original to the car.