test report for the EDM 88840016 :
Everything works great

as shown in this 4 gear WOT log with a target load of 260

time interval variable was set to 3 . With this value I get some boost overshoot in 2nd gear WOT (in 3/10th of a second the load goes from 225 to 280) . So I will try next week with 2

 

^^ yeah i've been lowering the interval as I discover more and more load spike situations where it needs to be even quicker.

 

Added instructions for 96420007, and 96420008 ROMs (Some 2004 USDM Evo VIIIs) in the first post. If your ROM is not on the list, let me know, and I'll prepare instructions for it.

 

94170015

 

Next on the list. Hopefully by this weekend. :-)

 

Bro, why are you running so much negative timing ???

 

agreed . its the OEM mitsu EDM 88840016 ignition map ! Up to now I have concentrate on fuel & turbo . As it is almost ok now I'm gonna start ignition soon.
Can anybody with an IX with a similar configuration give me some advices on how/where to start . Thanks

 

Start at 1-2* advance at 3500-4k and log. You will probably need to tweak AFR once you start adding timing in.

 

I have been trying to find out how to find the addresses for the tables that need to be added to the .xml files.

Both for boost control and 2 byte logging for my EVO 8 EDM romid 96530006

Do I need a disassembler to do this ? or will a hex editor do ?

regards
Gudmundur

 

You need a disassembler to do this, IDA pro seems to be a favorite. Have a look this site for more info http://www.aktivematrix.com/forum/viewforum.php?f=11

MB

 

Ok I will start with +2* in the cell at 3500+ and load 160+
should I change all 3 high ign. tables or just table#2 (despite some search in the forum , still not clear for me what are the purpose of table #1 and #3)

 

You will have to change all 3. The ECU will interpolate from all 3 High Oct. Timing Maps and you will be very frustrated unless you set them all the same

 

Assuming the stock boost control system is a PI Controller (as it must be), then it should have (or we should be able to access) two separate TBEC tables, a Proportional (short term) error correction & an Integral (long term) correction.
Otherwise, with just one of these corrections we will only be able to partially control the boost error, either the initial spiking, or the long term boost "creep", but not both.

Ideally, we also need a gear dependent delay time adjustment (or some form of boost compensation), because the system's response time should be much faster in 2nd gear than in 5th gear, for example. An over-sensitive (very fast) boost error correction in higher gears may cause a lot of boost oscillation, while it may actually be needed in lower gears to "catch up" with boost spiking.

All these variables are incorporated in other boost control systems, such as the AVC-R and the stock Subaru system.

 

Its not quite a PI controller. Instead of a proportional correction, there is just the baseline duty cycle vs rpm tables (Max WGDC tables). It does have an integral term though which is controlled through the "correction interval" value and the TBEC table. Despite lacking a true proportional term, it works pretty well. With my direct boost control mods (different thread), I get exactly the same boost in 3rd-6th gear (within the limits of spool-up at low rpm). I can get very close to the target boost in 2nd gear (might run low by 1/2 psi on some runs). 1st gear is a write-off. The boost control hardware are not fast enough to allow significant closed-loop operation in 1st gear.

When I get a little better at assembly code, I will likely introduce a true proportional term so that the BCS can be run at 100% until nearing the target boost.

 

mr. Fred - Figured you the best person to ask about this.

What exactly is the "min temp for full boost control" What does it do if you are below the threshold?