Can someone here look at my .uni file to diagnose a problem?
Can someone here look at my .uni file to diagnose a problem?
My laptop is dead but I still have the data file from last year when my problems started.
http://members.shaw.ca/fbody_god/Gripdiag1.uni
Note the timing, rpm dip, and knock count. Bad knock sensor? Bad MAP? Or bad PCM?
Only happens at idle. Car wants to constantly die. If I hold it at 1000 rpm or higher, it sounds normal. At idle it sounds like marbles in a tin can.
http://members.shaw.ca/fbody_god/Gripdiag1.uni
Note the timing, rpm dip, and knock count. Bad knock sensor? Bad MAP? Or bad PCM?
Only happens at idle. Car wants to constantly die. If I hold it at 1000 rpm or higher, it sounds normal. At idle it sounds like marbles in a tin can.
Re: Can someone here look at my .uni file to diagnose a problem?
Thanks for the ttop guide, I am loving my tops now.
When I open the file I get garbage, maybe I have a different version of DM.
When I had this problem though the sensor was bad.
Check the wire running down the pass fender to the KS. With headers that really likes to get hot.
My KS passed the test as listed on Shoeboxes site, but after rerunning the wire, and replacing the knock module in the pcm I decided to change it anyways.
Pretty easy to do, just have a bucket ready cause the coolant likes to rush out when you pull the sensor. Its cheap too.
Mine would constantly count knock and run pig rich. Rich enough to stall it at idle.
One thing that worries me is the sound though, if its really pinging then there could be something else wrong.....
When I open the file I get garbage, maybe I have a different version of DM.
When I had this problem though the sensor was bad.
Check the wire running down the pass fender to the KS. With headers that really likes to get hot.
My KS passed the test as listed on Shoeboxes site, but after rerunning the wire, and replacing the knock module in the pcm I decided to change it anyways.
Pretty easy to do, just have a bucket ready cause the coolant likes to rush out when you pull the sensor. Its cheap too.
Mine would constantly count knock and run pig rich. Rich enough to stall it at idle.
One thing that worries me is the sound though, if its really pinging then there could be something else wrong.....
Re: Can someone here look at my .uni file to diagnose a problem?
It pings at idle only but only at 500 rpm when its stalling.
You need a DM for 93s to read the file. I'll pick up a knock sensor and some wire today anyways.
You need a DM for 93s to read the file. I'll pick up a knock sensor and some wire today anyways.
Re: Can someone here look at my .uni file to diagnose a problem?
Re: Can someone here look at my .uni file to diagnose a problem?
Looks like your IAC is pegged at 160 at idle for most of the scan, adjust your throttle stop until that is around 40ish, then get the TPS sensor to read ~.5v at closed throttle. If you can get it to idle smoothly then it won't ever hit that 500rpm ping, and you certainly can't have your IAC stay like it is if you want a smooth idle.
Thread
Thread Starter
Forum
Replies
Last Post
NewsBot
2010 - 2015 Camaro News, Sightings, Pictures, and Multimedia
0
Mar 30, 2015 12:40 PM
NewsBot
2010 - 2015 Camaro News, Sightings, Pictures, and Multimedia
1
Mar 19, 2015 02:24 PM
NewsBot
2010 - 2015 Camaro News, Sightings, Pictures, and Multimedia
3
Mar 16, 2015 12:51 PM
NewsBot
2010 - 2015 Camaro News, Sightings, Pictures, and Multimedia
1
Mar 13, 2015 07:15 AM



