Bad running Z-28
#1
Bad running Z-28
Hi! I wonder if anyone can take a look of my logs?
It all started with a bad waterpump, I changed the pump, and it was all fine. About 3 days later I took it for a run, and it didn´t feel right when I started it up, bad throttle respons, and when it heated up it sometimes backfired.
Oh well, the opti wasn´t new and the waterpump hade been leaking, so I changed that. No changes.
So, I got myself a cable and made this log.
And another thing, after this log, I tried to start the engine again, then the heaterfan started, and i couldn´t connect to the PCM
https://www.bredbandsbolaget.se/port.../Camaro%20Log/
It all started with a bad waterpump, I changed the pump, and it was all fine. About 3 days later I took it for a run, and it didn´t feel right when I started it up, bad throttle respons, and when it heated up it sometimes backfired.
Oh well, the opti wasn´t new and the waterpump hade been leaking, so I changed that. No changes.
So, I got myself a cable and made this log.
And another thing, after this log, I tried to start the engine again, then the heaterfan started, and i couldn´t connect to the PCM
https://www.bredbandsbolaget.se/port.../Camaro%20Log/
#2
Re: Bad running Z-28
Downloaded the .csv file. Could you reformat it with decimal points rather than commas? The .csv file cannot be mathematically manipulated in Excel, at least without changing the Excel settings.
Have you seen this? Much better scanning software:
https://www.camaroz28.com/forums/com...95-lt1-874306/
I'll try downloading the .uni file in the meantime.
Have you seen this? Much better scanning software:
https://www.camaroz28.com/forums/com...95-lt1-874306/
I'll try downloading the .uni file in the meantime.
#3
Re: Bad running Z-28
OK. Tried downloading the .uni file and it opened as a bunch or symbols, letters, etc. Not usable.
�îô�@J��R¸Åµä@ô„������ý��77ž@€����ý��F��� �€S��>/@�`�•����������������������������������������� �����
#4
Re: Bad running Z-28
Thanks for your time.
I uploaded a Excel file in the link above.
I haven´t tried Scan 9495, I will give it a try, will it work with the serial interface cable?
Edit: Spelling..
I uploaded a Excel file in the link above.
I haven´t tried Scan 9495, I will give it a try, will it work with the serial interface cable?
Downloaded the .csv file. Could you reformat it with decimal points rather than commas? The .csv file cannot be mathematically manipulated in Excel, at least without changing the Excel settings.
Have you seen this? Much better scanning software:
https://www.camaroz28.com/forums/com...95-lt1-874306/
I'll try downloading the .uni file in the meantime.
Have you seen this? Much better scanning software:
https://www.camaroz28.com/forums/com...95-lt1-874306/
I'll try downloading the .uni file in the meantime.
Edit: Spelling..
Last edited by Jonas Ohman; 02-10-2016 at 05:32 AM.
#5
Re: Bad running Z-28
You need to add mass air flow (g/sec), and system voltage. See below for recommended fields for exporting data.
The throttle % and volts are jumping all over the place, opening and closing and opening again in fractions of a second. For example, at record 2709 the throttle is 0%. Withing 0.50 second, it increases to 64%, then closes immediately, stays closed for the next 0.50 second, then increases to 57% over the next 0.50 second. The speed and the RPM are doing the same. Were you actually driving like that? The data seems almost impossible.
In record 2786 it's standing still. In the next 0.117 second, it is moving at 11 KPH. In the next 0.118 second it is moving as 19 KPH. And 0.117 second later it is standing still again. Log would appear to be corrupt.
At idle, throttle closed, 0 KPH the PCM should be operating in fuel trim cell 16. It isn't. It's in Cell 4, then it's in Cell 1. At idle, in Cell #4 the left long term fuel trim (LTFT) is adding 20% extra fuel. At the same time time the right LTFT is subtracting 3% of the normal fuel. In the same area, the left O2 stays at an extremely rich 900+ millivolts for 1.855 seconds. Should be switching rapidly back and forth between 0xx - 9xx millivolts.
I just don't have enough confidence in the validity of this data to spend any more time on it. Maybe you could clear things up.
I'll have to get GaryDoug to answer your question on the serial cable.
TTS DATAMSTER RECOMMENDED EXPORT FIELDS:
1. Runtime
2. RPM
3. MPH
4. TPS – Volts
5. TPS - %
6. MAP (kPa)
7. CLT Temp (Degrees F)
8. IA Temp (Degrees F)
9. IGN Volts
10. IAC Position
11. AFGS
12. SPARK ADV
13. SPARK RETARD
14. KNOCK COUNT
15. Injector BPW – Left
16. Injector BPW – Right
17. Fuel Trim Cell
18. Left O2
19. Right O2
20. Long Term – L
21. Long Term – R
22. Short Term – L
23. Short Term – R
24. CCP Duty Cycle
25. EGR Duty Cycle
26. Barometer
27. IAC Target
28. Idle RPM
29. Injector Duty Cycle – L
30. Injector Duty Cycle - R
The throttle % and volts are jumping all over the place, opening and closing and opening again in fractions of a second. For example, at record 2709 the throttle is 0%. Withing 0.50 second, it increases to 64%, then closes immediately, stays closed for the next 0.50 second, then increases to 57% over the next 0.50 second. The speed and the RPM are doing the same. Were you actually driving like that? The data seems almost impossible.
In record 2786 it's standing still. In the next 0.117 second, it is moving at 11 KPH. In the next 0.118 second it is moving as 19 KPH. And 0.117 second later it is standing still again. Log would appear to be corrupt.
At idle, throttle closed, 0 KPH the PCM should be operating in fuel trim cell 16. It isn't. It's in Cell 4, then it's in Cell 1. At idle, in Cell #4 the left long term fuel trim (LTFT) is adding 20% extra fuel. At the same time time the right LTFT is subtracting 3% of the normal fuel. In the same area, the left O2 stays at an extremely rich 900+ millivolts for 1.855 seconds. Should be switching rapidly back and forth between 0xx - 9xx millivolts.
I just don't have enough confidence in the validity of this data to spend any more time on it. Maybe you could clear things up.
I'll have to get GaryDoug to answer your question on the serial cable.
TTS DATAMSTER RECOMMENDED EXPORT FIELDS:
1. Runtime
2. RPM
3. MPH
4. TPS – Volts
5. TPS - %
6. MAP (kPa)
7. CLT Temp (Degrees F)
8. IA Temp (Degrees F)
9. IGN Volts
10. IAC Position
11. AFGS
12. SPARK ADV
13. SPARK RETARD
14. KNOCK COUNT
15. Injector BPW – Left
16. Injector BPW – Right
17. Fuel Trim Cell
18. Left O2
19. Right O2
20. Long Term – L
21. Long Term – R
22. Short Term – L
23. Short Term – R
24. CCP Duty Cycle
25. EGR Duty Cycle
26. Barometer
27. IAC Target
28. Idle RPM
29. Injector Duty Cycle – L
30. Injector Duty Cycle - R
#6
Re: Bad running Z-28
Ok, thanks for the feedback. I wasnt even driving the car, since I live in Sweden its cold and too much snow :-)
I accelly think its the PCM thats the problem.
I went to the garage yesterday, to get another scan, but the car won´t even start. Below is a link to a short video of whats happening.
https://www.bredbandsbolaget.se/port...Camaro%20Misc/
When the engine dies, both heater fans starts.
I tried to connect to the PCM, but when I turn the key, Datamaster just shortly connects, then starts the fans, and the connection dies. I did make a try with Scan 9495, but I am not sure if it works anyway with my interface.
I checked the connections on the PCM, I have seen some pictures of bad connections, but it´s all good.
So, where do I continue, is there some sure way to rule out the PCM?
//Jonas
I accelly think its the PCM thats the problem.
I went to the garage yesterday, to get another scan, but the car won´t even start. Below is a link to a short video of whats happening.
https://www.bredbandsbolaget.se/port...Camaro%20Misc/
When the engine dies, both heater fans starts.
I tried to connect to the PCM, but when I turn the key, Datamaster just shortly connects, then starts the fans, and the connection dies. I did make a try with Scan 9495, but I am not sure if it works anyway with my interface.
I checked the connections on the PCM, I have seen some pictures of bad connections, but it´s all good.
So, where do I continue, is there some sure way to rule out the PCM?
//Jonas
You need to add mass air flow (g/sec), and system voltage. See below for recommended fields for exporting data.
The throttle % and volts are jumping all over the place, opening and closing and opening again in fractions of a second. For example, at record 2709 the throttle is 0%. Withing 0.50 second, it increases to 64%, then closes immediately, stays closed for the next 0.50 second, then increases to 57% over the next 0.50 second. The speed and the RPM are doing the same. Were you actually driving like that? The data seems almost impossible.
In record 2786 it's standing still. In the next 0.117 second, it is moving at 11 KPH. In the next 0.118 second it is moving as 19 KPH. And 0.117 second later it is standing still again. Log would appear to be corrupt.
At idle, throttle closed, 0 KPH the PCM should be operating in fuel trim cell 16. It isn't. It's in Cell 4, then it's in Cell 1. At idle, in Cell #4 the left long term fuel trim (LTFT) is adding 20% extra fuel. At the same time time the right LTFT is subtracting 3% of the normal fuel. In the same area, the left O2 stays at an extremely rich 900+ millivolts for 1.855 seconds. Should be switching rapidly back and forth between 0xx - 9xx millivolts.
I just don't have enough confidence in the validity of this data to spend any more time on it. Maybe you could clear things up.
The throttle % and volts are jumping all over the place, opening and closing and opening again in fractions of a second. For example, at record 2709 the throttle is 0%. Withing 0.50 second, it increases to 64%, then closes immediately, stays closed for the next 0.50 second, then increases to 57% over the next 0.50 second. The speed and the RPM are doing the same. Were you actually driving like that? The data seems almost impossible.
In record 2786 it's standing still. In the next 0.117 second, it is moving at 11 KPH. In the next 0.118 second it is moving as 19 KPH. And 0.117 second later it is standing still again. Log would appear to be corrupt.
At idle, throttle closed, 0 KPH the PCM should be operating in fuel trim cell 16. It isn't. It's in Cell 4, then it's in Cell 1. At idle, in Cell #4 the left long term fuel trim (LTFT) is adding 20% extra fuel. At the same time time the right LTFT is subtracting 3% of the normal fuel. In the same area, the left O2 stays at an extremely rich 900+ millivolts for 1.855 seconds. Should be switching rapidly back and forth between 0xx - 9xx millivolts.
I just don't have enough confidence in the validity of this data to spend any more time on it. Maybe you could clear things up.
#7
Prominent Member
Join Date: Jul 2010
Location: Born on the Florida West Coast, now where can I retire?
Posts: 1,505
Re: Bad running Z-28
Any cable that works for Datamaster will work for Scan9495. Make sure any jumper that is on the cable is removed.
What is that Innovate Motorsports device in the video? Is it attached while you are scanning? If so, disconnect it.
Scan9495 is indicating that the pcm is not responding. That may be due to a conflict with the Innovate device.
What is that Innovate Motorsports device in the video? Is it attached while you are scanning? If so, disconnect it.
Scan9495 is indicating that the pcm is not responding. That may be due to a conflict with the Innovate device.
Last edited by GaryDoug; 02-15-2016 at 11:39 AM.
#8
Re: Bad running Z-28
Any cable that works for Datamaster will work for Scan9495. Make sure any jumper that is on the cable is removed.
What is that Innovate Motorsports device in the video? Is it attached while you are scanning? If so, disconnect it.
Scan9495 is indicating that the pcm is not responding. That may be due to a conflict with the Innovate device.
What is that Innovate Motorsports device in the video? Is it attached while you are scanning? If so, disconnect it.
Scan9495 is indicating that the pcm is not responding. That may be due to a conflict with the Innovate device.
Good to know about Scan9495, I will use that in the future
#9
Re: Bad running Z-28
Ok, so now the car starts atleast, bud it still runs bad, tryed to run some more logs, but it still seems to be corrupt, posts them anyway. It´s one log with Scan9495 and one with EEHacks.
Any suggestions on why they becoms corrupt?
https://afonline-my.sharepoint.com/p...4dc86a18ffb07b
https://afonline-my.sharepoint.com/p...b9c6e03434fcca
Any suggestions on why they becoms corrupt?
https://afonline-my.sharepoint.com/p...4dc86a18ffb07b
https://afonline-my.sharepoint.com/p...b9c6e03434fcca
#10
Prominent Member
Join Date: Jul 2010
Location: Born on the Florida West Coast, now where can I retire?
Posts: 1,505
Re: Bad running Z-28
They are corrupt because your pc is using commas in the number separators instead of periods. Temporarily change the pc setting to English.
#11
Re: Bad running Z-28
The setting is already english. But when i scan it drops the connection now and then, maybe that corrupts the file?
Attached is a video of a scan.
https://afonline-my.sharepoint.com/p...b2433b27748d19
Attached is a video of a scan.
https://afonline-my.sharepoint.com/p...b2433b27748d19
#12
Prominent Member
Join Date: Jul 2010
Location: Born on the Florida West Coast, now where can I retire?
Posts: 1,505
Re: Bad running Z-28
On the pc Control Panel: Click on Region, then on the Formats tab, click on Additional Settings. On the Numbers tab, change the Decimal symbol to a dot. Right now it is a comma and that messes up the log file since it uses the comma to separate values.
Last edited by GaryDoug; 05-21-2016 at 09:53 AM.
#14
Re: Bad running Z-28
So, I finaly managed to make a log, thanks GaryDoug!
It would be nice if someone could look at it.
https://afonline-my.sharepoint.com/p...558151afd69bfa
It would be nice if someone could look at it.
https://afonline-my.sharepoint.com/p...558151afd69bfa
#15
Prominent Member
Join Date: Jul 2010
Location: Born on the Florida West Coast, now where can I retire?
Posts: 1,505
Re: Bad running Z-28
There are a lot of errors in the log file. That could be due to a defective ground somewhere, which could cause the engine problems also. The log file frequently shows 25 volts as the battery voltage, which is wrong.
Thread
Thread Starter
Forum
Replies
Last Post