Does it grab a sample of MAP and store it statically at start up?

That's how many deal with it.

1G or 2G setups? (cylinder head and manifold, mostly)

 

No, there is nothing at all, no start up sample or compensation maps.
I'm not sure how altitude changes are dealt with, I think a possibility is they have the Fuel Trims do all the compensation. All the Mitsu SD cars are more economy type then performance, so just a MAP sensor may be good enough.

 

Cams.

 

03whitegsr, I'm still not sure that closed loop threshold being controlled with baro compensated load is such a problem, can you measure EGT whilst being in closed loop at 5PSI relative at elevation? Is it knocking there? There are other effects on cylinder pressure, so your 90kPa absolute at 70kPa atmosphere may have lower VE for example because the turbine will be rotating faster. Most VE effects can be summarised by inlet manifold divided by exhaust manifold pressure.

Bottom line is does the stock closed loop control threshold work on a baro compensated load or a raw load? If baro compensated then obviously Mitsubishi don't think it will melt. If raw and there are knock or EGT problems that is another matter.

 

To first answer jcsbanks' question, baro+airtemp compensated load is used for the open loop threshold down to 0.78 bar which equates roughly to 7000 feet of elevation. If baro drops below that, then uncompensated load is used.

As far as incorporating an active baro signal into the SD setup, jcsbanks' concept of including division by baro into the SD masterload calc makes the most sense to me. It is simple to implement, makes SD master load even more like MAF master load, and is still compatible with locking baro at a single value for those people that don't want to deal with adding a baro sensor.

 

It seems then that the only two real remaining issues with the present patch are:

1. jrohner's situation of wanting a single map to support various boost levels so he would benefit from a 3d VE map.

2. 03whitegsr's situation of starting the engine at altitude.

 

Baro would fix the second issue, correct? As baro is used as part of the startup IPW calcs where MAP is not?

Also, I definitely have a low load low RPM issue, however I'm wondering if it is related to all of this too? Maybe my loads are so out of wack due to altitude that it's putting the ECU into conditions it really isn't meant to deal with?

 

Engine start at altitude would be handled by reenabling baro.

So 3D VE map and an option to reenable baro? We could also add an option to be able to use two 2D VE maps or use a single 3D VE map. What do you think?

 

It was mentioned some where above, but would it be possible to set it up so you could run the MAF but then log the calculated MAF if you were to run speed density?

DSMlink did this and it made it super easy to setup the VE maps. You just log the car and mak the actual MAF signal match up with the calculated MAF signal.

 

Yes, it can be done straightforwardly.

 

Ceddy did it with the DSM Ecu, so it shouldn't be too much trouble to do it to the Evo code. That would be nice. You may even be able to write a program that compares the 2 values in a log and makes a "suggested VE map". It wouldn't be live, but it wouldn't need to be. That would save some headaches.

 

My comments were directed towards my cars running the SD patch. 70kpa is 70kpa no matter what the elevation. It is the same "airspeed" in the patch.

 

I'm thinking about adding this capability. However, it will only be useful to people who use the fuel tank temp ADC to read MAT.

 

Yes, with the IAT on the MAF plug, you will have the wrong Temp scaling with the MAF plugged in.


I have the SD code in my normal MAF rom just for logging.

Then for the SD rom, Temp Scaling, Baro Lock, MasterLoad/Clip NOPs, etc, must me added.

But I just have just have two pre made roms for users, MAF and SD.
(MAF = Mitsu Temp Scaling, SD = GM Temp Scaling)



But if you are releasing as a xml DIY patch it may be to hard for users to switch between MAF and SD. (Would have to change 4 Load NOPs and Temp Scaling)

I use the video game patcher SamIPS2, you make two diff patches MAF->SD and SD->MAF, that way I can easily switch.



Edit:

Since MasterLoad and MasterLoadClip are pre IAT compensation, we may be overthinking this.

You are just comparing the MAF's signal(MasterLoad) and SD emulated signal(MasterLoadClip), IAT has no bearing on them.

If GM and Mitsu IAT scalings are not too different at normal temps, you could maybe just leave the GM scaling. Depends if user is just getting a quick log, or if going to use the MAF rom for a while.

 

Yeah, I suppose it is fair game to compare MAF master load to MAP master load before doing any temperature compensations. Sounds like a plan.