NCS Dummy - Taking the expert out of NCS Expert

[MParallel]

If it already says 00 is off, 01 is on, you only have to set it to the on value.

I don't have 2011 335i Daten file. Can you copy-paste the parameter/values here?

doesn't it say aktiv on either one?

[vnt]

Wert_00 was the only availble option.
Wert_01 was a parameter that I added because of the function description.
Adding this parameter resulted in NCSexpert failing to reading this module since.

[vnt]

the only parameter originally available was Wert_00 value 00
I added the parameter Wert_01 value 01 it was unsuccessful and NCS EXPERT will no longer read the DSC module.
I have posted a picture in my profile album since i could not here.

[revtor]

vnt: What error message does NCS Expert give when trying to read the DSC module?

[MParallel]

Can you upload the file somewhere? I'd like to give it a shot.

[vnt]

The errors recieved when trying to read module DSC_89.C03 after adding parameter are:
[08:34:53.929] [2015-01-21] [SERIE] 2062 PABD/CABD A_E65.IPS Cod 379
[08:34:53.929] [2015-01-21] [SERIE] Error on reading coding data DSC_87, C_C_LESEN: ERROR_BIN_BUFFER


[08:34:54.035] [2015-01-21] [SERIE] 2062 Error COAPI2.CPP coapiRunCabd 6
[08:34:54.035] [2015-01-21] [SERIE] Error on reading coding data CODIERDATEN_LESEN

The changes made to the DSC_89.C03 viewed as text are as follows:

Original DSC_89.CO3 file
PARZUWEISUNG_FSW : {00003008} 00000010 0001 1C43 {63} (20) {68} {} :
PARZUWEISUNG_PSW1 : 0066 (00) :
UNBELEGT1 : {00003008} 00000010 0001 {} (C0)
UNBELEGT2 : (00)

Modified DSC_89.CO3 file
PARZUWEISUNG_FSW : {00003008} 00000010 0001 1C43 {63} (20) {68} {} :
PARZUWEISUNG_PSW1 : 0066 (00) :
PARZUWEISUNG_PSW1 : 09C2 (01) :
UNBELEGT1 : {00003008} 00000010 0001 {} (C0)
UNBELEGT2 : (00)

Original

Modded



Thank you for your responses.

[MParallel]

Do you have your daten file for me. The DTC_089 file.

- - - Updated - - -

Oh wait you get errors in NCS Expert, thought it already went bad in NCS Dummy.

[vnt]

Attached are the original and modded files.
change file extension to .C03

[MParallel]

Thx. Not behind my pc right now. Will check later.

- - - Updated - - -

Just a brainfart here: what about not adding wert 01, but changing the value of wert 00 to value 00?

- - - Updated - - -

I don't recall exactly not sitting behind my pc, but length is 01, doesn't that mean just one parameter allowed?

in that case do what I brainfarted.

[vnt]

- - - Updated - - -
Just a brainfart here: what about not adding wert 01, but changing the value of wert 00 to value 00?

- - - Updated - - -

Not adding another parameter and changing the existing Wert 00 to Value 01 was floating around in my head as one of the next attempts.
The ony problem is that it does not seem to be as simple as replaceing DSC_89.C03 with the original file. Still unable to read the Module but I can read all other modules.??????

[MParallel]

Just so I understand correctly, you can't read the original from the car with NCS Expert?

Dummy makes a backup so you can recode the module with the original file.

[revtor]

I don't recall exactly not sitting behind my pc, but length is 01, doesn't that mean just one parameter allowed?

The number of permitted different values in a function depends on both the length and (bit)mask. Length 01 means the functions sits within a single byte. A single byte, or 8 bits, is good for a total of 256 different values. However, the function's (bit)mask is 20h (00100000b) which means it spans only a single bit in the byte which is good for only 2 different values: 0 or 1. Anyway, you don't have to calculate the bitmasks - NCS Dummy does that for you. Between brackets in the mask field is the range of values that is valid for the function (00 .. 01).

The ony problem is that it does not seem to be as simple as replaceing DSC_89.C03 with the original file. Still unable to read the Module but I can read all other modules.??????

