Craziest problem ever
Professional
Joined: Oct 2018
Posts: 157
Likes: 3
From: New Hampshire(NH)
I've been working on vehicles for most of my life. Started when I was 14.... I am going to be 61 here in a few short weeks. 
I haven't always done it for a living, but, as I generally couldn't afford to pay someone else to work on my stuff..... I had to learn how to deal with the various and sundry problems that would crop up. It has been extremely rare that I have owned a vehicle that was built in the same decade that I owned it. Most were more than 15 years old. Some more than 20...... So yeah, I got a LOT of practice sorting through interesting problems. Learned a lot over the years.
I was at a Mensa event in St. Louis a bunch years back, and there I met an engineer that worked on GM engine design. That was an eyebrow raising revelation. I told him "I know a lot of folks that would like to kill you." He was shocked! "But, WHY????" And I pointed out stupid things like have to drop an engine cradle to change a water pump, as one bolt was so long, you couldn't get it out otherwise. Or the various parts that were extremely common failures, but were buried DEEP in the engine compartment, to the point that you had to disassemble half the car, to change a 20 dollar part. Or the fact that on the 'new' engines, changing the dern sparkplugs was 4 hours according to the Labor Time guide. That's just stupid....... I don't think our chat had any effect on how he designed engines though, witness the early 90's LT5 motor, with the starter buried under the intake manifold..... Yeah, that was a brilliant idea........
What's really depressing though, is I can usually sort out the problems of a fuel injected V-8 engine, that has more computer power than the entire Apollo program, but, a single-cylinder 2 cycle engine? I haven't gotta clue.
I haven't always done it for a living, but, as I generally couldn't afford to pay someone else to work on my stuff..... I had to learn how to deal with the various and sundry problems that would crop up. It has been extremely rare that I have owned a vehicle that was built in the same decade that I owned it. Most were more than 15 years old. Some more than 20...... So yeah, I got a LOT of practice sorting through interesting problems. Learned a lot over the years.I was at a Mensa event in St. Louis a bunch years back, and there I met an engineer that worked on GM engine design. That was an eyebrow raising revelation. I told him "I know a lot of folks that would like to kill you." He was shocked! "But, WHY????" And I pointed out stupid things like have to drop an engine cradle to change a water pump, as one bolt was so long, you couldn't get it out otherwise. Or the various parts that were extremely common failures, but were buried DEEP in the engine compartment, to the point that you had to disassemble half the car, to change a 20 dollar part. Or the fact that on the 'new' engines, changing the dern sparkplugs was 4 hours according to the Labor Time guide. That's just stupid....... I don't think our chat had any effect on how he designed engines though, witness the early 90's LT5 motor, with the starter buried under the intake manifold..... Yeah, that was a brilliant idea........
What's really depressing though, is I can usually sort out the problems of a fuel injected V-8 engine, that has more computer power than the entire Apollo program, but, a single-cylinder 2 cycle engine? I haven't gotta clue.
Getting nowhere
Well, I've gotten nowhere. Bypassed splices for map sensor direct to PCM circuit. Wired map direct with spades to rule out the connector. Only codes I get are 107 and 1296 shortly thereafter. Both map codes from what I can tell. I don't know why originally a search of code 1296 came up as TPS...
I've changed the map three times since summer to no avail. Wondering about my soup canned exhaust, if it's messing with the o2 sensors. I don't think so because it did run great for a week like this.
Is there a way to rule out the o2 sensors?
At this point otherwise all I can think is:
- bad connector plug at PCM
- plenum gasket ( vacuum tests fine, but I see oil residue in throttle body)
Going to the dealer tomorrow morning. This will be the fourth shop, also to no avail.
I've changed the map three times since summer to no avail. Wondering about my soup canned exhaust, if it's messing with the o2 sensors. I don't think so because it did run great for a week like this.
Is there a way to rule out the o2 sensors?
At this point otherwise all I can think is:
- bad connector plug at PCM
- plenum gasket ( vacuum tests fine, but I see oil residue in throttle body)
Going to the dealer tomorrow morning. This will be the fourth shop, also to no avail.
I am thinking at this point though, it must be something simple like that, that I've overlooked. I mean it has to be something...!
Yes I'm pretty sure it's p1296. I'll double check but pretty certain. It's a cheap scanner I have. It's manual doesn't even show 1296 code for me to know, so I googled it,. P1296 for Dodge ram. Google says map sensor voltage, which I didn't question since I've been getting the other map code for ages. P0107.
No it can't do that, but I'm thinking a scanner capable of that would be a worthwhile investment. Any recommendations?
Administrator
Joined: Apr 2010
Posts: 87,482
Likes: 4,223
From: Clayton MI
I think there is a thread about that in the FAQ section here.... (might be in the 2nd Gen Ram FAQ/DIY section too for that matter..... check both.)
I don't have enough experience with the latest and greatest scanners to make a recommendation.... Last scanner that I used was a Snap-On Solus...... if that tells ya how long ago that was. I have some crappy software on my laptop, but, it sucks, and I would NOT recommend it. Torque is supposed to be pretty good, Torque Pro even better, but, requires a bluetooth adapter for the OBD port. (which are pretty cheap.)
I don't have enough experience with the latest and greatest scanners to make a recommendation.... Last scanner that I used was a Snap-On Solus...... if that tells ya how long ago that was. I have some crappy software on my laptop, but, it sucks, and I would NOT recommend it. Torque is supposed to be pretty good, Torque Pro even better, but, requires a bluetooth adapter for the OBD port. (which are pretty cheap.)
Professional
Joined: Oct 2018
Posts: 157
Likes: 3
From: New Hampshire(NH)
Alpha-OBD is ok but you need a compatible laptop and USB scanner or android+bluetooth. Dealer level software including programming and more but the UI is complicated but it does support graphing and telling the truck to do maintenance things.