TPS% value 1227747 ADX

I've been working on the 1227747 ADX and can't get the TPS% to display correctly. When I looked at other ADX files the TPS voltage and TPS percent were 2 differant hex address. This seems to be why none of the conversions work properly in the 1227747 ADX because both the TPS voltage and TPS Percent are from the same addrress.

Since there are settings in 7747 XDF based off TPS% I thought this should be a working item in the ADX.

Does anyone have correct info to put into 7747 ADX for TPS%? Or learn me how to?

I could never get it to work correctly using just a conversion, so I learned to live with it "being close."

I had wanted to set up a look up table for TPS percent, but never got around to it (a round tuit?), since I rarely use a '7747 anymore. The last one I installed and tuned was in my bosses '62 Suburban, and the only reason I used it over a '7427, is because I had experienced idle issues with a '7427 and non e-tranny in another conversion. I didn't want to have to figure out why on my bosses truck. I believe I have since figured out the issue, but have no real way to test anymore.

I guess if I had a $42 hack and learned who to dissasemble, then comment, then... I've been avoiding that for years because it's already done on everything. Wonder if you could find the TPS% in the XDF?

You don't need to go that far... I don't think it would help you at all to disassemble the BIN, to work on an ADX...

You can create a look up table, and link it in the ADX, it just may take some testing to determine how the look up table should be set-up.

You can also look at the ALDL datastrem def. It's on Moates in a zip file that contains all or just about all OBD1 GM datastreams.

We have them all here to.
http://www.gearhead-efi.com/gearhead-efi/

Didn't you get my PM about adding this to the GM Bins and stuff how to use forum?



LO5 for the 5.7L is A033 but I've never done a lookup table. Maybe we better learn since Robert went on vacation?

//--------------------------------------------------------------------------------------// Created by TunerPro. Hand editing is *not* recommended or supported.//--------------------------------------------------------------------------------------//--------------------------------------------------------------------------------------//--------------------------------- HEADER ------------------------------------//--------------------------------------------------------------------------------------{ fDefFrmtVers =1.21; strDefVersion =Version 1.0; strDefTitle =A033; strAuthor =Robert Saar; strEngine =4.3/5.0/5.7; strYear =86-88; strVINCode =Z/H/K; strCodeMask =?; strComments =check A033.ADS for specific details. robertisaar@yahoo.com for comments/questions.; iBaud =160; dwFlags =0x00000000; dwCSID =0x00013AE7; btNumDumpRequests =1; strCommandName =160 Baud; rgbtCommand =; iTotalBytesInCommand =0; bChecksumCommand =0; iNumBytesInPayload =20; iNumBytesBeforePayload =-1; bMaster =1; bMonitor =1; iChainTo =-1;}//--------------------------------------------------------------------------------------//---------------------------------- DASH -------------------------------------//--------------------------------------------------------------------------------------{ dwItemType =6; strItemComments =<Comments>; bSeparator =0; bVisible =1; dwUniqueID =0; btNumGauges =6; strIDsDisplayed =0,0,0,0,0,0,; btNumMonitors =4; strMonsDisplayed =0,0,0,0,;}//--------------------------------------------------------------------------------------//--------------------------------- VALUES ------------------------------------//--------------------------------------------------------------------------------------{ dwItemType =1; strItemComments =<Comments>; bSeparator =0; bVisible =1; dwUniqueID =9; btByteNumber =2; btMessageNumber =1; dwItemSizeBits =16; dwOperation =3; dFactor =1.000000; dOffset =0.000000; strItemTitle =PROM ID; strUnitLabel =; dwAlarmHigh =255; bAlarmHighENable =0; dwAlarmLow =0; bAlarmLowEnable =0; iRangeHigh =255; iRangeLow =0; iLookupTableIndex =-1;}{ dwItemType =1; strItemComments =<Comments>; bSeparator =0; bVisible =1; dwUniqueID =10; btByteNumber =4; btMessageNumber =1; dwItemSizeBits =8; dwOperation =3; dFactor =1.000000; dOffset =0.000000; strItemTitle =IAC Position; strUnitLabel =Steps; dwAlarmHigh =255; bAlarmHighENable ;}

I deleted the rest...

