94170715 V7 Issues
#136
Evolved Member
iTrader: (5)
My car doesn't go silly lean as yours did when giving it gas.
#138
Evolving Member
iTrader: (2)
MUT00 / 01 are predefined as airflow rate at 94170715 V7, so if you do not log airflow rate at the same time, you should not have any problem.
This evoscan definition should work (just display 8 bit data as 0~255 integer):
<DataListItem DataLog="Y" Color="" Display="Tephra_Var" LogReference="TephraVar" RequestID="00" Eval="x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
Last edited by ace33joe; Apr 12, 2010 at 06:36 PM.
#139
Evolved Member
iTrader: (5)
Indeed AND I have the problem solved!
The solution was simple just renabled closed loop and the SWFT for the o2 sensor kicks back in stopping the weird AFRMAP dip. I'm not sure why this is but it must be something related to temperature.
I discovered this by reading an old post where AFRMAP was moving around on its own. MrFred said that it was related to the o2 sensors so on a hunch i enabled closed loop again solving the problem.
So warning to those using SD and tuning with open loop disabled
The solution was simple just renabled closed loop and the SWFT for the o2 sensor kicks back in stopping the weird AFRMAP dip. I'm not sure why this is but it must be something related to temperature.
I discovered this by reading an old post where AFRMAP was moving around on its own. MrFred said that it was related to the o2 sensors so on a hunch i enabled closed loop again solving the problem.
So warning to those using SD and tuning with open loop disabled
#144
Evolved Member
iTrader: (5)
I also noticed that AFRMAP was rock solid until exactly 70C engine temp on my car which may correlate to the min temp for closed loop variable.
#145
Evolved Member
Thread Starter
iTrader: (19)
Join Date: Oct 2004
Location: CT
Posts: 885
Likes: 0
Received 0 Likes
on
0 Posts
Any progress on the boost problem? Has mrfred looked at this??? I can't log the above MUTs as my car is apart. I have a race Sun. that I am trying to make. Any news/help would be appreciated.
#147
Evolved Member
iTrader: (4)
I plan to change MUT00 address to 0x8CCD temporarily and log it at evoscan as is (no scaling).
MUT00 / 01 are predefined as airflow rate at 94170715 V7, so if you do not log airflow rate at the same time, you should not have any problem.
This evoscan definition should work (just display 8 bit data as 0~255 integer):
<DataListItem DataLog="Y" Color="" Display="Tephra_Var" LogReference="TephraVar" RequestID="00" Eval="x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
MUT00 / 01 are predefined as airflow rate at 94170715 V7, so if you do not log airflow rate at the same time, you should not have any problem.
This evoscan definition should work (just display 8 bit data as 0~255 integer):
<DataListItem DataLog="Y" Color="" Display="Tephra_Var" LogReference="TephraVar" RequestID="00" Eval="x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
#149
Evolved Member
iTrader: (5)
I was on a tangent but just a related 94170015 issue. I found the solution to my afrmap going all wonky but I didn't have a solution to the gear based boost control.
Side notes:
I do have a log of some brief interaction of my red being controlled by psi based boost control but nothing to really test out the gear based boost. I really need to turn down my boost via the map and see if its more heavily controlled and get more accurate results :P