P1514 trouble code and reduced engine power

[dillonnottingham]

My first post ever after having Hptuners for over a year, I hope someone can help me solve this issue!

I have tuned the truck from stock to now using the search function on this forum and thus never had the need to post. Every problem i have had has been resolved on this forum and it is always full of helpful information. That being said i have searched thoroughly, and though this topic has been covered i did not find a solution to the problem.

I have an 03 silverado ss, it has the p59 ecu. It has a turbo 408ci with cam, worked heads, and quite a bit more, it has a built trans, and really has been a fun vehicle to own and upgrade. Recently I went with a more efficient precision turbo, and used hptuners 2 bar OS vcm enhancement. i have been having the issue of a "reduced engine power" message coming onto my display, and a p1514 code coming into my DTC codes. this signifies that the amount of airflow and the tps sensor readings do not match, and that the engine is flowing too much air for the amount that the throttle body is opening. After reading some literature on this forum, i found some info saying to enlarge the values in the p1514 table in Hptuners, i have adjusted little by little with no success, and even completely maxed all the values in the table to 4.1, and i am still having the same problem. Other literature on hptuners forums says that i will need to scale my VE and IFR tables to overcome this issue, but i am at a standstill, if i need to do the scaling, what is the proper procedure? and will i need to scale other tables as well, including but not limited to my trans tables? I am not able to tune or drive about 4000 rpm because that is when this issue happens, and it happens every time. I have attached a copy of my tune in case you wanted to have a look.I have also attached a log file, and you can see where this happens at the very end of the log (my apologies for the 12 minute log time, i was logging afr error for the VE table) when the truck hit 3904rpm and almost 50% tps, but notice the cylinder airmass is at 2.34g even though i have the table in the tune maxed out to 4.1g. it happens at this rpm no matter how much throttle is applied. Thank you for your time, and i would genuinely appreciate any help that is given.

2 Bar SD tuning december 2017.hpt
REP message.hpl

[EErock]

SORRY FOR THE LONG POST. Hi. Your first post and my first reply. Even though this is 2 years old, I wanted to add some info. Why, because I've spent an enormous amount of time searching for help and following a post/thread only to have it either just suddenly end, or turn into an argument, or turn into some other topic, etc. I have been posting on LS1tech regarding my ride. I've made a lot of changes to it and it sits in my garage. Now, your issue. I don't know what you have tried, I am no tuning expert, but I can tell you what I have come across. P1514 was just one of my Engine DTC codes. I also had P0068,P0121,P2101,P0101,P0106. After trying to ignore these codes while trying to tune my ride(2004 Silverado 5.3) including my newly rebuilt transmission, I finally wised up a little maybe and went back to the basics. I began to check all of my electrical connections and vacuum hoses, thinking just maybe I messed up something when I was rebuilding the top end of the motor, or when I installed the Trans. This same day, this clicking noise that I had been hearing for a while became louder. When I turned my key on, there was a click. It got much louder. I had someone turn the key on for me, so I could check it out. It led me to the TPS on the side of my throttle body. (Fuel injected). I previously had counted out the possibility of this being the TPS, because it was the second one I had purchased in a year. I figured frikin Dorman junk. What I found was both a disappointment and a relief, a glimpse of hope for me . The throttle body was messed up. Something in the gear mechanism under the TPS.The butterfly/throttle plate was not working correctly. It smelled of fuel big time. Most of my codes, even the transmission code P1870, could possibly be because of this? The P1514 along with the other codes is most likely the cause of my Transmission code P1870 because they caused misfires. Misfires can cause a P1870. I have a new throttle body on the way. I recently replaced the Throttle actuator, the brain behind the TPS. Expensive, and wasn't the fix, even though DTC codes led me that way. My own fault for not doing electrical tests on it. I tested accelerator pedal sensors, found they were ok, purchased the actuator, and here I am now, waiting on the throttle body, which I know is shot. I will follow up by posting the outcome. I hope this helps someone and does not mislead anyone. This is my story behind the P1514 and I by no means am trying to tell you this is your problem too. But maybe it's worth checking into should this kind of thing happen to you? CyA

[Mcpimpin]

Did the new throttle body work ? I'm having same issue lol

[blindsquirrel]

You can start your own thread, it's free. Not likely to get a reply from other one-posters from seven and five years ago.

[dillonnottingham]

Someone messaged me asking if I found a solution to this problem, and I had completely forgotten that I made this post.

I talked to about 2 dozen people looking for a solution, which was as follows:

-I had to scale the entire map by 0.5, as I was hitting the hard limit of the oem MAF sensor (I believe this is 511g/s, iirc, but it has been a number of years). I remember finding a video on how to do this, i believe it was from sloppy mechanics on youtube, i cant find that video now, so here is another that is about the same topic. I did not watch it in its entirety, but it should help get anyone needing a solution to this same problem on the right track.

