You are currently viewing our forum as a guest, which gives you limited access to view most discussions and access our other features. By joining our community, at no cost, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is free, fast and simple, so please join our community today!
I got my GPS last week and still haven't been able to get it to connect to my EVO.
I've installed PPC v2.2 of EVOScan and changed my setting to read off my 1.3 cable as per Hamish's suggestions and still no luck.
I've sent several 'support tickets' to the help desk since last week and all have gone unanswered...
Hi mate,
I got mine earlier in the week and had the same issue. The GPS thing was running an old version of EvoScan and didn't have the drivers for my OP 1.3D or OP2.0 cables.
There were directories for newer versions on the SD card. I changed the name of the EvoScanPPC folder to EvoScanPPCOld and changed EvoScanPPC v2.2 Beta to EvoScanPPC. Suddenly I had the drivers, but there were bugs in the gauges part of the app, so I downloaded v2.1 and it sort of works.
The only issue I have now is that when i try to datalog, I get a voltage error. I'm not sure if it's a pin 9 thing (I have a Legnum VR-4) or if it's something silly like the little on/off switch on the bottom of the device I only noticed this morning.
Anyways, try renaming each of the folders in the SD card to "EvoScanPPC" (one at a time) and see which version works for your car.
Macka
EDIT: My issues turns out to be that the GPS doesn't like to 2.0 cables for H8 ECU's. Luckily I also have a 1.3 cable.
Last edited by MackTheKnife; Oct 13, 2010 at 05:35 PM.
It does contain FULL sets of drivers, the 1.3D/R/U driver is prebuilt into the firmware in the \windows folder, there is no known issues with drivers on EvoScanPPC, this probably confused you a little.
Yeah, its no wonder you had initial problems, my website clearly states that op2 is only for EvoX on EvoScanPPC and op1.3U is for 1994-2007 mitsubishi's on EvoScanPPC
Op1.3U is faster for 1994-2007 mitsubishis, and op2 doesn't support ayc/acd bleeding.
Hi timmiii, yes absolutely it will work. tephra mods still just use the standard MUT datalogging, so all the same highspeed MUT datalogging goodness will still work. including 62500baudrate datalogging (which is exactly what I use) I use tephra v7 mods with big maps and I don't have rear o2 wb logging. but you just copy the data.xml line for it. actually, yeah if you didn't know, the gps navigator also uses the same data.xml format, so you can copy any lines out of your laptop version of evoscan data.xml and put it into the gps navigator to log you rear o2 WB logging.
Drives: Prepared by R/T Tuning Wrecked by Oakes Detailing
Points: 3,549, Level: 37
Daily Activity: 38.1%
Hamish aka evoscan,
any updates on getting the LM1 to log in EvoScan PPC v2.2? When last we spoke you said it would be a quick fix, that was about a month ago. lol. I would really like to tune my car but can't without logging A/F. I've tried contacting you on MSN a couple times and I'm heistant to open another support ticket because I know you're busy so any help would be appreicated.
Thanks
Hi dude, yep I still have your logs, I have another guy in Hamilton that needs the same thing for LM1... will have a new version this week for you both.
If anyone is trying to Log MAF Volts on EvoX in EvoScan v2.7.0090, set the ResponseBytes="1" in the data xml file to ResponseBytes="2"
If anyone is finding that Windows7 is making the dataitem list fonts go blurry when scrolling, then PM me for a copy of EvoScan v2.8.0004Beta.
If anyone is trying to Log 2byte Load on the GPS Navigator, PM me and I'll send you an updated version to fix this. (Prefer Load1B which is part of tephra mod roms, but if you really want 2byte load you will need the update for the v2.2 EvoScan GPSNav beta version.
I'll send you an email when its ready.
