LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852
- antus
- Site Admin
- Posts: 8261
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852
Its a regular tunerpro adx. You can add extra fields and calculations, yes.
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
-
- Posts: 81
- Joined: Sun May 11, 2014 6:36 pm
- cars: Z06
Re: LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852
I still fail to see how the adx works
For instance: we get RPM to be at memory location: 0xFFA562
on the ADX its: 0x08 0x00 0x6C 0xF1 0x10 0x62 0x11 0x55
anyone have the rundown on what each command represents?
Thanks
For instance: we get RPM to be at memory location: 0xFFA562
on the ADX its: 0x08 0x00 0x6C 0xF1 0x10 0x62 0x11 0x55
anyone have the rundown on what each command represents?
Thanks
Re: LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852
part of it is the AVT protocol, feel free to look up the AVT website and download their guide.
the command you show above is part of the Received packet for GM RPM PID.
the adx sends: 0x07 0x6C 0x10 0xF1 0x22 0x11 0x55 0x01
0x07 = send 7 bytes
0x6C = priority byte
0x10 = PCM address (for getting extended pids)
0xF1 = address of AVT
0x22 = initiate mode 22 data request
0x11 0x55 = GM enhanced PID for RPM
0x01 = I forget but just put it there lol.
the command you showed in your post is part of the receive packet (used by tunerpro to pattern match and align the actual value byte to the header) :
0x08 0x00 0x6C 0xF1 0x10 0x62 0x11 0x55 0xXX 0xXX
0x08 = here is a packet, 8 bytes in length (not including length and status bytes)
0x00 = status byte (no errors)
0x6C = Priority byte
0xF1 = Dest (address of AVT interface)
0x10 = address of PCM
0x62 = responde to mode 22 (22+40 = 62)
0x11 0x55 = GM enhanced PID for RPM
0xXX 0xXX = 16 bit value for RPM. convert from hex to DEC then use formula 163840 / X to get actual RPM.
so basically, there are 2 formats of send/receive. one for SAE pid's and a different one for GM enhanced PID's. I dont know how to get data from a memory location, but it will be in the vpw protocol somewhere in a document.
what are you trying to add to it anyways?
if you really want to be confused, have a look at my DPID adx on the first page. instead of getting PID's seaprately, it dumps them into collections, and gets them all at once. its way faster. (ignore hte aldldroid tag at the end of the file. it wokrs in tunerpro too)
the command you show above is part of the Received packet for GM RPM PID.
the adx sends: 0x07 0x6C 0x10 0xF1 0x22 0x11 0x55 0x01
0x07 = send 7 bytes
0x6C = priority byte
0x10 = PCM address (for getting extended pids)
0xF1 = address of AVT
0x22 = initiate mode 22 data request
0x11 0x55 = GM enhanced PID for RPM
0x01 = I forget but just put it there lol.
the command you showed in your post is part of the receive packet (used by tunerpro to pattern match and align the actual value byte to the header) :
0x08 0x00 0x6C 0xF1 0x10 0x62 0x11 0x55 0xXX 0xXX
0x08 = here is a packet, 8 bytes in length (not including length and status bytes)
0x00 = status byte (no errors)
0x6C = Priority byte
0xF1 = Dest (address of AVT interface)
0x10 = address of PCM
0x62 = responde to mode 22 (22+40 = 62)
0x11 0x55 = GM enhanced PID for RPM
0xXX 0xXX = 16 bit value for RPM. convert from hex to DEC then use formula 163840 / X to get actual RPM.
so basically, there are 2 formats of send/receive. one for SAE pid's and a different one for GM enhanced PID's. I dont know how to get data from a memory location, but it will be in the vpw protocol somewhere in a document.
what are you trying to add to it anyways?
if you really want to be confused, have a look at my DPID adx on the first page. instead of getting PID's seaprately, it dumps them into collections, and gets them all at once. its way faster. (ignore hte aldldroid tag at the end of the file. it wokrs in tunerpro too)
Re: LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852
AVT interfaces? How passe'
Coming soon....
Coming soon....
- antus
- Site Admin
- Posts: 8261
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852
Unless this is AVT compatible, I think it needs to be split to a new thread?
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
Re: LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852
Jayme,
What type of wideband sensor is the equation for ?(e.g bosch lsu 4.2 or bosch lsu 4.9)
What type of wideband sensor is the equation for ?(e.g bosch lsu 4.2 or bosch lsu 4.9)
- Holden202T
- Posts: 10311
- Joined: Sat Feb 28, 2009 9:05 pm
- Location: Tenambit, NSW
- Contact:
Re: LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852
i wouldn't think it would matter as the wideband would do the 0-5v scaling but i'd guess Jayme has a 4.2 non the less.
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
Re: LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852
Does anybody know the equation for 2 bar MAP for ls1 adx 1.6
I've tried using the equations posted on thread viewtopic.php?t=3509
The equations in the above thread are the same as used on 12P files, these don't work for the LS1 adx
From my test's it appears that the MAP SAE is not suitable for reading boost as it take a RAW value of X in its formula and seems to be restricted at max 105 kpa even if changing the gauge values, I've tried a generic scan tool with elm327 interface and have the same restriction (max's at 105 KPA)
The GM enhanced MAP seems to be appropriate for using 2 bar or 3 bar MAP sensor and playing with various formula's shows hope , the formula currently loaded for GM MAP KPA in the LS1 adx is (X + 28) / 2.71 which seems to apply to 1 bar MAP.
Does anyone know what the formula should be for a 2 BAR MAP sensor for the LS1 ADX ?
P.S i had posted a similar question on another thread a few days ago but this thread seems more appropriate.
I've tried using the equations posted on thread viewtopic.php?t=3509
The equations in the above thread are the same as used on 12P files, these don't work for the LS1 adx
From my test's it appears that the MAP SAE is not suitable for reading boost as it take a RAW value of X in its formula and seems to be restricted at max 105 kpa even if changing the gauge values, I've tried a generic scan tool with elm327 interface and have the same restriction (max's at 105 KPA)
The GM enhanced MAP seems to be appropriate for using 2 bar or 3 bar MAP sensor and playing with various formula's shows hope , the formula currently loaded for GM MAP KPA in the LS1 adx is (X + 28) / 2.71 which seems to apply to 1 bar MAP.
Does anyone know what the formula should be for a 2 BAR MAP sensor for the LS1 ADX ?
P.S i had posted a similar question on another thread a few days ago but this thread seems more appropriate.
- antus
- Site Admin
- Posts: 8261
- Joined: Sat Feb 28, 2009 8:34 pm
- cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B - Contact:
Re: LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852
try putting the whole equasion in brackets and *2
this is because high point 5volt was 100kpa, but now its 200kpa so ×2. if that doesnt work, what is the equasion now?
this is because high point 5volt was 100kpa, but now its 200kpa so ×2. if that doesnt work, what is the equasion now?
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
Re: LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852
I did try that equation ((X + 28) / 2.71) * 2 but found that it reads correct at full range 202 kpa with a voltage from map sensor to ref of 4.996v, sensor open to atmosphere i'm getting 106 kpa at 2.27 v (a little higher than expected as my elevation is around 240M) and if if disconnect MAP sensor wire i'm still getting 20.664 KPA on tuner pro enhanced GM MAP.
If I go back to SAE MAP i'm showing 9 KPA.
My 2 bar sensor linear is 207.66 with an offset of 9 (tables c6301 and c6302)
I've tried using values 190 & 10 but no major difference
If I go back to SAE MAP i'm showing 9 KPA.
My 2 bar sensor linear is 207.66 with an offset of 9 (tables c6301 and c6302)
I've tried using values 190 & 10 but no major difference