how to find pid location to add to adx?

[???]

so this might be the wrong location, but is there a way to find a location of a pid you want to log from another scan tool? like I have pids from other places on the net, add them to torque app and they display. I'm guessing it's the same thing with tuner pro.. if I have the pid I can add it under edit ads. but how are these guys finding these pid locations? I've got access to paid scanners with that will show the data, I just don't know how to get that info and put it into a more handy program.

is there some thing I can use to log what the scanner doing?

[kur4o]

You don`t need pid location, You need pid number, pid size and pid scaling. Than use the information to add the needed data in other software.

For logging you can try this program. It have a list of pids and you can add more if you want.Go to utilities->logger
https://github.com/joukoy/UniversalP...tcher-Full.Zip

[???]

I'm sorry, I said location, that is the wrong term since it's not changing a value in a bin file. I'm still not sure what that number is called. address?

anyways, I'll take a look at that patch file when I'm on my computer and can open it. on my phone now. but I thought patches were things to add into the bin file. like you add patch to add a function?

I'm probably not understanding what you mean. I've always been able to tune with what's provided but I'm missing some understanding of how it all works as far is making xdf and adx. in this particular case I'm not looking to adjust anything in a tune. just view interesting data easily and TP is handy and I've used it before. so like this is what I have inputted onto torque app for reference. this data I found online someone else figured out. this is is the hybrid battery charge and discharge current from a yukon hybrid. normally you need a tech 2
to find this level of data, but someone found the pids for it. I would like to learn how it's done. and make a nice adx file with all the stuff I wanna see quicky without the clunky tech 2. off the top of my head, say rear ride level air pressure. it's super handy when towing a trailer as about 160psi they start failing. my tech 2 shows this and I use it for loading tongue weight but it would be nice to have up on tp over a blue tooth connection on trips.

thanks for any help understanding this data steam stuff.

[kastein]

There are a few excellent threads on this process over on GMTnation actually, in fact I joined over there before I joined over here because they were the best data I could find. But they don't do much in the way of custom tuning and ROM reverse engineering so here I am. The basic process is, if you have a tool that already supports the PID you want, you use an OBD2 Y-cable with your existing tool and a ELM327 class device that allows rs232 port emulation mode on your device (that's a topic for another day, there's a lot of variance in quality and device support between both devices and OSes) and set up your filters on the elm327, record a big data collection and troll through it till you get past the setup handshaking and find the repeated requests to a small set of PIDs you don't recognize, then investigate them more closely till you figure out what they do.

The second is to cast a wide net by creating a script or program that just requests one PID after another while recording responses till it's got the whole set, then filter out the ones rejected as invalid, then begin probing each new unknown PID while exercising hardware inputs till you find the one you are looking for. It is very time consuming.

Another method I'm hoping to use is to simply reverse engineer the firmware on the ECU and find which input it is reading and where it's putting it in memory, combine that with factory service manual wiring diagrams and knowledge of OBD2 standards and you can find PIDs working backwards from the way most people do.

[In-Tech]

Another method I'm hoping to use is to simply reverse engineer the firmware on the ECU and find which input it is reading and where it's putting it in memory, combine that with factory service manual wiring diagrams and knowledge of OBD2 standards and you can find PIDs working backwards from the way most people do.

Hiya, no offense, this is no small task :)

[kastein]

I completely agree. It's one that I hope to get to, but it's definitely not the simplest way, just the most complete way.