vmoses
Newbie
Karma: +0/-0
 Offline
Posts: 13
|
 |
« on: December 10, 2017, 11:44:03 PM »
|
|
|
I installed a reconditioned 4b920981P cluster in my 01 A6 2.7t (Immo III). Had it running with no problems until I decided to correct some of the speedometer error between the donor Allroad and my sedan.
Attached is the origina bin file and my modified file. Neither wants to load DEF free at this point. There is always the possibility that I've somehow corrupted the original.
Any help would be appreciated.
|
|
|
|
|
Logged
|
|
|
|
|
macxxx
|
|
« Reply #1 on: December 14, 2017, 10:08:10 AM »
|
|
|
only def in odometer? no other symptoms?
try to load up oringnal dump and correct odometer , it sometimes works
|
|
|
|
|
Logged
|
|
|
|
vmoses
Newbie
Karma: +0/-0
Offline
Posts: 13
|
|
« Reply #2 on: December 14, 2017, 11:17:13 AM »
|
|
|
That was my first reaction.
I took a couple of days off to go skiing so I'm not home right now, but will try again when I get back on Saturday. There are some other symptons that are a bit confusing.
When I try to read the cluster with VAG K+CAN 2.5, I just get garbage. But I know the cluster isn't completely corrupted because everything seems to work as expected except:
-DEF in trip odometer
-erratic speedo behavior...reads 170 at rest and then bounces around as i drive.
Odometer reads correct mileage.
When I try to rewrite the cluster, I know that something is working because the cluster has to be adapted again afterwards.
The software shows the last read at 0x715. I'm not sure if that is normal or not. I do see a full listing through 0x7FF.
|
|
|
|
|
Logged
|
|
|
|
|
macxxx
|
|
« Reply #3 on: December 14, 2017, 11:47:22 AM »
|
|
|
try epprom programeer 1.19 and KKL cable , works better
|
|
|
|
|
Logged
|
|
|
|
vmoses
Newbie
Karma: +0/-0
Offline
Posts: 13
|
|
« Reply #4 on: December 14, 2017, 03:01:23 PM »
|
|
|
 Great idea. I was thinking the same thing. Not sure how people feel about mentioning other fourms here, but I didn't see a copy of 1.19 here, so I tried to download a copy off the DK forum. For some reason it just logged me off with each attempt. I'll try again today but if anyone has a copy they can leave for me it would be appreciated.
