12P TPS issue?

[Dave001]

Hey Everyone,
Just put an ecotec out of a VX into a 4runner, running an 082 ECU with 12p (OSE $12P V112 BLCD V6) on a homemade ds1230y - 100+ memcal, all seems to be working sweet, with the exception of one thing, the TPS is giving me weird results in Tuner Pro RT (using the OSE_$12PV112_1BAR - Petrol with calcVE.adx), as you can see from the log below, the TPS voltage is showing correctly, but the percentage just drops off at the 1.08min mark, at which point it logs a code 19 (TPS stuck).

Iv'e replaced the TPS, checked continuity on the wiring from the TPS to ECU, C14 has 5.01v, c13 has 1.4v at idle and 3.88v at WOT.

I'm guessing that the ECU doesn't actually give out the TPS% and it's calculated by the logging software from the TPS voltage, and this is just a software glitch, but thought I better find out for sure, before I continue tuning it.

Any help would be appreciated.

TPS Fault.xdl

Log

(533.63 KiB) Downloaded 249 times

[VL400]

The XDL you posted might be different to what you meant to post, there are no faults set in it.

[Dave001]

This is my first time tuning with Tuner Pro RT, so I'm probably doing something wrong mate.

Here's how I've been doing it.
Startup Tuner Pro RT, under Acquisition, choose Load Definition File, and choose "OSE_$12PV112_1BAR - Petrol with calcVE.adx", then again under Acquisition, choose Load Log File, and choose "TPS Fault.xdl"
Open up Item List, choose Mode1Message0, all MALFS are Clear, as soon as I press play, it shows Set DTC 19 - TPS Stuck.

Does that help to see where I'm going wrong?

Thanks.

[VL400]

Can you post the XDL from your screenshot in the first post?

The one you posted has the code set, but to work out what triggered it need a log of when the code is first set to look at the operating conditions.

[Dave001]

That is the XDL that I took that screen capture from, but I mustn't have reset the ECU before I took that log.

Just went back through some older logs, this one starts off with the code clear, then changes to Set at 1.22 min mark.

Log.xdl

(1.07 MiB) Downloaded 269 times

[VL400]

You will need to change the item "Malf 19 - Min Delta TPS Between Loops" to 1.17% and "Malf 19 - Max MAP for error condition" to around 50 kPa. Then if its still being set, which is likely, adjust the table "Malf 19 - Expected TPS vs RPM"

In the log you posted at the point the code was set, 40% TPS and 1900 RPM with 56kPa MAP. It started checking this code about 9.6 seconds earlier while idling (Malf 19 - Time Before Error Is Logged). The Malf 19 table has something close to 25% at the point the code was set. The table values need to be higher than operating values, but you dont want it being checked at high MAP values.

[vn5000]

In your first post you say tps voltage at idle is 1.4 volts , should be around half that at idle.

[Dave001]

You will need to change the item "Malf 19 - Min Delta TPS Between Loops" to 1.17% and "Malf 19 - Max MAP for error condition" to around 50 kPa. Then if its still being set, which is likely, adjust the table "Malf 19 - Expected TPS vs RPM"

In the log you posted at the point the code was set, 40% TPS and 1900 RPM with 56kPa MAP. It started checking this code about 9.6 seconds earlier while idling (Malf 19 - Time Before Error Is Logged). The Malf 19 table has something close to 25% at the point the code was set. The table values need to be higher than operating values, but you dont want it being checked at high MAP values.

Thank you very much VL400, that sorted it.
I had to crank it up quite a bit.

TPS vs RPM.jpg (27.77 KiB) Viewed 5612 times

Went for a nice long drive, and no error codes logged.
Thanks again mate,. I owe you one.

[Gareth]

I can't understand even on a modded engine why that would need to be adjusted? Is it not masking the real problem?

[vlad01]

I've never had to touch any of that on even a highly modified engine. There is some problem for sure.