A place to discuss hardware/software and diagnostic procedures
Problems with crankshaft frequency waveform
- Farseer
-
Topic Author
- Offline
- Senior Member
-
Less
More
- Posts: 40
- Thank you received: 5
1 week 3 days ago - 1 week 2 days ago #92828
by Farseer
Problems with crankshaft frequency waveform was created by Farseer
Hi, everyone.
I've lately been learning how to incorporate exhaust pulse and crankshaft frequency testing in order to identify misfires.
Getting more and more American imports here in Poland, so it's become useful with all those V6s and V8s with coils under the intakes.
Anyhow, as much as I think I have figured out using exhaust pulses, I cannot, for the life of me, manage obtaining a usable crankshaft frequency!
I was wondering am I doing somehting wrong or is my scope my limiting factor? I'm using a Picoscope 2204a with 100 MS/s.
If I use a longer timebase, the frequency waveform comes out... spikey.
What gives? No amount of playing with the frequency base changes anything, it's still unusable. Changing the sample rate achieves nothing either.
Wrong scope? I know the 2204a isn't listed as an automotive scope, but it's still used by many with successful results.
The second attached picture shows the "best" I could get at 10ms/div but it's still too little data. You can see a slight suggestion of a downward slope. Any more timebase and it's spikey.
P.S. what do you guys like using to identify "fishbite" style misfires? The kind sthat appear only once in a while, but a very sensitive driver might pick up? I've heard that the crankshaft method isn;t as accurate then. Apparently, an exhaust pulse would be better.
I've lately been learning how to incorporate exhaust pulse and crankshaft frequency testing in order to identify misfires.
Getting more and more American imports here in Poland, so it's become useful with all those V6s and V8s with coils under the intakes.
Anyhow, as much as I think I have figured out using exhaust pulses, I cannot, for the life of me, manage obtaining a usable crankshaft frequency!
I was wondering am I doing somehting wrong or is my scope my limiting factor? I'm using a Picoscope 2204a with 100 MS/s.
If I use a longer timebase, the frequency waveform comes out... spikey.
What gives? No amount of playing with the frequency base changes anything, it's still unusable. Changing the sample rate achieves nothing either.
Wrong scope? I know the 2204a isn't listed as an automotive scope, but it's still used by many with successful results.
The second attached picture shows the "best" I could get at 10ms/div but it's still too little data. You can see a slight suggestion of a downward slope. Any more timebase and it's spikey.
P.S. what do you guys like using to identify "fishbite" style misfires? The kind sthat appear only once in a while, but a very sensitive driver might pick up? I've heard that the crankshaft method isn;t as accurate then. Apparently, an exhaust pulse would be better.
Last edit: 1 week 2 days ago by Farseer.
Please Log in or Create an account to join the conversation.
- Chad
-
- Offline
- Moderator
-
- I am not a parts changer.
Less
More
- Posts: 2173
- Thank you received: 727
2 days 20 hours ago #92847
by Chad
"Knowledge is a weapon. Arm yourself, well, before going to do battle."
"Understanding a question is half an answer."
I have learned more by being wrong, than I have by being right.
Replied by Chad on topic Problems with crankshaft frequency waveform
My apologies for the late response. I have been on vacation.
Crankshaft frequency is my preferred method of identifying fish-bite misfires.
Post a screen-shot of the whole screen so that we can see your channel settings.
Crankshaft frequency is my preferred method of identifying fish-bite misfires.
Post a screen-shot of the whole screen so that we can see your channel settings.
"Knowledge is a weapon. Arm yourself, well, before going to do battle."
"Understanding a question is half an answer."
I have learned more by being wrong, than I have by being right.
Please Log in or Create an account to join the conversation.
Time to create page: 0.284 seconds