Help us help you. By posting the year, make, model and engine near the beginning of your help request, followed by the symptoms (no start, high idle, misfire etc.) Along with any prevalent Diagnostic Trouble Codes, aka DTCs, other forum members will be able to help you get to a solution more quickly and easily!

2000 Jeep 4.0. Multiple cylinder misfire

  • Tootalltocare
  • Tootalltocare's Avatar Topic Author
  • Offline
  • New Member
  • New Member
More
8 years 5 months ago #14103 by Tootalltocare
2000 Jeep 4.0. Multiple cylinder misfire was created by Tootalltocare
Need map sensor wave patterns .

Please Log in or Create an account to join the conversation.

More
8 years 5 months ago #14111 by EricGoodrich
Replied by EricGoodrich on topic 2000 Jeep 4.0. Multiple cylinder misfire
iatn subscription gives access to thousands of both good and bad waveforms. Also, when you buy a Picoscope you get a bunch of good and bad waveforms. Buying from autonerdz gets you even more. A quick Google search can give you information about how to test a map sensor and even show you what you'd expect to see in a waveform.

Generally a map sensor will run off a 5 volt reference with near 0v or 5v at 0in or 30in. Confirm power/ground circuits, confirm baro/map correlation koeo, confirm map signal by open/short, gradual sweep with intake pressure change. Map sensors don't necessarily have a consistent waveform, not compared to something like a crank sensor anyway.
The following user(s) said Thank You: Tootalltocare

Please Log in or Create an account to join the conversation.

More
8 years 5 months ago #14145 by Andy.MacFadyen
Replied by Andy.MacFadyen on topic 2000 Jeep 4.0. Multiple cylinder misfire
Usually I find the best of way of checking MAP sensors is OBD2 live data, also if the map sensor is out it will show up first as a fuel trim DTC

" We're trying to plug a hole in the universe, what are you doing ?. "
(Walter Bishop Fringe TV show)



The following user(s) said Thank You: Tootalltocare

Please Log in or Create an account to join the conversation.

Time to create page: 0.232 seconds