Hi,

if you wanna create/query with evoscan and look for a new CAN pid, you do the following in the xml file:

<DataListItem DataLog="Y" Color="" Display="CAN2116" LogReference="CAN2116" RequestID="2116" Eval="x" Unit="NONE" MetricEval="" MetricUnit="" ResponseBytes="4" GaugeMin="0" GaugeMax="8000" ChartMin="0" ChartMax="8000" ScalingFactor="0.01" Notes="CAN2116" Priority="1" Visible="False" />

However, anyone understand the CAN6-0:
<DataListItem DataLog="N" Color="" Display="Boost (MAP)" LogReference="Boost" RequestID="CAN6-0" Eval="0.49*x" Unit="kPa" MetricEval="" MetricUnit="" ResponseBytes="1"

to what does the CAN6-0 resolve to? it doesnt seem to be CAN2106 byte 0 as anyone would expect...

thanx for your time.

Mart

 

If you use mode23 then you can set any MUT address you like... CAN already has all of the available parameters in EvoScan. there are no more to discover. but there is plenty in Mode23 to discover if you disassemble and compare the ROMs like Golden and Tephra.

 

Hi,

I am talking about mode 0x21. I know mode 0x23 is better bla bla. I cant do it right now.

I have some not very useful parameters in mode 0x21 that are not listed in your xml.

Can you please answer the previous question?

Regards,

Mart

Mart