Zeroing the TPS signal

[Juan]

I'm sure this is going to be just the first of many posts I make as I wrap my head around learning to tune this TCU, so ill keep it short and sweet. I'm having trouble zeroing the TPS signal.

AEM infinity ecu, CAN 3,
DBW, 13
TPS 13
still reads 5% with the foot off, included a screenshot, suggestions?

tps.PNG

[M4comp]

In TunerPro do you have 'Use DBW to Automatic calculations' checked?

In TunerPro use Ctrl-F, make sure you set the Find parameters to 'Any Parameter' in the left box and the right box is 'With This Phrase in the Title'
Type dbw for the search Word and hit enter.

Look through the list for 'Use DBW to Automatic calculations'. Confirm this is not checked.

If this is not checked, have a look at your AEM software and confirm the PPS is not at 5%.


If the PPS in NOT at 5%, turn the 'DBW Input' in TunerPro to OFF ( set to 0 )

[Juan]

thanks for taking a look, not much luck I'm afraid; the two APP signals are <.2% and the dbw auto calculation setting was off. I tried both ways just to see but the tps remains at 5%

dbwautocalc.PNG

apps.PNG

[Juan]

to add: seems to me that the turbolamik is reading the wrong byte

5c8c1d61feb836cf26ac3d546e2244a0.png

looks like byte 3 instead of 0, reading the actual throttle value instead of the pedal position, is there a way to edit this in tunerpro, or would i need an updated .dbc from turbolamik?
or am I simply misunderstanding that we want the APP signal instead of the true throttle signal?

[M4comp]

The Lamiki uses the PPS or APS (pedal position sensors) because it is modeled around the OEM torque request strategy. In other words, when you press the pedal, you are requesting more torque, and the PCM responds by delivering as much as it can to meet that request.

If you have the TPS input set to 13 and the DBW input disabled, yet it still shows 5%, and then switching the DBW input to 13 causes no change, that does indicate something isn’t behaving correctly.

Typically, enabling DBW input with a non-zeroed TPS will cause the system to interpret the lowest value as 0%. This happens because the DBW throttle motor is active and not physically at 0%—if it were fully closed, the engine wouldn’t be able to idle.

If you’ve confirmed that the ECU software is not showing 5% TPS, and the TCU is showing a proper range (whether 0–100% or 5–100%), then implementing a custom CAN solution could be a viable approach.

Also, just to confirm—your TunerPro file may not have been saved or uploaded. Please reopen TunerPro and read the tune directly from the TCU to verify that the changes you made were actually written. Keep in mind that modifying values alone does not update the tune; each change must be explicitly uploaded to the device for every edit.

[Juan]

I feel like tunerpro is gas lighting me into thinking I'm crazy, take a look at this screenshot: both the TPS and DBW signals should be disabled, but it's still receiving a 5% TPS signal from somewhere. It really does feel like my changes aren't committing, but the floppy disk symbol in each window doesn't have an up arrow over it and the values aren't red so this should mean the changes are committed and saved to the bin right? Am I crazy? As for the PPS signal, there's definitely 2 pps readings in the top left of the screenshot I posted of my aem tuner software, both at 0-0.1%

zerotps.PNG

[Juan]

nevermind, false alarm, it was in fact just having trouble changing the value and writing to the TCU, so I did manage to set it to 0 and lose TPS signal, which is good i guess, shows that my changes are doing something.
I set it back to 13 TPS and 13 dbw and I'm back to square 1, stuck at 5%