my buddy has it on his sti sounds bad a$$

 

heck yeah! How would i be able to set my evoscan to record that particular memory location?

 

94170008 0xFFFF88A3
94170014 0xFFFF88A3
94170015 0xFFFF88A3
88590015 0xFFFF6A35
96940011 0xFFFF88DF
88840016 0xFFFF6A1D

OK so same way that you do 2byte load... So setup MUT00 (or whatever) with the memory address from above, so if you are 94170008 set MUT00 to 0x88A3.

Then setup evoscan to log Mut00 as a single byte (not 2byte) and then log it.

When you get on the clutch it should read 0x1 and off should read 0x0. NOW there are other flags in there as well, ie acceleration is 0x16. So if you are on the accelerator AND the clutch it will read 0x17.

Cheers
D.

 

Tephra-

So just to check what your saying here as I am a little confused, if I have evo9 ver15 then I add the following to EcuFlash definition

<table name="MUT00" category="MUT" address="88A3" type="1D" level="1" scaling="Hex16"/>

Add this to EvoScan, can you fill in the blank.

<DataListItem DataLog="N" Color="" Display="Clutch Switch" LogReference="ClutchSwitch" RequestID="??" RequestID2="??" Eval="" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="8000" ChartMin="0" ChartMax="8000" ScalingFactor="1" Notes=""/>


Thanks

 

nope

Dont add any new XML into EcuFlash - just go and change your MUT00 (in the mut table) inside EcuFlash to poing to 0x88A3

Inside EvoScan just add this:
<DataListItem DataLog="Y" Display="ClutchFlag" LogReference="ClutchFlag" RequestID="00" Eval="x" Unit="unit" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" Notes=""/>

 

I don't see any MUT table??

 

GRRR You are 88590015 right? Add this to your XML in EcuFlash

<table name="MUT Table" category="Advanced" address="3ee84" type="3D" level="1" scaling="Hex16">
<table name="X" type="Static X Axis" elements="32">
<data>-</data>
<data>0</data>
<data>-</data>
<data>1</data>
<data>-</data>
<data>2</data>
<data>-</data>
<data>3</data>
<data>-</data>
<data>4</data>
<data>-</data>
<data>5</data>
<data>-</data>
<data>6</data>
<data>-</data>
<data>7</data>
<data>-</data>
<data>8</data>
<data>-</data>
<data>9</data>
<data>-</data>
<data>A</data>
<data>-</data>
<data>B</data>
<data>-</data>
<data>C</data>
<data>-</data>
<data>D</data>
<data>-</data>
<data>E</data>
<data>-</data>
<data>F</data>
</table>
<table name="Y" type="Static Y Axis" elements="16">
<data>0</data>
<data>1</data>
<data>2</data>
<data>3</data>
<data>4</data>
<data>5</data>
<data>6</data>
<data>7</data>
<data>8</data>
<data>9</data>
<data>A</data>
<data>B</data>
<data>C</data>
<data>D</data>
<data>E</data>
<data>F</data>
</table>
</table>

 

very cool, thanks soo much.

 

Dave, I give you so much credit for the massive amounts of patience you have. I have been using ECUFlash and evoscan for a little over a week now and its like greek to me, (though I'm not new to this stuff in general) yet you are always willing to help the newbies with the programming hurdles.

 

Hate to bring this back from the dead, but I don't understand the x bits at all. Can someone explain/show me the correct x bit to log only clutch operation?

Thanks!

 

Ok, I think I've got it. The Evoscan formula for logging clutch discreetly with that MUT value at 00 is

And furthermore acceleration would be

That could be interesting to see what conditions cause the acceleration flag to be set related to MAF tuning.