NCS Dummy - Taking the expert out of NCS Expert

[revtor]

jduffett: To be honest, I don't know what would happen if you try to code the module with the FSW/PSW trace file containing conflicting entries for "EHC_KENNFELD". NCS Expert should not accept it.

Given the fact that NCS Expert cannot read the underlying nettodata value, I doubt it can write it. So you probably can't alter "EHC_KENNFELD" at all.

Nevertheless if you want to recode the module and include "EHC_KENNFELD" I would keep only one parameter. For an E39 touring parameter "e39_ab_sensor" should be the right one.

I must admit I'm also a bit confused about the content of "OFFSET_HI_LI" and "OFFSET_HI_RE" in your trace files. As you may have noticed these functions are missing from your FSW/PSW trace files. The reason for this is because their (nettodata) data values do not match any of the predefined parameters in the module description file. When loading the nettodata trace file in NCS Dummy you'll see it selects "<tatsächlich>" (<actual>) which is just a placeholder for undefined values. This by itself is not an issue or cause for alarm. Some parameter values can diverge from the predefined ones during normal usage. However in this case I don't think it should. If you take a look at the trace files provided by wyccka in 2013 (link) you'll see that "OFFSET_HI_LI" and "OFFSET_HI_RE" do match the predefined values. The data values from your 540 nettodata trace file differ only a tiny bit from the predefined values (0x76 vs 0x77 and 0x9A vs 0x9F) so I don't think it's much of an issue - it's just strange. If there really was an issue with the air suspension you should get the dreaded "SELFLEVEL SUSP.INACT" fault message.

If you decide to recode the module I would use following trace file though:

EHC_KENNFELD
	e39_ab_sensor
OFFSET_HI_LI
	ab_sensor
OFFSET_HI_RE
	ab_sensor

[jduffett]

I must admit I'm also a bit confused about the content of "OFFSET_HI_LI" and "OFFSET_HI_RE" in your trace files. As you may have noticed these functions are missing from your FSW/PSW trace files. The reason for this is because their (nettodata) data values do not match any of the predefined parameters in the module description file. When loading the nettodata trace file in NCS Dummy you'll see it selects "<tatsächlich>" (<actual>) which is just a placeholder for undefined values. This by itself is not an issue or cause for alarm. Some parameter values can diverge from the predefined ones during normal usage. However in this case I don't think it should. If you take a look at the trace files provided by wyccka in 2013 (link) you'll see that "OFFSET_HI_LI" and "OFFSET_HI_RE" do match the predefined values. The data values from your 540 nettodata trace file differ only a tiny bit from the predefined values (0x76 vs 0x77 and 0x9A vs 0x9F) so I don't think it's much of an issue - it's just strange. If there really was an issue with the air suspension you should get the dreaded "SELFLEVEL SUSP.INACT" fault message.

Thanks again revtor!
I believe "OFFSET_HI_LI" and "OFFSET_HI_RE" are short for "Offset, Hinten [Rear], Links [Left]" and "Offset, Hinten [Rear], Rechts [Right]". If one were to adjust ride height using INPA, I assume it has to store that adjustment somewhere, and in the absence of any other function in this module, this seems like where it would logically go, and why you might end up with an <actual> value instead of the predefined values? I know for sure I had adjusted ride height on 525.

[revtor]

jduffett: That makes sense and is probably what is going on.

[Nicer]

Anyway, let's assume that "LRR_60.C53" is the right module for your car. Luckily a similar approach as for the ACC2 modules is possible for the LRR modules. Function "LHT" is present but hidden in an unoccupied block.

Disassemble "LRR_60.C53" with NCS Dummy and open the resulting text file in a plain text editor. Locate and replace

