Mopar1973Man

I'm in the process of renewing my CCW permit with Idaho. I still carry my 9mm Star Pistol every time I take off from the house. JAG1 was kind of surprised about that. At first didn't realize I had with me and then after then he paid attention to if I was carrying or not. I'm a firm open carry person but have the CCW for the slim chance that I'm caught in a condition that would conceal the weapon. For me it more of a issue locally of the four legger (Animals) messing with you. Then when I travel to the Big City then you have to worry about the two leggers messing with you.

I like the wheels those are pretty sharp looking...

No not currently... But I'm fairly sure with a bit of digging I might be able to address it. (Might...)

Well I got a neighbor that stopped in last night to tell me here sister in New Meadows, ID is have vehicle problems. The vehicle in question is a 2004 Dodge Dakota 4.7L V8. She was explaining a surging issue she has been having issues with. Before I left the house I grabbed my Android Tablet and the OBDLink LX Dongle. So Looking over the vehicle its just a good old used Dodge Dakota and nothing seemed out of place. So I hooked up the OBDLink LX and turned on the ignition and read the error codes. It came up right away with error code number and the generic definition of the code. (Oxygen Sensor) Then I figure I would verify the code is real so making note of the code number I reset the codes. So now I started the engine and let the OBDLink LX read all available PID's and show me live data. This is way nicer than the old ScanGauge II. You can see like 15-20 live data PID's at once. So it was fairly obvious of what was wrong you can see the oxygen sensor in question was stuck at 1.23 Volts and the rest where cycling as normal. Also the code came back instantly. This impressed the owner big time being I was able to pin point the problem without really getting my hands dirty. So she'll be bringing this truck to work on in the near future. So I will have to admit the new OBDLink LX I picked up is a well worth it tool for anyone's toolbox. Works extremely well. The only mistake I should of done was smacked the screen capture function and I would of had all the vehicle data. During the diagnostic period it all ready tapped the Mode $09 area of the ECM and pull the VIN number and year of the truck for me. To me that's awesome to practically have everything in a single diagnostic run. Comparing to the old school Innova scan tool and the ScanGauge II I'm highly impressed with the data this little OBDLink LX Dongle can pull for you!

Nice job. Yeah the color is a bit off. You could of ordered a can of dash paint from most of the vendors and colored it to match. But it's got to be better than looking a shattered dash.

Now if this something EGT gauge could of prevented or is it a designed weakness of the engine that was resolved later in time?

That's some serious carnage. Question to the 3rd Gen gurus what is the cause of this failure?

Geez...

Even my +50HP are fun... Just ask JAG1 about them...

Heading to 200k for my AirDog 150. But I bought it back in 2006 when thing were better back then... Only need 7k more of the VP44 to cross 200k miles.

http://swepcolube.com/ http://swepcolube.com/products/swepco-308-premium-cj-4-plus-diesel-engine-oil Been around awhile...

Russ got it... But sad to say looking at the history of Russ truck it looks like the RusT won though...

I see that the fuel temperature shows up on the Cummins Onsite but its limited to just the ECM. Lots off good data there just limited to Cummins Onsite.

Nevermind... I can't play at all. 243,000 and climbing every day.

If I had time on my side I would consider making a removal tool out of the broken tap. Take notice there is four hollow gaps along the broken part of the tap in the housing. Now carefully mill out the center of the old tap till you have two pins basically to fit into the hollow gap in the broken piece. Before going on I would blow out all debris, lube and heat the part. Now carefully attempt to spin it out broken piece of tap. But that's much easier...

As long at the oil meets or exceeds the minimum requirement of the device... Why not. The only other factor will be is cost.

First off let me be very very clear about something. OBDII information will not add more gauges than there is sensors for. So if people are looking to replace conventional gauges with OBDII directly it's not going to to happen. Being fuel pressure and EGT's are not part of the ECM sensor array. So that being said I want to learn how to dig out the hidden bits of data that are floating around the ECM & PCM like fuel temperature and Transmission temp. Those would be a nice addition and goal to reach for. As for what I know. I know that both my 1996 Dodge Ram (Gas) and 2002 Dodge Ram both use ISO 9141-2 (5 baud init, 10.4k baud). The refresh rate is roughly 4.2 PID's per second. I know that out of the standard OBDII data there is 10 known PID's for the 2002 and 14 PID's for the 1996. Being the 1996 is a 46RE automatic I should be able to tap the transmission temp sensor and get the fluid temp. Then on the 2002 Dodge I know the VP44 has the fuel temp sensor and modules like Quadzilla and Edge both can read this data from the OBDII port. The biggest thing is doing all the reading of SAE and different OBDII standards. Bad part is Cummins did NOT follow the OBDII rules so the extended data is going to be a bit tricky to find. Now are a rule of thumb most manufactures changed from Mode $01 to Mode $22 for extended data. But like after doing my study work for the past two days finding Toyota uses Mode $21 for extended data. So this just makes addressing a bit tough. So I've been digging into ScanGauge II and seeing similar things of data and addressing. That's what gave me the break I needed was looking around and finding header address 68 6A F1 used on most ISO 9141-2 even if you look close you'll see ScanGauge uses the same thing. http://www.scangauge.com/support/x-gauge/xgauges-for-iso-vpw-vehicles/ Which now looking again tonight as I type this. I starting to understand the ScanGauge II X Gauge format in rough layout. TXD (Transmit Data), RXF (Receive Filter), RXD (Receive Data), MTH (Math). So after the ELM 327 document you'll see how the ScanGauge II does the data search for the information and displays it. But to keep the confusion down I like the Android Tablet idea much better because your working with human readable information and not strictly Hexadecimal like ScanGauge II. So now just look at (link below) and look over the Mode $01 data. This is what most tools like ScanGauge II are capable of seeing. Now If you got the talent for ScanGauge II and Hexadecimal then you could follow along and get the extended data to work also. http://en.wikipedia.org/wiki/OBD-II_PIDs Now open this up and flip to page 15. These PRN's are the extended data hidden in the ECM. SAE J2178_2v002.pdf Like PRN 102F is engine oil pressure, PRN 1044 Fuel Temperature, PRN 180B on page 16 is Transmission Temperature. Just going to take more study time.

Look a bit long at the picture the filter appears to been struck from the firewall side. (On the end cap?) Look close at how the metal screen folded up.

Always love every ones fuel pressure numbers. Fact is Dodge states 10 PSI as a minimum. As a group we state 14 PSI to keep the overflow valve open (Unofficial). But I love hearing the all the pressures ranging from 5 PSI to 10 PSI from all the different shops.

Just for information value... If your ECM did die then here is a spot you could try. http://www.kleinbottlecomputer.com/

Ummm... Stock bulbs. Funny thing is I've still got factory light bulbs all the way around the truck yet (except headlights). Never lost a taillight yet. http://www.napaonline.com/Catalog/CatalogItemDetail.aspx/Taillight-Bulb/_/R-LMA3157_0455488658

Dorkweed's sense of humour is still going...

Ummm... You are too quick to give up. How about... http://www.obdlink.com/mxwf/ Designed just for Apple products (iPhones, iPads, etc.)

That's the thing the metal screen is what gives it structure. So I really doubt its heat cause. Your hood isn't making contact with the filter is it? (Crushing)