Q re reading readiness codes for 1996 and 1997 12V 2.8L engines
05-29-2008, 06:55 AM
#1
AudiWorld Super User
Thread Starter
Join Date: Aug 2005
Location: beside the Great Salty Wetspot
Posts: 4,898
Likes: 0
Received 0 Likes
on
0 Posts
Q re reading readiness codes for 1996 and 1997 12V 2.8L engines
I can not access readiness codes for the one 1996 12V and two 1997 12V Audis I've recently tried. An error message pops up asking if the vehicle is OBDII compliant. I'm using the shareware version of VAGCOM and an OBDTOOL cable. (My old version of VWTOOL also generates an error message, fwiw.)
My setup will access all the control modules, as well as readiness codes on the 1999 30V 2.8L (wife's daily driver) I tried it on.
I've noted some references that single out the 96 and 97 12V's as being 'different' in several regards. They are:
from: http://www.ross-tech.com/vag-com/tour/readiness.html
"12V 2.8L V6 engines may have readiness bits stored in or near Measuring Block Group 029."
from: http://www.ross-tech.com/vag-com/audi_issues.html
1996-1997 Audi A6 2.8L 12V V6 Engine
"There is a bug in the Hitachi ECU that does not allow reliable monitoring or logging of multiple measuring groups. For these vehicles, we recommend only viewing or logging one group at a time."
I'm wondering if the unique aspects of the ECU noted above could be causing the problems I'm experiencing, or if there's a different cause...or even a work around.
My block 029 reads "000_000". Wild guess, but is the program looking for 8 bits?...instead of the 6 bits it appears my ECUs may be providing?
Any insight would be appreciated.
My setup will access all the control modules, as well as readiness codes on the 1999 30V 2.8L (wife's daily driver) I tried it on.
I've noted some references that single out the 96 and 97 12V's as being 'different' in several regards. They are:
from: http://www.ross-tech.com/vag-com/tour/readiness.html
"12V 2.8L V6 engines may have readiness bits stored in or near Measuring Block Group 029."
from: http://www.ross-tech.com/vag-com/audi_issues.html
1996-1997 Audi A6 2.8L 12V V6 Engine
"There is a bug in the Hitachi ECU that does not allow reliable monitoring or logging of multiple measuring groups. For these vehicles, we recommend only viewing or logging one group at a time."
I'm wondering if the unique aspects of the ECU noted above could be causing the problems I'm experiencing, or if there's a different cause...or even a work around.
My block 029 reads "000_000". Wild guess, but is the program looking for 8 bits?...instead of the 6 bits it appears my ECUs may be providing?
Any insight would be appreciated.
05-30-2008, 04:54 AM
#2
AudiWorld Super User
Thread Starter
Join Date: Aug 2005
Location: beside the Great Salty Wetspot
Posts: 4,898
Likes: 0
Received 0 Likes
on
0 Posts
Here's the exact text of the error message
"Readiness status not available!"
"Vehicle not OBD-II compatible?"
Data 0A19 0000
Block 29 reads 000_000
Bin
Readiness Byte
"Vehicle not OBD-II compatible?"
Data 0A19 0000
Block 29 reads 000_000
Bin
Readiness Byte
06-02-2008, 08:08 AM
#4
Audiworld Premium Sponsor
Join Date: Mar 2002
Posts: 1,907
Likes: 0
Received 0 Likes
on
0 Posts
Here ya go. :-)
<ul><li><a href="http://www.ross-tech.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=VSWR& ;Category_Code=VAGCOM">http://www.ross-tech.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=VSWR& ;Category_Code=VAGCOM</a</li></ul>
__________________
Andy
Andy
06-02-2008, 02:18 PM
#5
I have the same issue on a 1996 A6 with paid-for software.
I did build the interface myself, though. Does the OBD2 readiness check require a different electrical interface than the proprietary VAG setup to access the control modules?
06-02-2008, 02:28 PM
#7
Okay, I will do so the next time I have that car in the garage.
I will also probably ask you if there is anything I need to save, license-wise, off my old and slowly dying laptop for when I need to transfer the software to a new one.
Trending Topics
Thread
Thread Starter
Forum
Replies
Last Post