PARZUWEISUNG_FSW : {00003000} 0000000E 0001 1841 {b} (01) {h} {} // LRR_FUNKTION_1
PARZUWEISUNG_PSW1 : 0026 (01) // wert_01
PARZUWEISUNG_PSW1 : 001C (01) // wert_02
PARZUWEISUNG_PSW1 : 001D (00) // wert_03
PARZUWEISUNG_PSW1 : 001B (00) // wert_04
PARZUWEISUNG_PSW1 : 0027 (00) // wert_05
PARZUWEISUNG_PSW1 : 0028 (00) // wert_06
PARZUWEISUNG_PSW1 : 00F7 (00) // wert_07
PARZUWEISUNG_PSW1 : 00C6 (00) // wert_08
UNBELEGT1 : {00003000} 0000000E 0001 {} (FE)
UNBELEGT2 : (7F)
UNBELEGT1 : {00003000} 0000000F 0001 {} (0F)
UNBELEGT2 : (0F)
UNBELEGT1 : {00003000} 0000000F 0001 {} (10)
UNBELEGT2 : (01)
UNBELEGT1 : {00003000} 0000000F 0001 {} (60)
UNBELEGT2 : (03)
UNBELEGT1 : {00003000} 0000000F 0001 {} (80)
UNBELEGT2 : (01)
CODIERDATENBLOCK : {00003001} 00000000 0010 "ACC_1"

with

PARZUWEISUNG_FSW : {00003000} 0000000E 0001 1841 {b} (01) {h} {} // LRR_FUNKTION_1
PARZUWEISUNG_PSW1 : 0026 (01) // wert_01
PARZUWEISUNG_PSW1 : 001C (01) // wert_02
PARZUWEISUNG_PSW1 : 001D (00) // wert_03
PARZUWEISUNG_PSW1 : 001B (00) // wert_04
PARZUWEISUNG_PSW1 : 0027 (00) // wert_05
PARZUWEISUNG_PSW1 : 0028 (00) // wert_06
PARZUWEISUNG_PSW1 : 00F7 (00) // wert_07
PARZUWEISUNG_PSW1 : 00C6 (00) // wert_08
UNBELEGT1 : {00003000} 0000000E 0001 {} (FE)
UNBELEGT2 : (7F)
UNBELEGT1 : {00003000} 0000000F 0001 {} (0F)
UNBELEGT2 : (0F)
UNBELEGT1 : {00003000} 0000000F 0001 {} (10)
UNBELEGT2 : (01)
UNBELEGT1 : {00003000} 0000000F 0001 {} (60)
UNBELEGT2 : (03)
PARZUWEISUNG_FSW : {00003000} 0000000F 0001 046A {} (80) {h} {} // LHT
PARZUWEISUNG_PSW1 : 0008 (00) // nicht_aktiv
PARZUWEISUNG_PSW1 : 0007 (01) // aktiv
CODIERDATENBLOCK : {00003001} 00000000 0010 "ACC_1"

Re-assemble the file and replace the existing "LRR_60.C53" module with the modified module file (always keep backups of the original files). On the "Modules and Traces" tab, select chassis "E60" and module "LRR_60.C53". If the module was already selected from before replacing the module file, reload the module to make sure NCS Dummy is using the new file (right click on the dropdown and select "Reload" or simply restart NCS Dummy). Next load your trace file, use the NCS Dummy search (click the magnifier button or press CTRL+F) to locate function "LHT" and check its parameter "nicht_aktiv" (not enabled). Now export the "FSW_PSW.MAN" file and recode the module in the car following the instructions from chapter 6.2 in the NCS Dummy user manual.

The radar lens heating should now be disabled.

I have tested your fix for some weeks now and it works without problems!
Thanks Revtor for your great contribution!! Many thanks!

[MParallel]

...

Anyway, let's assume that "LRR_60.C53" is the right module for your car. Luckily a similar approach as for the ACC2 modules is possible for the LRR modules. Function "LHT" is present but hidden in an unoccupied block.

Disassemble "LRR_60.C53" with NCS Dummy and open the resulting text file in a plain text editor. Locate and replace...

I had no idea functions could be hidden inside unoccupied blocks? Lookinf at the before and after, there is nothing in the before that suggests "LHT" is hidden there. How do you know that these specific lines are for that?

Makes you wonder what else could be hidden in modules. Like say (wishfull thinking) remote comfort opening/closing in the GM4.

[deepblonde]

Instrument lights (speedo etc) always on , regardless of whether headlights are on or off - in Kombi module e70 X5 found this and works - M_TAG_SKALENBELEUCHTUNG Instrument lights on with daytime running lights- the discription isnt really correct, as it implies either - instrument lights will only be on with daytime running lights, or that it enables daytime running lights as well. I've tested it and it just keeps instrument lights on regardless of headlights, and has no effect on daytime running lights .

