8.0 Doesn't care about misfires?
#1
8.0 Doesn't care about misfires?
98 Ram 2500 4x4 with the 8.0. Engine is all stock, as is the computer. Had some issues a while back with misfires, so, had the plugs and wires replaced. That solved the problem, temporarily...... Now the issue is back, and I have a dead miss on at least one cylinder, however, no check engine lite, no misfire code, and neither the Autel, or Launch scanners will show me misfire counters. There simply is no option for it..... (both scanners are the several hundred dollar versions... though I can't say I am impressed with 'em. VERY slow to do ANYTHING......) So, question becomes, does the 8.0 PCM even CARE about misfires????? I want to see which cylinder(s?) the PCM thinks are problematic, (there are, after all, 10 of them....... ) and then dig into WHY said cylinders are dead..... Seems like figgering out which ones though, isn't gonna be easy.
#2
Again, I asked about misfire counts a few days ago and you said it was an OBD-II thing. I know that, but I also mentioned I had started a thread about this previously and 2nd Gen misfire counts are difficult to access.
According to my previous thread, only SnapOn, OTC or OEM dealer-level scanners will get you misfire counts on these trucks:
https://dodgeforum.com/forum/2nd-gen...d-surging.html
I've acquired an old Modis and haven't tried for misfire counts (I also never got around to trying my brick as mentioned in the thread above), but the Modis pulls 2nd Gen 4WABS codes and RABS codes, so I'm optimistic. RABS codes from a '98:
According to my previous thread, only SnapOn, OTC or OEM dealer-level scanners will get you misfire counts on these trucks:
https://dodgeforum.com/forum/2nd-gen...d-surging.html
I've acquired an old Modis and haven't tried for misfire counts (I also never got around to trying my brick as mentioned in the thread above), but the Modis pulls 2nd Gen 4WABS codes and RABS codes, so I'm optimistic. RABS codes from a '98:
#3
I once tried to pull RABS codes for my '96 Ram 2500 using the Snap-On MT-2500 (red brick) scanner and was not able to do so. That year is the 1st year for OBD-2 for that truck, so the MT-2500 doesn't have me plug up the truck's OBD-1 connector to access the RABS codes. I think I may have to tell the scanner that the truck is a later year and it may then be able to access those codes through the OBD-1 connector, as I haven't tried that path yet..
#5
I haven't pulled any yet...... I had the work done at a local shop...... (as I couldn't even get the plugs to break loose..... think they had been in there a while. ) I may take it back to them, see what they can figger out. I was hoping it would be 'easy' with a scanner.... but, not so lucky.
#6
I haven't pulled any yet...... I had the work done at a local shop...... (as I couldn't even get the plugs to break loose..... think they had been in there a while. ) I may take it back to them, see what they can figger out. I was hoping it would be 'easy' with a scanner.... but, not so lucky.
#7
Trending Topics
#8
Usually you can contact their tech support directly and ask if their product will do "X".
#9
I'm only guessing that some of the tablet-style Xtool, TOPDON and Launch offerings are every bit as powerful as SnapOn. OTOH I'm not sure how much they're focusing on relatively obscure PIDs from trucks that are now at least 22 years old.
Usually you can contact their tech support directly and ask if their product will do "X".
Usually you can contact their tech support directly and ask if their product will do "X".
#10
Misfire detection is iffy on the V10 because it relies on the crank slowing down ever so slightly causing the crank position sensor signal to be uneven. With more cylinders the effect becomes less noticeable.
The OBD2 implementation on the 2nd gens is an afterthought and only the bare minimum to be compliant. It also runs over a very low speed 1 wire communication protocol. For more detailed info a scantool needs to talk on the CCD bus which many newer products don't bother to implement because the vehicles are now 20+ years old and are disappearing fast. Misfire counters are not required for OBD2 and I know on my truck I need to use a vintage OTC tool to see them.
The OBD2 implementation on the 2nd gens is an afterthought and only the bare minimum to be compliant. It also runs over a very low speed 1 wire communication protocol. For more detailed info a scantool needs to talk on the CCD bus which many newer products don't bother to implement because the vehicles are now 20+ years old and are disappearing fast. Misfire counters are not required for OBD2 and I know on my truck I need to use a vintage OTC tool to see them.
The following 2 users liked this post by DerTruck:
Jimythefan (11-15-2023),
Keith_L (11-13-2023)