I know in normal evoscan theres a setting to disable that as it indicates diagnostic mode for a dealer scantool.

 

My tablet won't boot up properly now, its stuck at Android splash screen... Was working earlier lol any tips on to get this thing working again?

 

Can you expand a bit on what it took to get Evoscan working on the Galaxy Tab.

I am attempting the same thing on a Nexus 7 but I'm not quite there yet.

I haven't been able to access the installer on the website. From what I can gather most people are finding this so I copied the evoscan and backups directories from the EvoDroid to the Nexus. With the Nexus (version 1 not 2013) recently upgraded to Android 4.4 :

1. I ran the Evoscan.apk in the backups folder. It appeared to install without issue.
2. It was having trouble with the gauge file names not matching the screen size. I copied the existing files to new ones named 800x1205_Carbon1. png and .txt and 1280x736_Carbon1.png and .txt. These don't render quite right and will need modification later to suit the higher screen resolution but for the moment they get us through to the next step.
3. Initially the Nexus didn't know what to do with the USB cable and was taking me off to another unrelated web site. I enabled developer mode, then enabled USB debugging (the EvoDroid is set up this way).
4. Evoscan now starts and runs to the point where there is the "Re-plug in the Open Port Cable" message in the top right. Replugging doesn't bring about any change of state.
5. Nothing indicated that the device had to be rooted but I decided to give it a try. It made no difference to Evoscan, the only change I have noted to date is that the MPT USB mode from the Nexus to my PC is now broken. Something else to fix.
6. The only other thing to report is that Evoscan installs to start whenever the Nexus is started. I can't see where to turn this option off. This causes evoscan to hang when the device first starts up. You need to stop and restart evoscan once you gone past the lock screen. I suspect that this might be caused by a conflict with the lock screen.

 

I was never able to get it to show water temps in imperial even though thats what its set to.

Any word on flashing ability yet (I know its early)

 

When I plug the 1.3DA droid cable in and use the droid my AFR's with a AEM EUGO are cruising around at 10 AFR .
When I use the evoscan cable it reads normal. Is there something simple to select to have them read similar?
It is not using the inputs on the new cable.
It was being read with the old evoscan cable thru the stock ECU.
There are only 3 options in wideband selection Aem being the one i selected... I have selected all 3 and the all seem to stay in the 10.0-10.99 AFR range in the WB02 Column of the CSV file
This is the sensor/gauge I have
http://www.aemelectronics.com/wideba...safe-gauge-84/

 

Has anyone gotten a wideband to work with this that did not use the inputs on the new cable?

 

All I want for christmas is to be able to log my AFR's on EVODROID :O

 

12

 

Got my EvoDroid in three days ago, was so stoked and excited to get using it. Spent the last three days trying to get it to work, not so stoked now. This thing throws up all types of error codes, can't get any of the gauges to work. I have tried every vehicle setting, country setting, model setting, wideband setting, even tried switching out the cables. The newest code error is NullPointerException. As of now I would not recommend this to anybody unless I can get some feedback or assistance from Hamish. Please if someone can explain some options or setup assistance, would be appreciated. If not this thing must go back.

 

Sounds like your new to evoscan.

 

Yeah a little new, learning process. Just a few pointers would be great.

 

subscribed

 

It was set up to work with EvoX out of the box. I was datalogging an EvoX with it 10 seconds before putting in your box and sending it. Try and untick all the dataitems. select EvoX, and select OpenPort 3.0DA that should take it back to the defaults. try TPS and RPM firstly. then tick more items. when changing Vehicle type or Cable type.. select the settings, close the app, click as per the video guide on the task manager, slide to close the app.. start the app. plug in the vehicle, and the datalogger will start automatically.

 

Sweet success, got the RPM, Throttle POS, Battery Charge and the Speedo working. Still need to try some data logging but seams to be working nicely. Was trying to change out some of the List items with no luck, also still wont display temperatures or knock. I know someone else on this thread had this problem but cant seam to locate where it is. Any ideas or suggestions you might have? Thanks in advance

 

The temperatures in the standard gauge display don't work because they don't map the correct LogReference. The following fix worked for me:

Open the appropriate XML in the Evoscan\DataSettings Folder. In your case it is probably Mitsubishi EvoX Mode23 USA.xml. (If this bit makes no sense on its own you will need to backtrack through this thread and figure how to hook up to a PC - post #785 here. If you haven't already, make a backup of the \EvoScan directory).

Check the logReferences for "Manifold Air Temperature (MAT)" and "Engine Coolant Temperature (ECT)"; i.e. two lines that will look a lot like this:

The LogReferences you are after are IAT and ECT respectively.

Now open the two gauges .txt files in the \EvoScan\GaugeTemplates directory and correct the LogReference entries. These appear to be the third entry in the line, so

gets changed to

Repeat for the other 2 entries in the two files.

I have also just noticed that Windows Notepad doesn't pick up the end of lines in the .txt files and it gets particularly hard to follow the structure. It does display OK in Notepad++. You can get Notepad++ here