So do I simply edit the numbers to what I want in MPH? Or does it have to be an exact conversion from KPH-MPH? And can I log any AFRs without an aftermarket wideband? How do I fix the datalogging error?

Thanks, Jered

 

Press the power button to bring up the options screen, and then press the three dots (ellipsis) and then click on settings, change from metric to imperial. and restart the android. Failing that, you can edit the xml file, and put the mph formula in both the metricEval and Eval field. and copy it to the evodroid datasettings folder overwrite the existing xml.
You need an aftermarket wideband sensor (mitsubishi does not install one at the factory), to log Air Fuel Ratio for tuning or engine safety. you can wire it directly into the evo ecu, and log it via the xml file.

 

Hamish sent you a message through the site. I reset the device and need to download the APK. Can you PM me a link?

 

send me an email evodroid at evoscan.com thanks.

 

Ben Wiggins: Run your MAP sensor out put to Pin 75 on the ECU.

Then you'll be able to log boost through Evoscan via Request 3C.

 

Hamish could we have a page on evoscan.com with index and quick links to problems and solutions for the evodroid? DIgging thru this thread is a pita ie. why the temp logging doens't work

 

grimgrak: can you try logging it with the Eval and EvalMetric formula set to just "x" does it work ok then?

 

Hamish, I will email you politely begging for a link to reinstall the software on the droid because I am concerned about the fact that when the app launches, it immediately displays 1.8billion errors. Let me see if copying the xmls fixes it first.

Thanks for your help

 

Grimgrak I have got mine working. Had to change something in the xml. I will have a look at the original and my modified 1 and post up the changes.

Thanks benja I'll try that out. Where did u get a pinout diagram for the ecu?

 

In the Original XML file:

line 25: Display: Air Temperature, Log Reference: AirTemp xxxxxxxx

looks like this..

In the XML that i have changed:

line 25: Display: Air Temperature, Log Reference: MAFAirTempScaled (copy line 26 from Log reference on and put into line 25. line 26 should be "MAF Air Temp Scaled"

this seems to be working for me with intake temps 2 deg higher than ambient. and rises by 5 - 10 deg on WOT.

Anyone please chime in if i am actually logging way off track!

hope that helps Grimgrak

 

Hamish,

Thanks for your reply. I copied EvoX Mode23 USA.XML into the EvoScan\DataSettings\ folder on the EvoDroid7. For some reason the transmission temp is not logging. It is returning a value of -50. Thus value is always reporting as '0.' It is strange, all of the other items log properly. When I log with evoscan via my lap top computer it logs fine with same XML. I am not to point the where I can I am building gauges yet because I am not getting trans temp data. The whole reason for getting the product was to monitor trans temp. Please advise. I am not software guy.

Please advise

Line item from XML file (Mitusbishi EVOX Mode23 USA)
DataListItem DataLog="N" Color="" Display="MR/SST Transmission Temp" LogReference="SST_TM_Temp" RequestID="CAN28-0" Eval="x-50" Unit="Deg F" MetricEval="x-50" MetricUnit="Deg C" ResponseBytes="1" GaugeMin="0" GaugeMax="1000" ChartMin="0" ChartMax="1000" ScalingFactor="1" Notes="" Priority="1" Visible="False" />

Options setting selected in Evodroid evoscan

Select vehicle: Mitusibusi
Select Country: USA
select Year: 2008
select ECU: Mitusbishi EVOX Mode23 USA
Select Cable: OpenPort 3.0 ODA
Units: Imperial - I did notice notice a difference.
Application folder path- I left blank. I do not know purpose.

I selected (checked ) the item that I wanted logged to Evodroid7Datalog.csv, included MR/SST Transmission Temp

 

[QUOTE=evoscan;11132620]Hi Rob,

You can copy your xml file Mitsubishi EvoX Mode23 USA.XML file from the windows based evoscan, and place it in your EvoScan\DataSettings\ folder on the EvoDroid7

And you can edit the EvoScan\GaugeTemplates\854x480_Carbon1.txt file to alter the LogReference to display any of the dataitems listed in the xml. ensure the spelling is correct.

Hamish,

Thanks for your reply. I copied EvoX Mode23 USA.XML into the EvoScan\DataSettings\ folder on the EvoDroid7. For some reason the transmission temp is not logging. It is returning a value of -50. Thus value is always reporting as '0.' It is strange, all of the other items log properly. When I log with evoscan via my lap top computer it logs fine with same XML. I am not to point the where I can I am building gauges yet because I am not getting trans temp data. The whole reason for getting the product was to monitor trans temp. Please advise. I am not software guy.

Please advise

Line item from XML file (Mitusbishi EVOX Mode23 USA)
DataListItem DataLog="N" Color="" Display="MR/SST Transmission Temp" LogReference="SST_TM_Temp" RequestID="CAN28-0" Eval="x-50" Unit="Deg F" MetricEval="x-50" MetricUnit="Deg C" ResponseBytes="1" GaugeMin="0" GaugeMax="1000" ChartMin="0" ChartMax="1000" ScalingFactor="1" Notes="" Priority="1" Visible="False" />

Options setting selected in Evodroid evoscan

Select vehicle: Mitusibusi
Select Country: USA
select Year: 2008
select ECU: Mitusbishi EVOX Mode23 USA
Select Cable: OpenPort 3.0 ODA
Units: Imperial - I did notice notice a difference.
Application folder path- I left blank. I do not know purpose.

I selected (checked ) the item that I wanted logged to Evodroid7Datalog.csv, included MR/SST Transmission Temp

???

 

Havn't tried it yet but is scanning for service engine soon lights the same as with the older evo scan cables? If so does anyone have a link of how to pull codes?

 

The current android version won't read or clear DTCs. You need PC based Evoscan.

 

Hamish, having used the software for a while now I was wondering if we could get a status update on bugs and feature requests and what would be in the next version.

Firstly we need to compile a list of them.

1. template switching doesn't work which means that you can only have one gauge display.
2. having to unplug the cable to get it to reconnect.
3. circular bar gauges work but linear bar gauges don't work.
4. trigger images don't work.

Also it would be useful to have a list of compatible tablets.

My Samsung Galaxy tab 3 works very well but with one bug that has a workaround.

Thanks...