Which PID with E38 ecm to show 100% throttle position at WOT

[67SS509]

Currently using SAE.TP but it only shows 83 or 84% throttle at WOT. Tried GM.APP and GM.ETCTP today but they shut the logging down while either one were in the PID list.

[swingtan]

A quick search.....

http://forum.efilive.com/showthread.php?17634-Throttle-position-Pid

http://forum.efilive.com/showthread.php?16505-E38-Basic-Questions

http://forum.efilive.com/showthread.php?12321-Only-seeing-84-throttle



In summary.... Log GM.ETCTP and not SAE.TP

Simon.

[67SS509]

I did the search and found plenty of threads asking the same thing and pointers to the PID GM.ETCTP, but when I add it to the PID list and scan screen and start the logging nothing shows up including all the other things being scanned. It does show logging started but nothing shows up.

[ScarabEpic22]

Did you put your foot on the throttle and move it? Ive logged all 3 throttle PIDs at the same time to figure out exactly what each one does.

[67SS509]

Did you put your foot on the throttle and move it? Ive logged all 3 throttle PIDs at the same time to figure out exactly what each one does.

"but when I add it to the PID list and scan screen and start the logging nothing shows up including all the other things being scanned. It does show logging started but nothing shows up."

Seems more like a software malfunction to me.....V2 ailments?

[joecar]

You may need to install the latest software/firmware, and for BBx do Program All.

More info: Setting-up-a-FSV2-from-scratch (http://forum.efilive.com/showthread.php?20699-Setting-up-a-FSV2-from-scratch)

[67SS509]

You may need to install the latest software/firmware, and for BBx do Program All.

More info: Setting-up-a-FSV2-from-scratch (http://forum.efilive.com/showthread.php?20699-Setting-up-a-FSV2-from-scratch)

Will this eliminate the "pass thru logging" capability?

I'm on Build 211, Bootlock 2.07.04, Firmware 2.07.35

[ScarabEpic22]

Will this eliminate the "pass thru logging" capability?

I'm on Build 211, Bootlock 2.07.04, Firmware 2.07.35

No, there are no current issues regarding pass through. I believe you are referring to V8, which cannot do pass through yet.

Are you just logging or have you tried recording? The dashboards dont work unless you're recording.

[67SS509]

I always record.

[ScarabEpic22]

Weird, so if you have GM.ETCTP selected NONE of the PIDs return info while recording?

Id start with the latest RC1 software and firmware (must be programmed manually using EFILive Explorer) to see if that fixes it. Have you tried BBL'ing to see if it records?

[67SS509]

Weird, so if you have GM.ETCTP selected NONE of the PIDs return info while recording?

Id start with the latest RC1 software and firmware (must be programmed manually using EFILive Explorer) to see if that fixes it. Have you tried BBL'ing to see if it records?

That's correct, nothing records if GM.ETCTP is in the PID list. What are the advantages of the RC1 software (I'm assuming this is what Joecar referred to)

I have never tried BB logging, just too much for my little brain!

[joecar]

Can you post a log file.

[joecar]

When viewing a chart of the pids (where the waveform is not showing), righclick in the respective corner of the chart and re-choose the pid into that chart position, do this for all the pids not showing waveforms, then click the replot button.

[67SS509]

When viewing a chart of the pids (where the waveform is not showing), righclick in the respective corner of the chart and re-choose the pid into that chart position, do this for all the pids not showing waveforms, then click the replot button.

Quite often I have to "re-choose" a few pids in some of the chart positions when I first open a dashboard and it has a line thru the PID even though it's in the PID list. It doesn't help in this case.

Here is a log with the GM.ETCTP in the PID list and one without it.

14736

14737

[67SS509]

Everytime I have updated new wierd things happen to logging. In my above post the second log, which is after adding the latest updates several things are not working correctly. Commanded AFR has incorrect numbers, spark numbers are wrong and one of the mv readings for O2 won't follow. Someone please look at the log and tell me what's going on. Go to frame 4040

I'm looking at upgrading to the RC1 software but right now I'm afraid to try it without further understanding how to do it. It looks difficult for a "gearhead" like me without great computer skills like many of the people on here seem to have.

[joecar]

This is the second log, I'm viewing it using RC1 and it seems ok:

14760

[joecar]

Also, try logging SAE.LAMBDA and compare this to GM.AFRATIO_DMA.

[67SS509]

This is the second log, I'm viewing it using RC1 and it seems ok:

14760

Joecar, do one more thing please. Set your cursor on frame 4040 and post a screen shot of that. Also choose both O2 mv's
Your graph seems to be more condensed than mine from end to end, were is that setting located at?

[joecar]

Your log contains HO2S12 which is the O2S located at B1S2 (bank 1 rear).

14764

[joecar]

...
Your graph seems to be more condensed than mine from end to end, were is that setting located at?
Click the zoom all button (blue magnifier labelled "All").

Or click zoom minus button (blue magnifier labelled "-").

[67SS509]

Your log contains HO2S12 which is the O2S located at B1S2 (bank 1 rear).

14764

Yep....you win the prize on that one! Shame on me for that silly mistake.