|
|
|
|
|
Logged
|
|
|
|
|
macxxx
|
|
« Reply #5 on: December 16, 2017, 11:54:37 AM »
|
|
|
https://mega.nz/#!fsMiBLbK!2YePYVcmJwmN5oWNOAh9slyn1SM5wzDwSO9WwxjUXTo the upload on forum doesnt work so I uploaded to a server
|
|
|
|
|
Logged
|
|
|
|
vmoses
Newbie
Karma: +0/-0
Offline
Posts: 13
|
|
« Reply #6 on: December 16, 2017, 12:17:27 PM »
|
|
|
Thank you. Downloaded and will try this afternoon.
|
|
|
|
|
Logged
|
|
|
|
vmoses
Newbie
Karma: +0/-0
Offline
Posts: 13
|
|
« Reply #7 on: December 16, 2017, 02:21:41 PM »
|
|
|
I really appreciate all the help.
Okay, I tried to upload the original dump and correct the odometer. Didn't solve problem. This was using still using VAG Commander.
I was able to get EEPROM Programmer running on Com 1 in Win XP compatibility mode, but whatever I tried to do I just got back a message that it couldn't find an ECU (even when I tried to read the "Dash").
I think port settings are okay because both VCDS-Lite and VAG Commander work without problem.
Just out of curiosity, I thought 1.19 had an option to read/write either encrypted or unencrypted. I didn't see anything on the menus to indicate that. Did I miss something or was I just mistaken on the capability?
|
|
|
|
|
Logged
|
|
|
|
|
macxxx
|
|
« Reply #8 on: December 16, 2017, 02:25:50 PM »
|
|
|
you setup USB not com1/com2
the a6 C5 clusters can be read only decrypted thru OBD so you just use DASH and READ
|
|
|
|
|
Logged
|
|
|
|
vmoses
Newbie
Karma: +0/-0
Offline
Posts: 13
|
|
« Reply #9 on: December 16, 2017, 02:39:23 PM »
|
|
|
Sort of. My KKL cable is USB. I couldn't get it to recognize the cable using the USB Menu option, so I configured a USB port to run as a serial port (com 1). It's the same thing I do with VCDS-Lite. Then the menu option for Com 1 worked and it tried to read the cluster. Spun for a while and then said no ECU. Same thing happened if I just tried to read the ECU.
One of my problems was that I didn't realize the cluster was encrypted. My '01 wasn't and I didn't even think about the possibility that the new one was, so I don't have an encrypted bin file to fall back to.
What kind of a bench setup do you have to build to read/write encrypted? Do you have to pull the chip from the cluster?
|
|
|
|
|
Logged
|
|
|
|
|
macxxx
|
|
« Reply #10 on: December 16, 2017, 02:50:26 PM »
|
|
|
desolder epprom and read by programeer
|
|
|
|
|
Logged
|
|
|
|
vmoses
Newbie
Karma: +0/-0
Offline
Posts: 13
|
|
« Reply #11 on: December 17, 2017, 10:21:12 PM »
|
|
|
Reinstalled my old cluster today. EPROM Programmer read it with no problem and updated mileage. So now, I'll just figure out how to work on the new one that I DEFed one out of the car.
As far as being able to read/write ecrypted, it looks like all I need is a 93c capable writer and an 8 pin clip for the chip.
I'll look around to see what people are using for bench testing. I guessing that some connectors from a wrecking yard donor and a 12v power source will do the trick. The cables may take a little work to find.
I'm a little baffled over how I messed up the cluster in the first place. It may have just been an issue the VAG Commander software. Tomorrow I'll post my before and after coding for the speedo map and see if anyone can see a problem with it.
|
|
|
|
|
Logged
|
|
|
|
|
macxxx
|
|
« Reply #12 on: December 18, 2017, 01:18:00 AM »
|
|
|
You wont read IT with a clip , only desoldered can be read.
What do you want to with the Speedo? In the files you upload earlier its done completly wrong
And how to power up the cluster on bench you can find on this forum
|
|
|
|
|
Logged
|
|
|
|
vmoses
Newbie
Karma: +0/-0
Offline
Posts: 13
|
|
« Reply #13 on: December 18, 2017, 11:43:30 PM »
|
|
|
Thanks. I realized I'd screwed it up after i posted the files. I think I had the right idea, but I copied my changes into the wrong part of the speedo map. I'd calculated my check sum incorrectly also.
Here is what I was trying to do...just raise the speedo readings at the same set points. I only meant to change 0xD4 through 0xE3. Does this look better (or does the Audi speedo have a "k factor" to scale up the tranny pulses?
Original bin:
0xB0 FC 86 07 D0 07 23 10 3A 10 23 10 3A 10 F6 0E 22
0xC0 0F 01 01 08 18 00 80 00 04 03 0B 07 F9 09 CD 0D
0xD0 9A 10 11 11 03 00 78 00 C1 02 68 06 26 09 CD 0C
0xE0 8A 0F 00 10 08 00 00 20 03 40 06 60 09 80 0C A0
Modified bin:
0xB0 48 86 07 D0 07 23 10 3A 10 23 10 3A 10 F6 0E 22
0xC0 0F 01 01 08 18 00 80 00 04 03 0B 07 F9 09 CD 0D
0xD0 9A 10 11 11 0D 00 78 00 EB 03 F2 07 DB 09 94 0D
0xE0 4B 11 B3 11 08 00 00 20 03 40 06 60 09 80 0C A0
The checksum only appears to be one byte. I don't know whats in 0xB1 through 0xC3. So anything anyone can add about these would be appreciated. Also are there any other checksums that need to be updated?
Sorry for all the questions. First time through this.
|
|
|
|
|
Logged
|
|
|
|
|
macxxx
|
|
« Reply #14 on: December 19, 2017, 12:43:44 AM »
|
|
|
What was wrong with your speed?
Wysłane z mojego GT-I9505 przy użyciu Tapatalka
|
|
|
|
|
Logged
|
|
|
|
|
