Pages: [1]
Author Topic: Another new member can't start his car!  (Read 813 times)
stein
Newbie
*

Karma: +1/-0
Offline Offline

Posts: 9


« on: January 03, 2019, 07:17:01 PM »

Hey everybody,

New guy here in the Seattle, WA area. I've spent the last 2 years wrenching on my project allroad, mostly just replacing consumables around the engine and in the auto transmission.

Its a 2004 allroad 2.7t tip.

Well, I commuted in it to work today for the first time, after driving it on a few longer trips. I deleted my SAI and I was planning on creating a custom ROM down the road to delete those codes once I got more comfortable.

Today after work I decided it was perfectly safe to read the ROM of the ECU: what could possibly go wrong? Turns out something went wrong with the communication and it set the dreaded P1681. I did manage to get to 100% read, but was unable to save my stock binary unfortunately. When I overwrite an existing .bin, the resulting saved file is 0 bytes, and I am completely unable to save as a new file (windows error: file not found).

Anyway, because I have so far been unsuccessful in saving my stock image, I'd rather not download another image with the below fix, or make that change myself, as I don't want to lose the stock image.
http://nefariousmotorsports.com/forum/index.php?topic=6719.0

I also haven't touched my immo, so that might not be helping things.

Anyway, I'm glad to be here and I'll be around for a while as I play around with this car. Next time I won't do anything when its my only ride home from work...

edit: it is indeed a 551S box.
Quote
==============================================================================
ME7Check v1.12 (c) mki, 06/2004-05/2012
Checking file C:\Users\User\Desktop\ECU Tuning\audi\allroadStock.bin (size=1048576)
Reading Version Strings...
-> Bootrom Version = 06.02
-> EPK = 42/1/ME7.1.1/5/6030.03//25A/Dst48o/030603//
-> Contents of ECUID data table:
   - '0261208288'         (SSECUHN)         
   - '1037368391'         (SSECUSN)         
   - '4Z7907551S  '       (VAG part number)
   - '0020'               (VAG sw number)   
   - '2.7L V6/5VT    '    (engine id)       
-> Contents of ECUID data table:
   - 'HW_MAN004'                           


-> No errors found. File is OK.   *********************
« Last Edit: January 04, 2019, 10:00:06 AM by stein » Logged
stein
Newbie
*

Karma: +1/-0
Offline Offline

Posts: 9


« Reply #1 on: January 03, 2019, 08:10:14 PM »

I was at least able to read a 1024k file finally.

Letting the ecu rest and laptop charge. Worst case I'll fall back on daz's fix here:
If you attempt to read a 2.7t Allroad or A6 4Z7907551AA, or 4Z7907551S, you will then be stuck with a "programming not completed" DTC, as well as a no start situation!

To remedy this, reconnect with nefmoto (which will still work, thank god for small miracles) and flash one of the attached files. Neither of these have this issue and are compatible with all BEL Allroads/A6's.

Any tuning done on ME7.1.1 equipped 2.7t's should use the 551R (North American) or 551N (Euro) file as a base to avoid complications.



Edit: waiting after a full read didn't do anything. And of course I'm re-reading the getting started thread over dinner at home (car is still at work), I saw a new faq item I hadn't seen before about late model allroads having reading problems... I'll integrity check read image and flash that if it looks good.
« Last Edit: January 03, 2019, 09:18:56 PM by stein » Logged
vdubnation
Turboman
Global Moderator
Sr. Member
*****

Karma: +45/-2
Offline Offline

Posts: 431


« Reply #2 on: January 03, 2019, 09:53:05 PM »

I m guessing your box code was 551S common for late model allroads. If you attempt to read via boot it will shit it self basically wont let you start you can just flash a 551R issue resolved pm me if you need help.
Logged
stein
Newbie
*

Karma: +1/-0
Offline Offline

Posts: 9


« Reply #3 on: January 04, 2019, 10:51:30 AM »