I went through that A033 file and didn't see anything for TPS% but it did have some more information I added to the 7747 ADX I am working on.

Have you ever got a conversion to work from kpa to vacuum?

No, again a look up table would likely work best. ;)

Never did figure out how to use the lookup table. But I did spend hours reading old DIY-EFI threads, also found the TPS% on 1227747 has always been an eqation from the TPS voltage, other ECM ADX had a seperate datastream address for voltage and percent.

What was getting to me was there is no way to set some paremeters even close to percent value? With the eqaution my TPS was showing .67, little high but well within guidlines for 125K. At that voltage my TPS% was 13.3% so I'm guessing it may go as low as 13% at .54. Then I spent some time looking through all the XDF written for the 1227747 and comparing them to origanal ALDL datastreams and found the problem!!!! Some of the parameters in the XDF for TPS are voltage but in the XDF they had been commented as %. No wonder I could never get them close...

So I spent about 15 hours over 2 days and went through all the XDFs and ADS and ALDL information. There are now new $42-1227747-V2.xdf and $42-1227747-V2.adx in the 1227747 ECM information thread without conflicting information.

Some were obvious voltage and some were obvious percentage some I had no concrete evedence on so I did not list voltage or percent but when you look you can see the TPS setting of 25 to 75 is never going to be voltage because the highest voltage possible is 5.0. Others have readings of 1.95 which is well within the relm of TPS voltage and never going to be close to the minimum 13% in the equation. Now it all makes sense.

Anyway the new ADX in list view gives sensor information needed for tuning and troublshooting on one page, then theres a Malfunction list for checking error codes on another page. Also several dashboards all work, one extra starter dashboard for anyone wanting to start one of their own. Monitors are set to be easily read for tuning and watching recorded data. BLM history table was re-made to match VE fueling and match Daves VE tuner. Knock counter can be matched to spark table but I left it up to 6200 RPM IIRC so you can watch for knock way beyond spark tables. It's the ADX we started on a year ago and I have been tweaking it since every time I use it. Hope those that use it enjoy.

Kinda strange I was reading up on the new SMT8 Piggy Back tuner because of the other thread, it's a new unit I have not used yet.

One of the questions was:
Why does my throttle position start at 14% and end at 85%
on the SMT8 piggy-back?

Answer was:
This is because the voltage of your throttle position starts at 0.7 volts and
ends on 4.25 volts. If your tps voltage starts at 0 volts and ends at 5.0 volts
then the range would be 0% to 100%.

This was on an Import car but the voltages are pretty close to GM and validates what I found in the equation and test results of doing my 1227747.

I actually just started my '7747 to '7427 swap into my truck so I don't really have things set up to check this out but I think it should work.

I looked through a $42 hac, and found that the datastream is commanded at LD4F5 to output the TPS volts located at L0048 while running. As I looked further I noticed that for running calculations the "current TPS Value" in the code is loaded from L0049. Now I have done this type of thing with my $0E.ads to output different things than the original datastream was told to and it's not so hard. So what I do is take some obscure data like 02 cross counts and replace it with something useful, in this case TPS%. The easy way to change it, and make it easily reversible is as follows.

Create another .xdf parameter, label it as something like "TPS % instead of 02crosscounts"
In the parameter box set the address to 0x50B, size 2 bytes, output type hex. This is the spot where the .bin tells the ecm where to look for the data to spit out in the datastream.
In the comments area write "Change this setting from $00BA (O2 cross counts) to $0049 (TPS%)"

Now add a .adx value with the same packet offset as the o2 cross counts but title it TPS%. This way you can have both TPS Volts and % if you like.
Unfortunately there is nothing in the .bin to tell us what the conversion is for this data, but it stands to reason it will be the normal "X*.392157".

If anybody tries this let us know how it works.

Well you had me lost in the hex, I really need a beginner lesson there. Maybe someday this winter someone could do a beginner course?

But I didn't have to anything in XDF or hex. I made another ADX value, it was identical to TPS Voltage address but renamed TPS %. It worked so you can have more than one output from same address in the adx file. Then I changed the range from 0.000000 to 5.000000 to 0.000000 100.000000 used the calculation "X*.392157". found in other adx files for TPS % like you said and it works.

