Discuss anything TunerPro related.
9 posts • Page 1 of 1
I was able on friday to get Emulation and ALDL functions to work great in the morning. I sat on the AWD DynoJet friday morning doing pulls, having a wideband from the exhaust to the Dyno, and changing my BIN accordingly. Getting 30 hp and 40 ftlb of torque just by fuel changes and not even to timing yet, I took a break. I saved my BIN, shut my truck down, and left. I came back 30 min later, turned the key on, and I got a "strobe like flashing" of the MIL. My ALDL indicated bad PROM. I already have Disable Checksum by Uploading 0x AA to offset 0x 08. I go and upload the 'stock' BIN and the vehicle then starts up fine! So while the stock BIN is running I upoad the Modified BIN and go from there. Altho this is possible to do, it gets EXTREMELY frustrating! Every minute my vehicle is sitting on the DynoJet I am losing money instead of working on customers cars. This is my FIRST time using TunerPro, and I use stand-alone systems primarily. Is there any reason why I cannot START the vehicle and not go into Limp mode? Is it possible for the stock ECU to indicate there is something odd with my MEMCAL? Thank you! This is a 1993 Silverado, I am using E6.xdf, E6_ECM.ads, and a BIN from Saar here on TunerPro.
Im running code 59, and yea, my starter bin was setup without the checksum disabled. And it worked fine for like, a couple weeks and then all of a sudden stopped. my starter bin will still start the truck, and i can upload my modified bin and it will work fine, until i go to start it again. and it will start, but it runs super lean, and with the timing super advanced. Ive tried to take my starter bin and make a new modified bin, but as soon as i modify it it seems to do the same thing, even just doing a bit of work on the F29x table and what wideband to use...