Chrome ECU Flash - Connection Issues / Questions

[white92vr4]

Hi all, thanks in advance for the help!

First of all, here is my setup:
1992 VR4
Newer 4 bolt JDM motor swap ( all my old sensors , electronics and engine accessories moved over from original motor)

I have a new Jester Chrome V2 ECU that I am not 100% sure is installed correctly. I received my unit from 3SX about 2 weeks ago. I installed it per the included instructions. However, there were some differences in what I received vs. what the instructions say was included.
The Chrome ECU "package contents" section make note of
"1x Gray 12 pin connector with Yellow Wire"
"1 Red Wire (to be installed)"

What I actually received was a Gray 12 pin with a short red and yellow wires attached.

My install:
I Installed a yellow jumper wire from the ODB1 diagnostic pin 6 to the and connected that to the yellow wire on the provide Gray plug going into the Chrome ECU. I ran a red jumper wire from the ODB1 Diagnostic pin 2 and connected that to the Red wire on Gray plug going into the Chrome ECU. Is this where I went wrong? Is this correct or did I receive the wrong gray plug?
Do I need a red wire to goto pin 77 as my instructions state not that gray plug?

As of right now:
While I am able to log in Evoscan, it randomly drops the connection and stop the log with the follow error:
Info: Initializing At 5 baud...
Info: Timer: 2106.2257ms
Info: Initialization Complete...
Info: Waiting for INIT Response...
Info: ECU ID: E6AE
Info: Connection successful...
Error: J2534 Read Error - 16
Info: Datalogger Ended.

The bigger problem I am having is I cannot read or flash using Ecu Flash. I was attempting to flash the ECU using ECU Flash 1.44.42xx. I am using an openport 2.0 tactrix cable and adapter. when using the diagnostic post to ODBII connector with the Tactix box I am not able to even pull the current ROM. ( I tried charging the battery, letting the car run for a while, and uninstalling and reinstalling ecuflash in a non- program files folder).

Do I need to use the included flash plug along with the normal ODBII tactrix adapter?
How would I hook that up since the ODBII adapter occupies the ODBI diagnostic port currently? (sorry for the basic/stupid questions I did try to RTFM and searching) The only youtube video I could find on this shows a guy attaching both the ODBII and the flash plug which I cant see how I would be able to do on my setup.

The ECU flash Log is as follows:

[10:32:09.915] opening rom file C:/ecu programs/flash/EcuFlash/rommetadata/mitsubishi/23862006.bin
[10:32:09.955] 131072 byte image read.
[10:32:09.956] using metadata XML ID 23862006 from file C:/ecu programs/flash/EcuFlash/rommetadata/mitsubishi/23862006.xml
[10:32:12.742] using metadata XML ID 23862006 from file C:/ecu programs/flash/EcuFlash/rommetadata/mitsubishi/23862006.xml
[10:32:12.759] J2534 API Version: 04.04
[10:32:12.759] J2534 DLL Version: 1.01.4247 Apr 18 2014 1637
[10:32:12.759] Device Firmware Version: 1.15.4126
[10:32:12.759] Device Serial Number: TAM9OG9b
[10:32:14.685] sending init sequence 2
[10:32:19.186] J2534 error [no data was read].
[10:32:19.686] J2534 error [no data was read].
[10:32:19.686] interface close

Please let me know how to proceed. Sorry for the long winded / I wanted to include as much detail as possible.


Thanks!

[Shawzy44]

Any luck with this? I am experiencing the same thing.