Hi... 1227730 ECM, 8D, S_aujp as base bin. Anyone know what causing this? Sometimes, not always as you see, the SA follows the rpm up during a WOT pass, and the next time it matching the SA-table.

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.

It may be the forced knock SA being added in.

RBob.

How much does it add?

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.

This is dependent upon the calibration, base distributor timing and the upper timing limit of the distributor.

RBob.

Well it adds a lot then, it topped out at 71.4 deg in the logfile.

Here are the logfiles I would be happy if anyone have any suggestions on what to do. 383v5 I think is the only one thats normal.

I've also looked at alot of 8D scan I have done, never seen it before.

Also checked some 6$, 58$,59$,60$

email me at gta324@hotmail.com and I'll send the logs...

I take it you are seeing the same thing as gta324? Same S_AUJP as the base calibration?

Note that the full 71* of timing won't be reached. The distributor limit is 42*, and with the base timing at 6*, the max at-crank timing is 48*.

RBob.

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).

RBob.

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.

Not in V4, timing goes crazy without CCP enabled..........

Weird.......in V4 it doesnt follow rpm, its just "linear" to something?
then in v6 it follows rpm sometimes and sometimes not.............

And its always when the engine is hot.........Will set Forced knock to 150 Deg C.

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

ed: Also look here at post #16 about going from V4 1024 to V4 1026 version.
http://www.thirdgen.org/techboard/di...-released.html (S_AUJP V4 released!)

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.

This bin have the S_AUJP_V2 as base.

All changes have been done in TP.

Will read some about corrections now, thx.

/N.