2G Reflash connection location

[1997DSMALEX]

I have a Tactrix 2.0 cable for tuning I'm trying to connect the reflash cable, where in the vehicle would that connection be I have a 1997 GST but with a blackbox ECU.

 

[chrysler kid]

Usually its right behind the obd2 plug on my cars that came with the ecu from the factory

 

[CrackedDSM]

I don’t think on a 97 you have that connector. You may have to add it. My memories fuzzy though and someone will definitely correct me if I’m wrong.

 

[steve]

I don’t think on a 97 you have that connector. You may have to add it. My memories fuzzy though and someone will definitely correct me if I’m wrong.

That's what I remember too.

What I do remember is that the flash connector on the 98/99 models looks like a 1G ODB connector with only one pin in it.

 

[1997DSMALEX]

I don’t think on a 97 you have that connector. You may have to add it. My memories fuzzy though and someone will definitely correct me if I’m wrong.

Yea you’re right I do need to add it so my question is would I have to open the ECU to add it from the inside going out of the black box with the mono plug? That’s where I’m trying to understand since there’s a harness already on that location

 

[motomattx]

You add it to pin 79 on the ecu as I recall, you dont need to open the ecu to do it, just add a terminal to your ecu plug, there should not be one in that cavity on the 97' and older cars, and it needs to go to the TIP of the phono plug.

 

[steve]

From https://www.dsmtuners.com/threads/first-flashed-dsm-ecu-98-99-flashing-faq.338754

On 95-97s you must add a pin at position 79 of your ECU Harness.
This must be connected to the 2.5mm phono plug on your OpenPort 2.0 cable.
It must be connected to the tip of your phono plug.

ECU Harness Pins:
The EVO guys have reported these are the correct pins -> TYCO ELECTRONICS / AMP|175265-1|Contact | Newark.com

 

[1997DSMALEX]

You add it to pin 79 on the ecu as I recall, you dont need to open the ecu to do it, just add a terminal to your ecu plug, there should not be one in that cavity on the 97' and older cars, and it needs to go to the TIP of the phono plug.

Ok awesome I see now I just ordered some terminals from the ones ceddy posted on his post also will just need a wire I have the mono plug but what kind of wire would I need for the terminal? Also when it says connect to the tip of the plug do I just wrap it around the tip or solder would work?

 

[steve]

You would typically run the wire through the eyelet for the tip terminal to make a mechanical connection and then solder it.

 

[chrysler kid]

Did you buy a real tactrix cable or a fake one on amazon

 

[1997DSMALEX]

Did you buy a real tactrix cable or a fake one on amazon

It’s a real one from the tactrix website itself

 

[1997DSMALEX]

You would typically run the wire through the eyelet for the tip terminal to make a mechanical connection and then solder it.

