Me78569

likely just related to disconnecting the wiring when the key is on. I would clear codes and see what codes are left, if any.

unless you can explain your need for higher pop dont bother.

I dont follow. You should see a tune in your list called "nick" do you?

So Something about the json file structure your phone /s dont like. Dont ask me why or how. Anyways I took the tune you sent me, built a tune on it then exported it back to you. Try loading it up, does it load the tuning variables or fail them? You will have to edit the tune on your phone, but that should at least your tune to load.

Try to load this tune. Does it show up? nick.json

It's not normally hard. We are overlooking something. Do this for me. Load the default tune in the iquad app > save > export that tune and post it here.

Did you buy a 4k box or a normal box? something isn't lining up

there is something up with your device, it is not downloading the right vehicle profile when it is turned on. When you uninstall then reinstall from the play store you should get a "refreshed" list from the quadzilla server and that will match the current version on the box. current profile version is V2 Dodge 1998-2002 version 2.7

Some good info there, some issues as well. Biggest thing is no you should not stack timing boxes. while he is right you can't "overtime" the collar in the pump you can command too much timing at a given point in time. IE 30* of timing at 1200 rpm = poorly running truck. the thing he didnt know what it was is the fueling solenoid the thing he called the fueling solenoid is the timing solenoid The biggest issue with the vp is a p0216 code or a stuck timing piston due to bad fuel /low fuel pressure or old age. over heating isn't a huge issue with the vp now days.

You don't have V2 on the box under the hood then. you need to flash it if you want to run V2 or select the non v2 vehicle profile in order for it to work. This is why it wont connect worth a darn, mismatch between code sets.

In the datalog do you have a date in the build date field at the bottom? If yes, you dont need to do anything If no, do you want v2? If yes, you need to flash If no, you dont need to flash

I would byuy from DAP as they are the same owner as quadzilla.

Yep, this is related to the switch itself. I have adjusted the testing of the switch before sending out to catch these bunk parts before they go out.

wehn did you get the switch? This is typically a bad switch, the last batch of switches ( the actual rotatary switch) has a higher rate of bad connections internal to them. Put a support ticket in to get it warrantied. Support@mopar1973man.com

almost 8k 2k of that towing

the 6.7 will pull circles around the 5.9 I dont have a ton of miles on mine yet, but it has been great so far and I have yet to miss the 2nd gen.

no relays just the conversion plugs to split the single into 2. @int3man alright it should be fixed. I forgot to add a prize lol. we have a wiring diargram for the relay mod in the articles.

try again I refreshed the settings.

Time

Any white smoke out the tailpipe? How bad is the bucking? I am wondering if you aren't running enough timing down load when not in cruise state timing. Try this If that doesn't work give this a try this out. It is a "hidden" mode of doing timing on the quad. It will add to stock rather than running it's own. Have you looked at the tune on the phone to verify that all the variables loaded? You shouldn't see any 0's or 150's in the lower psi area of the fueling tune setup.

I dont have the specs on them anymore and I dont have a 2nd gen to rebuild them from scratch. If you want I can give you the part numbers for the fittings you need, but you will need to source the hose.

So no bucking on lvl2? Boost defuel and egt defuel. Turn them off for testing. If it does buck onlvl2 then try lvl 3 and repeat. If it pannes on lvl3 it should happen on lvl 2 if it is timing related. If it only happens on lvl3 + we should look at the fueling curve.

what level is it bucking on?

where is the datalog is it bucking? Line #'s would be great Edit: the data log doesn't match the tune you posted. the cut off for lgiht throttle timing is %20 in the datalog and %30 in what you posted. I also note you are using backdowns, which is fine, but I would disabled those for this testing. Are you using wiretap when it bucks? does it do it on level 2? 3? 4+?

I dont see why a Board member can't buy a ticket, the process for picking is %100 programmical.