At first sight I don't see anything wrong with the changes you made to "DSC_89.C03" so I'm quite sure that has nothing to do with the reason why NCS Expert refuses to read the module. If you make changes that are not permitted (and in theory you can't when using the graphical trace editor) NCS Expert usually gives error messages that clearly hint at a problem with the (modified) module description file. To be honest I have never seen the error you mentioned before. The fact that you restored the original file and NCS Expert is still unable to read the module suggests at another cause (although I don't have any clue at this moment).

Just to rule out any issue with NCS Expert and its DATEN files, can you remove the contents of NCSEXPER\DATEN\E89 and restore a fresh copy from the SP-Daten. Next remove all files from the NCSEXPER\WORK folder, then launch and close NCS Dummy. The WORK folder should now contain only a single file: "FSW_PSW.MAN". Now try again to read the module...

[MParallel]

Just to add information. Sometimes NCS Expert gives me error codes when coding a module, but after I re-read the module, the changes I wanted to make were succesfull.

[Vasilii]

After add e53 e39 body with standart operation - have a problem with load files to modify
dummy say- invalid keyword:
[E] 18:15:44 An error occurred while reading "C:\NCSEXPER\DATEN\E53\E53_CONF.BAP": Invalid keyword index in chassis configuration file.
how to fix it?
other body files loaded good.

[Vasilii]

After add e53 e39 body with standart operation - have a problem with load files to modify
dummy say- invalid keyword:
[E] 18:15:44 An error occurred while reading "C:\NCSEXPER\DATEN\E53\E53_CONF.BAP": Invalid keyword index in chassis configuration file.
how to fix it?
other body files loaded good.

[TerraPhantm]

If you aren't already, make sure you're on Ediabas 7.x; the newer modules sometimes error out with older versions. Also make sure the latency of your cable is set to 1 msec

[Vasilii]

i run only Dummy sw (no run ediabus,no connect car), and can't see modules in this old body. Other body - no problem.
may be problem from WIN7 ?

[revtor]

Vasilii: My guess is that your DATEN\E39 folder is corrupt/incomplete. You are missing vital files for proper operation. Are the files "SWTASW01.DAT", "SWTFSW01.DAT" and "SWTPSW01.DAT" present in the E39 folder?

[MParallel]

In my E89 folder I have the 3 files listed by Revtor, and I can't open your original DSC_89 nor your modded files.

Since my folder is complete, I would have expected that there would already be a DSC file in there. So I doubt that file is even something that is part of this chassis group.

Opening either file gives a "[E] 00:14:01 An error occurred while reading "C:\NCSEXPER\DATEN\E89\DSC_89.C03": Unknown function keyword (0C88)." error.

[Vasilii]

yes, in ncsexper/daten/e39 - this files not present. I try to here copy this files from sp-daten e39,daten folder - but still don't work. What wrong?

[revtor]

MParallel: The "DSC_89.C03" module description file is included with the E89 chassis. Your E89 DATEN might be outdated. Anyway, the modified "DSC_89.C03" will not work on any installation but vnt's unless vnt also distributes the modified "SWTPSW01.DAT". Besides, it is not recommended to use module description files from different DATEN versions than yours. It's a recipe for errors.

I checked vnt's modified "DSC_89.C03" and it's a perfectly sane file. Whatever is preventing the module from reading, it's not the changes vnt made to the file...

[MParallel]

Hmm strange. I was sure these were the latest Daten files. Have to recheck.

[vnt]

NCSEXPERT is now working again due to reverting to my backup folder. Now I have to apologize for waisting y'all's time. I somehow decided to rename the original file MK60_8*.*** to DSC89.C03.
With all of that said the MK60 file has the same function (DCC_DTC) and contains both parameters for enable and disable no mod needed. When I enable DCC_DTC VALUE 01 nothing happens so it must be linked to something else. Thank you for your responses

[MParallel]

No wonder my folder didn't have that file. I do have the MK60 files.

Somehow Revtor did have a DSC file though?!

[revtor]

MParallel: See screenshot below. Please note that these aren't the latest E89 SP-Daten either, so it is possible these files got substituted in later revisions. Anyway, the point was that you should not mix module description files from different SP-Daten versions because you will very likely get errors even though the files by themselves might be perfectly sane.