Reply to thread

Message: [QUOTE="Charles, post: 1316730, member: 103"] Surely a stumble if they don't switch the truck off isn't the reason for all of the above? Is there no other reason to care about whether it's VDH2 or VDH600? If not, that seems like a minor, to non-existent problem. For me, non-existent, I don't run but one program. And I still don't see why you would for that matter. As for the addressing offsets needed for special chips, just say what the thing needs, unless the converter is online, or comes with the thing and people have access to it. Back when my first templates were 56K DAT files IIRC, I drove myself nuts having to cut the 56k out of the 224k file in a hex editor over and over again and then paste the altered portion back in and eventually just opened my template in notepad and fixed the problem there so it would address the 224k file appropriately. If my template wasn't locked in minotaur I would have already addressed a few things more than likely. If anything pissed me off enough I would just go table by table in a hex editor by setting entire maps to say 100 and then noting their addresses to fill out my own unlocked version of each one. Yeah, locking them kinda pisses me off. I may "unlock" them as above at some point. Then having a template for any device that wanted less than 224 would be a 5 minute deal. Anyway, it all sounds like the same old whose gonna address from where to where again game. Don't tell me the Hydra uses a 56k file again, lol. If I have incorrectly remembered the dat file size, my bad. Been a long time. Sucks. But this isn't a payed deal. No money and no expressed, inferred or alluded to notion of safety. Adult swim. No lifeguard on duty. Swim at your own risk. If you can't bounce back from the possibility of a rod hanging out the side of your engine, don't come here. If it sounds wrong, it probably is. Stop running the file. Luckily we don't have to care if everybody gets a piece of cake. It's not a birthday party. If nobody writes a file for your cache code, then you don't get to play, lol. Or.... you could write one yourself. Why do you think I bought PHP tune from Bill? And I would expressly discourage anyone from copying and pasting anything, even on the exact same everything. The chances of the file running as intended is nill. There's way too much total horsesh*t in the background for that to have much success. Copying and pasting would be for advanced users who were actively uploading files.... not for someone downloading files.... Even then.... the chances of them getting it right would be low. Better to open two instances of the tuning software. Sounds like some really shoddy over gap "tolerances", lol. All that ends up meaning is a little bit of timing, and mean a [i]little[/i] bit, and lost or gained effective pulsewidth. But very little. The truck's not going to go from perfect to a smoky pile of fail based on that. Not even close. Biggest thing you might notice is the distance you push the pedal before the truck moves on tip-in. Why on earth are your injectors so slow??? Load the file up. LOL Fwiw, I haven't changed anything I'm aware of other than Fuel injector pulsewidth Mass fuel desired Altitude timing (I don't have one for sea level) ICP desired and the base idle speed Other than that, turning off the Map sensor SES. I'm going from memory, so there's probably something else, but I can't remember what. Now for whatever reason, when I started messing with the VDH (haha) the truck wouldn't run in any of the provided files that had 0 where the power number is listed. So I grabbed the 25t file, it cranked the truck so I used it for a base file. When I moved to the AEB PCM I just grabbed the 25t file again to start. Is there anything in that file that was already changed from stock that would affect the smoke? Lastly, my truck doesn't smoke like a train. It's not horrendous. I just think it could be less. And thanks for the input. That's what contribution looks like. [/QUOTE]