Has anyone else ran into this? My factory tach reads fine. My snap-on scanner reads fine. but the gauge or list isnt showing any rpm reading.
Has anyone else ran into this? My factory tach reads fine. My snap-on scanner reads fine. but the gauge or list isnt showing any rpm reading.
Are you logging RPM in the Table(primary) display? If not, start there.
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
Yes. I made sure it was there. and it isnt showing either.
ok, post your scanner log.
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
You aren't logging it. Start by logging engine speed(rpm) and everything else will fall into place.
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
Engine rpm ( sae) is selected.
Not from what I can see.
It doesn't have to be perfect, it just needs to be done in two weeks...
A wise man once said "google it"
from that can you tell why this freakin TM is kicking my butt?? lol. whatever changes ive made feel great in the mid to upper rpms. and the shifts feel better. but from a dig its still fully active.
If you are logging Engine RPM (SAE) then you need to select the Engine RPM (SAE) PID in the gauge and chart displays for them to work, the default for the gauge and chart are the RPM sensor, the other way around it is to log the RPM (sensor) instead of Engine RPM (SAE), they are two different things.
2010 GXP Maloo ute, LS3, 6L80E.
MM heads, 240/252@50 solid cam, 12.75:1 compression, 4500 Dominator converter, 3.46 rears.
Shooting for 10s eventually.
gotcha. i will see what i can do about it this morning.
Yep i have that there. and as i was driving it wasnt logging.
I'm having the exact same problem as the OP. I can clearly see that Engine RPM SAE is selected in my chart and it's got a column in the logs accordingly but it's full of 0s. It wasn't doing this earlier but since I had to fix a couple of other parameters that weren't logging properly, now engine speed isn't working, causing all my histograms to collapse to single columns.
Disregard. I found out what the problem is.
If the memory used to log the variables (not store the logs) is full and you add another variable to track, it'll add but won't actually log. I had deleted RPM, added a bunch of crap and then added RPM back. Since RPM was the last thing I added and the mem was full, it didn't log. When I blew everything away (including RPM) and then added RPM back it started logging again.
Reply With Quote