Defective OpenPort 2.0 Cable?
Feb 4, 2012, 03:28 PM
#1
Newbie
Thread Starter
iTrader: (1)
Join Date: Oct 2011
Location: Calgary
Posts: 35
Likes: 0
Received 0 Likes
on
0 Posts
Defective OpenPort 2.0 Cable?
Normally, I wouldn't start a new thread for OP2.0/EcuFlash help, but in this case, no amount of searching online has found anyone with a similar problem. And I've spent dozens of hours trying to get this to work without success.
Basic problem is: I think my OpenPort 2.0 cable is defective.
Here's the email I sent to support@tactrix.com.
Admittedly, I am a newcomer to business of tuning/flashing/logging etc, but how can I learn if I can't get past step 1?? 
Any suggestions are welcome.
Thanks.
Basic problem is: I think my OpenPort 2.0 cable is defective.
Here's the email I sent to support@tactrix.com.
Hi,
I am having extreme difficulty getting anything to work. I recently purchased an OpenPort 2.0 cable (Jan 2012) and have been trying to connect to my 2011 Mitsubishi Ralliart without any success.
I'm running Windows 7. Here's what I've tried:
-First, I installed EcuFlash Version 1.42.2595. All default locations - Program Files (x86) etc etc
-That also installed three (3) drivers called:
CDM Drivers Package 2.04.06
CDM Drivers Package 2.02.04
Tactrix Inc (usbser) Ports 1.00.0000
- I downloaded the XML definition file from GoldenEvo.com for my particular car: 2011 USDM Ralliart SST - 56940007. I copied this file into the EcuFlash>rommetadata>mitsubishi>lancer folder. But I haven't got to the point where I do anything with it yet.
-Then I plugged my OP2.0 into my laptop, and it automatically detected and installed a driver. Something (COM3) I think.
-Then I inserted my microSD card into the OP2.0. Another driver was installed. Something (COM4) this time.
-I can see the microSD card on my laptop as a "removable disk". I did a quick format on that to ensure it was clean.
-But when I load EcuFlash and click Help>Licensing, it says this:
"Unable to connect to OpenPort 2.0 Licensing information cannot be displayed."
Does this mean it isn't even detecting the cable at this point? Don't I have a license? Do I NEED one? Was one not provided when I paid for this? Did I miss a step?
Not having any idea what else to do, I then take all this out to my car and do this:
-Plug one end of the USB cable into the Tactrix OP2.0 unit.
-The car ignition is fully OFF, then plug the Tactrix OP2.0 unit into the OBDII port of the Ralliart.
-Plug the other end of the USB cable into the running laptop.
When I run EcuFlash, it doesn't appear to recognize that the cable is plugged into my car AT ALL. Under the "ECU" menu, all options are greyed out. Nothing is selectable. The log doesn't change from when the car is not plugged in.
Turning the cars power on (but not starting the engine) does nothing either.
Anytime the OP2.0 unit is plugged in, the blue, green and red lights just turn on and off in sequence. Is this unit defective? What am I doing wrong?
Please help.
Yours sincerely,
Alex
Additional info:
Here is what the EcuFlash log says when I load the program to begin with:
[15:31:40.635] EcuFlash Version 1.42.2595
[15:31:40.635] OS Version Windows Vista Why does it say this? I DON'T have Windows Vista. I have Windows 7.
[15:31:40.635] Qt Version 4.5.0
[15:31:40.641] 56 memory models read.
[15:31:40.642] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[15:31:40.853] 344 ROM metadata models scanned.
[15:31:40.853] checksum module "subarudbw" loaded.
[15:31:40.853] checksum module "mitsucan" loaded.
[15:31:40.854] flashing tool "wrx02" loaded.
[15:31:40.854] flashing tool "wrx04" loaded.
[15:31:40.854] flashing tool "sti04" loaded.
[15:31:40.854] flashing tool "sti05" loaded.
[15:31:40.854] flashing tool "mitsukernel" loaded.
[15:31:40.854] flashing tool "mitsukernelocp" loaded.
[15:31:40.854] flashing tool "mitsubootloader" loaded.
[15:31:40.855] flashing tool "shbootmode" loaded.
[15:31:40.856] flashing tool "shaudmode" loaded.
[15:31:40.856] flashing tool "subarucan" loaded.
[15:31:40.856] flashing tool "mitsucan" loaded.
In the EcuFlash folder in my Program Files (x86) folder, it has FTD2XX.dll and op20pt32.dll present. There are also a whole bunch of files in the "drivers" folder including DPInst.exe. I've searched online for information, and this stuff was mentioned, but generally due to error messages popping up. At this point, I'd be happy to see an error message.
On the OP2.0 unit, it says Rev E, and this: T A v g I $ m W I don't know if that is relevant at all.
It shows up as OpenPort 2.0 in Devices & Printers, but I an error comes up when I click "Eject". The device properties says "The device is working properly". I am beginning to doubt that.
I am having extreme difficulty getting anything to work. I recently purchased an OpenPort 2.0 cable (Jan 2012) and have been trying to connect to my 2011 Mitsubishi Ralliart without any success.
I'm running Windows 7. Here's what I've tried:
-First, I installed EcuFlash Version 1.42.2595. All default locations - Program Files (x86) etc etc
-That also installed three (3) drivers called:
CDM Drivers Package 2.04.06
CDM Drivers Package 2.02.04
Tactrix Inc (usbser) Ports 1.00.0000
- I downloaded the XML definition file from GoldenEvo.com for my particular car: 2011 USDM Ralliart SST - 56940007. I copied this file into the EcuFlash>rommetadata>mitsubishi>lancer folder. But I haven't got to the point where I do anything with it yet.
-Then I plugged my OP2.0 into my laptop, and it automatically detected and installed a driver. Something (COM3) I think.
-Then I inserted my microSD card into the OP2.0. Another driver was installed. Something (COM4) this time.
-I can see the microSD card on my laptop as a "removable disk". I did a quick format on that to ensure it was clean.
-But when I load EcuFlash and click Help>Licensing, it says this:
"Unable to connect to OpenPort 2.0 Licensing information cannot be displayed."
Does this mean it isn't even detecting the cable at this point? Don't I have a license? Do I NEED one? Was one not provided when I paid for this? Did I miss a step?
Not having any idea what else to do, I then take all this out to my car and do this:
-Plug one end of the USB cable into the Tactrix OP2.0 unit.
-The car ignition is fully OFF, then plug the Tactrix OP2.0 unit into the OBDII port of the Ralliart.
-Plug the other end of the USB cable into the running laptop.
When I run EcuFlash, it doesn't appear to recognize that the cable is plugged into my car AT ALL. Under the "ECU" menu, all options are greyed out. Nothing is selectable. The log doesn't change from when the car is not plugged in.
Turning the cars power on (but not starting the engine) does nothing either.
Anytime the OP2.0 unit is plugged in, the blue, green and red lights just turn on and off in sequence. Is this unit defective? What am I doing wrong?
Please help.
Yours sincerely,
Alex
Additional info:
Here is what the EcuFlash log says when I load the program to begin with:
[15:31:40.635] EcuFlash Version 1.42.2595
[15:31:40.635] OS Version Windows Vista Why does it say this? I DON'T have Windows Vista. I have Windows 7.
[15:31:40.635] Qt Version 4.5.0
[15:31:40.641] 56 memory models read.
[15:31:40.642] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[15:31:40.853] 344 ROM metadata models scanned.
[15:31:40.853] checksum module "subarudbw" loaded.
[15:31:40.853] checksum module "mitsucan" loaded.
[15:31:40.854] flashing tool "wrx02" loaded.
[15:31:40.854] flashing tool "wrx04" loaded.
[15:31:40.854] flashing tool "sti04" loaded.
[15:31:40.854] flashing tool "sti05" loaded.
[15:31:40.854] flashing tool "mitsukernel" loaded.
[15:31:40.854] flashing tool "mitsukernelocp" loaded.
[15:31:40.854] flashing tool "mitsubootloader" loaded.
[15:31:40.855] flashing tool "shbootmode" loaded.
[15:31:40.856] flashing tool "shaudmode" loaded.
[15:31:40.856] flashing tool "subarucan" loaded.
[15:31:40.856] flashing tool "mitsucan" loaded.
In the EcuFlash folder in my Program Files (x86) folder, it has FTD2XX.dll and op20pt32.dll present. There are also a whole bunch of files in the "drivers" folder including DPInst.exe. I've searched online for information, and this stuff was mentioned, but generally due to error messages popping up. At this point, I'd be happy to see an error message.
On the OP2.0 unit, it says Rev E, and this: T A v g I $ m W I don't know if that is relevant at all.
It shows up as OpenPort 2.0 in Devices & Printers, but I an error comes up when I click "Eject". The device properties says "The device is working properly". I am beginning to doubt that.
Any suggestions are welcome.
Thanks.
Feb 4, 2012, 04:38 PM
#2
Evolved Member
Join Date: May 2009
Location: Eastern NC
Posts: 844
Likes: 0
Received 0 Likes
on
0 Posts
Well I can tell you that your boot up screen in ECUFlash looks exactly like mine, so there isn't a problem with the software. Also, it is normal to list Windows 7 as Vista and you do not need a license for this software, I got the same message you did when I went to that screen.
I'm not sure what's going on with your setup, but the problem seems to be located in two areas, the xml file and the OBDII connection.
First, double check the instructions from Goldenevo to make sure you followed them exactly.
Second, make sure the Openport is fully plugged in to the car's OBDII port. It can look like it is fully engaged when its not.
I hope this helps. Keep us informed of the situation.
I'm not sure what's going on with your setup, but the problem seems to be located in two areas, the xml file and the OBDII connection.
First, double check the instructions from Goldenevo to make sure you followed them exactly.
Second, make sure the Openport is fully plugged in to the car's OBDII port. It can look like it is fully engaged when its not.
I hope this helps. Keep us informed of the situation.
Feb 7, 2012, 12:39 PM
#3
Newbie
Thread Starter
iTrader: (1)
Join Date: Oct 2011
Location: Calgary
Posts: 35
Likes: 0
Received 0 Likes
on
0 Posts
Update: Tactrix was fast with their response!
So I uninstalled everything and used the v1.43 beta. So far so good, I could actually select Read from ECU. But I must be part of the dreaded 1% because it then spits out some kind of driver conflict error. Next step is a DEEP CLEANSING. Sounds painful. I'm starting to think a new computer might just be simpler! I understand baby steps, but this is super frustrating.
So I uninstalled everything and used the v1.43 beta. So far so good, I could actually select Read from ECU. But I must be part of the dreaded 1% because it then spits out some kind of driver conflict error. Next step is a DEEP CLEANSING. Sounds painful. I'm starting to think a new computer might just be simpler! I understand baby steps, but this is super frustrating.
Thread
Thread Starter
Forum
Replies
Last Post
