Is there any reason why this was chosen for the Injector Duty calculation, and not the normal RPM?


I have a log of the 2-byte injector pulse width for anyone who want to see.

 

cool looks good

 

Not sure I follow what you mean chosen for the injector duty calculation? We could get a more accurate IDC in the logger by using 2 byte IPW and 2 byte RPM, but do we need the resolution for IDC? I think we do benefit from the resolution of IPW, especially at idle.

 

By default in Evoscan it uses the RPM signal from MUT 21. I was just curious why this RPM source was originally chosen when there is already another RPM source (MUT 02).

I also did some playing with MUT 8A. Is it just me or is this TPS and not Load Error?

I just noticed that MUT 98 and 99 are also sequential and maybe an OEM 2-byte item to log. So to are 80, 81, and B7, B8, B9 and BA.

 

MUT2+3 is 2 byte RPM only if someone modifies the MUT table IIRC?

 

I'm looking for a cylinder index variable, have you found anything?

 

Cylinder Index Variable, as in what determines which cylinder is which output?

MUT 2 should be of the same resolution as MUT 21, it just had me thinking why Hamish chose MUT 21 for RPM when MUT 2 was available. I guess it doesn't matter.

 

Thanx you worked this out, makes more sense for me. I was already posting the question about the same.
Correct MUT 8A is a throttle.

EvoScan/mitsulogger is based on MMCd Datalogger so they took what was already known for ALDL, hopefully it answers your question.

MUT 80 is ROM ID upper part (e.g. 8859)
MUT 82 is ROM Version lower part (e.g. 0015)
I believe 81 is reserved for future use when they will run out of the word sequence.

98 is a bit coded DTC, 99 has no sense unless the DTC table is larger.

B7, B8, B9 and BA are processor output ports states, e.g. O2 heater circuit monitoring is within

 

Mattjin, yes I want to pair "increase in knock sum" with "cylinder no" and then decay four variables - one for each cylinder, so I can get a knock sum per cylinder.

 

you want individual cylinder knock retard.

how are you going to determine which cylinder is knocking? by timing - ie we are ABOUT to fire cylinder #2, and we get knock - so #2 must be knocking?

 

Acamus, I remembered that you once wrote something about 8A, so I was sort of hoping you would chime in here. It logs as being different to the other TPS we commonly log. I cannot remember which was it was, but one was 11% and the other was 13% at idle but both went to the same 100%. I tend to believe one of them is the learned and one is the raw. The easy test is to physically move the sensor, allow the system to calibrate, and see which one moves its readings.

jcsbanks, I remember a while ago searching for a fuel cylinder trim but never found anything substantial. There is only one 2D 4-element map that looked like a candidate but I never looked into it. For 80700010 it is at 4a66 (map is 4a6c). Most likely it is nothing to do with trims but might be worth a look to check.

Tephra, you know when the knock is most likely to have occured i.e. it isnt going to happen on the intake or the exhaust phases, so it will only happen when there is some compression... therefore you know within a certain narrow range when it can occur. This is also how I would have expected the knock control to trim out some of the false knocking.

You could time which cylinder is firing based on the crank and cam sensor signals. I just haven't seen anything yet to show it.

 

Just logging initially, if I have a cylinder index variable I can store the latest knock sum increment in the right variable for the right cylinder.

 

I will just steal the thread a bit,
MUT_51-MUT_53 variables used in calculation of O2 feedback trim

MUT_54 logs "MUT_C0"
MUT_55 logs "MUT_C1"
MUT_56, MUT_57
variables used in IPW calculation

MUT_58_AFR_CT_Adder_Compensated

 

I am sorry to say John, but we will have to disassemble 4th largest subroutine to find this one out,
good news is thou it is smaller than IPW calculation, bad news is that it is larger than knock calculation. Bez once pointed to MUT_DA-MUT_DD as disabling for injectors.

Hope it helps.

 

I was looking at F9/A/B/C commands to disable injectors based on Evoscan definitions and what look to be injector enabled bits, but the routines that access them are a nightmare, but I'll also look at DA-DD. Mattjin, I couldn't work anything out from that 4 item table.