Title: Any tips on reading my 4B0 906 018 R Post by: jiggle on February 27, 2013, 01:06:03 PM Hi guys, I have a euro 2000 a6 1.8tq , I have been attempting to read the ecu and failing,
The car hasn't been flashed and its running standard everything, I have looked everywhere for info but found nothing which mentions my ecu which is 4B0 906 018 R I have a cheap ebay vagcom cable, which connects fine with slow init, stays connected until I hit read flash then anywhere from 1% to 3% it will fail with a failed to read ecu error. I wondered if there is anything I need to do? is it possible to read the flash via obd with the immobiliser untouched? I tried pulling fuses today but it made no difference. Ive really put off asking on here :) Ive looked everywhere and never found anything that really helped. Be great if anyone can let me know why it isn't reading, or what I need to do to get it to work. Thanks in advance, Jas Title: Re: Any tips on reading my 4B0 906 018 R Post by: jiggle on March 01, 2013, 04:12:16 AM Im still not having any luck, Ive been looking on ebay for a new cable, Ive found some in the uk which wont take long to get here, which would you guys suggest out of
MPPS clone cable, v3 or v13 (2 types with box or built into cable) Galletto clone, although im not sure I want to open the ecu up for boot mode or a KWP2000+ cable? it comes with more adapters which I don't need but also includes some tunes Which would you guys buy? Be great to get some good advice. Thank you Title: Re: Any tips on reading my 4B0 906 018 R Post by: vagenwerk on March 01, 2013, 05:05:13 AM try nefmoto with slow init, check all speeds , also car battery voltage have to be 12.5V or higher
Title: Re: Any tips on reading my 4B0 906 018 R Post by: jiggle on March 01, 2013, 05:45:47 AM Thank you for getting back to me, I cant get the car on a charger where I live, I have tried it with jump leads on a second battery both fully charged, but same result.
I noticed yesterday, if I change the baud rate, the status at the bottom of nefmoto still says 124800, like it didn't change. That's why I started looking for a better cable. My cable has a fdti 232bm chip in it so it doesn't support all the tools out there. It works perfectly with VCDS Lite and nefmoto connects slow init everytime, it always fails between 2% and 3% reading flash. Title: Re: Any tips on reading my 4B0 906 018 R Post by: sweegie on March 02, 2013, 12:49:53 PM Galletto will read many things without the need for boot mode. MPPS also. In the long run, mpps is probably a more worthwhile tool IMO though.
Title: Re: Any tips on reading my 4B0 906 018 R Post by: vagenwerk on March 03, 2013, 08:55:23 AM If you can't get charger , you should borrow voltage from the other car.
connect both batteries with start cables and start the car then try to connect nefmoto to your car , i try and this way somtimes also help and work like a charm. test and give some info Title: Re: Any tips on reading my 4B0 906 018 R Post by: jiggle on March 03, 2013, 10:36:44 AM Thanks for all the help guys, Ive ordered a cheap mpps cable from ebay. Im going to attempt to read the flash again in a moment, with the ebay vagcom cable.do you think I should pull the dash fuses? Last time I tried I pulled the fuse that the lid said was for the cluster but the cluster stayed on, after a few minutes I had a warning beep, oil level I think. Il go give it a try and post back what happens. Fingers crossed
Title: Re: Any tips on reading my 4B0 906 018 R Post by: vagenwerk on March 04, 2013, 03:12:17 AM check my solution , probably will work ,
with mpps you also have to connect charger to battery , voltage must be at least 12.5V or higher ! so try one more time with nefmoto and second fired car to borrow the voltage Title: Re: Any tips on reading my 4B0 906 018 R Post by: jiggle on March 04, 2013, 09:06:00 AM Thanks again, I tried a few times today with jump lead hooked up to a running vehicle, the voltmeter on the dash was showing over 14v. Same results :( gets to 2% read then fails, reads really really slow. I tried a few baud rates from 10400 to 124800 same results. The log file shows the same as normal it looks like the errors starts like this
04/Mar/2013 02:48:26.348: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.350: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x00 04/Mar/2013 02:48:26.353: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.355: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0xD4 04/Mar/2013 02:48:26.358: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.360: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0xB4 04/Mar/2013 02:48:26.362: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.365: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x04 04/Mar/2013 02:48:26.367: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.369: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x00 04/Mar/2013 02:48:26.372: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.374: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0xCC 04/Mar/2013 02:48:26.377: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.379: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x00 04/Mar/2013 02:48:26.381: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.384: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0xC4 04/Mar/2013 02:48:26.386: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.388: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0xA0 04/Mar/2013 02:48:26.391: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.393: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x08 04/Mar/2013 02:48:26.395: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.398: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x00 04/Mar/2013 02:48:26.400: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.402: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0xC4 04/Mar/2013 02:48:26.405: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.407: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0xB0 04/Mar/2013 02:48:26.410: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.412: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x0A 04/Mar/2013 02:48:26.415: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.417: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x00 04/Mar/2013 02:48:26.419: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.421: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0xA8 04/Mar/2013 02:48:26.424: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.427: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x40 04/Mar/2013 02:48:26.429: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.431: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x08 04/Mar/2013 02:48:26.434: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.436: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x44 04/Mar/2013 02:48:26.438: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.441: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0xDC 04/Mar/2013 02:48:26.443: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.445: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x55 04/Mar/2013 02:48:26.448: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.450: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0xD4 04/Mar/2013 02:48:26.452: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.454: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x74 04/Mar/2013 02:48:26.457: LOG: Could not construct valid message from received data: InvalidChecksum 04/Mar/2013 02:48:26.460: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x06 04/Mar/2013 02:48:28.465: LOG: Double checking receive buffer for embedded messages before flushing receive buffer due to P1 ECU response inter byte time out. 04/Mar/2013 02:48:28.467: LOG: Flushing 196 bytes from receive buffer due to P1 ECU response inter byte time out. 04/Mar/2013 02:48:28.469: LOG: Message received no replies. 04/Mar/2013 02:48:28.472: LOG: Resending message. Send attempts: 2 04/Mar/2013 02:48:28.474: LOG: Sent message with service ID TransferData 04/Mar/2013 02:48:28.557: LOG: Received message with service ID: TransferDataPositiveResponse 04/Mar/2013 02:48:28.562: LOG: Sent message with service ID TransferData My ebay mpps cable might arrive tomorrow, hopefully il have more luck with it. Thanks again Jas Title: Re: Any tips on reading my 4B0 906 018 R Post by: jiggle on March 05, 2013, 06:58:45 AM Great news, my cable turned up and it appears to have read the flash off first time :) 1mb bin was saved.
It might be a silly question, will the file the mpps program made be the same as the file nefmoto would have made if I pulled the ecu and read it? I mean in the same format? Thank you for all the help, this site is brilliant. Thank you |