So I tried again with coolant temp. Duplicated the adx value, changed some settings in TP and now there is coolant temp in Celsius and Fahrenheit.

One thing I don't understand in adx is why some things are just set to Native and conversion is just X while others are set to Native X and need a conversion calculation?

The only thing I don't like about the idea of making a % directly from the voltage is the the fact that there is a minimum TPS voltage right? Somewhere around .5 volts? I was under the impression that the ECM looks at this voltage at startup and sets this voltage as 0% TPS. If this is the case then the while idling, the ECM sees 0% TPS, but the datastream shows 10%TPS. Right? I guess you could adjust the bottom end of the range to take up for that though.

Yeah but it figures correctly to every paremeter in the mask (XDF), couple posts up even Perfect Power Piggy Back Tuners have the same issue.

But your point may be valid on ECM that have a seperate address for TPS%. 1227747 does not. Actually if you hook up a ScanTool there is no TPS%, but there is when you deal with others like the 97427 and my LT1. I've spent a lot of time with the 1227747 and what your saying won't ever come into play. Settings are mostly off TPS Voltage and low end of that. Ones that involve percent are so high it would never be close to TPS Voltage even if you subtracted what your saying.

Well actually what I meant was if you make a conversion for that as follows:
0.00V = 0% TPS
0.05V = 1%
0.10V = 2%
~~~~~
0.55V = 11%
0.60V = 12%
~~~~~
5.00V = 100%

Then for instance at idle the TPS sensor is reading .56 volts, this is what the ECM sees. But your .adx would show (0.55V) 11%. Right? That can be worked around but.......

somewhere in the '7747 there has to be a conversion written to put out a %TPS, there are tables and constants that are defined as %TPS in a column or row. So somewhere in the bin there is a conversion already. It is just matter of feeding it out through the data stream.

For instance:

HTML Code:

---

;
; CK FOR LOW TPS ERR TEST ENABLE
;
D6D8: LDAA LD50D ; ERR ENABLE WD 1
D6DB: BITA #$04 ; b2, ERR 22, TPS lo
D6DD: BEQ LD6F8 ; BR IF NOT b2
; ... else
D6DF: LDAA L0048 ; TPS, VDC
D6E1: CMPA LD523 ; TPS limit, 0.20 VCD, (ERR 22)
D6E4: BCC LD6F8 ; IF TPS > .195 BR
; ... else

---

So here, as the code is running when it reaches D6DF the instruction is LDAA L0048 which to paraphrase "load from register A L0048" ; comment says TPS, VDC, this is also the register that the datastream spits out TPS Volts from.

HTML Code:

---

F0FF: LDAA L001A ; RPM/25
F101: ASLA
F102: BCC LF106
; ... else
F104: LDAA #255
F106: LF106 BRA LF120
F108: LF108 LDAA L0049 ; CURRENT TPS VALUE
F10A: LF10A PSHA

---

Now here is a portion of the TCC routine. Here at line F108, the instruction is again LDAA but this time it is "from register L0049" ; and is commented TPS Value.

My point is there are many references to TPS% in both of the hacs, and the .xdf posted here. It is just a matter of getting that value to be put in the data stream.

But for me to do that I have a lot of catching up to do in hacs and hex and dissambly, that is something I have never done yet! Even you have spent time and can only find reference of TPS to volts (VDC). Now if I can figure out how to use the lookup table and make a graph I could do exactly what you explained.

I'm trying to spend time working on ADX files now, to improve what we have, convert them to adx and get the layouts in a more user freindly work space. That is how this topic came up. I realy wish someone would do a starter course on hex, hacks dissasembly, commneting etc... so we could all understand how you do what you just did above. Maybe if I start a topic people will jump in and get it going like this one did?

Quote:

---

My point is there are many references to TPS% in both of the hacs, and the .xdf posted here. It is just a matter of getting that value to be put in the data stream.

---

What I was trying to tell you ealier is the hacs are wrong, well probably just the commenting! They mention a TPS paremeter as % and it is not! It is volts. The only paremeters in the 1227747 hacs/xdf/mask that mention TPS% have values of 25% or better which can not be volts. Well within the range of the origanal conversion for %. If you look at old XDF you will see them. I made a new XDF and took out reference to % where it was volts.