Quote:
|
Originally Posted by 86GT
I wish I could answer the weird things that you are seeing but I cant. It does not make logical sense that it would makes changes in more than one function or the MAF making changes to three bytes at a time. Tis could only happen if the def file was not set up correctly or if the memory locations were crossed.
This was in Cal Edit that you saw this in?
You might have to start with a fresh binary and make all of the chnages again. Some how it got corupt. I used PCMX to make all of my binary edits. I have used TunerPro on a few parameters and seems to work. I have yet to try a fresh binary from TunerPro.
|
I'm using the A9L that I got from TwEECer site. I'm doing the "difference tool" in TunerPro to see the changes AFTER I change particular functions. Most work fine except for MAF & a couple of others. I've used THREE different definition files (yours, dex's & one I made) and the issues appear every time. I can change the filling by messing with the def file, but I haven't been able to stop the weird behavior with certain cells as described above. Either my computer (work laptop that I do heavy CAD on) is messed up or TunerPro is messed up (I don't think the definition files are messed up but they may be). Maybe you could try using a fresh copy of A9L in TunerPro & make the changes I described above & use the "difference tool" to verify what I am talking about.
NOTE!! The data looks OK in CalEdit when I look at it BUT there are bytes that are changed that don't show up in CalEdit, and the resultant bin from TunerPro corrupted the crap out of my Tweecer - I still can't get CalCon to log correctly!! I doubt anyone else has done a tune entirely in TunerPro as I have - especially MAF curves since I was the first one to find that the file wouldn't work in CalEdit due to integer format for "Y" values. I hope someone can verify this since I'm no expert in digital engineering. Mechanical - yes, electrical - yes, digital - NO! just learning...
Edit: Also note that I took the SAME A9L starting file and changed ALL of the scalars for my current tune in TunerPro & then copied all the functions in CalEdit and the tune works fine also. No bytes got filled "out-of-place" when I just changed scalars.
Oh, and I hope I'm not coming across like a grump - just that I've been sick as a dog for a week and i had a little while beween raindrops to burn my new tune and it was nothing but trouble - I don't mean to take it out on anybody
