firstfirebird

iTrader: (3)

CAUTION, USE AT OWN RISK!

Not much discussion here on $12p for the 808 ECM, figured a thread might be due, we can get some discussion going on it. Anyone else have success with it? I have found some old threads using the 808 masks, but not much on $12p.

Thanks to Six_Shooter for pointing me to the code mask!

I have a friend's Trans Am GTA at my shop with a 350TPI, cammed, larger runners/porting, headers, forged pistons, and would like to go with some additional atmospheric pressure later on. Rather than converting to a 7730, after much reading, figured if the Aussies are using it widely, why not try it? Been a minute (or maybe close to a decade?) since messing with the GM ECM's, but have been using TPRT and Ostrich for some time on BMW's that my shop caters to. In fact, have even been using TPRT to manipulate BMW OBD2 files, along with another piece of flashing software, and an OBD/USB cable to flash the ECU's. Seeing that the German Siemens has been thoroughly disassembled not sure why GM OBD2 market is cornered by a third party (HPTuners, which also familiar with), but that's another subject.

Here is a link to the download for the .bin for a TPI in a Toyota Landcruiser that I will be starting with (about half way down post #1):

https://pcmhacking.net/forums/viewtopic.php?f=7&t=375

Here's a link to a zip file that includes .xdf, .bin and .adx

https://pcmhacking.net/forums/viewtopic.php?f=27&t=356

My plan is to use the MAF wiring re-pinned to the MAP/IAT inputs and change the pigtail in the engine bay to suit. Install a wide band sensor/gauge and see if I can get this ill running car sorted for the man.

EDIT: Realized I can upload directly here vs making people follow links (thanks admins for making non photo extensions allowed):

OSE_12P V112.zip (adx, bin, xdf included)

350TPI landcruiser 12p v112.bin

So, this coming week we will be starting the conversion, wish me luck!

GeneralDisorder

iTrader: (1)

Eh - wouldn't it be easier (and certainly better) to go with an EBL Flash II? I mean considering your time to figure this out vs a plug in solution that's proven and would be running in 20 minutes.

GD

Six_Shooter

iTrader: (2)

This is still a quick setup, converts to speed density, using all OEM parts, inexpensive and works quite well, and is also a proven swap.

"Better" is subjective.

Also the EBL would require the same or possibly a little more repinning as this modification does, so the effort is about the same.

GeneralDisorder

iTrader: (1)

Same effort till you get to the tuning phase. Then the EBL pulls out in front.

Also it has a lot of features useful to this build if the plan is forced induction. And it has help for big cams, etc.

GD

firstfirebird

iTrader: (3)

"Figure it out" is a matter of moving the MAF pins on the ECM to the MAP locations, purchasing MAP/IAT sensors, and using an Ostrich so tuning on the fly is not an issue either. I can just burn a chip when happy with the results. Much like stated in this thread: https://www.thirdgen.org/forums/diy-...f-165-map.html, two re-pins, and removing six from the connector. Reversing it would even be very simple.

Tuning this "should" be a walk in the park compared to using Ostrich on my BMW clients - as there's no datalog/data stream (only Ostrich tracing in TPRT), no knock sensors, and some models even have variable camshaft timing. I have to use a dyno to find MBT (engines are NOT knock limited, power is lost before knock), and either a stand alone WB gauge, or use my LC-1 with a second window open on the laptop. Using the ALDL and a WB, everything will be handy on one screen in TP with thge '165 and $12p.

Just ordered a g2 adapter and some more chips. The $$ investment is less, and the time for installation will be similar.

Six_Shooter

iTrader: (2)

Tuning each one would be about the same, especially for someone with an emulator, which anyone that is into tuning GM ECMs should have anyway.

If you don't want to use $12p, that's fine, but there's no reason to try to **** on this thread from your lack of understanding why there are some of us that want to use the unmodified OEM ECM and and sometimes a different code.

$12P supports 1, 2 and 3 BAR MAP sensors, so forced induction is very doable, it also has programmable I/O based on what ever input or calculation you want.

So please, unless you're going to add anything useful to the thread, just click that back button, M-kay?

GeneralDisorder

iTrader: (1)

I was merely mentioning it as an option. The 7165 is not the most reliable piece of hardware. Regardless of ease of tuning it would not be my choice. Availability of ECM's is getting poor and besides their tendency to disconnect in 8192 mode, the circuit boards like to crack. I do understand the appeal of the $12P though since it's essentially free.

GD

mikeceli

iTrader: (2)

Question. My Actron scanner sometimes displays text like " $12p" or other text, containing a dollar sign. I have no idea what that means. Anyone?

GeneralDisorder

iTrader: (1)

The "$" is used in many programming languages, including the assembly code used in the GM ECM's, to represent a number given in Hexadecimal (base 16). In this case that means the PROM ID will be a hexadecimal value of 12. The P is misleading as that is not a hex "digit" (only A-F are hex digits). The P stands for "Pro" as this is a custom modified $12 code that's been named "$12 Pro" or just $12P for short.

What your Actron scanner means by $12p is anyone's guess because AFAIK that character string can't be found in any PROM ID or other data stream on a GM ECU. By normal assembly language convention it's not valid. It's just what people call this particular modified BIN file.

GD

mikeceli

iTrader: (2)

I only used $12p" as an example. My Actron sometimes displays $ Something, which means nothing to me. Thanks.

Six_Shooter

iTrader: (2)

Using $12P, the high speed datalink is rock solid. The issue there is the coding, not the ECM. IIRC there was some hack that the coders used to get a higher data rate than 8192, or just doubled up on certain parameters per set of data sent out. Either way, it's solid and fast.

mikeceli: When that shows up, it means that the information doesn't have a key to decode it to be readable in units humans understand. In HEX code a "$" is a signifier for the beginning of that value. "0x" is another indication of HEX, I.E.: "0x3B"

GeneralDisorder

iTrader: (1)

If that's true, it's really sad that GM never fixed that code bug across $32, $32b, and $6e. I had assumed they must have been unable to fix it due to hardware limitations. Guess they were just lazy.

GD

Makeitreal81

So I see others have done similar stuff. I just went through your post. How did this work out? Also if I noticed inputs for the wide band o2 is that just for data logging or can the ecu use it instead of the narrow band?