So who wants their ECU's "Chromed"?

[jras312]

Yeah the longest it would stay active was like 10 seconds, not sure what the deal
is. Im just going to wire it on pin 93 on the ecu and make changes later on if needed.

On a brighter note, up and running on e85 with rc550's and 3.5" gmMaf/maft, and the ol' 98sl ecu flashed. Can't wait to start logging WOT runs to lean out the maps and advance the timing some.

[Greg E]

So how do we log ''air mass/grams per cyl." through evoscan. Need to know what I am comparing when I go to tune the fuel maps when it's rpm vs. g/cyl.

Add this to your EVOScan XML.

        <DataListItem DataLog="Y" Color="" Display="Air Mass" LogReference="Air Mass" RequestID="02" RequestID2="03" Eval="x/512" Unit="g/cyl" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="3" ChartMin="0" ChartMax="3" ScalingFactor=".001" Notes="Measure of how many Grams of air in each cylender of the motor.&#xD;&#xA; grams/cylinder&#xD;&#xA; (x/512)  &#xD;&#xA;&#xD;&#xA;-Greg E" Priority="1" Visible="False" />

[jras312]

lol k I'll see how that goes here in like 20 mins.

[jba3]

OH! You gotta clear the codes with just the ignition on and the motor NOT running. Otherwise it don't work sometimes.

EVOScan has it's issues for sure, but it's the only program I've been able to find where I can edit it to log the parameters we need for the flashable ECUs. I'm not attached to it by any means. If someone wants to create a different program, I'm more than willing to assist.

I stumbled onto this a year or two ago when I was testing code reading / clearing for BlackStealth's LCD boost controller. My car is a 95, and doesn't seem to like clearing unless the engine is off. Not sure if it's a 94/95 thing.

[Greg E]

I stumbled onto this a year or two ago when I was testing code reading / clearing for BlackStealth's LCD boost controller. My car is a 95, and doesn't seem to like clearing unless the engine is off. Not sure if it's a 94/95 thing.

I think it has to do with the processor of the ECU being tied up with all it's calculations with keeping the motor running. That's why it's laggy when it comes to clearing codes. Jeff or Brett could probably answer this better than I can.

[jras312]

Add this to your EVOScan XML.

        <DataListItem DataLog="Y" Color="" Display="Air Mass" LogReference="Air Mass" RequestID="02" RequestID2="03" Eval="x/512" Unit="g/cyl" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="3" ChartMin="0" ChartMax="3" ScalingFactor=".001" Notes="Measure of how many Grams of air in each cylender of the motor.&#xD;&#xA; grams/cylinder&#xD;&#xA; (x/512)  &#xD;&#xA;&#xD;&#xA;-Greg E" Priority="1" Visible="False" />

So exactly how do I do this? Sorry if it's an obvious answer, not the best with computers.

[jras312]

Well I can't get ''air mass'' to show up in evoscan. What am I doing wrong? The info you posted IS in the data file under evoscan's folders.

[Jeff V.]

I think it has to do with the processor of the ECU being tied up with all it's calculations with keeping the motor running. That's why it's laggy when it comes to clearing codes. Jeff or Brett could probably answer this better than I can.

The MUT protocol in the 94 and 99 ECUs checks to see if the engine is running before allowing you to clear codes. It looks like OBD2 will let you clear codes with the engine running though.

If the ECU was too busy to do something as simple as clearing codes, you'd never have enough power to actually log anything.

[Greg E]

The MUT protocol in the 94 and 99 ECUs checks to see if the engine is running before allowing you to clear codes. It looks like OBD2 will let you clear codes with the engine running though.

If the ECU was too busy to do something as simple as clearing codes, you'd never have enough power to actually log anything.

Looks like I got some bad info from someone......... (as usual)


Updated the Q/A post and rehosted the links for you guys!

[jba3]

The MUT protocol in the 94 and 99 ECUs checks to see if the engine is running before allowing you to clear codes. It looks like OBD2 will let you clear codes with the engine running though.

If the ECU was too busy to do something as simple as clearing codes, you'd never have enough power to actually log anything.

I think you mean 94/95 and not 94/99? I wonder why they decided to only allow clearing codes with the engine off. Strange.