Me78569

With some modding prob. You would have to be more versed in code to do it.

More than likely yes, The ecm does it's damnedest to keep the engine running so you will see odd stuff.

Once the ecm data stream stops the variables for rpm or temp etc are never updated so you will see the last value. So the ecm in the first set is confused and not sending data thus the Quadzilla is not getting data and not updating the screen. Kinda like If ( RPM data update = T) { update rpm data } else { Don't update rpm } If I were you I would wire up 2 led test lights for the injection pump relay. 1 on the incoming power source and one on the outgoing power source. Drive around and see if the LED's stay on when you have issues. I am wondering if you have an upline power issue.

that mega should work fine. My code uses a lcd screen to display boost / drive / shaft speed / and turbo position.

So serious question, Do you want it just to work, or do you want to mess with it and understand it? Lilbb.com makes a plug and play unit that my code shares alot of code with. It works VERY well and has really cool features, like bluetooth tuning from your phone. If you want to get your hands dirty in the computer world then I will help as much as possible. My current code still uses drive and boost with TPS, but the main tuning variable is shaft speed, as it needs to be. I divided the article to show boost / drive control vs shaft speed control. You will find the shaft speed below. No updated parts list, The code really hasn't changed in more than a year now. I think 1.11 version of the code is for an Uno and the 1.13 is for a mega. let me know your path and I will go into more detail if need be.

Ouch, man I hope your luck turns around. I just did bearing myself.

cheap and green is my method.

Try dropping your fuel load timing to ~1* and drop the 1500 rpm timing by 1* - 2*

flush your system

Is it limited to only boost or is it in a given rpm ranges or to range etc? Once I have some filters to apply to can take a peek.

@NightHawk Don't take how I said it the wrong way, not blaming or yelling or whatever. The only thing that I needed to make %100 clear is that the quadzilla it not doing anything new in terms of the roots of how our truck work. I would never say that because it is flat out a lie. The vp44 crowd has fallen victim to smoke and mirrors for way to long. It is vastly important to me that people understand that nothing new is going on here from a communication standpoint, only the way the box gets its variables. I don't want new guys to think that the quadzilla is somehow doing something new that no other box can do. IE: the rumored 2nd injection event. The only thing the quadzilla is doing is opening up the ability to choose the variables in the software. There are absolutely risks in running something at and beyond the limits, but those risks are the same regardless of the tuner. No voodoo magic going on here.

My truck's shifter linkage bushing was worn causing the truck to not go fully into park. how are yours?

Nuetral safety switch? or whatever the autos use to tell if the truck is in gear or not when you crank.

Is there an issue or something you are looking to fix? I can't remember my last name these days so you are gonna have to help me out.

There is no cat to expensive for me to get rid of. Saly I think I would have to fit in the box as well..welll my wife would ensure that I was packed in too. and coyotes would be acceptible by me....

I have the perfect solution. Send me an address and I will get this anti bird device packed up and ready for you. No charge needed.

I hate to be the bear of bad news, but the V2 isn't going to work well with your dying ECM. The V2 relies too much on solid sensor input that the ECM doesn't appear to be giving you. If it was anything but the WTS being delayed I would say you shoudl dig more, but the WTS issue is pretty damning. You can revert back to the older tunes, they should work better as they read from the Map sensor directly since they don't need filtered reads to have smooth fueling. However I would serously consider looking for a new ecm before you are left somewhere.

The Key here is we play within the VP44 world. Our trucks are not like CR trucks, you can't just command anything you want...doesn't work. The ECM does not control the fueling solenoid directly, same for the timing solenoid, rather it asks the VP44 to do a 0-100% of duration on both using a Fueling message that the VP44 decodes and follows. The way it asks for this is Via the canbus network. Rules to play by for the VP44 to work. If your fueling command is not normal to the below stucture then nothing happens. Canbus fueling command needs to be between 0-4095 timing command needs to be within 0-4095, but only 0-3800ish or 0*-~30* So how it works with a Quadzilla Type tuner 1. ECM calculates how much fueling and timing to ask for based on a multiple sensor inputs 2. ECM packs those commands into the Canbus Fueling message Green is fueling Blue is timing 3.Quadzilla reads that data string and alters it using user input, note it still has to play by the above rules or the vp44 won't be able to follow the command. 4. VP44 reads the command and decodes the fueling and timing message to be a duration for both solenoids. Again none of those steps have changed with the V2 tuning. Look at the Data Logs I posted of the smarty S03, and compare them to the data logs I did of the Quadzilla on various tunes. It is plain as day that the smarty is more fuel and timing aggressive as it just maxes out fueling and puts timing at or above 18* If you want to know more jdonoghue figured this out nearly a decade ago with his work. Just google his name followed by VP44 and you will see.

I feel it is import to stress that the quadzilla is even controlling timing and fueling in the exact same manner as any other tuner. There is no reinventing the wheel going on, only thing that is different is the user sets the variable in the code to change the fueling, rather than using a built in map. Rather than doing a 1 map fits all the Quadzilla allows the end user to set the variable.

I'd just stick them in personally. Look at it this way, if you were to buy new tappets you would be in the same situtation you are right now. The Tappet hole wouldn't be "honed" to fit the tappet in question.

You gotta remember that NOTHING in the read or send section of the code has been changed. The communication framework is the same as a decade ago. The Quadzilla still speaks EXACTLY the same j1939 protocol that it did before V2. The Quadzilla IS NOT doing stuff that hasn't been done before. Still keeping canbus fueling in the 0-4095 range, still keeping wiretap between 0- 2200 us, still keeping timing in the 0-30* range. I cannot stress this enough, there is absolutely nothing different going on from the point of the ECM, or VP44. The Only changes for V2 are in the calculation of how much fuel / timing to use at a given point. The min's and maxes are unchanged. Rather than the Quadzilla looking into a predefined map for a fueling % it looks at the user defined variable to see what % to use. like I said before the Old Quadzilla tunes are much more aggresive when it comes to timing, The V2 tunes actually ask for significantly less timing than before. Compare the Datalogs I posted in the Smarty thread to the ones I've posted in the V2 thread, nothing different. It is VERY easily blame the tuner, I understand that. Remember I've been running the V2 the longest here, I've prob flashed my box ~500 times at this point. I've run code that was %100 backwards, IE asking for 3* timing at 3500 rpm. 4095 at 500 rpm etc.

well when you do get a new pump make sure to run it without Wiretap for at least a month. Drive it HARD during that month to ensure you bring to light any rebuild issues. Ask Trevor about his rebuilt pump...

still having WTS light delay?

Well couple of things to point out in terms how what the Quadzilla is doing vs other tuners / OEM. There is no magic going on in the Quadzilla. all the V2 does it allow you to choose the adjustment to oem. As an example, I ran a data log with the old Beta comp tune, timing set to 8* which is normal for old tunes. By 2400 rpm the Quadzilla was asking for 36* of timing because of the way the map works. Anything over ~30* wasn't possible. When you look at the output of the V2 tuning vs the output of older tunes the V2 stuff is actually way way way less aggressive in terms of timing output. Smarty on Lvl 1 really never allows timing to come below 18-19* of timing, Steady state fueling on OEM will ask for the same timing number for as long as you hold the pedal in 1 position. IE if you are cruising down the road for 2 hours at 65 mph your timing does not jump around at all. I encourage you to test this yourself by running around on lvl 0 for awhile. Do a WOT run and watch where timing maxes out, you will find that OEM will ask for almost 26* when hot and over 28* when cold. That is the reason why I always recommend 25 or 26* as your max timing mark in the tune. The Quadzilla is playing by all the same rules, only differences is the variables that set how much and when are user defined. The outgoing message to the vp44 is still formatted the same way. @Mopar1973Man you are correct the Quadzilla shows on the screen how much timing was commanded. I don't have the documentation to spit back how much was actually used. I know it's there, but I can't really start unlessI know where to look. Sucks about the Vp44, but after that many miles I would say you got your moneys worth. anything that makes it 240k is not unreliable.

Post of the week right there. @jag1 just click in the upper right and go to account settings