There are weekly EvoScan usergroup meetings, where we all get together in a voice channel using a teamspeak server, and connecting to a demonstration PC via TeamViewer. Where we will talk about logging, tuning, features, questions, answers. Even if you don't have a microphone you can you join the chat group on msn messenger, add me hamish_ahern at hotmail.com

Download Teamspeak from www.goteamspeak.com and connect to nickware.dnsalias.com:8767 channel: "EvoScan UserGroup"

Download Teamviewer from www.teamviewer.com
Click on the "EvoScan UserGroup" TeamSpeak Channel Name to view the TeamViewer ID and Password for the group shared desktop screen.

Weekly Sessions: (Eastern Daylight / Summer Time)
Friday 5:00pm-8:00pm (GMT-4)
Saturday 3:00pm-6:00pm (GMT-4)

 

Would it be possible for you to post the minutes for these meetings. I think they would provide a great resource for those of us who are unable to attend. Maybe we could finally get some official Evoscan documentation started

 

Quick question - Can data be logged to a folder other than the default in EvoScan? Such as an SD card? Thanks

 

Its hardcoded into EvoScan, but thats a good idea, perhaps I'll put a setting that you can change the default file path for logging. If the folder set by the user doesn't exist then it would default back to the original location.

 

Am building a new website, which will become the basis for a huge resource for all the 16Gigabytes of Mitsubishi documentation I have on my harddrive lol

I can also record the shared desktop session, I'm not sure how to record the sound though and join them together though.

 

I would appreciate that. It would make it easier to transfer logs since they can be stored on removable media and it would prevent the hard drive from getting so hot as it is continuously writing. Thanks

 

How to get Mitsubishi AYC/ABS support from an OpenPort 1.3U cable.
Step 1) Pin1 must be linked to pin15.
Early OpenPort cables did not have Pin15 linked to pin1(check with a multimeter continuity test) to see if its connected.
a) No pin1 on the OpenPort cable. Move pin1 on the vehicle side to the pin15 position.
b) Pin1 is connected to Pin4/5 on the OpenPort cable. Move pin1 on the vehicle side to the pin15 position.
c) Pin1 is connected to Pin15 on the OpenPort cable. Cable is AYC/ABS ready.

Step 2) Try logging with EvoScan v2.5 or later. Select Mitsubishi, and select ECU to "AYC" or "ABS", Press start datalogger. If it doesn't connect, then perhaps you have pin9 interference. Goto Step 3.

Step 3) Subaru 2002 vehicles use Pin 9 for reflash support, but it interferes with the AYC/ABS ecus on some Mitsubishi obdII ports, so you can either break pin9 off the OpenPort Cable, or put a switch on pin9 on the vehicle OBDII connector.

 

Hamish,

Any updates on Evo 10 and OP 2.0 EvoScan version?

 

I am struggling to find a spare Evo10 ecu to test on, can you help find one on ebay or wreckers for up to $250USD?

 

Hamish,
can you add an option to only load the hex file in addition to loading the two files currently? The reason is after the first time loading the base xml and hex files, we'll only need to load the hex file again since it's what will be modified when tuning. The current work but I have to load both files every time which is tedious. Also, remember the last directory when loading the file will be nice addition. Thanks.

 

Yep, already done a few weeks ago, you can beta test it if you like, add me on msn, hamish_ahern@hotmail.com

 

thanks! i love to. Will send you an email for it.

 

do you require the actual physical ecu or just the .rpg data,

 

cool, the first fellow NZer I've seen in a long time I require the actual EVOX ecu, as I connect up the pins and test via the CANBus and/or MUTIII diagnostic line. I already have access to an MUTIII with EVOX support, I just need the ECU so that I can listen-in on the CANbus or MUTIII diagnostic line.

 

is the fact the variant coded ecu's going to pose a problem?