Pinouts and Code masks

[robertisaar]

and the confusion factor just went up for me...

[SappySE107]

Why did that make it harder to understand? Ready last post. That is what the guy at GM just confirmed.

[robertisaar]

Why did that make it harder to understand? Ready last post. That is what the guy at GM just confirmed.

fill in what i miss:

resistor packs don't determine the pinouts

PROM does not determine pinouts

pins are tied to specific inputs/outputs

????

i think i'm overthinking this. i think i should just accept that its the way it is and quit asking questions...

[SappySE107]

I have no idea what you are overthinking because you are simplifying the ecm as a giant USB port where any wire can become whatever you want it to in software and that is not the case. Lets try this.

The axles go to the hubs. You can't change that in software. The seat belt won't go to your abs module no matter what you do in software.

Each wire goes to a controller of some sort inside the ecm. There are injector drivers, timers, etc. This is not software based.

[bszopi]

http://www.cruzers.com/~ludis/1227749schematic.html

Look at those schematics and you will see that the connector pins are tied to various chips on the ECM's motherboard and don't necessarily tie into the PROM at all. Those various chips interact with the software in the PROM to perform various functions.

To expand on Ben's USB analogy... Think of the PROM as your computer's Intel processor, and the codemask as an OS ($A1 is Windows XP, $88 being Linux, etc). Inputs such as the keyboard and mouse, and outputs such as speakers and monitor aren't tied to the processor directly, but are controlled by other chips on the memory board, which are controlled by the processor. Yet the processor is controlled by OS on the hard drive. The OS still controls the same inputs and outputs, but it controls them differently.

[robertisaar]

interesting how it takes an analogy like that for me to understand...

both helped, a lot, but i'm just going to quit asking questions before i get confused again...

[SappySE107]

I see you wrote the A1.ads file for tunerpro. I may need your help with 2E if I can't get this to work (94-95 DOHC code). This code stuff just isn't my thing, but I can play with hardware all day long.

[robertisaar]

I see you wrote the A1.ads file for tunerpro. I may need your help with 2E if I can't get this to work (94-95 DOHC code). This code stuff just isn't my thing, but I can play with hardware all day long.

interestingly enough, i'm like the exact opposite.

i breeze through the ADS files. the old 160 Baud ones, i finish within 20 minutes, organised and labeled. obviously the newer P4 ECM/PCMs take longer, but i finish most within an hour...

and if you see that i did the A1, i'm sure you noticed that the majority of the ADS files that are on mark's site were done by me. i'm actually taking requests in the forums. i guess unemployment/laid-off has one upside.

[SappySE107]

I only looked at A1 on tunerpro to see if I could compare with the 2E document and was surprised to see your name. I already closed tunerpro, put my book away, and am contemplating getting a beer. I really want to tune my car and I am close to putting a 9396 in there with DF code just to see what it does.

[robertisaar]

heres the entire dissasembly of 2E, its haunted me for quite some time. some of the tables don't describe the axis numbering, but thats about the only big issue. i imagine this is what the tunercat people used to create their definition.

[SappySE107]

I used to have this as well and once printed it off too. Could you make a .ads file with it? That would be a big step forward for me to see what my code is. I know it needs to be tuned as well but last I knew it was a QDMA error. I get a code on 2 ECMs (about to test a 3rd).

[robertisaar]

i could make an ADS with this(i think thats the only thing the first 19 pages are good for), but the DS file from ALDLStuff.zip from moates has a much easier to read version. shouldn't take me too long....

[robertisaar]

well, this is interesting:

the 94-95 3.4 PCM pushes out 2 datastreams, both with important data, but i don't think tunerpro V4 can get both to read at the same time. V5 might, but i can't guarantee it...

[SappySE107]

I once had efi-live setup with the 94-95 DOHC but lost the files. First I have heard of 2 datastreams but it sounds like I should just not bother and get a different car if I want to scan or tune.

[robertisaar]

I once had efi-live setup with the 94-95 DOHC but lost the files. First I have heard of 2 datastreams but it sounds like I should just not bother and get a different car if I want to scan or tune.

the 94-95 3100s have the same idea, but not with extremely important data on different streams...

this one has engine speed on stream 2, along with coolant temp, and a lot of the important statuses, like closed loop, TCC, and a few other things

interestingly enough, there is an option to use a 5 speed with $2E..... yet GM never utilized it from the factory...

EDIT: i just went over the 3100 stuff again, that actually has 5 streams... most of them are pretty pointless though, 1 main one, another for VIN, etc...