Speedo offset fix...

[wpoll]

Well, I had some spare time today to look into this further and so I got out the laptop and started coding.

I wanted to reset the coolant over temp (UEBERTEMP) alarm down to 110c so I started with that. Seemed to go ok, used NCSDummy to modify my LCM.C23, loaded the LCM trace from the car, updated it, reloaded the modified .man file - all good. Except it didn't work - when I read the LCM trace back from the car (after several ignition recycles) the overtemp alarm is still set at 125c. What the heck.

So I moved on to the speedo error fix, read the trace for the IKE (KMBI), added the Japan speed settings, then reloaded the modified .man file - and got a nasty CABD! error and the coding failed! The error was COAPI-2061 which seems related to checksums.

As we say downunder - bugger!

I re-checked everything, and reloaded to factory default trace - all OK this time, coding completed without error. IKE was fully reset, had to reset time and date, lost any stored fuel consumption values and settings on the BC etc. Also lost about 30km from my ODO, I guess caused by the IKE reset and the ODO value being replaced by that in the LCM.

Scary shite....!

All seems ok, car is working as it should, but nothing I tried to code worked. Going to give it a while to re-settle my nerves after all that! In hindsight, screwing with the two modules that hold the ODO data at the same time might be a bad idea!

So it currently seems that simply adding the Japan speedo settings resulted in a checksum problem but it may have been an error on my part. I guess maybe if someone else is game to try it, we might find out if it works on the e53 platform?

[Overboost]

Originally Posted by wpoll

Well, I had some spare time today to look into this further and so I got out the laptop and started coding.

I wanted to reset the coolant over temp (UEBERTEMP) alarm down to 110c so I started with that. Seemed to go ok, used NCSDummy to modify my LCM.C23, loaded the LCM trace from the car, updated it, reloaded the modified .man file - all good. Except it didn't work - when I read the LCM trace back from the car (after several ignition recycles) the overtemp alarm is still set at 125c. What the heck.

So I moved on to the speedo error fix, read the trace for the IKE (KMBI), added the Japan speed settings, then reloaded the modified .man file - and got a nasty CABD! error and the coding failed! The error was COAPI-2061 which seems related to checksums.

As we say downunder - bugger!

I re-checked everything, and reloaded to factory default trace - all OK this time, coding completed without error. IKE was fully reset, had to reset time and date, lost any stored fuel consumption values and settings on the BC etc. Also lost about 30km from my ODO, I guess caused by the IKE reset and the ODO value being replaced by that in the LCM.

Scary shite....!

All seems ok, car is working as it should, but nothing I tried to code worked. Going to give it a while to re-settle my nerves after all that! In hindsight, screwing with the two modules that hold the ODO data at the same time might be a bad idea!

So it currently seems that simply adding the Japan speedo settings resulted in a checksum problem but it may have been an error on my part. I guess maybe if someone else is game to try it, we might find out if it works on the e53 platform?

Question for you. When you tried the LCM coding and did not get the results you were expecting did you close out the NCS Expert and NCS Dummy before heading to the cluster? If you have any text in the .man file you will see that error as it needs to be blank when exporting the .MAN file.

On my 115C alert modification in the LCM, it went fine. I even pulled the file back out after sending and saved it as my current LCM TRC file and showed the correct modification. It did take 5 extra seconds when loading the updated module processing the ECU. (Long enough for me to gasp)

[Overboost]

2060..2079: Codierfehler

2060 = faulty coding (general)
2061 = error during writing coding
2062 = error during reading coding data
2063 = error verifying coding data
2064 = error erasing coding data (eg ZCS)
2065 = ecum checksum error "

[80stech]

It's been a while since I coded with NCS Dummy but I seem to remember the not having the .man file blank thing having me tearing some of whats left of my hair out!

[wpoll]

The .man is blank before I start and I only perform coding on one module in any session.

Been out for a motorcycle ride to clear my head and just tried the UEBERTEMP LCM code again. Same result - no change when I check the trace. I checked the updated module (LCM.C23) still contains the new parameter and the .man file contains the correct parameter data before the code. Everything looks good, the code seems to work but if I close NCSDummy, close NCS, cycle the ignition, start NCS, read a new LCM trace, check it in NCSDummy, it's back on 125c again.

I'm missing something...

[wpoll]

I disassembled the LCM.C23 module file and verified the change was there and correct (it was), then I performed a manual code via hand editing the LCM trace file, saving it as a manipulation file then coding. Same result. No change.

Poodoo....

[Overboost]

Wayne, go out and try a simple change to your LCM like fogs on with high beams or something we can verify that your NCS profile is correct.

A couple of years ago when I started coding, I had an issue with my expert profile not being setup properly.

If you can have success doing something other than the 110C warning then this will not come into play.

Let me know your results and we can take the next step.

https://forum.e46fanatics.com/showpo...5&postcount=16

[Overboost]

Wayne, just checking here but when you added the new parameter to your MOTOR_UEBERTEMP, you did not forget this step did you?

Open up the LCM.Cxx file with NCS Dummy without loading any FSW_PSW files, go down to MOTOR_UEBERTEMP, right click it, and click "add parameter". Name it whatever you want, and under data put the hex value of the temp alarm you want. Then click on module functions -> update module.

[wpoll]

Thanks for the extra info. OB.

I was thinking along the same lines as you - confirm the tool operation first.

Funny you should mention the profile - I can't edit it - it is password protected. Must look at that...

Re. The module update - yes, I'm updating it. That is confirmed by the disassembly of the updated LCM.C23 file and confirmation of the new parameters in the module.

I'll get back to this in a day or two - gotta go back to work! :-(

[Overboost]

Originally Posted by wpoll

Thanks for the extra info. OB.

I was thinking along the same lines as you - confirm the tool operation first.

Funny you should mention the profile - I can't edit it - it is password protected. Must look at that...

PM sent