Me78569

Run a 1000 series tune, set to mins at 20 and 30 wieetap min. Keep fuel stretch at 1200

does your power level stay the same from key off to key on or does it always revert back to lvl 0

neither of those will read off far enough to matter. If 50* or even 150* difference is enough to blow something up you have something wrong. fuel pressure reads steady and good, again 1 or 4 psi doesn't matter you will clearly see if your lift pump fails regardless. as with any sensor data you have to compare trends in order to read them correctly.

I would not be thinking the updates will improve accuracy. It simply isn't possible for the most part. One truck reads one way another reads another. EGT's being off, is typical from gauge to gauge. I used only my quadzilla EGT gauge and never had issues, even towing up some of the steepest and highest grades in the country with really big injectors. 50* is not going ot make or break you if that makes sense. boost reading off, is just the nature of the beast. Some trucks are accurate others are not, again I never had a mech gauge and I was never the wiser as to if the stock map was accurate or not. again never an issue. Coolant over 204* is just a dumb dodge thing. The dash works so I was happy with that. mph is a passthrough, never figured out why mikes reads 1 mph off. as the developer I wasn't worried enough to mess with it. oil pressure gauge works on trucks that did not have the oil pressure switch installed rather than the oil pressure sensor. typically late year trucks had a switch, early trucks had a sensor. it may or may not work. again none of this stuff in my mind really matters when it comes to keeping things safe. A well setup / tuned truck will not have issues within the margin of error in any sensor / gauge setup.

I like to use all my radiators

says monster pump

it was stainless diesel, you can look it up. I dont remember exactly.

18* is less than stock at 25* max. The VP record is 1000 something on fuel.

Yes and less than stock. Again the edge maxes out timing at 32* and it holds the hp records.

boost fooling, the ecm only sees a max of 16 psi. the baro reading on 2nd gens is not reliable truck to truck, same as calculated engine load.....real PITA

no, 24* - 26* unless you are at %100 duration in which case, on any level other than sw3, timing goes static to 18* regardless of rpm

you picked up power because of timing. the Smarty does 18* at WOT and peak duration. you gain alot of power by upping timing.

If it happened at WOT I see no reason timing was the issue, nearly every edge truck on the roadis running nearly the same timing curve, if not more aggressive. I think it was just hte headgaskets time to go. timing pop might have been telling you too much timing up top, but I flat out abused my truck during the testing of V2 and had more timing pop than most guys and never had an issue. Not a great thing to do to the truck, but doesn't worry me overall.

I dont see any reason why that would be too much timing. I ran a very similar tune in sub 0 temps towing. If that timing curve was an issue, people would smarty S03's would be blowing headgaskets going to the store. only difference in timing is my low throttle timing, yours is 1.5* higher. yours prob results in ~21* at cruise maybe 22* . little on the high side, but duration would be tiny at that point.

I would like to see it. that will allow me to give a guess as to if it was too much timing resulting in the gasket issue.

full timing at full duration at low rpm can hurt things, but up top I am not so sure.about it. our trucks have a long drawn out injection event. I think I read someplace that at full duration and wiretap at 3000 rpm you get something like 100* crank angle of injectioon event. I really think your gasket issue was just luck of the draw though. during normal driving I would not expect a vp truck to give enough timing to blow a headgasket. if you compare the typical tune I see with the quad you are actually running now where near as much timing as say a guy running a smarty on timing levels + edge combo. what tune where you running?

it reads 60 psi at idle state? or only at wot? I believe the longer time to heat hte air will trump the denser air. N02 is 2 parts O so it has much more effect than cooler air.

fueling the vp can't realy mess anything up, timing is a bit easier to cause issues, but not a huge deal. I wouldn't be running 30* at sub 3k rpm unless in a race application. I would be interested in seeing your tune though. My first thought is luck of the draw though. colder air should delay the combustion event so you should be less likely to have issues.

Don't drive like a dingus and you will be fine. The engine is tough.

Some advancements are both good and bad......well most every change is in some way or another. On a personal level I just have to ensure I am thinking through the changes in the future to ensure I can continue to live the life I want. Free market wins Go America!

I understand your concerns with it, I share them, but from a pure technical standpoint the computer can do some pretty incredible things. The telsa crashes gain a ton of news publicity, however the stats show you are SIGNIFICANTLY less likely to get in a car accident in a tesla than you are in any other brand. If you look purely at the numbers in america there are roughly 5.5 Million accidents per year with 32000 deaths. NHTSA studies have shown that a tesla with auto pilot is %40 less likely to be in a crash than a tesla without auto pilot. the rate of deaths per mile driven is 1 death per 320 million miles with auto pilot. NHTSA shows an average of 1 death per 80 million miles driven nation wide without automation. So the tesla with auto pilot has killed 4 times less people than the average car on the road per mile according to the NHTSA. That means that RIGHT NOW you are %75 less likely to get in a car accident with a Tesla with auto pilot than your 2nd gen. your driving skill is not important when you consider that there are other people on the roads with you. It's not a direct apples to apples, but the numbers are impressive even it was half of that. things like computer controlled emergency braking, lane assist, traction control, abs are all steps towards self driving. They are widely accepted and have statistically lowered the accident rate. as for the jobs argument, it is widely unknown what will happen, but humans are resourceful. Lots of people have been having these same talks through history. I am sure there were people up in arms when the combine came into play, how many field workers lost their jobs? industrial revolution etc etc etc. Times change people adapt. Now that is not to say that we should just jump in blind folded, but be aware of the argument on both sides. The world is up in arms over mass shootings, but when someone says " we can cut down traffic deaths by %75" everyone yells and screams. again there are issues that need to be worked out, but it is promising.

use another scanner. you are only getting results for CELS from 1 of the 2 computers. The P1693 means that one computer has a code and the other computer is giving a P1693 to let you know.

They can handle ice and snow better than you can. Not to say that you are a bad driver by any stretch, but sensors and computers calculating wheel slip on all 4 wheels 1000's of times a second mean it is impossible for a human to beat that. Humans react to a slide, a computer with correct sensor data would catch the issue before the slide. Being able to programically adjust wheel torque, per tire, based on live slip data is not something a human can compete with. It is seriously impressive, but not new. Land Rover has been doing this via computers and abs for years, electric motors takes that to the next level. very similar to the f22, a human cannot react quick enough to actually fly one, the pilot tells the computer where to go, the computer flies the plane. Your should watch videos of the current systems. If nothing else it is impressive

It's in the software section.

I've loaded the 1.12 and reinstalled the libraries in the article and it is compiling. Try installing your libraries from the article.