03OZstocker

I have gone back to NA from being turbo with some headers and i am wanting to go back to my saved stock ECU. The issue as of right now is i cannot connect to the ECU through ECUflash. Ive done tuning before in this car with this same PC and the same version of ECUflash. I've deleted and reinstalled ECUflash and updated the definition files from Senate.

Here is the Log from ECUflash which shows near the bottom that it has no response to any code.

[21:34:32.752] Logging to file C:/Users/Owner/AppData/Roaming/OpenECU/EcuFlash/logs/ecuflash_log_20190323t213432.txt

[21:34:32.752] EcuFlash Version 1.44.4799

[21:34:32.752] OS Version Windows 10

[21:34:32.752] Kernel Type winnt

[21:34:32.752] Kernel Version 10.0.14393

[21:34:32.752] CPU x86_64

[21:34:32.752] Product Name Windows 10

[21:34:32.752] Product Type windows

[21:34:32.752] Product Version 10

[21:34:32.752] Qt Version 5.6.0

[21:34:32.752] Qwt Version 6.1.2

[21:34:32.752] QwtPlot3D Version 0.2.6

[21:34:32.752] Boost Version 1.60

[21:34:32.752] FTDI Library Version 3.02.11

[21:34:32.752] Openport J2534 Library Version 1.02.4798

[21:34:32.767] 67 memory models read.

[21:34:32.767] scanning for metadata models in C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata

[21:34:54.034] 774 ROM metadata models scanned.

[21:34:54.034] checksum module "subarudbw" loaded.

[21:34:54.034] checksum module "subarudiesel" loaded.

[21:34:54.034] checksum module "subaruhitachi" loaded.

[21:34:54.034] checksum module "mitsucan" loaded.

[21:34:54.034] checksum module "mitsuh8" loaded.

[21:34:54.034] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.

[21:34:54.034] patch module "Mitsu CAN RAM Parameter Logging" loaded.

[21:34:54.034] using metadata XML ID read_evo7 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo7.xml

[21:34:54.299] flashing tool "wrx02" loaded.

[21:34:54.315] flashing tool "wrx04" loaded.

[21:34:54.315] flashing tool "sti04" loaded.

[21:34:54.315] flashing tool "sti05" loaded.

[21:34:54.331] flashing tool "mitsucan" loaded.

[21:34:54.331] flashing tool "mitsukernel" loaded.

[21:34:54.331] flashing tool "mitsukernelocp" loaded.

[21:34:54.331] flashing tool "mitsubootloader" loaded.

[21:34:54.331] flashing tool "shbootmode" loaded.

[21:34:54.331] flashing tool "shaudmode" loaded.

[21:34:54.331] flashing tool "subarucan" loaded.

[21:34:54.331] flashing tool "subarucand" loaded.

[21:34:54.346] flashing tool "subarubrz" loaded.

[21:34:54.346] flashing tool "subaruhitachi" loaded.

[21:34:54.471] FTDI Driver Version 2.12.12

[21:34:54.487] Using interface OpenPort 1.3 Mitsubishi TX36v9DKa98637d5b362fcac7fc025e4a0ee94216b6db90b

[21:34:54.502] interface close

[21:34:54.565] FTDI Driver Version 2.12.12

[21:34:54.581] Using interface OpenPort 1.3 Mitsubishi TX36v9DKa98637d5b362fcac7fc025e4a0ee94216b6db90b

[21:34:54.581] interface close

[21:34:54.643] FTDI Driver Version 2.12.12

[21:34:54.674] Using interface OpenPort 1.3 Mitsubishi TX36v9DKa98637d5b362fcac7fc025e4a0ee94216b6db90b

[21:34:54.674] interface close

[21:34:54.737] FTDI Driver Version 2.12.12

[21:34:54.752] Using interface OpenPort 1.3 Mitsubishi TX36v9DKa98637d5b362fcac7fc025e4a0ee94216b6db90b

[21:34:54.752] interface close

[21:34:54.815] FTDI Driver Version 2.12.12

[21:34:54.831] Using interface OpenPort 1.3 Mitsubishi TX36v9DKa98637d5b362fcac7fc025e4a0ee94216b6db90b

[21:34:54.831] interface close

[21:34:54.909] FTDI Driver Version 2.12.12

[21:34:54.924] Using interface OpenPort 1.3 Mitsubishi TX36v9DKa98637d5b362fcac7fc025e4a0ee94216b6db90b

[21:34:54.924] interface close

[21:34:59.018] using metadata XML ID read_evo7 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo7.xml

[21:34:59.034] FTDI Driver Version 2.12.12

[21:34:59.049] Using interface OpenPort 1.3 Mitsubishi TX36v9DKa98637d5b362fcac7fc025e4a0ee94216b6db90b

[21:35:02.864] interface close

[21:35:08.956] using metadata XML ID read_evo7 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_evo7.xml

[21:35:08.956] FTDI Driver Version 2.12.12

[21:35:08.972] Using interface OpenPort 1.3 Mitsubishi TX36v9DKa98637d5b362fcac7fc025e4a0ee94216b6db90b

[21:35:11.347] sending init sequence 1 (F0F0)

[21:35:14.619] sending init sequence 1 (0001)

[21:35:17.885] sending init sequence 1 (0003)

[21:35:21.150] sending init sequence 1 (FFFF)

[21:35:23.900] no response to any known code

[21:35:23.900] interface close

What does this stuff mean and what the heck am i supposed to do.
The current ROM is a tephra.v7 tune adjusted for my turbo setup etc which i dont feel comfortable running this ROM being NA again.

xCasserole 420

It sounds to me like its not reading the immobilizer code in your ROM, check to make sure you have that in there.