GPS portion works, why would the the gps need a com port anyway?

 

I have not subscribed to msn messenger (or any other instant messenger), it would be one more piece of software to learn and get working; I would prefer not to at this time but I will if I have to. I am busy searching for and reading every thread I can find on EvoScan gps in hopes of actually being able to use this cool device!

My GPS came with no documentation, none, zip (except for the map sw with I could care less about till I get the EvoScan sw to work) Is there not a "quick start guide" somewhere? Anywhere? How is it supposed to be wired up, what wire goes where? Why does it keep asking me for a com port name every time I plug it into the op2 cable? What is the name of the com port? How would I type anything into the pop up window even if I did know what to type In?

2010 Evox MR-T

The ECU is flashed with mode 23 and I am able to log with v2.8 of the windows software.

The data card has v2.2 beta on it.

In EvoScan options "OpenPort 2.0 Cable" and "EvoX Mode23 USA RA" are checkmarked.

The 5 volt included power supply is plugged into one pigtail of the the included "y" cable.

Other pigtail of "y" cable is plugged into GPS.

The red pwr light in the upper right corner is on.

The UPS end of the "y" cable is plugged into the op2 cable using the included USB to mini extension cable.

The cars ignition is on.

If I start EvoScan first then plugin the USB end of the "y" cable into the OP 2.0 cable I get the popup asking me the name of the com port, if I close the popup I get: "Auto connect retry #*** No OpenPort 2.0 Cable Conn. or No Pwr. Auto retry in 2 seconds..."

If I reset the sw or do a hard reset I get the same result.

If I plug the OP 2.0 cable in into the "y" cable before I have started the EvoScan sw, I get the same result.



Anyone?

 

yes for OP2 EvoX it is still beta. The drivers were fudged to get them into the system since I lost support from the manufacturer to embed them in the rom, hence the soft reset, but runs just fine for extended periods of time.

but for OP 1.3U Evo4/5/6/7/8/9 it is rock solid. I run it daily for 8 hours some times, and it never crashed on me using v2.2

 

Interesting post. I will comment on your last few questions. EvoScan reads the ECU parameters using the Mitsubishi MUT protocol, but (and correct me if I'm wrong) DashDAQ reads data via the OBD protocol which is much much slower than the MUT protocol.

 

Yeah but mine never runs at all! It would be nice if I just get it started once then deal with occasional crashes.

 

kmart888 sounds like your sdcard has had files deleted by accident. I'll send you the EvoX zip folder that we are all using. . you have PM.

 

Hi, Hamish

I have similar kmart888 problem. In my case the popup windows ask for usb driver instead com port as I send mail told you today.

Please contact me either email or msn. I am waiting for your help.

 

I installed MS Live Messager and TeamView as instructed in your PM last night, still waiting, can anyone ? A driver file, if that is what I need, by email would helpful.

 

toeng, THIS is the problem I had and solved by not plugging the openport into the evoscan unit until after evoscan started. Trying shutting down the unit, boot it up, start evoscan and then plug in the openport. That solved my issue. kmarts comm port issue does seem different than mine/yours and so I'm not surprised my suggestion didn't help.

That said: Hammish, is there a way to avoid needing to do this? If not I'll survive but it would be nice if I didn't have to.

 

My mistake, we have the same problem, my popup does indeed ask for the name of the USB driver, not the "com port" I just ran out to the car and checked.

 

My problem is the same as "toeng"s apparantly (see above) . Acording to Hamish I need the the USB driver I think.

I Just looked in my mem card and the is nothing labled "driver" on it so I guess it is missing, can anyone send me the driver?

 

Ah well fair enough then. Makes me wonder if I'm missing something too [shrug] but mine does work if I plug in afterwards and I did copy the entire evoscan folder from the 2.2 zip onto my card ... twice.

 

Thanks, I just looked at the 2.2 zip downloaded from the site, it does not have anything labled "driver" or "USB Driver" in it either, it is identacle to the folder already on my card so maybe I have everthing I should need already? Anyone know? I think I will try renaming the folders on the card as someon suggested earlier and maby try a op 1.3 cable if I can find one instead of the OP 2.0 cable causing me so much frustration at the moment.



2010 MR-T (SST)
Stock clutch packs
OEM DiaQueen SST fluid
SSP trans Deep Sump
SSP Front mount trans cooler
OEM intake w/dropin
CBRD BBX full Turbo
AMS DP
RRE Rally test pipe
MXP II CBE
DP 1000 injectors
BlaqOps single pump
WORKS tune using OP (cleaned up by Bryan)
Green relay (yeah that’s it, it MUST be a faulty fuel pump relay!)

 

I would stop where you are. You likely can't really mess anything up, that I can think of, by renaming folders in evoscan since you can always just rename them back or recopy from the zip file.

However there is also no darn good reason it should work. Save yourself the hassle and work with Hammish.

What I do know, or at least am damn near sure I know, is that there is more software going on than what is on the SD card. I am basing this on the fact that the unit will boot to the home screen without an SD card installed. But of course neither evoscan nor the GPS will actually run. So that tells me the underlying WinCE OS is loaded to internal memory on the unit and what you might have is a missing, corrupt, or unreferenced driver file there. And for that, I once again suggest dealing with Hammish.

Just my 3 cents.

 

I have tried every way include Jumperalax and kmart888 tried. But the problem can not fix, I can not find any usb driver for OP2. One and last Hammish mail ask me about EvoX or 9 is mine for he will sent folder for that. I do not understand what he say and I am waiting his mail.

This problem do not should occur if Hammish say it support OP2. It is basic testing that support or not.

Thank everyone that follow this issue, I have friend to overcome.