[TrAl]

Hello to all (my first post),
First off appreciate all the work youve put into this Revtor, thank you.

I have been trying to code out the cornering lights on my car but have had success for 2 minutes only. The green light was back to solid on the light switch for this time
then all of a sudden the bong noise and the fault came up!
This was using NCSExpert only so came across this post and got hold of NCSDummy. Followed a procedure and changed 4 settings to not active but still error message pops up.
I cant remember what the settings were off the top of my head but I previously removed $524 using NCSExpert.
I dont have any experience with coding and not at all up on the talk I have read in these posts, forgive me, thanks for any help with this.

[peroni1000]

I just created new trace files using Read Data Job in NCS Expert. But when i load them into NCS Dummy i'm getting these error messages and therefore no check boxes. Please help thanks.

[amitsekhon]

Hi all,

I would like to code AGM battery on my E70 which currently has a lead acid conventional battery. I have done coding on my E70 few years ago and wondering if I code AGM , will I loose my existing coding? If yes then what's the easiest way to create backup and restore? as I don't want to loose my existing coding. Thanks.

[FlyM3Fan]

Revtor,

I was looking at post #219 on page 9. I know that is an old post but what a good post. I am trying to add a value to the K_ZAHL_WEG and K_ZAHL_TACHO imp/km options on an E46 M3 so that the speed displayed in the speedometer is correct. I have measured the actual (gps) speed and compared it to the speed shown in the speedometer and came up a new value of 5103 imp/km to have the correct setting for both the speedometer and the odometer. I used NCS Expert/Dummy to download and look at the trace file for the KMBE46M3 module and using the preexisting values and information from this post I believe the new hex value for the K_ZAHL_WEG and K_ZAHL_TACHO setting would be 13,EF (5103) and the value for the K_ZAHL_WEG_KOMPL and K_ZAHL_TACHO_KOMPL should be EC,10 (-5104) using Hex signed 2's complement. 2 questions: 1) Could you verify those values are correct and 2) Can NCSDummy "Add parameter" function be used to edit the KMBE46M3 options and not have to manually edit it. Any other information you might think would be useful would be greatly appreciated.

Thanks

[revtor]

FlyM3Fan: 13,EF and (complementary) EC,10 are the correct hexadecimal values for 5103 impulses per kilometer. Yes, you can (and should) use "Add FSW/PSW parameter" in NCS Dummy to add the new values to the module description file.

Whether it will work remains to be seen. Several modules have additional built-in protection to prevent tampering with certain addresses. Just try.

[FlyM3Fan]

Revtor,

It worked perfectly! It took less than 10 min and speedometer is spot on with GPS. The hardest part was figuring out the dec to hex conversions. Thanks for your help.

[DrCharles]

Is it possible to reset adaptations in the E38 transmission control module using NCS? Or is INPA required?
thanks.

Edit: there is a list of modules at https://ncs-expert.com/modules and unfortunately the trans computer is not one of them.

[favetta82]

first of all congrats, you clearly have done an amazing work! Hope you are getting the recognition you deserve!


May i trouble you with a possibly stupid question:



so i have upgraded 318i to 320 ecu. It is all working fine but i get EML light.


The 320i ecu has got 4 lambda/02 sensors where the 318 engine loom clearly has got only 2 lambda.


is there a way to code out the 02 sensorplease?

if not possible to disable EML light (clearly I understand the implication)

thank you so much!

[revtor]

favetta82: This is not something you can achieve through coding with NCS Expert. Maybe a chiptuner can help with this.

[scarede46er]

favetta82: This is not something you can achieve through coding with NCS Expert. Maybe a chiptuner can help with this.

Hi revtor.. I installed a completely aftermarket audio system in my e70 LCI and it works fine but obviously the service info and tire pressure etc dont show anymore. If I delete the VOs of the CIC and NAV, would those things automatically display on the BC or would I have to code the BC as well?
If I indeed delete the VOs, would the car still continue to supply power to the harnesses because now I am using them to power the aftermarket head unit.
I appreciate your help in advance.

[m20b27es]

Hi, I'm not sure if it's an issue on my end or not, but I cannot seem to download the NCS Dummy file from your link. A new tab opens briefly, then closes, and I don't see any newly downloaded files. I've tried searching other folders on my computer and don't see it anywhere. This happens on 2 different computers of mine, one is a Windows 11 laptop, and the other is a Windows 10 desktop.

