Flash issue

[DCIV]

Okay so I am trying to flash my new ecu to my injectors and what not and it was giving me problems. I downloaded the newest version of ecu flash, out the xml files where they are suppose to be. Downloaded the extra drivers for the cable. Let the cable instal before I opened up the program.

I go to do a test write and it starts and I get the sound that I unplugged the cable and it says “J2534 error” says it 3 times and times me out.

I go to google and look it up, download more drivers....still no go.

What am I doing wrong? It’s a cable issue as the computer gives me the sound that I unplugged the usb and I didn’t.


Coop

[DCIV]

Seems to be a win7 issue. Any suggestions?


Coop

[DCIV]

I’ve downloaded, installed in multiple ways, upgraded java, made sure everything was tight. Still it’s a driver issue. Anyone have an older version of ecu flash?


Coop

[Jeff V.]

Windows 7 and Windows 10 use the same drivers. An older version of ECUFlash won't work with the newer firmware that's on your cable. ECUFlash doesn't use Java.

Uninstall ECUFlash.
uninstall the OpenPort 2 drivers.
Reboot.
Reinstall the newest version of ECUFlash.

[DCIV]

[quote=""Jeff V.""]Windows 7 and Windows 10 use the same drivers. An older version of ECUFlash won't work with the newer firmware that's on your cable. ECUFlash doesn't use Java.

Uninstall ECUFlash.
uninstall the OpenPort 2 drivers.
Reboot.
Reinstall the newest version of ECUFlash.[/quote]

I will try again because I am basically out of options. But I have done this twice. Tried to use a different spot to install ecuflash the second time. I just got done going over everything again. It’s all correct. I’m almost at the point in sending all this stuff to someone to test it to make sure I’m not losing my mind.


Coop

[DCIV]

Anyone have any other suggestions? I sent Jeff a video, it literally acts like I unplugged the usb and plugged it right back in the moment I go to flash, well test flash.

Coop

[aaronatstate]

I've had issues where I have to hold the aux power wire in the Tactrix to get it to flash. I figured it was something with the aux port in the Tactrix. I've always been able to get it to work, so it hasn't been an issue for me.

[Jeff V.]

Copy the error log from ECU Flash and post it here. I don't think this is a Windows problem.

[DCIV]

[quote=""aaronatstate""]I've had issues where I have to hold the aux power wire in the Tactrix to get it to flash. I figured it was something with the aux port in the Tactrix. I've always been able to get it to work, so it hasn't been an issue for me.[/quote]

I will try that.

[quote=""Jeff V.""]Copy the error log from ECU Flash and post it here. I don't think this is a Windows problem.[/quote]

I will get it, maybe not tonight but tomorrow. You can kind of see it in the video. The cable literally disappears from the drivers and then reappears. Maybe I don't have it set up correctly.


Coop

[Jeff V.]

No, I can't see it in the video. It's such low quality when you send it via text message that I can't even tell what program you're running, let alone read errors.

[ChargerX3]

[quote=""Jeff V.""] I don't think this is a Windows problem.[/quote]

What are you trying to say?

[stealthee]

It's a Doodle problem.

[DCIV]

He’s saying the iPhone takes such good video that his android can’t handle it


Coop

[DCIV]