https://youtu.be/xO_b8T6d_nI?si=q5NaNIHI8Qg7vmqz

[edcmat-l1]

You don't have to scale anything on 99.9% of the vehicles out there. There is a P1514 table in the diagnostic section. Max that table (for forced induction) and multiplying x2 usually will cure anything NA.

[InandOutPerfromance]

I know this thread is super old but i just had to resolve this problem on a ss silverado this week. Back story, customer had a whipple on his truck and upgraded to a
LSA blower setup and had to change the map sensor to the 3 bar that was stock on LSA blower. So he went through the tune file and did all the related scaling on the
the required tables. Set it up for speed density and broke out the iat from the maf and mounted it in the blower. Well after getting everything buttoned up he fired it up
and after a bout a minute truck goes into reduced power and cuts off.

Only codes were obviously the failed maf and p1514. So after trying a couple things and failing I got my computer and mpvi3 out and hooked to it. While watching the log
I noticed that the second the truck went into closed loop is when it died. So it got me thinking. What was happening while in open loop truck was running on default but as
soon as it went closed loop it started looking for feedback it saw the map sensor was out of range and it didnt know where it was in the ve table. Set code and died. So for those
that are in speed density and see this code, look into you map sensor, chances are you'll find your issue.

[gtstorey]

I know this thread is super old but i just had to resolve this problem on a ss silverado this week. Back story, customer had a whipple on his truck and upgraded to a
LSA blower setup and had to change the map sensor to the 3 bar that was stock on LSA blower. So he went through the tune file and did all the related scaling on the
the required tables. Set it up for speed density and broke out the iat from the maf and mounted it in the blower. Well after getting everything buttoned up he fired it up
and after a bout a minute truck goes into reduced power and cuts off.

Only codes were obviously the failed maf and p1514. So after trying a couple things and failing I got my computer and mpvi3 out and hooked to it. While watching the log
I noticed that the second the truck went into closed loop is when it died. So it got me thinking. What was happening while in open loop truck was running on default but as
soon as it went closed loop it started looking for feedback it saw the map sensor was out of range and it didnt know where it was in the ve table. Set code and died. So for those
that are in speed density and see this code, look into you map sensor, chances are you'll find your issue.

So did you "tune it" or just turn the code off?

[edcmat-l1]

I know this thread is super old but i just had to resolve this problem on a ss silverado this week. Back story, customer had a whipple on his truck and upgraded to a
LSA blower setup and had to change the map sensor to the 3 bar that was stock on LSA blower. So he went through the tune file and did all the related scaling on the
the required tables. Set it up for speed density and broke out the iat from the maf and mounted it in the blower. Well after getting everything buttoned up he fired it up
and after a bout a minute truck goes into reduced power and cuts off.

Only codes were obviously the failed maf and p1514. So after trying a couple things and failing I got my computer and mpvi3 out and hooked to it. While watching the log
I noticed that the second the truck went into closed loop is when it died. So it got me thinking. What was happening while in open loop truck was running on default but as
soon as it went closed loop it started looking for feedback it saw the map sensor was out of range and it didnt know where it was in the ve table. Set code and died. So for those
that are in speed density and see this code, look into you map sensor, chances are you'll find your issue.

You don't have to scale anything on 99.9% of the vehicles out there. There is a P1514 table in the diagnostic section. Max that table (for forced induction) and multiplying x2 usually will cure anything NA.

Perhaps you missed this post ^^^^

[bk2life]

Someone messaged me asking if I found a solution to this problem

me...it was me finding you on youtube

glad you came in for the update

[edcmat-l1]

I love it when guys come here to announce to the tooning world that they've finally solved an issue that's not been an issue for 20 years.

[InandOutPerfromance]

I fixed the wiring on the map sensor and fixed it. Not tune nor turn off.

[InandOutPerfromance]

Perhaps you missed this post ^^^^

That had nothing to do with the root problem. Doing that will bandaid it. I had a physical issue. Never tune around those

[InandOutPerfromance]

I love it when guys come here to announce to the tooning world that they've finally solved an issue that's not been an issue for 20 years.

Also if it hasnt been a problem for 20 years as you say. Why did a customer bring me it this week?

[edcmat-l1]

That had nothing to do with the root problem. Doing that will bandaid it. I had a physical issue. Never tune around those

In a forced induction application running speed density IT HAS to be done. It's not a band-aid. You can't get around it in that specific application.

Additionally, in a modified NA application running it speed density that table HAS TO BE modified or again, it will trip that code. It's not a band-aid.

[edcmat-l1]

That had nothing to do with the root problem. Doing that will bandaid it. I had a physical issue. Never tune around those

