PCM Diagnostics & Tuning HP Tuners | Holley | Diablo

5.3 ls random codes after possible overheating

Old Sep 9, 2022 | 07:31 PM
  #1  
KyleKetterhagen's Avatar
Thread Starter
Staging Lane
 
Joined: Apr 2022
Posts: 81
Likes: 5
Default 5.3 ls random codes after possible overheating

So I have a 1979 firebird swap and the other day I took out my car for it’s first drive and I believe it wouldn’t over heat but I think I was wrong. I believe my engine may have overheated and now I have several codes. I was driving and it just started sputtering and died

I have
po300
po327
po332
po154

+

po650 (this is just an engine light I think and I have to hook it up eventually, I had this before test drive)

any suggestions on what do do?
Reply
Old Sep 10, 2022 | 07:40 AM
  #2  
Old Buzzard's Avatar
TECH Fanatic
15 Year Member
Liked
Loved
Community Favorite
 
Joined: Jan 2009
Posts: 1,053
Likes: 470
From: Bostwick, GA.
Default

Sounds like you have multiple electrical issues;
Knok sensors, O2 sensor inop.
I'd start with a wiring system check up.
Reply
Old Sep 10, 2022 | 09:05 AM
  #3  
KyleKetterhagen's Avatar
Thread Starter
Staging Lane
 
Joined: Apr 2022
Posts: 81
Likes: 5
Default

Yeah everything is freshly rebuilt so did a few wires just get burnt and ground out?
Reply
Old Sep 10, 2022 | 03:02 PM
  #4  
B52bombardier1's Avatar
TECH Fanatic
5 Year Member
Liked
Loved
Community Favorite
 
Joined: Dec 2017
Posts: 1,461
Likes: 265
From: Bossier City, Louisiana
Default

Feel the various pieces of wire insulation with your hands to see if it got melted. Do the codes clear if you clear them or do they return?

Use an infrared temperature gun to see if it REALLY IS hot in the engine around the temperature sending unit - whichever port on the head you have chosen. On my LS engine, my temperature actually is hotter at the passenger side rear head port than the driver's side front port by usually 15-20 degrees - as seen on my PCM parameter stream data and my Dakota Digital temperature gauge -- and crosschecked with an infrared thermometer.

Run a PCM parameter stream on your OBD2 data and see if your O2 sensors are responding and if your Long and Short Term Fuel Trim data looks reasonable. Reasonable for me is plus or minus 10%.

Rick
Reply
Old Sep 10, 2022 | 06:56 PM
  #5  
KyleKetterhagen's Avatar
Thread Starter
Staging Lane
 
Joined: Apr 2022
Posts: 81
Likes: 5
Default

None of my wires look nor feel as if they’ve been burned. The only ones I can’t see are my knock sensors. I also don’t have anything to look at obd 2 parameters, I will try deleting the codes to see if they go away tomorrow when I have more time.
Reply
Old Sep 12, 2022 | 08:50 PM
  #6  
KyleKetterhagen's Avatar
Thread Starter
Staging Lane
 
Joined: Apr 2022
Posts: 81
Likes: 5
Default

Yeah I deleted the codes and they came back so it’s got to be something electrical, I’m gonna check over all my spark wires and plugs then start tracing from there
Reply
Old Sep 14, 2022 | 06:55 PM
  #7  
KyleKetterhagen's Avatar
Thread Starter
Staging Lane
 
Joined: Apr 2022
Posts: 81
Likes: 5
Default

Ok so I replaced my knock sensors and everything seems fine right now. All my codes went away and I think what was happening was my knock sensors got over torqued or maybe they were just cheapos from Amazon but they were causing timing to be messed up so it cause the po300 (random misfire) which then led to my o2 sensors throwing a code.

will update in a couple of days to see if anything changed, if I forget then that means everything is good

thank you!!!
Reply


Thread Tools
Search this Thread

All times are GMT -5. The time now is 06:13 AM.