I was wondering why I usually see some knock counts recording (WinALDL) when I start the engine (7747). And it happens on a cold engine too. SOmetimes a cell will fill with a large number (+200). Anybody got any ideas? I thought maybe the KS was seeing starter noise, but isn't the ESC disabled below a temperature?

 

Yes it's the starter. It's normal.
No the ESC isn't disabled below a temp, only knock retard BECAUSE of knock counts is disabled. The knock retard is also disabled below a certain RPM and I believe MPH, it's been a while and I'm in a rush right now.

 

thanks! Perfect explanation why its usually (but not always) 400RPM / 100MAP cell...

 

Just think of it this way; The computer is thinking a LOT faster than it's talking to you through winaldl . It'll pick-up knock if you sneeze funny. Or if your transmission is clunking, or if the through out-bearing is shot, or if you're driveshaft is too long for your suspension travel (yeah, that was a hard one to figure out).
I can't recall if the 7747 is like the 8746 but the knock counts displayed in the 8746 aldl data-stream were msb (most significant byte) as apposed to lsb (least significant). What this means is that the lsb would detect knock and the ecm would be taking out timing but you wouldn't now it unless you changed the ALDL data-stream to display any of the following; Final SA, Knock SA, or PA3 (knock counts) lsb. I was getting 8 degrees of knock retard with the ANLU.bin as a base for the knock parameters but was registering ZERO msb. Not until I got lockers did I start noticing the knock retard that I was never registering. I think the 7747 is handled slightly differently and only does knock retard when the PA3 msb increaments.

 

I understand that the update of Winaldl is slow, but, if I understand you correctly, it is possible that the serial data to WIndaldl may not be showing me all of the knock counts that the ECM is seeing and reacting on?? If that is true, is there something that can be done about that? I am in the middle of tuning VE tables and am about to move to the SA table...

 

Modify the ALDL data-steam to spit out a different ram location in place of something you don't need.

Read the text file and it should answer you questions. Then look through the RAM locations and you'll find the locations for final SA and knock SA.http://www.moates.net/files/3)%20Bin...DL%20patch.zip

 

thanks man. so I am wondering why I didn't ask this a year ago. I got alot to learn...

 

ok, i am trying to do this. I imported your ecu file and saved it as an xdf in tunerpro. But it doesn't want to save a new value for eprom id (for example)...it reverts back to D002.

 

I also noticed in the XDF header info it says $61, does it matter that I am running a $42??

 

You're right, look at that, it's broken! It worked before I don't know what to say except that I can't seem to get it to work.

edit: I got it to work. You just need to go into the header info and change the Bin size (hex) from 0000 to 1000.

 

thanks again.

 

...remember, knock counts are considered normal(even while driving). The key is to find out if the ECM is retarding timing...

 

Could someone help me decipher what I logged last night. I setup the datastream to log locations 066 and 067 (total spark advance; msb and lsb) in place of prom id. The spark advance value was: one value was always zero, the other value ranged from 104 to 30. I'm just trying to make sense of the numbers. THey don't really agree with my spark advance table, not even close. Maybe the decimal point is not correct, but still if it was 6.6 at idle, that's not close to my prom table???

 

Yeah, I don't think the SA lsb does anything. To convert from raw decimal to degrees of SA just use x*90/256. So if that range of 30 to 104 is correct your seeing about 10.5 to 36.5 PLUS whatever your base timing is set at. So if you've got your base (aka initial) at 2 degrees then you're looking at 16.5 to 42.5 which should make sense.
Replace the the location that isn't working with Knock SA. While you're at it, if your alternator and battery are doing OK why not replaced the battery voltage with desired (aka commanded) AFR. The way battery voltage is calculated is x/10 and it's the same formula to derive desired AFR making your scan tool a little easier to "read".

 

Hmm, I logged a value of 66 last night at idle rpm which would convert to 23.2 deg. advance. My prom shows 33 (ok, I know that sounds like a lot, but I think my harmonic balance has slipped and I jacked that value up to test things). So there must be other things contributing to the total spark?

I did the bat. voltage to AFR swap, that works great! I suppose i don't have a highway lean cruise mode because at 75 mph and light throttle, the AFR still showed 147. ANy way to help that?

 

Did you convert that value and then add the base timing?
Make sure your highway mode is enabled and all of the parameters are being met. There is a lot that has to be right before it's enabled. Engine temp and speed are 2 major ones. Highway mode doesn't stay. It'll cycle in and out of highway mode as you're cruising to relearn the BLM.

 

How do you check if highway mode is enabled? I don't see a flag that can be set? I always assumed it wasn't an "option"...

 

I haven't messed around with the 7747 in a WHILE. All I know is it's not enabled from the factory and you need to "patch" it to get it to work. The code is there but it needs some tweaking. Do a search for it and I think it'll turn up something useful.