openport 2.0, ecuflash 1.41, and evolution 9, not working!
#1
Evolving Member
Thread Starter
iTrader: (1)
Join Date: Sep 2007
Location: SGP
Posts: 107
Likes: 0
Received 0 Likes
on
0 Posts
openport 2.0, ecuflash 1.41, and evolution 9, not working!
hey guys..
have a small problem hope you guys can help me out with
i recently purchased the openport 2.0 from tactrix and downloaded the ecuflash 1.41 program.
i plug the head of the tactrix cable into the obd2 port as well as the evo 9 connector but ECUflash is unable to read anything. comes out the error code which says 'unable to read from ECU' or something like that.
am i connecting the plugs wrongly or do i have to download a definition file or something like that?
thanks in advance for any help!
have a small problem hope you guys can help me out with
i recently purchased the openport 2.0 from tactrix and downloaded the ecuflash 1.41 program.
i plug the head of the tactrix cable into the obd2 port as well as the evo 9 connector but ECUflash is unable to read anything. comes out the error code which says 'unable to read from ECU' or something like that.
am i connecting the plugs wrongly or do i have to download a definition file or something like that?
thanks in advance for any help!
#4
Newbie
Join Date: Jun 2009
Location: Western Australia
Posts: 11
Likes: 0
Received 0 Likes
on
0 Posts
i having same issue:
[20:50:04.076] EcuFlash Version 1.41.2483
[20:50:04.076] OS Version Windows XP
[20:50:04.076] Qt Version 4.4.0
[20:50:04.086] 26 memory models read.
[20:50:04.086] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[20:50:04.376] 345 ROM metadata models scanned.
[20:50:04.376] checksum module "subarudbw" loaded.
[20:50:04.376] checksum module "mitsucan" loaded.
[20:50:04.376] flashing tool "wrx02" loaded.
[20:50:04.376] flashing tool "wrx04" loaded.
[20:50:04.376] flashing tool "sti04" loaded.
[20:50:04.376] flashing tool "sti05" loaded.
[20:50:04.376] flashing tool "mitsukernel" loaded.
[20:50:04.376] flashing tool "mitsukernelocp" loaded.
[20:50:04.376] flashing tool "mitsubootloader" loaded.
[20:50:04.376] flashing tool "shbootmode" loaded.
[20:50:04.386] flashing tool "shaudmode" loaded.
[20:50:04.386] flashing tool "subarucan" loaded.
[20:50:04.386] flashing tool "mitsucan" loaded.
[20:50:41.420] J2534 API Version: 04.04
[20:50:41.420] J2534 DLL Version: 0.50.2464 (DEBUG) Jan 29 2009 10:58:58
[20:50:41.420] Device Firmware Version: 1.06.2536
[20:50:43.282] sending init sequence 1 (0001)
[20:50:46.567] sending init sequence 1 (0003)
[20:50:49.862] sending init sequence 1 (FFFF)
[20:50:53.137] sending init sequence 1 (F0F0)
[20:50:55.860] no response to any known code
[20:50:55.870] interface close
[20:50:04.076] EcuFlash Version 1.41.2483
[20:50:04.076] OS Version Windows XP
[20:50:04.076] Qt Version 4.4.0
[20:50:04.086] 26 memory models read.
[20:50:04.086] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[20:50:04.376] 345 ROM metadata models scanned.
[20:50:04.376] checksum module "subarudbw" loaded.
[20:50:04.376] checksum module "mitsucan" loaded.
[20:50:04.376] flashing tool "wrx02" loaded.
[20:50:04.376] flashing tool "wrx04" loaded.
[20:50:04.376] flashing tool "sti04" loaded.
[20:50:04.376] flashing tool "sti05" loaded.
[20:50:04.376] flashing tool "mitsukernel" loaded.
[20:50:04.376] flashing tool "mitsukernelocp" loaded.
[20:50:04.376] flashing tool "mitsubootloader" loaded.
[20:50:04.376] flashing tool "shbootmode" loaded.
[20:50:04.386] flashing tool "shaudmode" loaded.
[20:50:04.386] flashing tool "subarucan" loaded.
[20:50:04.386] flashing tool "mitsucan" loaded.
[20:50:41.420] J2534 API Version: 04.04
[20:50:41.420] J2534 DLL Version: 0.50.2464 (DEBUG) Jan 29 2009 10:58:58
[20:50:41.420] Device Firmware Version: 1.06.2536
[20:50:43.282] sending init sequence 1 (0001)
[20:50:46.567] sending init sequence 1 (0003)
[20:50:49.862] sending init sequence 1 (FFFF)
[20:50:53.137] sending init sequence 1 (F0F0)
[20:50:55.860] no response to any known code
[20:50:55.870] interface close
#5
Evolving Member
iTrader: (14)
Join Date: Oct 2006
Location: Los Angeles, CA
Posts: 179
Likes: 0
Received 0 Likes
on
0 Posts
I used to get the same thing when tuning with a low voltage battery, try starting the car and leaving the car on for 20 seconds and then try flashing then(with Ecu unlocker). If that fails, check the battery voltage at a local autozone its free, and they also recharge batteries for free. Also, check if the cable is working by using EvoScan and try to log your car.
Last edited by ohhgyeahfasho; Jun 26, 2009 at 12:59 PM.
Trending Topics
#13
Newbie
iTrader: (3)
I beleive the voltage varies internally to the tactrix cable..something between 12-19v if im not mistaken, so you cant just put battery voltage on on the littlle 2.5mm jack.. That is the same message I get when I try to connect but forget to plug in the mini 2.5mmconnector. Also I just made my own connector with parts bought from Radioshack. Probably a bad connection. Good luck!
Thread
Thread Starter
Forum
Replies
Last Post
WTB[MidWest]: Tactrix Cable
Evodetailer123
For Sale - Engine / Drivetrain / Power
0
Oct 3, 2016 07:37 AM
Mitsu.kid.02
Lancer Engine Management / Tuning Forums
217
May 25, 2016 10:47 AM
Me-So-Bishi
Lancer Engine Management / Tuning Forums
13
Sep 24, 2010 03:32 AM