hey so i got the pin in #79 with the 2.5mm mono plug but I still get this error log in ecu flash but in evoscan works great.
[16:40:30.492] Logging to file C:/Users/alexi/AppData/Roaming/OpenECU/EcuFlash/logs/ecuflash_log_20221029t164030.txt
[16:40:30.492] EcuFlash Version 1.44.4870
[16:40:30.492] OS Version Windows 10
[16:40:30.492] Kernel Type winnt
[16:40:30.492] Kernel Version 10.0.22000
[16:40:30.492] CPU x86_64
[16:40:30.492] Product Name Windows 10
[16:40:30.492] Product Type windows
[16:40:30.492] Product Version 10
[16:40:30.492] Qt Version 5.6.0
[16:40:30.492] Qwt Version 6.1.2
[16:40:30.492] QwtPlot3D Version 0.2.6
[16:40:30.492] Boost Version 1.60
[16:40:30.492] FTDI Library Version 3.02.11
[16:40:30.492] Openport J2534 Library Version 1.02.4870
[16:40:30.496] 67 memory models read.
[16:40:30.496] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata
[16:40:30.550] 745 ROM metadata models scanned.
[16:40:30.550] checksum module "subarudbw" loaded.
[16:40:30.550] checksum module "subarudiesel" loaded.
[16:40:30.550] checksum module "subaruhitachi" loaded.
[16:40:30.550] checksum module "mitsucan" loaded.
[16:40:30.550] checksum module "mitsuh8" loaded.
[16:40:30.550] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[16:40:30.550] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[16:40:30.550] using metadata XML ID read_evo65 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo65.xml
[16:40:30.550] flashing tool "wrx02" loaded.
[16:40:30.550] flashing tool "wrx04" loaded.
[16:40:30.565] flashing tool "sti04" loaded.
[16:40:30.565] flashing tool "sti05" loaded.
[16:40:30.565] flashing tool "mitsucan" loaded.
[16:40:30.565] flashing tool "mitsukernel" loaded.
[16:40:30.565] flashing tool "mitsukernelocp" loaded.
[16:40:30.565] flashing tool "mitsubootloader" loaded.
[16:40:30.565] flashing tool "shbootmode" loaded.
[16:40:30.565] flashing tool "shaudmode" loaded.
[16:40:30.565] flashing tool "subarucan" loaded.
[16:40:30.565] flashing tool "subarucand" loaded.
[16:40:30.565] flashing tool "subarubrz" loaded.
[16:40:30.565] flashing tool "subaruhitachi" loaded.
[16:40:30.583] J2534 error [no devices available].
[16:40:30.583] J2534 error [no devices available].
[16:40:30.584] J2534 error [no devices available].
[16:40:30.584] J2534 error [no devices available].
[16:40:30.584] J2534 error [no devices available].
[16:40:30.584] J2534 error [no devices available].
[16:40:42.911] using metadata XML ID read_evo65 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo65.xml
[16:40:42.911] J2534 error [no devices available].
[16:40:42.911] unable to connect to vehicle interface.
[16:40:45.913] using metadata XML ID read_evo65 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo65.xml
[16:40:45.914] J2534 error [no devices available].
[16:40:45.914] unable to connect to vehicle interface.
[16:40:56.836] using metadata XML ID read_evo65 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo65.xml
[16:40:56.851] J2534 API Version: 04.04
[16:40:56.851] J2534 DLL Version: 1.02.4870 Feb 3 2017 23:36:31
[16:40:56.851] Device Firmware Version: 1.17.4877
[16:40:56.851] Device Serial Number: TADJ1Sta
[16:40:58.392] J2534 error [ERR_TIMEOUT].
[16:40:58.898] sending init sequence 2
[16:41:00.902] J2534 error [ERR_TIMEOUT].
[16:41:01.412] J2534 error [ERR_TIMEOUT].
[16:41:01.913] J2534 error [ERR_TIMEOUT].
[16:41:01.913] interface close
[16:41:09.316] using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[16:41:09.316] using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[16:41:11.827] using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[16:41:11.843] J2534 API Version: 04.04
[16:41:11.843] J2534 DLL Version: 1.02.4870 Feb 3 2017 23:36:31
[16:41:11.843] Device Firmware Version: 1.17.4877
[16:41:11.843] Device Serial Number: TADJ1Sta
[16:41:12.936] sending init sequence 2
[16:41:14.938] J2534 error [ERR_TIMEOUT].
[16:41:15.449] J2534 error [ERR_TIMEOUT].
[16:41:15.950] J2534 error [ERR_TIMEOUT].
[16:41:15.950] interface close
[16:41:40.728] using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[16:41:40.743] J2534 API Version: 04.04
[16:41:40.743] J2534 DLL Version: 1.02.4870 Feb 3 2017 23:36:31
[16:41:40.743] Device Firmware Version: 1.17.4877
[16:41:40.743] Device Serial Number: TADJ1Sta
[16:41:42.131] sending init sequence 2
[16:41:44.134] J2534 error [ERR_TIMEOUT].
[16:41:44.639] J2534 error [ERR_TIMEOUT].
[16:41:45.141] J2534 error [ERR_TIMEOUT].
[16:41:45.141] interface close
[16:41:52.427] using metadata XML ID read_evo65 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo65.xml
[16:41:52.427] using metadata XML ID read_evo65 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo65.xml
[16:41:53.983] using metadata XML ID read_evo65 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo65.xml
[16:41:53.999] J2534 API Version: 04.04
[16:41:53.999] J2534 DLL Version: 1.02.4870 Feb 3 2017 23:36:31
[16:41:53.999] Device Firmware Version: 1.17.4877
[16:41:53.999] Device Serial Number: TADJ1Sta
[16:41:56.114] sending init sequence 2
[16:41:58.123] J2534 error [ERR_TIMEOUT].
[16:41:58.623] J2534 error [ERR_TIMEOUT].
[16:41:59.125] J2534 error [ERR_TIMEOUT].
[16:41:59.125] interface close
[16:42:18.377] using metadata XML ID read_evo65 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo65.xml
[16:42:18.393] J2534 API Version: 04.04
[16:42:18.393] J2534 DLL Version: 1.02.4870 Feb 3 2017 23:36:31
[16:42:18.393] Device Firmware Version: 1.17.4877
[16:42:18.393] Device Serial Number: TADJ1Sta
[16:42:19.581] sending init sequence 2
[16:42:21.584] J2534 error [ERR_TIMEOUT].
[16:42:22.085] J2534 error [ERR_TIMEOUT].
[16:42:22.587] J2534 error [ERR_TIMEOUT].
[16:42:22.587] interface close
[16:42:26.755] using metadata XML ID read_evo65 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo65.xml
[16:42:26.771] J2534 API Version: 04.04
[16:42:26.771] J2534 DLL Version: 1.02.4870 Feb 3 2017 23:36:31
[16:42:26.771] Device Firmware Version: 1.17.4877
[16:42:26.771] Device Serial Number: TADJ1Sta
[16:42:27.868] sending init sequence 2
[16:42:29.874] J2534 error [ERR_TIMEOUT].
[16:42:30.375] J2534 error [ERR_TIMEOUT].
[16:42:30.877] J2534 error [ERR_TIMEOUT].
[16:42:30.877] interface close
[16:42:45.882] using metadata XML ID read_evo65 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo65.xml
[16:42:45.898] J2534 API Version: 04.04
[16:42:45.898] J2534 DLL Version: 1.02.4870 Feb 3 2017 23:36:31
[16:42:45.898] Device Firmware Version: 1.17.4877
[16:42:45.898] Device Serial Number: TADJ1Sta
[16:42:47.045] sending init sequence 2
[16:42:49.059] J2534 error [ERR_TIMEOUT].
[16:42:49.570] J2534 error [ERR_TIMEOUT].
[16:42:50.075] J2534 error [ERR_TIMEOUT].
[16:42:50.075] interface close

 

[1997DSMALEX]

it's a real tactrix as well from their website. could it be the ECU? I've posted which kind of black box i have on another post.

Ok, recently i just got this error:

using metadata XML ID read_evo5 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/readtemplates/read_evo5.xml
[17:29:50.115] J2534 API Version: 04.04
[17:29:50.115] J2534 DLL Version: 1.02.4870 Feb 3 2017 23:36:31
[17:29:50.115] Device Firmware Version: 1.17.4877
[17:29:50.115] Device Serial Number: TADJ1Sta
[17:29:51.260] sending init sequence 2
[17:29:51.260] got 0xF1 response instead of 0x11

am i getting closer to being able to read ecu? I had a different option selected in ecuflash? because now it just keeps saying "interface closed" see log for details.

also does it matter that i am reading at 11.5v of battery according to evoscan?