Having a comical issue with the 96530006 (well, tephra v7 test 5, but I don't think its related to the mods).

The address 1784 works, but only if you block out the address 1780 for "Knock Adder - Single Gain".
If you put the address for the decay timer ahead of the knock adder, the knock adder shows up but not the decay timer. If you flip them, its vice versa.

Hopefully this is just some sort of strange typo on my part, but I've copied and cut and pasted and the same thing keeps happening.

Thoughts?

 

If you use ECUFlash 1.41 and the XML def. tephra and I posted in that thread you won't need to define the addresses. It comes stock with ECUFlash 1.41 for that ROM version (9653).

Am I answering your question?

 

I just looked at a Ralliart ROM and found the timer set at 80, so it seems like a good value.

 

It doesn't actually, I have both of these(unless I missed the listing somehow in the tephra xml, its not in the base 0006). However, my issue is not a rom version issue, it turns out there's something weird going on when I edit any xml file (I broke evoscan this evening ) Tracking down a better text editor and going to give it another shot.

I appreciate the response, I'm getting a windows version of vim. If you have any suggestions on the issue I'm all ears, the only time I normally encounter windows text formatting issues is @ work when going between windows and unix boxes.

Drove around a bit with v7-t5 this evening, and aside from running over my licp ( its been a rough afternoon for the evo) and having to sort that out until, eh, about 30 minutes ago (2.5 licp piping welded to the intercooler ftw), Car drives great, so far no hiccups, I'm looking forward to sorting out these few software issues and tuning the car some more tomorrow

 

The decay timer was not defined in the beta tephra XML. We added it, but as Linux said, there was some sort of strange issue with editing the XML in notepad or wordpad. Ended up just doing a copy and paste of another table with the right address to get it to work, but evoscan broke when trying to add the proper code for 1 byte load. Is there a documented issue editing with the built in WP or NP?

 

Can anyone see what I have done wrong with regards to the knock timer? It will not show up (am I missing something in another xml file or is this a sinister bush/obama plot to hold the man down )

I thought I'd tracked it down to an xml corruption issue with wordpad, and downloaded an xml editor (as well as vim for windows.. man its great having that), but after copying over a virgin unmolested xml and adding that line, I still get a no show in ecu flash. I'm afraid I've broken evoscan in the same manor, but haven't gone out and hooked up to the car to tell. I still get the impression that this is some sort of XML corruption issue with my laptop but I can't for the life of me figure out where.

 

is there a corresponding "Knock Timer" entry in the base? ie with scaling etc...

 

there is not. if I put the scaling info in the 0006 def, it still won't show up (I assume this is still due to the same reason?)

 

hey john,
i'm trying to get the knock load threshold, timer, and adder tables for 962600099. i've only seen the xml for the multiplier table posted here. hope you can help.
thanks.

 

For reference, rom 962600... what are the values code for Knock sensitivity load threshold?

TIA

 

Just use the multiplier table. I wouldn't bother adjusting the load, add, decay tables.

 

Well gentelmen, after reading about this while deployed for a month, I switched to the 9653006 ROM and went logging today and was getting crazy amounts of phantom knock (36 counts) I came back home added the code to ecu flash with the settings below, and I have a much more fluid map now... no hitting a brick wall in second gear anymore! Thanks to all those involved in making this a reality! Still get a few single counts here and there but I can live with it! No more janky WOT pulls due to phantom knock!

set 2500 and 3000 to 100
low-18
mid-20
high-20

 

I have what I believe to be significant phantom knock and I'm not planning on doing anything about it until I can verify it by throwing some 110 in the tank but I'd like to be ready when I get that far. I'm relatively new to ecuflash so I hope that someone will verify for me that the xml I'm going to add is correct. I took the following from an example for 9417 and changed the addresses that I know.

<table name="Knock Load" category="Knock Control" address="38f2" type="2D" level="2" scaling="Load8">
<table name="X" address="594e" type="X Axis" elements="10" scaling="RPM"/>
</table>

<table name="Knock Multiplier - Low RPM" category="Knock Control" address="21DC" type="1D" level="1" scaling="uint16"/>

<table name="Knock Multiplier - Mid RPM" category="Knock Control" address="24A8" type="1D" level="1" scaling="uint16"/>

<table name="Knock Multiplier - High RPM" category="Knock Control" address="177A" type="1D" level="1" scaling="uint16"/>

<table name="Knock Adder - Single Gain" category="Knock Control" address="1780" type="1D" level="1" scaling="uint16"/>

<table name="Knock Adder - Triple Gain" category="Knock Control" address="177c" type="1D" level="1" scaling="uint16"/>


90550001:

Adders are two single values:
177c = 7 (triple gain)
1780 = 2 (single gain)

Multipliers are three values:
21DC = 20
24A8 = 18
177A = 13


I would like to verify what addresses I should have in the first two tables. I did not change those addresses from the example because I'm not sure what they go to. The only other question (I think) is whether I got the order for the multipliers right, they might need to go the other way.

Thank you for your help.

 

I <3 this thread. Just got it all working with my knock control disabled (for now). Will start scaling that back down until it is working correctly. Thanks for all the help guys.

P.S. I have had no knock control for a year now, since my motor is so loud.

 

Ok so my original rom is 96420008. Ive got all the knock tables up and running. the only problem Im having as the scaling of RPM on the knock vs load threshold table is off. Everything else is good.

Does anybody know the correct addresse for RPM scaling in the table in 96420008?

Thanks alot.