In that application it is absolutely the root problem.

[edcmat-l1]

I know this thread is super old but i just had to resolve this problem on a ss silverado this week. Back story, customer had a whipple on his truck and upgraded to a
LSA blower setup and had to change the map sensor to the 3 bar that was stock on LSA blower. So he went through the tune file and did all the related scaling on the
the required tables. Set it up for speed density and broke out the iat from the maf and mounted it in the blower. Well after getting everything buttoned up he fired it up
and after a bout a minute truck goes into reduced power and cuts off.

Only codes were obviously the failed maf and p1514. So after trying a couple things and failing I got my computer and mpvi3 out and hooked to it. While watching the log
I noticed that the second the truck went into closed loop is when it died. So it got me thinking. What was happening while in open loop truck was running on default but as
soon as it went closed loop it started looking for feedback it saw the map sensor was out of range and it didnt know where it was in the ve table. Set code and died. So for those
that are in speed density and see this code, look into you map sensor, chances are you'll find your issue.

What does "look into your map sensor" mean? What exactly did you do to "fix" it? If the linear and offset were wrong and you fixed them, it would still set a P1514 if that table is left stock and you're running it in speed density. But since you didn't describe exactly what you did to fix it and haven't posted the tune file and before and after logs I'll assume that the P1514 table is NOT left stock in this vehicle. Because it can't be. That or you're actually in MAF mode and don't realize it.

[edcmat-l1]

Actually the more I think about it there is one way you could set that up to not trip that specific code while running a forced induction setup in speed density. You could scale it so bad it thinks it's pumping less air than it would in stock form. So how about post up the tune file and accompanying data log so we can see how you "fixed" this so it could run on the stock P1514 table.

[InandOutPerfromance]

What does "look into your map sensor" mean? What exactly did you do to "fix" it? If the linear and offset were wrong and you fixed them, it would still set a P1514 if that table is left stock and you're running it in speed density. But since you didn't describe exactly what you did to fix it and haven't posted the tune file and before and after logs I'll assume that the P1514 table is NOT left stock in this vehicle. Because it can't be. That or you're actually in MAF mode and don't realize it.

When i was referring to look into your map sensor i was actually saying to look into the actual functioning of it. Like is it is range or does it have some sort of circuit code.
The fix was that the sensor itself was out of range. Not the tune nor scaling of the tables. "Sometimes" we get lost in the "tune" and forget parts fail. Then we get lost
in fixing problems with the tune instead of the hard parts them selves. Hence the " look into your map sensor". Specifically speaking while in speed density.

Because the map is the only way the pcm is able to account for the air model and yes i am positive it was in speed density because i proved my theory by putting it
in to maf blend and the code went away. Basically giving the pcm a way to measure air. At that point i focused on the map sensor and found it faulty. I guess i wasnt
very clear on my fix, my bad. Just trying to help anyone coming across this type issue, and offering my resolution. I know your way beyond me in this "tooning" thing,
but there is no need in those type of comments. If you wanna help, AWESOME!! If not, well there is always the keep quite option. Appreciate the response.

[edcmat-l1]

When i was referring to look into your map sensor i was actually saying to look into the actual functioning of it. Like is it is range or does it have some sort of circuit code.
The fix was that the sensor itself was out of range. Not the tune nor scaling of the tables. "Sometimes" we get lost in the "tune" and forget parts fail. Then we get lost
in fixing problems with the tune instead of the hard parts them selves. Hence the " look into your map sensor". Specifically speaking while in speed density.

Because the map is the only way the pcm is able to account for the air model and yes i am positive it was in speed density because i proved my theory by putting it
in to maf blend and the code went away. Basically giving the pcm a way to measure air. At that point i focused on the map sensor and found it faulty. I guess i wasnt
very clear on my fix, my bad. Just trying to help anyone coming across this type issue, and offering my resolution. I know your way beyond me in this "tooning" thing,
but there is no need in those type of comments. If you wanna help, AWESOME!! If not, well there is always the keep quite option. Appreciate the response.

You're still not being very clear about your "fix". How was it "out of range"? HOW did you fix it? I'm telling you that in a forced induction setup you HAVE to increase the P1514 table because YOU WILL EXCEED THE AIRFLOW THAT CAUSES IT TO TRIP THAT CODE. Raising that table is not a band-aid. You are incorrect in that statement. Why won't you post the tune and data log to go with it?

Don't try to tell me what I'm saying isn't correct and not post a tune and data log to back up your incorrect statements.

That had nothing to do with the root problem. Doing that will bandaid it. I had a physical issue. Never tune around those

In case you're wondering why I'm hounding you on this, it's this post right here. You're telling me modifying the P1514 table is a band-aid in this application. I'm telling you you're wrong.