Edit: Seems like it's me. I was able to download it on my phone, then emailed it to myself and could open it that way.

[MParallel]

Hi, I'm not sure if it's an issue on my end or not, but I cannot seem to download the NCS Dummy file from your link. A new tab opens briefly, then closes, and I don't see any newly downloaded files. I've tried searching other folders on my computer and don't see it anywhere. This happens on 2 different computers of mine, one is a Windows 11 laptop, and the other is a Windows 10 desktop.

Edit: Seems like it's me. I was able to download it on my phone, then emailed it to myself and could open it that way.

I tested the links on my pc and have no problems. Download start right away.

[Roadwarrior1956]

I just had a E60 M5 instrument display cloned to my 2009 E60 550I and everything works as before, But now the oil temperature gauge operated like the original vacuum gauge. I there a way to make it operate as a Oil Temperature gauge again like it did on the M5.
It did operate correctly before I cloned it and showed the oil Temperature, but also showed many errors on the display.

[MeGuinness]

hi guys , such a great and helpfull amount of informations...THANK YOU to all involved.
is there a way to code/adding code to have the angels lights ON as DLR on a e39 ? what is the name refering to the angel on the lcm code ....STANDING LIGHTS..?
thanx

[MParallel]

hi guys , such a great and helpfull amount of informations...THANK YOU to all involved.
is there a way to code/adding code to have the angels lights ON as DLR on a e39 ? what is the name refering to the angel on the lcm code ....STANDING LIGHTS..?
thanx

I don’t know if it can be coded, never tested, but I do know, as I have it myself, with the use of an Intravee II interface.
That’s to connect an iphone/ipod, but they included all kinds of tricks. I can set any light as follow me home light. Like, the left foglight if you wish to do so.

Also comfort indicator, remote folding mirrors and other stuff.

[Bern416]

2000 BMW Z3M with S52 engine.

Hi folks. New to NCS expert and NCS Dummy.

I get an error in NCS Dummy when I load the ABG module trace file
I can choose between module ABGB.C02 or ABGZ.C01 they both generate the same error.
Does the error disable edit functionality in NCS Dummy?


[E] 19:22:24 An error occurred while reading "C:\NCSEXPER\WORK\FSW_PSW.TRC": Unresolved parameter keyword "e36_7" in function "BAUREIHE". Make sure chassis and module match those of the trace file.


The following are the last parameters in the trace file.

BAUREIHE
e36_7
CRASHPARAMETER_12
e36_7
CRASHPARAMETER_13
e36_7
CRASHPARAMETER_14
e36_7
CRASHPARAMETER_15
e36_7
CRASHPARAMETER_24
e36_7

[MParallel]

Have you first read the module (CODIERDATA LESEN) to see which is the correct file/coding index?

[Bern416]

I was able to figure it out. I used the filter button in NCS Dummy and selected one of the MRS** modules. I was able to edit and change parameters for the first time.

[Diolum]

Hi Revtor,

I was trying to go thru the decompiled trace file for my cluster. And some of the operations are not clear.

For example those on I can understand:

