Absolutely. The older versions used a LITTLE endian and the newer ones use a BIG endian.

 

For anyone upping the ante to 2.2b
RPM 2-byte
2.1 fix: 1000*x/256
2.2 value: 3.906*x
I believe these are the same, there may be the smallest rounding error (actual is 3.90625) but I think I'll probably stick with the default.

 

for guys using the tephra v5 and need to know the raw volt coming from the ADC input or to see if your in your alt map using evoscan

you can setup a new MUT request to log 0xFFFF8425, if its 0 then you are on standard maps, if its on 3 then you are on altmaps. The evoscan address below is requesting ID 08, so I would go into my MUT table change the value thats was currently there to 8425.


<DataListItem DataLog="N" Color="" Display="Map Switching" LogReference="Map Switching" RequestID="08" Eval="x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Notes="0= standard map 3= alt map" Priority="1" Visible="False" />


0= 0 volts 255=5 volts

<DataListItem DataLog="N" Color="" Display="ADC Input Signal" LogReference="ADC Input Signal" RequestID="83" Eval="x" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Notes="0=0 volts 255= 5 volts" Priority="1" Visible="False" />

I dont think this a problem or fix, LOL

edit*** dont request ID 06, that is for timing

 

I know the formula for WGDC is x/2, but is this formula for WGDC x/2-64 correct also?

 

Id like to know that and what the correct formula/addressing is for wgdc correction %. I'm flatlining 16 as soon as I hit boost.

 

has anyone had a problem logging there innovate lc-1? it was working fine but i had to redownload evoscan and now its not logging anything...

 

I take it you downloaded evoscan 2.2?

if so I'm pretty sure it doesn't work on that version yet.

.....best to go back to the version you were running.

 

Nope, im on 2.1 still....

I select it to log wideband and nothing comes up.

 

2.1 works for me with the LC1... however your best bet is to wire the analogue output into the ECU (rear 02 input)... LC1 serial sux the bigone

 

Ive been wanting to do that, I guess ill try that tonight and see if it fixes my issue.

 

just do the mrfred mod, did it to my ngk wideband works like a champ

https://www.evolutionm.net/forums/sh...d.php?t=337823

can logworks read the analog output from your lc-1

 

What is the correct request ID for Fuel Consumption, Gear, & IDC all of them request ID 21. Just notice that today looking thru my data.xml

 

lol it hasnt worked right since .97 and I see no effort or very little to address the multitude of problems in this If I thought it would work I would ask for a full refund since I purchased the .9x and the 2.x versions. Oh and upgrades are free he tells me . Too bad every upgrade breaks something else and what about the maptracer why does changing the injector scaling under load from 513 to any value break it completely?

 

Am not sure if it's a mistake or correct reading, I'm getting

Display="Fuel Trim Low (LTFT)" LogReference="FuelTrim_HIGH" RequestID="0C"
Display="Fuel Trim Mid (LTFT)" LogReference="FuelTrim_Mid" RequestID="0D"
Display="Fuel Trim High (LTFT)" LogReference="FuelTrim_Low" RequestID="0E"

The data.xml is unaltered. Should displayed, fuel trim low same as log reference fuel trim_low? Same goes for fuel trim high.

 

I happened to notice this almost immeditaely after 2.1 was relaeased and informed Hamish and he responded back to me so I know he knows of the typo. We'll see if he fixed it in v2.3