[20:57:28.189] Logging to file C:/Users/David/AppData/Roaming/OpenECU/EcuFlash/logs/ecuflash_log_20180515t205728.txt
[20:57:28.189] EcuFlash Version 1.44.4799
[20:57:28.189] OS Version Windows 7
[20:57:28.189] Kernel Type winnt
[20:57:28.189] Kernel Version 6.1.7601
[20:57:28.189] CPU i386
[20:57:28.189] Product Name Windows 7
[20:57:28.189] Product Type windows
[20:57:28.189] Product Version 7
[20:57:28.189] Qt Version 5.6.0
[20:57:28.189] Qwt Version 6.1.2
[20:57:28.189] QwtPlot3D Version 0.2.6
[20:57:28.189] Boost Version 1.60
[20:57:28.189] FTDI Library Version 3.02.11
[20:57:28.189] Openport J2534 Library Version 1.02.4798
[20:57:28.205] 67 memory models read.
[20:57:28.205] scanning for metadata models in C:/Program Files/OpenECU/EcuFlash/rommetadata
[20:57:29.001] 749 ROM metadata models scanned.
[20:57:29.001] checksum module "subarudbw" loaded.
[20:57:29.001] checksum module "subarudiesel" loaded.
[20:57:29.001] checksum module "subaruhitachi" loaded.
[20:57:29.001] checksum module "mitsucan" loaded.
[20:57:29.001] checksum module "mitsuh8" loaded.
[20:57:29.001] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[20:57:29.001] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[20:57:29.001] using metadata XML ID read_evo5 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/read templates/read_evo5.xml
[20:57:29.016] flashing tool "wrx02" loaded.
[20:57:29.016] flashing tool "wrx04" loaded.
[20:57:29.016] flashing tool "sti04" loaded.
[20:57:29.016] flashing tool "sti05" loaded.
[20:57:29.016] flashing tool "mitsucan" loaded.
[20:57:29.016] flashing tool "mitsukernel" loaded.
[20:57:29.016] flashing tool "mitsukernelocp" loaded.
[20:57:29.016] flashing tool "mitsubootloader" loaded.
[20:57:29.016] flashing tool "shbootmode" loaded.
[20:57:29.016] flashing tool "shaudmode" loaded.
[20:57:29.032] flashing tool "subarucan" loaded.
[20:57:29.032] flashing tool "subarucand" loaded.
[20:57:29.032] flashing tool "subarubrz" loaded.
[20:57:29.032] flashing tool "subaruhitachi" loaded.
[20:57:29.125] J2534 API Version: 04.04
[20:57:29.125] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[20:57:29.125] Device Firmware Version: 1.17.4877
[20:57:29.125] Device Serial Number: TAEIyt1y
[20:57:29.125] interface close
[20:57:29.172] J2534 API Version: 04.04
[20:57:29.172] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[20:57:29.172] Device Firmware Version: 1.17.4877
[20:57:29.172] Device Serial Number: TAEIyt1y
[20:57:29.172] interface close
[20:57:29.188] J2534 API Version: 04.04
[20:57:29.188] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[20:57:29.188] Device Firmware Version: 1.17.4877
[20:57:29.188] Device Serial Number: TAEIyt1y
[20:57:29.188] interface close
[20:57:29.219] J2534 API Version: 04.04
[20:57:29.219] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[20:57:29.219] Device Firmware Version: 1.17.4877
[20:57:29.219] Device Serial Number: TAEIyt1y
[20:57:29.219] interface close
[20:57:29.235] J2534 API Version: 04.04
[20:57:29.235] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[20:57:29.235] Device Firmware Version: 1.17.4877
[20:57:29.235] Device Serial Number: TAEIyt1y
[20:57:29.235] interface close
[20:57:29.281] J2534 API Version: 04.04
[20:57:29.281] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[20:57:29.281] Device Firmware Version: 1.17.4877
[20:57:29.281] Device Serial Number: TAEIyt1y
[20:57:29.281] interface close
[20:57:35.880] opening rom file C:/Users/David/Downloads/Nathan Modified Tune.bin
[20:57:35.911] 131072 byte image read.
[20:57:35.911] using metadata XML ID 23862006 from file C:/Program Files/OpenECU/EcuFlash/rommetadata/mitsubishi/3000gt/23862006.xml
[20:57:37.471] J2534 API Version: 04.04
[20:57:37.471] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[20:57:37.471] Device Firmware Version: 1.17.4877
[20:57:37.471] Device Serial Number: TAEIyt1y
[20:57:39.617] sending init sequence 2
[20:57:41.623] J2534 error [ERR_TIMEOUT].
[20:57:42.138] J2534 error [ERR_TIMEOUT].
[20:57:42.668] J2534 error [ERR_TIMEOUT].
[20:57:42.668] interface close

[ChargerX3]

[Jeff V.]

Look, mine does it too.

Code: Select all

