that should work.

whats the RPM_SPEED_RATIO_AVG showing?

 

RPM_SPEED_RATIO_AVG 747.2 with occasionaly 746. Gear is always "1"

 

u sure its not conflicting with other entries in evoscan?

 

Not logging the same mut request as far as I can tell. How else would it be conflicting? The gear and RPM_SPEED_RATIO_AVG was working on my 9653 rom. Pretty much the same evoscan xml.

 

I should have checked this thread before I post the exact same problem with 94170715 V7 at another thread.

Do we have any update on this one?

Now I am trying 96530706 V7 instead, but now I am encoutering all the other issues related with fuel as others have tackled for a while. (But other V7 functions including gear based boost control works great)

I know that would be extra efforts from Tephra and other ECU gurus, but it would be greatly appreciated if all the V7 functions work with 94170715 rom.

 

As for the gear based boost control, you need to make sure to set up the "RPM Speed to Gear" table properly.

00.0000 6
43.3186 5
61.9912 4
84.6903 3
117.301 2
176.195 1
2899.78 0

"Main Map Wastegate Duty" for the 0 and the 6 gear columns should be all 0

Lastly, your MAP sensor must be set up correctly as well.

 

Thank you again for your reply, Paul.

So 94170715 V7 gear base boost control works for you? As chmodlf posted, my RPM_SPEED_RATIO_AVG and Gear shows almost same(~747)/same(gear=1) value regardless of gear.

If that is only the MUT logging problem, I guess there is no reason why I struggle with 96530706 rom.

 

I don't use ECU boost control. I just wanted to make a suggestion to try and get you going in the right direction.

According to Tephra the logging "problem" should work as seen in previous posts here.

 

Yes, I think it should work as Tephra said, but I get the exact same logging problem as chmodlf said.

My MUT table is same as his, and I do not think it is a logging problem, because I get correct values with 96530706 rom.

I didn't try zeroing out the WGDC of 0 and 6 gear, so I might try that see if it works regardless of the logging problem.

Thanks for your help.

 

MUT table values are incorrect on the table Chmodlf posted

00 = 859C
01 = 859D
02 = 893A
03 = 893B
04 = 89BA
05 = 89BB

These settings should cure your errors in logging. (Remember to put =0x when entering new values into the MUT)

 

Thank you again, Paul, but I have problem logging MUT40, 42/43 = gear and rpm_speed_ratio_avg.

Are those MUT values are for 2byte load / airflow / rpm stuffs?

 

What you are logging is the 2 bytes (RPM, Load, Airflow). This is different from what Tephra put in his v7 roms 9653 and 94170715. Remember MUT logs what you the end user wants. There are no "wrong" answers here. MUT is only logging parameters not changing the way the code itself works. 2 byte RPM is unnecessary. 2 byte load can also be replaced by 1 byte which is in some sense a more efficient way of logging load. My only advice is to be careful which MUT addresses you overwrite.

BTW Some of my MUT requests are logging different compensated loads (temp, and baro and temp) which depending on which rom are used rather than the uncompensated or raw load.

 

As you can tell by my above posts with Tephra, we were unable to fix this problem. The rpm-speed ratio can be solved by dividing RPM by speed. That is what this MUT request was doing anyway in the code. You could even set it up in excel.

Here is the XML for Evoscan for the rpm speed ratio

<DataListItem DataLog="Y" Color="" Display="RPM/Speed" LogReference="RPM/Speed" RequestID="CALC" Eval="[RPM]/[Speed]" Unit="unit" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="RPM/Speed" Priority="2" Visible="False" />

This is the XML I am using for evoscan for gear. It works pretty well.

DataListItem DataLog="Y" Color="" Display="Gear" LogReference="Gear" RequestID="CALC" Eval="([Speed]*225)/[RPM]" Unit="unit" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="" Priority="2" Visible="False" />

NOTE you can change the priority to 1 to have the logging occur every sample vs every other like I have set.

Not having these is more of an inconvenience. It is troublesome that tephra could not solve the problem. I started down the road of dissasembly but I have had a crazy schedule this last month. Couple that with a head gasket install and well, you get it. It does make me wonder if there are bigger errors in that code lurking somewhere. I have to say though the 94170715 is working great other than these two small issues.

 

Sorry for my confusion. I just noticed that there was differences in your MUT and mine.

 

Thanks for your input. 94170715 was working great indeed.

The actual logging of RPM_SPEED_RATIO_AVG is not a big deal, since we can get pretty close value from the calculation (tire size + gear ratio), but I just want to use the gear dependent boost control function which makes Tephra V7 even more desirable.

Anyhow, I wish I could do disassembly myself, but I gave it up after I couldn't get the tool which ECU gurus here use most.

Well, I guess it is time to try to find it again.

I hope you can get a fix once you have time.

Thank you for your efforts!