pcmhacking.net

I have a 1987 Pontiac Fiero with a Cadillac Northstar 4.6 engine. I built the engine myself with 11.5 CP pistons, ceramic/moly coatings, Eagle rods, gapless rings, MLS gaskets and a few other tricks.
I have a GM 09354896 ECU (1999-2000 LS1 applications) with the program from a 1999 Shelby Series 1. This car uses the Olds Aurora 4.0 engine, which is the same as the Northstar except for bore and valve size. The Caddy/Olds engine requires a special program because it uses a unique trigger wheel and a DIS waste spark ignition.
HPTuners can tune the combo. For that suite it shows up as a "1999 Oldsmobile Shelby". I had a local dyno shop rough-in the tune for me so I can drive it on the street. I’m trying to use Torque to log data for fine tuning, but I’m having a couple of odd problems.
The first is that the O2 sensor voltages don’t log. I select sensor 1 voltages from Bank 1 and Bank 2 for logging, but when I open the logs (as .csv), those columns are all zeroes.
The second is that Knock Retard (KR) is not available for logging. I looked at the “add PID” capability in Torque, but it looks like I need the address of the PID in the data stream… I’m not sure how to get that info.
I’m using the OBDLinkMX bluetooth gateway. It’s really a bus gateway, as all it does is transfer data from the bluetooth bus to the OBD bus.

Thoughts?
Thanks!

You can load the adx from here in tunerpro https://pcmhacking.net/forums/viewtopi ... =10&t=2314 and check out some of the gm enhanced pids it uses there. Let us know if they work.

Thanks!

I downloaded the .ADX, and looked at it in notepad. I see the blocks defining the various data items. I downloaded TunerPro also, but I don't see how to load the .ADX or where to find the .ADX editor from which I see screenshots.

It looks like this is some of the info I need:
<ADXVALUE id="GM KNOCK" idhash="0x319621D6" title="GM KNOCK DEG">
<flags>0x00000004</flags>
<parentcmdidhash>0x17DE5E7A</parentcmdidhash>
<units>DEG KNOCK</units>
<packetoffset>0x00</packetoffset>
<range low="0.000000" high="27.000000" />
<alarms low="0.000000" high="1.000000" />
<digcount>2</digcount>
<outputtype>3</outputtype>
<MATH equation="X">
<VAR varID="X" type="native" />
</MATH>
</ADXVALUE>

<ADXVALUE id="GKD" idhash="0xCD33759B" title="GM KNOCK DETECT">
<parentcmdidhash>0xEC4881A8</parentcmdidhash>
<packetoffset>0x00</packetoffset>
<range low="0.000000" high="255.000000" />
<alarms low="0.000000" high="255.000000" />
<digcount>2</digcount>
<outputtype>3</outputtype>
<MATH equation="X">
<VAR varID="X" type="native" />
</MATH>
</ADXVALUE>

<ADXCLISTENPACKET id="KNOCK RX" idhash="0x17DE5E7A" title="GM KNOCK RX" flags="0x00000001">
<listentimeout>400</listentimeout>
<packetbodylength>1</packetbodylength>
<packetoffsetinbody>0</packetoffsetinbody>
<packetsize>1</packetsize>
<headerstring size="8">08006CF1106211A6</headerstring>
</ADXCLISTENPACKET>

<ADXCSENDCOMMAND id="KNOCK TX" idhash="0x17DC1A7A" title="GM KNOCK TX">
<bytestring size="0x8">076C10F12211A601</bytestring>
</ADXCSENDCOMMAND>

<ADXCLISTENPACKET id="GMKD RX" idhash="0xEC4881A8" title="GM KNOCK DET RX" flags="0x00000001">
<listentimeout>400</listentimeout>
<packetbodylength>1</packetbodylength>
<packetoffsetinbody>0</packetoffsetinbody>
<packetsize>1</packetsize>
<headerstring size="8">08006CF110621106</headerstring>
</ADXCLISTENPACKET>

<ADXCSENDCOMMAND id="GMKD TX" idhash="0xEC4AC5A8" title="GM KNOCK DET TX">
<bytestring size="0x8">076C10F122110601</bytestring>
</ADXCSENDCOMMAND>

in tunerpo v5 use the acquisition menu then load definition file to load the adx

then to edit it you can either use the icon on the menu the blue and grey gears to edit or the edit definition option under the acquisition menu.