[23:08:26.739] J2534 API Version: 04.04
[23:08:26.739] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[23:08:26.739] Device Firmware Version: 1.16.4769
[23:08:26.739] Device Serial Number: TAUUQUih
[23:08:29.880] -- reading ECU ID --
[23:08:31.888] J2534 error [ERR_TIMEOUT].
[23:08:34.099] J2534 error [ERR_TIMEOUT].
[23:08:36.303] J2534 error [ERR_TIMEOUT].
[23:08:38.521] J2534 error [ERR_TIMEOUT].
[23:08:40.727] J2534 error [ERR_TIMEOUT].
[23:08:42.930] J2534 error [ERR_TIMEOUT].
[23:08:45.640] J2534 error [ERR_TIMEOUT].
[23:08:46.359] J2534 error [ERR_TIMEOUT].
[23:08:47.069] J2534 error [ERR_TIMEOUT].
[23:08:47.782] J2534 error [ERR_TIMEOUT].
[23:08:48.480] J2534 error [ERR_TIMEOUT].
[23:08:49.194] J2534 error [ERR_TIMEOUT].
[23:08:49.396] interface close
[23:08:49.396] interface close

That happens when you have it plugged into a dead OBD2 port.

Stop messing with the car until you spend some time learning to do basic electrical troubleshooting.

[aaronatstate]

Did you wire up the OBD I port properly per Adams instructions to make it flash through the port with the plug and play ECU?

Steps 3-5 for 1g install on this page.

http://chromedecu.org/?page_id=1573

[DCIV]

[quote=""Jeff V.""]Look, mine does it too.

Code: Select all

[23:08:26.739] J2534 API Version: 04.04
[23:08:26.739] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[23:08:26.739] Device Firmware Version: 1.16.4769
[23:08:26.739] Device Serial Number: TAUUQUih
[23:08:29.880] -- reading ECU ID --
[23:08:31.888] J2534 error [ERR_TIMEOUT].
[23:08:34.099] J2534 error [ERR_TIMEOUT].
[23:08:36.303] J2534 error [ERR_TIMEOUT].
[23:08:38.521] J2534 error [ERR_TIMEOUT].
[23:08:40.727] J2534 error [ERR_TIMEOUT].
[23:08:42.930] J2534 error [ERR_TIMEOUT].
[23:08:45.640] J2534 error [ERR_TIMEOUT].
[23:08:46.359] J2534 error [ERR_TIMEOUT].
[23:08:47.069] J2534 error [ERR_TIMEOUT].
[23:08:47.782] J2534 error [ERR_TIMEOUT].
[23:08:48.480] J2534 error [ERR_TIMEOUT].
[23:08:49.194] J2534 error [ERR_TIMEOUT].
[23:08:49.396] interface close
[23:08:49.396] interface close

That happens when you have it plugged into a dead OBD2 port.

Stop messing with the car until you spend some time learning to do basic electrical troubleshooting.[/quote]

Jeff....how is this helpful? Basically quit messing with the car? You could have told me that before I got you the log you asked for.

[quote=""aaronatstate""]Did you wire up the OBD I port properly per Adams instructions to make it flash through the port with the plug and play ECU?

Steps 3-5 for 1g install on this page.

http://chromedecu.org/?page_id=1573[/quote]

Yes. Well kind of. The sheet I got with everything gave me a red and black wire and I put those into the obd1 port in the only open spots and the wires corespondent with the adapter. I know this is right, I’ve checked it 100 times and made sure they are tight and not coming out.

The jumper setting looks interesting though. I may check that out.


Coop

[aaronatstate]

[quote=""DCIV""]Yes. Well kind of. The sheet I got with everything gave me a red and black wire and I put those into the obd1 port in the only open spots and the wires corespondent with the adapter. I know this is right, I’ve checked it 100 times and made sure they are tight and not coming out.

The jumper setting looks interesting though. I may check that out.


Coop[/quote]

So the red wire goes to pin 56 on the small ECU plug (top right corner when looking at the side the wires go into), and then runs to pin 2 location on the OBDI connector (open spot not in the corner)?

The black wire goes from pin 51 on the small ECU plug (top left corner when looking at the side the wires go into), and then runs to pin 6 location on the OBDI connector (open corner spot)?

This is assuming you have a version 3 ECU (which I would say you do, since you just got it).

[DCIV]

That ecu plug you talk about was already pre wired. Then I took the pins to obd plug and I wanna say black was in the upper corner I read the directions 5 times as I put it in. Then I checked the adapter and the same wire coming in, is the same color wire coming out.

I can take a picture tomorrow if you want.

I will literally verify or show anything you all can come up with. This weekend I took off work sat, as the wife is gone, so baby and I are moving down to the basement and we going to work.

I just need ideas.


Coop