LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852

160 And 8192 Baud Aldl
Site Admin
User avatar
Posts: 4670
Joined: Sat Feb 28, 2009 8:34 pm

Re: LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852

Postby antus » Sat Dec 17, 2016 10:25 am

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: viewtopic.php?f=7&t=1396

Posts: 18
Joined: Sun May 11, 2014 6:36 pm

Re: LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852

Postby Highlander » Sun Jan 01, 2017 1:21 pm

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

User avatar
Posts: 2522
Joined: Sun Mar 01, 2009 8:59 am
Location: North Coast, NSW

Re: LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852

Postby Jayme » Tue Jan 03, 2017 10:53 am

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)

Posts: 19
Joined: Sat May 22, 2010 8:36 am

Re: LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852

Postby beyerch » Thu Jun 22, 2017 9:11 pm

AVT interfaces? How passe'

IMG_8301.JPG

IMG_8230.JPG


Coming soon....

Site Admin
User avatar
Posts: 4670
Joined: Sat Feb 28, 2009 8:34 pm

Re: LS1 ADX V1.6 to suit Tunercat OBD2 Cable, AVT 852

Postby antus » Thu Jun 22, 2017 11:32 pm

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: viewtopic.php?f=7&t=1396

Previous

Return to ALDL, OBDII Logging and Scanning

Who is online

Users browsing this forum: No registered users and 1 guest