I m guessing your box code was 551S common for late model allroads. If you attempt to read via boot it will shit it self basically wont let you start you can just flash a 551R issue resolved pm me if you need help.
Yep, its a 551S and of course I missed that one part of the Getting Started FAQ about reads being dangerous for late-model allroads.
The stock file I pulled checksummed out OK so I'm going to try flashing that first, and if that doesn't work, flash a 551R image from Daz.
I just want to confirm that flashing the 551R won't cause any issues with the stock immo setup: immo checks are in eeprom and doesn't care about flash contents, correct?
« Last Edit: January 04, 2019, 11:10:20 AM by stein » Logged
stein
Newbie
*

Karma: +1/-0
Offline Offline

Posts: 9


« Reply #4 on: January 04, 2019, 01:34:31 PM »

Reflashing the stock image did not work.
Flashing the 551R image did, although now I have these codes when running a full diag.
Quote
Address 02: Auto Trans       Labels: 01V-927-156.LBL
   Controller: 4Z7 927 156 M
   Component: AG5 01V 2.7l5VT USA 2222
   Coding: 01002
   Shop #: WSC 02334
   VCID: 50D3F34383FB
1 Fault Found:
18258 -  Powertrain Data Bus: Missing Message from ECU
            P1850 - 35-10 -   - - Intermittent

-------------------------------------------------------------------------------
Address 03: ABS Brakes       Labels: 8D0-907-389.LBL
   Controller: 4Z7 907 389 A
   Component: ABS/ESP allrad      D56
   Coding: 06497
   Shop #: WSC 02334
   VCID: 4AE7E12B65A7
2 Faults Found:
01119 -  Gear Recognition Signal
            35-10 -   - - Intermittent
18258 -  Powertrain Data Bus: Missing Message from ECU
            P1850 - 35-10 -   - - Intermittent
Address 17: Instruments       Labels: 4B0-920-xxx-17.LBL
   Controller: 4B0 920 983 FX
   Component: KOMBI+WEGFAHRS. VDO D17
   Coding: 20264
   Shop #: WSC 40233
   VCID: 83798C0F820D
   WA1YD64BX4N085843     AUZ7Z0D2598358
1 Fault Found:
01314 -  Engine Control Module
            49-10 -  No Communications - Intermittent

I put the gear shifter through its positions but didn't actually move the car anywhere.
Honestly, I have a feeling that these codes were already set. I think I've got a connector or two to clean up when I have time (or if the car gives up on me again). I'll post back again tonight whether or not I make it home :p.
Next steps will be to disable downstream O2s and SAI. I haven't decided if I will use this 551R image or the P1681-fixed 551S as a base.

At this point I think I have outgrown my welcome thread and will start a log.
« Last Edit: January 04, 2019, 02:07:52 PM by stein » Logged
SB_GLI
Hero Member
*****

Karma: +95/-7
Offline Offline

Posts: 1020


« Reply #5 on: January 04, 2019, 03:40:05 PM »

Just use the 551R and don't look back.   There is much more stuff available for this ecu.   Full a2l and 5120 available on nefmoto even.
Logged
stein
Newbie
*

Karma: +1/-0
Offline Offline

Posts: 9


« Reply #6 on: January 04, 2019, 08:17:28 PM »

Just use the 551R and don't look back.   There is much more stuff available for this ecu.   Full a2l and 5120 available on nefmoto even.
Flashed the 551R image from the linked post in #4.


Didn't realize I'd have to re-calibrate the air suspension, but I'd been meaning to do that anyway. Got it home just fine!

Gotta solve a few suspension/exhaust-pipe noises and then get cracking with ECU hacks again Smiley.
Logged
stein
Newbie
*

Karma: +1/-0
Offline Offline

Posts: 9


« Reply #7 on: February 16, 2019, 11:13:24 AM »

So I've been driving around with catless DPs without coding out downstream O2 fuel trims (sensors are in but with crappy spacers), so I'm spending the weekend making a new 551R file.

Is there any reason not to code them out completely so that I can just install plugs next time I'm under the car? I saw a thread on logging using widebands in place of the downstream sensors, but that even disabling the sensors did not disable a failsafe enrichening at certain voltages.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.021 seconds with 17 queries. (Pretty URLs adds 0.001s, 0q)