![]() |
Openport 2.0 won't connect to my 9 or gf's 8
Hello all. I wish my first post didn't have to be asking for help but I am at witts end here. I have searched for 5 hours for a similar problem but none of the proposed solutions have worked. Here is what ecuflash says when I try to pull the rom.
[17:48:30.687] EcuFlash Version 1.42.2595 [17:48:30.687] OS Version Windows Vista [17:48:30.687] Qt Version 4.5.0 [17:48:30.702] 56 memory models read. [17:48:30.702] scanning for metadata models in C:/Users/Turbo Chick/Desktop/Evo Stuff/EcuFlash/rommetadata [17:48:30.968] 343 ROM metadata models scanned. [17:48:30.968] checksum module "subarudbw" loaded. [17:48:30.968] checksum module "mitsucan" loaded. [17:48:30.983] flashing tool "wrx02" loaded. [17:48:30.983] flashing tool "wrx04" loaded. [17:48:30.983] flashing tool "sti04" loaded. [17:48:30.983] flashing tool "sti05" loaded. [17:48:30.983] flashing tool "mitsukernel" loaded. [17:48:30.983] flashing tool "mitsukernelocp" loaded. [17:48:30.983] flashing tool "mitsubootloader" loaded. [17:48:30.983] flashing tool "shbootmode" loaded. [17:48:30.983] flashing tool "shaudmode" loaded. [17:48:30.983] flashing tool "subarucan" loaded. [17:48:30.983] flashing tool "mitsucan" loaded. [17:48:38.955] J2534 API Version: 04.04 [17:48:38.955] J2534 DLL Version: 0.50.2598 Jun 26 2009 15:02:29 [17:48:38.955] Device Firmware Version: 1.10.3020 [17:48:42.823] sending init sequence 1 (0001) [17:48:43.531] J2534 error [ERR_TIMEOUT]. [17:48:44.048] J2534 error [ERR_TIMEOUT]. [17:48:44.048] interface close The battery is at 13.8 volts and has a charger hooked up. When I installed ecuflash it found the cable an installed just fine and in the ecuflash window it says connected to openport 2.0 on com 6. I plug both connectors in and turn on the then this is the message that comes up. It does this on my 9 and my girlfriends 8. Both of our cars have been scanned by friends with the 1.3u cable and they worked first try. Is there something I'm missing? Any help would be greatly appreciated. P.S. I have also completely uninstalled and reinstalled ecuflash 3 times and have been running ecu unlocker to no avail. Thanks in advance for any help. NoobyMcNooberson, Mattsubishi |
Have you tried scanning using more then one PC?
|
try the ecu unlocker with ecuflash to see if that helps. It seems like the ecu is lockerd.
|
I havent tried another computer yet but I will take my cable to work and try it on an XP laptop. (forgot to mention my laptop runs Windows 7)
I have been running ecu unlocker also. Both cars have previously had there roms pulled by friends without ecu unlocker. |
Well I feel like a knob now. I installed ecuflash on a work laptop running XP sp2 and it worked fine. I guess the cable just doesn't like either my laptop or windows 7. Does anyone have the openport 2.0 working on a vista machine? Did you have to use any weird settings?
|
IIRC there were issues with getting Vista to play nicely with the Openport or Evoscan version of the cables. And many people have had issues with the Openport 2.0 cables. Glad to see you got it working under XP. What version of Ecuflash are you using BTW? NVM i see 1.42
I think your issues are strictly with Vista. It acted weird when I had it on my laptop too. But it would connect though. I use an older cable Tactrix 1.3 and run that under Windows 7 Pro on a new laptop with no issues. I did use SilverEVO's cable hack as I still prefer to run Ecuflash 1.38 . Colby@Tactrix decided to force people to use the newer versions of the cable with 1.4 and up ( reads the serial number of the cable ) I also run EVOScan v2.7 and Scantech OBD2 diagnostics on the cable under Windows 7..no issues with them. Have you tried to log with the Openport 2.0 using EvoScan ? I know at some point I will have to get an Openport 2 as I want to be able to re-flash the ACD controller when the gurus have that ready and its been tested...until then Im happy as is. |
I haven't used Evoscan yet. I' kind of hesitant to put it on my laptop when ecuflash isn't working. I don't know what the odds of Evoscan working when ecuflash doesn't. I'm assuming that since there is a serial license code provided with Evoscan that I can only have it on one computer.... I guess I'll just try it anyway. It's only $25. I did order a 1.3U cable also so I will try that with my laptop and hopefully that works. Thanks for the input.{thumbup}
|
i just delt with this on my buddys ecu. it has something to do with the 2.0 drivers and windows 7. install the newest version of ecu flash located here
http://www.evoscan.com/evoscan-updates it should work after the new version installs the newest driver updates for 2.0 |
Originally Posted by Mattsubishi
(Post 8999993)
[17:48:30.687] EcuFlash Version 1.42.2595
[17:48:30.687] OS Version Windows Vista I will try the newest version when I get home tonight and let you guys no. Thanks for the input! |
Well last night I downloaded and installed Evoscan on the same Windows 7 computer that DOESN'T connect with Ecuflash and with the same OP2 cable and adapters Evoscan worked fine.:confused: :crap:
WTF is going on?? I downloaded the newest Beta of Ecuflash and that didn't work either. I still get the same error. [17:48:43.531] J2534 error [ERR_TIMEOUT]. [17:48:44.048] J2534 error [ERR_TIMEOUT]. This is really getting aggrevating. I really don't want to go buy another laptop because Ecuflsh wont work. Any other ideas guys? I'm at a loss here. P.S. I'm sure this doesn't really matter but this computer interfaces fine with DSMlink in my GSX also. |
I bought a new laptop with Windows 7 and have the same issue with ecuflash. I can log on evoscan all day long, just ecuflash, on windows 7, isn't recognizing the openport 2.0 cable, even when it says it installs the driver. It works fine on my other laptops, one with Windows XP and one running Vista. If I download the newest version of Ecuflash, it'll work for a few times, then start crashing all the time. Windows 7 sucks?
|
Try an older version of ecuflash
|
Originally Posted by EvO9 PiPER
(Post 9030302)
Try an older version of ecuflash
I found this on the internet tonight, as this issue was bothering the **** outta me, so I was looking for a solution: http://maximumpcguides.com/windows-7...-in-windows-7/ ^^^^*I'M NOT SAYING IT WILL WORK SO USE AT YOUR OWN RISK*^^^^^^^ I will be trying this tomorrow to see if it helps! |
Well it appears that we may be having different problems. When I connect my OP2 cable, Ecuflash does say connected to Openport 2.0 in the bottom right hand corner but when I try to connect it just say J2534 error everytime. I have seen a thread in my searching where someone had the same problem you were having though with the cable not even being recognized. I will check out that link though. Spec Ops If you come up with anything please post it on here and I will do the same.
|
Well the 1.3u cable I ordered when I couldn't get the OP2.0 to work showed up last night and that one worked great first try with the same car. I guess my problem was specifically an OP2.0 Windows 7 issue. I guess I will just use the 1.3U cable and keep the OP2.0 for when my girlfriend or myself buys an EvoX. Or I guess I can sell it as soon as I get to 50 posts.
|
| All times are GMT -7. The time now is 05:20 AM. |
© 2026 MH Sub I, LLC dba Internet Brands