LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852
LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852
Hi, for those who have a Tunercat OBD2 Cable like me and dont have any decent logging software to log with it, here is the answer!
for the latest update of this adx the following has been added:
Latest Version:
to swap between 1X and 4X, you need to change the Connection Command drop down box to either "CONNECT 1X MACRO" or "CONNECT 4X MACRO"
to get the wideband working, if you have ADC already enabled on your AVT, you can hook it up to channel 1, otherwise you may be able to add the missing components to get it working (which is what I did) details on this are difficult as each revision of AVT had different components missing. watch out for a separate thread detailing this.
Also, you will need to edit the formula for the wideband value to suit your range, currently it is set to: (((22.39-7.35)/255)*X)+7.35 im sure you can figure out where to type your range numbers in the equation
this screenshot was taken on my bench PCM, which is why some values look a bit funny.
if you have got a different AVT other than 852 and are getting errors because of the wideband, you can open the "P1 FAST MON MACRO" and remove ADC TX and ADC RX from the bottom of it.
for the DTC gathering the adx is a bit buggy due to the way tunerpro handles incoming packets. its a bit of a hack to get it working at all. You open your FAULT CODES item list and then execute the fault code macro from the send command toolbar. it can read up to four DTC's at a time. if you do clear codes, you must close and reopen tunerpro before checking codes again otherwise the first codes you read out will become stuck in the DTC2,DTC3 and DTC4 values.
I have also made a completely new ADX that loads up the PIDs into 3x 6 byte DPID's then requests each of the 3 DPID packets in turn. so instead of reading 20 PID packets each cycle it only reads 3 DPID packets. I recently got this adx working in aldldroid on the avt-852 with an android otg cable.
this adx doesnt have as many pids as the old style ADX so I have kept both available.
Archive
1.4 update - 6-12-2012 added some new pid's, knock stuff, and IAC motor position
1.2 update - 23-03-2012 found an issue with the coolant temp, packet offset off by one, explains the funny coolant temp readings some have been having.
1.1: I changed the default macro to update all the priority items in between each individual non priority PID and it now logs all of the items shown on the "GM & SAE DASH" it seems to work better that way.
for the latest update of this adx the following has been added:
- No More 1 speed and 4 speed as separate versions. you choose the connection macro yourself (defaults to 1x)
- Added Wideband input support for the AVT 852 equipped with ADC
- Added basic DTC gathering support - see viewtopic.php?f=10&t=2314&p=66894#p66894
Latest Version:
to swap between 1X and 4X, you need to change the Connection Command drop down box to either "CONNECT 1X MACRO" or "CONNECT 4X MACRO"
to get the wideband working, if you have ADC already enabled on your AVT, you can hook it up to channel 1, otherwise you may be able to add the missing components to get it working (which is what I did) details on this are difficult as each revision of AVT had different components missing. watch out for a separate thread detailing this.
Also, you will need to edit the formula for the wideband value to suit your range, currently it is set to: (((22.39-7.35)/255)*X)+7.35 im sure you can figure out where to type your range numbers in the equation

this screenshot was taken on my bench PCM, which is why some values look a bit funny.
if you have got a different AVT other than 852 and are getting errors because of the wideband, you can open the "P1 FAST MON MACRO" and remove ADC TX and ADC RX from the bottom of it.
for the DTC gathering the adx is a bit buggy due to the way tunerpro handles incoming packets. its a bit of a hack to get it working at all. You open your FAULT CODES item list and then execute the fault code macro from the send command toolbar. it can read up to four DTC's at a time. if you do clear codes, you must close and reopen tunerpro before checking codes again otherwise the first codes you read out will become stuck in the DTC2,DTC3 and DTC4 values.
I have also made a completely new ADX that loads up the PIDs into 3x 6 byte DPID's then requests each of the 3 DPID packets in turn. so instead of reading 20 PID packets each cycle it only reads 3 DPID packets. I recently got this adx working in aldldroid on the avt-852 with an android otg cable.
this adx doesnt have as many pids as the old style ADX so I have kept both available.
Archive
1.4 update - 6-12-2012 added some new pid's, knock stuff, and IAC motor position
1.2 update - 23-03-2012 found an issue with the coolant temp, packet offset off by one, explains the funny coolant temp readings some have been having.
1.1: I changed the default macro to update all the priority items in between each individual non priority PID and it now logs all of the items shown on the "GM & SAE DASH" it seems to work better that way.
Re: LS1 ADX to suit Tunercat OBD2 Cable
Good work 
Works at just over 40hz on my bench setup. No car to test on, though.

Works at just over 40hz on my bench setup. No car to test on, though.
Have you read the FAQ? For lots of information and links to significant threads see here: viewtopic.php?f=7&t=1396
Re: LS1 ADX to suit Tunercat OBD2 Cable
just had a thought, what if I could dump the pid's at VPW 4x......I wonder what hz tp5 would get up to.
results below. this was on my core i7 tho, and it slows to 60 hz on the monitor screen. guess it really does suck a lot of cpu power
results below. this was on my core i7 tho, and it slows to 60 hz on the monitor screen. guess it really does suck a lot of cpu power

- Holden202T
-
- Posts: 10054
- Joined: Sat Feb 28, 2009 9:05 pm
- Location: Tenambit, NSW
Re: LS1 ADX to suit Tunercat OBD2 Cable
you'll see some good saw tooth rpm traces with that speed!
No matter what the question is, the answer is always more horsepower! 
Just starting out? Have a read of the getting started guide
Basic tuning of a delco ECM with $12P thread
Advanced tuning of a delco ECM with $12P thread

Just starting out? Have a read of the getting started guide
Basic tuning of a delco ECM with $12P thread
Advanced tuning of a delco ECM with $12P thread
- delcowizzid
-
- Posts: 5322
- Joined: Sat Feb 28, 2009 8:38 pm
- Location: Wellington NZ
Re: LS1 ADX to suit Tunercat OBD2 Cable
i used both adx's today seem to work good
If Its Got Gas Or Ass Count Me In.if it cant be fixed with a hammer you have an electrical problem
Re: LS1 ADX to suit Tunercat OBD2 Cable
updated adx in first post to fix coolant temp packet offset issue.
Re: LS1 ADX to suit Tunercat OBD2 Cable
Thanks for the hard work shared Jayme! We are enjoying you adx files here in the states as well!
http://www.gearhead-efi.com/Fuel-Inject ... CM-Project!
http://www.gearhead-efi.com/Fuel-Inject ... CM-Project!
Re: LS1 ADX to suit Tunercat OBD2 Cable
thanks mate! didnt get much feedback in this thread so assumed nobody cared or used the adx... I have been mainly using it for my own tuning on aussie ls1's, feel free to give feedback on it and any changes or fixes I need to do... I dont log much normally other than the basics and knock.
Re: LS1 ADX to suit Tunercat OBD2 Cable
Don't feel that way! We all care! Some XDF are coming together as well. Once a flash and cable is available this will explode!
There's also some work going for ADX with VPW cable.
Thanks Mate!
There's also some work going for ADX with VPW cable.
Thanks Mate!
Re: LS1 ADX to suit Tunercat OBD2 Cable V1.6
Updated first post with new version 1.6
includes Wideband and DTC support!
includes Wideband and DTC support!
Return to ALDL, OBDII Logging and Scanning
Who is online
Users browsing this forum: No registered users and 6 guests