Cannot read flash from Evo9 (UK FQ)

[SilverBack]

OpenECU Version 2.7
OpenPort for Mitsubishi 1.3M

Cannot read flash image.

I get a 'No response to init' error when attempting to read (x2)

Car ignition is on, both connector are in.

I can hear a solenoid clicking in the dash as it attempt to initialise

I'm I missing something? Has anybody had this working on a UK FQ?

[S54fan]

Options... Port... OpenECU Mitsi 1.3 selected? (ie driver installed and cable found)?

Any DLL errors on starting ECUflash?

FQ340?

I've read a JDM GSR ECU on my IX FQ340. Wouldn't connect to my previously Ecutek'd ECU, and probably wouldn't connect to the original FQ340 ECU either since that has also been Ecutek'd. FQ300 or 320 should be OK I think as they should be the same as the GSR - will be interesting to compare.

[galvitron]

I know that the FQ400 uses a Motec M800 OEM ECU. So do the FQ340's have the same??

[SilverBack]

Options... Port... OpenECU Mitsi 1.3 selected? (ie driver installed and cable found)?

Any DLL errors on starting ECUflash?

FQ340?

I've read a JDM GSR ECU on my IX FQ340. Wouldn't connect to my previously Ecutek'd ECU, and probably wouldn't connect to the original FQ340 ECU either since that has also been Ecutek'd. FQ300 or 320 should be OK I think as they should be the same as the GSR - will be interesting to compare.

Yup, All installed OK. Option shows and is selected under Options.

No errors on app start. Log shows no errors.

I'm not sure it is driver related. I wondering what ECU the UK FQ320 has in it...

Log actually says:

Sending init sequence 1 (0001)
Sending init sequence 1 (FFFF)
No response to any known code.

[SilverBack]

I know that the FQ400 uses a Motec M800 OEM ECU. So do the FQ340's have the same??

I think the 8 FQ340 has a piggy back ECU (RalliArt?). Not sure if the 320 has a JDM ECU or something else. Not sure if the 9 FQ340 has a piggyback or is just remapped to get to 345.

Looks like my ECU is coming out at the weekend for a look-see...

[S54fan]

My understanding of the late UK models is as follows:

Evo VIII MR
FQ300/320-same as JDM GSR
FQ340-same ECU but with Unichip
FQ400-Motec M800 P&P locked

Evo IX
FQ300/320-same as JDM GSR
FQ340-Ecutek remap

[SilverBack]

Opps, sorry missed this bit:

"I've read a JDM GSR ECU on my IX FQ340. Wouldn't connect to my previously Ecutek'd ECU, and probably wouldn't connect to the original FQ340 ECU either since that has also been Ecutek'd. FQ300 or 320 should be OK I think as they should be the same as the GSR - will be interesting to compare."

Cheers for the info.

"Evo VIII MR
FQ300/320-same as JDM GSR
FQ340-same ECU but with Unichip
FQ400-Motec M800 P&P locked

Evo IX
FQ300/320-same as JDM GSR
FQ340-Ecutek remap"

Saved me from taking the bugger out to have a look-see

So if it is not the driver, not the ECU... what, dodgy cable? Idiot user?

There is an odd message about clicking OK quickly after switching on the ignition... prehaps I've been too slow...?

[S54fan]

I had a finger on the left mouse button and turned it on and within half a second clicked.

[SilverBack]

I had a finger on the left mouse button and turned it on and within half a second clicked.

It's driving me mad. It must be me...

I've been out and tried to connect another 20 or so times. Yeah, I'm on the OK button using the up-mouse. I've tried an number of thing, both at at same time, a fraction of a second later on the OK...

Looking back through the logs it looks to have made a partial / incomplete connection once but that's it.

Is the timing really that tight that I can be miss-timing the click still....?

[S54fan]

Don't think the timing is tight. Mine worked on the third go when I had the right ECU plugged in and the right cable set.

Post the logs?

[AutoXer]

Log actually says:

Sending init sequence 1 (0001)
Sending init sequence 1 (FFFF)
No response to any known code.

That's the same thing that I get when I try to read my EcuTek'ed ECU. I have read succesfully from my 2nd ECU that I bought off of eBay.

[SilverBack]

Log actually says:

Sending init sequence 1 (0001)
Sending init sequence 1 (FFFF)
No response to any known code.

That's the same thing that I get when I try to read my EcuTek'ed ECU. I have read succesfully from my 2nd ECU that I bought off of eBay.

Thanks but it's a standard ECU, it's had no mapping yet...

[cboles]

There is no "flast click" issue with Mitsubishis - only some Subarus. The wire on the second connector for the Mitsubishi hard boots the processor in a different mode. It really doesn't matter what the ECU was doing before (including running the car ).

Opps, sorry missed this bit:

"I've read a JDM GSR ECU on my IX FQ340. Wouldn't connect to my previously Ecutek'd ECU, and probably wouldn't connect to the original FQ340 ECU either since that has also been Ecutek'd. FQ300 or 320 should be OK I think as they should be the same as the GSR - will be interesting to compare."

Cheers for the info.

"Evo VIII MR
FQ300/320-same as JDM GSR
FQ340-same ECU but with Unichip
FQ400-Motec M800 P&P locked

Evo IX
FQ300/320-same as JDM GSR
FQ340-Ecutek remap"

Saved me from taking the bugger out to have a look-see

So if it is not the driver, not the ECU... what, dodgy cable? Idiot user?

There is an odd message about clicking OK quickly after switching on the ignition... prehaps I've been too slow...?

[SilverBack]

There is no "flast click" issue with Mitsubishis - only some Subarus. The wire on the second connector for the Mitsubishi hard boots the processor in a different mode. It really doesn't matter what the ECU was doing before (including running the car ).

Opps, sorry missed this bit:

"I've read a JDM GSR ECU on my IX FQ340. Wouldn't connect to my previously Ecutek'd ECU, and probably wouldn't connect to the original FQ340 ECU either since that has also been Ecutek'd. FQ300 or 320 should be OK I think as they should be the same as the GSR - will be interesting to compare."

Cheers for the info.

"Evo VIII MR
FQ300/320-same as JDM GSR
FQ340-same ECU but with Unichip
FQ400-Motec M800 P&P locked

Evo IX
FQ300/320-same as JDM GSR
FQ340-Ecutek remap"

Saved me from taking the bugger out to have a look-see

So if it is not the driver, not the ECU... what, dodgy cable? Idiot user?

There is an odd message about clicking OK quickly after switching on the ignition... prehaps I've been too slow...?

Thanks for the info.

So, what I'm I doing wrong?

[cboles]

You have the white connector plugged in, right? I can see that the OpenPort is transmitting OK, because the software verifies everything it sends, and you would get an error if it wasn't transmitting OK. I test every cable, so a bad cable is unlikely. It seems to me that the initialization code may be different. If you can try reading from another car, we can rule out the cable completely.