[HomeBrew]

The tach, gas gauge and mpg gauge all work for about 3 seconds, then fall to their resting positions (0 - empty, 0 rpms, 99 mpg).

Any coding has been undone. No errors were reported during coding.

Anyone have any ideas what would cause this?

[onebadmofo]

Daten files are too old.

[Coding@DetailAddict]

Not to come across harsh but have you searched? This is the most common error people come across and has been highly documented. I'm sure even searching "malfunction" in the coding section will show a bunch of threads.

[HomeBrew]

Originally Posted by Grant@DetailAddict

Not to come across harsh but have you searched? This is the most common error people come across and has been highly documented. I'm sure even searching "malfunction" in the coding section will show a bunch of threads.

Yep, did search.

[HomeBrew]

Originally Posted by Grant@DetailAddict

Not to come across harsh but have you searched? This is the most common error people come across and has been highly documented. I'm sure even searching "malfunction" in the coding section will show a bunch of threads.

Searched again (less specific terms).

are ISTA V2.41 still the latest files?

[Coding@DetailAddict]

Searching malfunction yielded these 3 out of a small number of threads. (One of them is almost the same exact title as yours)
Very detailed responses are in each thread. Happy coding.

http://www.e90post.com/forums/showth...ht=malfunction

http://www.e90post.com/forums/showth...ht=malfunction

http://www.e90post.com/forums/showth...ht=malfunction

[Coding@DetailAddict]

Originally Posted by SLeagle328

Searched again (less specific terms).

are ISTA V2.41 still the latest files?

42 is out but you should be golden with anything from 40 up

[HomeBrew]

Originally Posted by Grant@DetailAddict

42 is out but you should be golden with anything from 40 up

First time this happened, it was at a dealer, with the dealer coding the car.

So I (mistakenly) assumed that it was something serious...

[HomeBrew]

If it is so common, which apparently it is, why isn't it a sticky?

[Coding@DetailAddict]

It happened with a dealer?! Crazy.

There's no sticky because Mods aren't as active in here or I would make a few stickies myself. Just because somethings common with coding doesnt mean there will be a sticky in here lol. This here is no mans land

[DESI4life10]

Originally Posted by Grant@DetailAddict

It happened with a dealer?! Crazy.

There's no sticky because Mods aren't as active in here or I would make a few stickies myself. Just because somethings common with coding doesnt mean there will be a sticky in here lol. This here is no mans land

+1

[HomeBrew]

Originally Posted by Grant@DetailAddict

It happened with a dealer?! Crazy.

There's no sticky because Mods aren't as active in here or I would make a few stickies myself. Just because somethings common with coding doesnt mean there will be a sticky in here lol. This here is no mans land

Yep, as I was leaving noticed the cluster issues.

OK, so...

Copied and replaced the files in the folders from 2.42. But now, I get the wonderful 'VIN is faulty' error.

I know this cable works (unless it broke in the last hour)... so what's going on? (although I never disconnected pin 8, found that by searching )

[R 4 5 T 4 M 4 N]

did you make a backup of your files before updating them, so you can restore them and try again? did you follow the instructions on how to update the files correctly? many have done it without issue so it's clearly a user related issue.

Hopefully you can restore your files and attempt to update them again. BTW, I had the same problem, I searched, found the solution and applied with no issues at all. Maybe you can find someone in your area that knows what they are doing to fix it for you?

BTW, what was the dealer doing in the KOMBI module?

[HomeBrew]

Originally Posted by r45t4m4n

did you make a backup of your files before updating them, so you can restore them and try again? did you follow the instructions on how to update the files correctly? many have done it without issue so it's clearly a user related issue.

Hopefully you can restore your files and attempt to update them again. BTW, I had the same problem, I searched, found the solution and applied with no issues at all. Maybe you can find someone in your area that knows what they are doing to fix it for you?

BTW, what was the dealer doing in the KOMBI module?

Yes, I have a backup and have tried again, still same the same issue w/ the cluster.

Is there a write up somewhere on how to update 'correctly'? Is it more than just copy / replace?

