Ok, NSFW, I got my cable today and read my OSID..
It's OSID is: 12212156
Cal ID: 12212431
HW ID: 9386530

 

There are 2 very good XDF's for that OS, it's actually the most ideal OS for working with as every possible engine size, transmission type and vehicle platform are support for it.... including the SBC Vortec 5.0/5.7 when used with the proper engine segment.

 

Where do I find the XDF's for this OS??

 

Take a look and see if the XDF for your OS number from LRT has all the tables/settings your looking for. If that's not complete enough for you there is another one but it's not laid out nearly as fluid and I would say is more in line for someone who is well versed in Tuner pro.
http://www.gearhead-efi.com/Fuel-Inj...d-is-TunerPro)

 

Thanks so much Pete.. As I found one and read a little father down that the checksum bricked 2 PCMs.. So I'll check out your link instead.. lol

 

This is my system so far and it works for what I need it to do:

Manufacturer: ASUSTek Computer Inc.
Model: TP550LAB
Processor: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz 2.19 GHz
Installed Memory (RAM): 8.00 GB
System Type: 64-bit Operating System, x64-based processor
Pen and Touch: Touch Support with 10 Touch Points

OBDII Cable: ScanTool OBDLink SX USB

 

Does anyone have a ADX file created for logging in tuner pro any off the 5v inputs below to use with a wideband o2 sensor. for OS 12212156

