DIY PROMDo It Yourself PROM chip burning help. No PROM begging. No PROMs for sale. No commercial exchange. Not a referral service.
Welcome to ThirdGen.org!
Welcome to ThirdGen.org.
You are currently viewing our forum as a guest, which gives you limited access to view most discussions and access our other features. By joining our community, at no cost, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is free, fast and simple, join the ThirdGen.org community today!
I've noticed odd spark readings as well when I was messing around with s aujp. I haven't had a chance to convert back to a '730 to get it running, but I'd definately like an answer as well. I was getting random stuff like 120745 deg advance, then nothing. Checked it with the light and it was running on base timing.
I've never seen that happen. I checked DM files, TP files, ScannerPro and TP V5's. Went through about 50 logs just to see if it was on any of them and not one place. Could be the earlier version of DM and setup as a Corvette w/manual trans ??.
BTW, your AFR at that point is "666" so be careful at that RPM :-).
The newer version indicates the AFR commanded correctly and should playback the same file. email me the log, I'm curious.
RBob-->yes its my car and GTA324 is tuning it because I dont have the knowledge yet. And the highest spark adv number in the file 383v6 is 71.4 degrees and its pinging like hell and like gta324 said the SA follows the rpm why I dont know.
RBob-->yes its my car and GTA324 is tuning it because I dont have the knowledge yet. And the highest spark adv number in the file 383v6 is 71.4 degrees and its pinging like hell and like gta324 said the SA follows the rpm why I dont know.
After I posted the above I got that feeling that it was your car. But, since I already posted I left it.
I'll bet it is pinging like crazy. 48* at WOT will do that.
You can disable the forced knock test by setting the temperature threshold high. The parameter is at $29C, and is the typical *C conversion (C = N * .75 - 40).
There may be a bit that is set during the test (if that is what is doing it)
I'll see if there is something turning on at that point in the logs if it is in the datastream anyway.
Log is goofy, It isn't recognized by the $8D version of DM I downloaded.
I'v done some reading about "forced knock" in the forum and doesnt it only happen once until I turn the engine off, and next time I start it could happen again one time? Could this happen lots of times like it is in my 383v6.uni logg?
This probably doesnt have anything to do with it but everytime the CCP DC starts moving the timing does to.
I don't see exactly what is causing it but I do see enough to know there is a problem with the way the values were transferred into the new bin.
There are sections of code that have been over written by "00" towards the end of the calibration section.
I'm guessing the existing values from your base bin were pasted in to beginning and not entered via the compare tool in TP individually.
I suggest grabbing a fresh V4 1026 bin and doing a compare on your starting bin (not the one currently running if you don't have to)
Setup the difference tool and go one by one copying to create a new bin.
Do not copy anything from Address $"8"98A and higher from your existing bin.
This is where the custom code begins. Set these items up manually if you are using them and everything should come back in line.
No need to zero out any of the tables up there. If the flags are set to not use them, the code jumps past and never sees them anyway.
HTH
Check the thread down lower to see any of the corrections to the ADS and XDFs that have been found since release that you should correct in your config files.