I know what I'm doing, I've coded this car many times, this is the first issue. Just haven't needed to update the files before.

Any help on updating the files is appreciated.

Thanks.

[HomeBrew]

From another post:

Originally Posted by jyono
Update:
Solved my issue using ISTA v41 Daten Files.

1. Copied and pasted new daten files to [ C:\NCSEXPER\DATEN\E89 ] and ran laden.bat
2. Copied and pasted new sgdat files to [ C:\NCSEXPER\SGDAT ]
3. Copied and pasted new ecu files to [ C:\EDIABAS\Ecu ]

This time NCSexpert worked fine, no "Faulty Chassis" message!
Re-coded with a blank .MAN file and functionality my the analog gauges (rpm/mpg/fuel) were restored!

this one doesn't mention a laden.bat:

This guide was originally posted by FAL, I just redid the images and created the entry in this wiki!

To update your system properly it is highly recommented that you use the tool Total Commander. There is a 30 days trial available.
If you copy the files manually - without Total commander - you might overwrite newer files with old ones. That's the difference between updating and doing it properly...

What you need checklist:

Total Commander
v40/v41/newer/older ISTA/P files, includes
daten - folder
ecu - folder
sgdat - folder
common sense and basic knowledge in computers


Difficulty: easy

Make a copy of your EDIABAS, EC-APPS and NCSEXPER folders. It's always good to keep some backups...
Start Total Commander
In the left window of Total Commander, head for your new daten-folder. In the right window, move to C:\NCSEXPER\DATEN\E89 (or another model you want to update). Now your screen should look like this:
Click on 'Mark' > 'Mark newer, hide same files'
As you can see on the following pictures, the newer files on the left will turn red. Drag one of these red files to the right windows and drop it there.
A windows will come up, just confirm it with 'OK'
Another window will pop up, now comes the clue: Here, select 'Overwrite all older'. All newer files will now replace the old ones, while equal versions or even newer files stay untouched.
Bibidi, babidi, boo - else updating is poo


Repeat this with the following folders:

C:\EDIABAS\ECU
C:\NCSEXPER\SGDAT

I'm not sure which is correct...

[HomeBrew]

Ok, followed the second quote from above (using tool commander).

Worked perfect. Simply re-coded the cluster and all is well.

Thanks for the help!

[Peertwelve]

Originally Posted by SLeagle328

From another post:


this one doesn't mention a laden.bat:



I'm not sure which is correct...

Thanks all for the help

[Coding@DetailAddict]

Thanks for the sticky mods

[HomeBrew]

Originally Posted by Grant@DetailAddict

Thanks for the sticky mods

Nice!

Thanks for the sticky!

[FlashMonkey929]

I'm hoping one of you can help me, I've tried and tried but I can't get this damn error to go away. I've googled, searched, prayed, and no matter which thread I reference I still can't get my cluster to function normally.

I'm running Ediabas v6.4.7, though I have downloaded 7.0.x. I'm on a Netbook running Windows XP 32 bit, and I'm running v46 of the daten files, and when I do a check the in INPA, the Kombi module checks out okay but the error still remains on the cluster.

I originally coded the car using the files in the sticky DIY above, first the FRM module for the roll up windows with FOB and LED Corner delete. I then moved on to the Kombi to do the digital speedo and that's when I got the error.

The RED "car on lift" icon popped up and checking the code, it is CC-ID 60 (Speedometer failure). The tach, fuel, and temp gauges do not work.

I then did more research and figured I had outdated daten files and proceded to update via the many threads. I'm hesitant to update EDIABAS because I've read there may be compatibility problems with NCS Expert. I've reflashed it back to the original settings via Expert Mode in NCS and this still won't go away.

Someone please help me! Am I missing something?

[neilvosko]

You have to copy all the files from the files into appropriate directory including ediabias and bin

[FlashMonkey929]

Originally Posted by neilvosko

You have to copy all the files from the files into appropriate directory including ediabias and bin

I've done that already, any other possibilities?