All of these are 0-5v inputs:
EGR (need to disable spark and fueling modifiers)
AC (need to zero tq adders and bump spark so idle and spark manipulation doesn't occur at various voltage inputs)
Trans Temp Sensor (spare if no automatic trans is being used)
Fuel Tank Level Sensor 1
Fuel Tank Level Sensor 2
Fuel Tank Pressure

 

I ordered my scan tool today, need to start on my bench harness.
Still lost on id-ing of the pcm.


Stampede.

 

Did you get the cable from the link I shared??
IDing the PCM is simple if you have the sticker still attached

As for the OS, you'll learn that when you first read the PCM..
I lucked out and have a full running parts truck with the 5.3L, I saved the stock (untouched) PCM settings to one .bin file and deleted VATS on a second .bin file..
Oh, keep and untouched copy of your PCM, then do small changes and save that as a different .bin file.. That way if something goes wrong or doesn't go right, you can revert back.. Just something I've read while learning on the way..

 

Oh, and just for $hits and giggles, I tried the cable and software out on the wife's 2001 Pontiac Grand Prix with PCM Hammer..
Here's what I got:
[10:32:10:650] PCM Hammer 006
[10:32:11:888] Voltage: 11.9V
[10:32:11:904] Elm ID: ELM327 v1.3a
[10:32:11:952] ScanTool device ID: STN1130 v4.0.1
[10:32:12:356] Thanks for using PCM Hammer.
[10:32:21:041] VIN: 1G2WK52J61F235920
[10:32:21:120] OS ID: 12214425
[10:32:21:182] Calibration ID: 12214454
[10:32:21:247] Hardware ID: 12202600
[10:32:21:409] Serial Number: 1T97CM1074
[10:32:25:174] BCC query failed: Error
[10:32:25:245] MEC: 0

 

Something that would need to be done by the user to their bin file them selves. An ADX is only used to provides data, it doesn't change anything.

That may be possible but it would need to be supported by the OS....and unless your making your own one off ADX anything that's done needs to work on pretty much everything for a given PCM. There are not enough hours in the day to create one off files for every OS, vehicle, trans and fuel type.

Have you actually wired a wide band onto one of these and then checked the reading with a scan tool to see what they actually read? Saying it's 0-5 volts and actually getting a true 0-5 volt may not be the same and this is where voltage offset or VRef settings are used to "correct" the actual voltage the PCM would be reading from the theoretical voltage it should be reading.

Now some things you did not mention that are rather important...and may possibly answer your own question. What tool are you looking for an ADX for? There is an ADX for the AVT-852 that used the AVT's built in ADC channels but this version of the interface isn't exactly common. The Allpro and the Obdlink have much different logging capability even though they are both very similar.
The J2534 is going to be all by itself and to my knowledge is not going to be compatible in Tuner Pro for logging even if you wanted to create an ADX for it just due to how the J protocol works.
If your talking about a tool other then whats listed above....well then that also changes things.

And then lets discuss wide bands. As in what wide band? Unless your cool with just reading the raw 0-5 volt value and there is no need for a voltage offset the type of wide band does make a difference and they are not all the same. They may all put out a 0-5 volt signal but the A/F at a given voltage will not be the same between brand's X and Y. The curve of the sensors is also going to be different. There is a reason that HPT changed how a wide band is used with the new version of their interface and that's because trying to use the analog 0-5 volt scale and make it universal is a nightmare. It was far easier to just let the user plug the wide band into the computer via what ever method the wide band used and then pull the data from the wide bands own logging software.


So to wrap this up, there are a number of ADX's out their that are basic but work, a few that have the tool and PCM side done but need the byte values reassigned and scaled in tuner pro and one for the AVT that already does logging.
The issue is what parameters need to be logged. Aside of the difficultly of building an ADX that's capable of working with multiple pid tables you will never be able to select what specific pids you want to log with tuner pro. The best that will ever be possible is having multiple options of predefined tables but selecting what table is used when an ADX is setup that way is not exactly a simple task. It does require going into the ADX file settings to change what group would be used and it is possible to alter/damage an ADX if its not done correctly. For someone other then an end user to create an ADX that worked with a wide band would require an almost unanimous agreement from a large number of users on what wide band it should be done for. It would likely be very time consuming and require a great deal of live testing in a fully functional ADX(that also has yet to be finished).

 

I'm not sure if that Scantool chip is the Obdlink Sx or Lx off hand, if it's the LX(BT dongle).....and you have an Android phone/tablet you can check out Ls Droid if you'd like to read the Grandprix's Pcm . The 00-06 V6 Pcm's are officially supported for Read and I have an unreleased version with Write for the V6 as well that I'm sharing on a per request basis since I still have limited feed back on individual user experience flashing the V6 stuff right now.

 

I've got nothing on the ADX front, but I'm making pretty good progress on a data logging app that will make it easy to log (or just display) any parameter that the PCM supports.

If you get can me the PIDs for those parameters, I can whip something up for you.

 

I've been following this with interest....but OEM ecu's are not something I usually bother with across any marque although I have looked at a few opensource Subarus.

So...a few questions. Hopefully not daft or irrelevant.

As a few people seem to be doing this on the bench....I havent noticed any pinouts or wiring guides listed in order to help with this ? Is there a guide as to the ecu pins to power up and connect to a DL16 socket ?

I see one place, Bench Force offering various cables and systems to connect to an ecu on the bench. Cable is cheap, their little box maybe less so.....as to which box is necessary or preferred not sure also.

A friend has an old 2004 Monaro, with a LS1B ecu from what I gather ? OS 12225074, This ecu seems to be same or compatible with a 411 ? I also have a 411 ecu sitting in my garage I bought with some parts a few years ago. So potentially I could flash a tune file into this ecu on the bench, to try in his car rather than touching his own ecu ? ( just in case it goes **** up ). Only caveat I've found online is his is cable throttle, and not all 411's have the chip for the IAC.

 

Hi all,

Someone can correct me if I am wrong,
but it is MY understanding the ALL '0411 PCMs are Drive by Cable,
that the DBW only came out with the P59 PCMs?

Mike

 

The ecu I have defo says 411 on it, and it came along with a track manifold and DBW throttle. Although I never ended up using any of the parts lol.
Maybe I misinterpreted this article...it does seem to refer to 1MB where it shows the pictures. Friends car is defo a cable/512kb ecu.

https://www.lsenginediy.com/comparin...i-controllers/

 

That Subaru stuff is kinda what motivated me to work on this project. My daily driver is a Subaru and the community that sprung up around those open source tools and cheap hardware is pretty amazing. When I bought my Corvette I was sad to see that there wasn't something similar for GM. Hopefully we can fix that.

Here's the wiring diagram you need for bench flashing:
https://github.com/LegacyNsfw/PcmHac...bench-Flashing

My 2002 C5 has a 411 PCM and is throttle-by-wire, so they definitely come in both flavors.

 

All P01/512K LS Pcm's were by default setup for Drive by Cable but could also be configured to work with Drive by Wire.

The P59 on the other hand was by default only capable of Drive By Wire but some P59's were also capable of supporting Drive By Cable if it had the correct parts.

 

Hi all,

Figures they would use the DBW on the 'Vette!
Thanks for the clarification

Mike

 

I got the OBDLink SX off of Amazon from here ( )..
I only tried it on the wife's car for just $hits and giggles to see if it would.. lol