00000048 0001 01F6 {} (0F) () d // FAHRGESTELL_NR[5]
(Byte nr 0x48 length of 1 UUID "01F6" Mask "0F" decimal type // name)

or

PARZUWEISUNG_FSW : {} 00000000 0002 0102 {} (FF) {h} {} // K_ZAHL_WEG
(Byte nr 0x00 length 2 UUID "0102" Mask "FF" Hex type // Name)
PARZUWEISUNG_PSW1 : 001C (97,02) // 4663_imp/km (0x97 0x02 for 4663 imp)
PARZUWEISUNG_PSW1 : 005C (C8,02) // 4712_imp/km ( or 0xC8 0x02 for 4712 imp)

But those one give me headache:

00000048 0001 01F7 {} (F0) (-0030) a // FAHRGESTELL_NR[6]
Byte Number 48 of length 1 with UUID 01F7 with bit mask F0 "What is (-0030)" of type text is FAHRGESTELL_NR[6]

and

PARZUWEISUNG_DIR : {} 00000049 0001 01F7 {} (03) (-0030,>0004) a // FAHRGESTELL_NR[6] 
Byte Number 49 of length 1 with UUID 01F7 with bit mask 03 "What is (-0030) and >0004" of type text is FAHRGESTELL_NR[6]

or

PARZUWEISUNG_FSW : {} 00000134 0001 00F2 {b} (E0) {h} {} // GETRIEBE_TYP
Byte 134 length of 1 UUID "00F2" b? Mask  E0 Hex data is gearbox type
PARZUWEISUNG_PSW1 : 0029 (00) // handschaltung
PARZUWEISUNG_PSW1 : 016D (02) // automatik_5_gang

I can't understand the meanings of:
(-0030) is it a Data-0x30 ?
>0004 is it a bit shift to the right of 4?
{b} what is this ?

also at the start I can find this: (comment in bold)

SIGNATURE : 00010001010163 02 Unknown function with CS?
--------------- Unknown function
0000 - DATEINAME - S - NAME
0001 - SGID_CODIERINDEX - B(B) - WERT,WERT2
0002 - SGID_HARDWARENUMMER - S(S) - WERT,WERT2
0003 - SGID_SWNUMMER - S(S) - WERT,WERT2
0004 - SPEICHERORG - SS - STRUKTUR,TYP
0005 - ANLIEFERZUSTAND - (B) - WERT
0006 - CODIERDATENBLOCK - {L}LWS - BLOCKNR,WORTADR,BYTEADR,BEZEICHNUNG
0007 - HERSTELLERDATENBLOCK - {L}LWS - BLOCKNR,WORTADR,BYTEADR,BEZEICHNUNG
0008 - RESERVIERTDATENBLOCK - {L}LWS - BLOCKNR,WORTADR,BYTEADR,BEZEICHNUNG
0009 - UNBELEGT1 - {L}LW{B}(B) - BLOCKNR,WORTADR,BYTEADR,INDEX,MASKE
000A - UNBELEGT2 - (B) - WERT
000B - KENNUNG_K - SS(S) - IDENT,WERT1,WERTN
000C - KENNUNG_D - WW(WW) - HEXWERT1,HEXWERT2,HEXWERTN1,HEXWERTN2
000D - KENNUNG_X - WW(WW) - HEXWERT1,HEXWERT2,HEXWERTN1,HEXWERTN2
000E - KENNUNG_ALL - SW(W) - KENNUNG,HEXWERT1,HEXWERTN
000F - PARZUWEISUNG_PSW2 - (B) - DATUM
0010 - PARZUWEISUNG_PSW1 - W(B) - PSW,DATUM
0011 - PARZUWEISUNG_DIR - {L}LWW{B}(B)(A)B - BLOCKNR,WORTADR,BYTEADR,FSW,INDEX,MASKE,OPERATION,EINHEIT
0012 - PARZUWEISUNG_FSW - {L}LWW{B}(B){B}{B} - BLOCKNR,WORTADR,BYTEADR,FSW,INDEX,MASKE,EINHEIT,INDIVID
---------------
DATEINAME : "KMB_E36.C25" File Name
SGID_CODIERINDEX : 25 () For coding index 25
SGID_HARDWARENUMMER : "**" () Hardware number all
SGID_SWNUMMER : "78" ("82","8C","96","A0","AA","B4","BE","C8") SW number of list
SPEICHERORG : "BYTE" "FREI" What is it ?
ANLIEFERZUSTAND : (00) Delivery condition ?
KENNUNG_ALL : "G" 0046 () What is it ?
KENNUNG_ALL : "B" 0000 (0060,0061) What is it ?
KENNUNG_ALL : "Z" 0062 () What is it ?
KENNUNG_K : "$IDCDNR" "25" () For coding index 25
KENNUNG_K : "$IDHWNR" "**" () Hardware number all
KENNUNG_K : "$IDSWNR" "78" ("82","8C","96","A0","AA","B4","BE","C8") SW number of list
KENNUNG_D : 0000-0003 (0005-001D,0024-002F,0031-0031,0033-0033,0035-0035,0037-0037,0039-003B,003D-003F) What is it ?
KENNUNG_D : 0045-0045 (004A-005B) What is it ?

Can you please provide me some information regarding those thing in red? I can't find nothing in the manual

Thank a lot for your work.