Why are my LTFTs sticking at -100%?

Have I accidentally disabled them somehow (I didn't mean to if I did). They were logging normally, but then something recently switched to this behavior (same config file while logging).

Did you try stopping the log & restarting? Did/does the problem go away?

I have seen what you are seeing but it's usually before I start the car.

It's been in every log I've done the last couple of weeks, whether I start logging before or after starting the car.

Try deleting that PID and while connected, not logging, re-insert the LTFT PID you desire. This solves that problem most of the time for me. It comes about when switching cars (OS's or platforms), now I have seperate config's for those situations. :)

Just out of curiosity, what car and ECM is this?

What HPT version are you running? Did you upgrade to .18?

Reason for asking is that I've have been unable to get the scanner to properly log of number of things under .18 with my E67 ECM that worked fine previously. HPT is aware of this issue and says they're working on it.

Just a shot in the dark that may possibly apply.

It's an 07 NBS Silverado, 6L. I believe that's an E67 ECM - so maybe it's the same issue.

I'm not totally positive that it started at the same time that I upgraded to .18, but it was pretty close - so maybe that's the issue.

I haven't had a chance to try 12secSS's suggestion yet.

Try backing up a version for the time being for now if you have the E67 ECM.

Also, don't forget to sent support @ hptuners dot com and email to let them know of this issue.

For me it's been over 2-1/2 weeks after sending many files and a "we're working on it" response with no resolution to date.

With the headaches I've had with compatibility on my car, I don't know how they can claim that they "support" it with HPT. They've been helpful so far, but my frustration level is building for sure.

I have the same issue on my 98 Camaro PCM w/ the newest version of HP Tuners. I've been playing with PIDs to try and resolve the issue. If that doesn't solve it I'm just going to step back a version and try that.