Motor Blew Last Night

[Kodename47]

Originally Posted by John Rambo

The 2015 ECU didn't work for some reason, so I'm going to have to return it. They think a new 2013 one will solve the issue.

Here you go:
http://www.ft86club.com/forums/showt...light=ZA1JD00G

This is what I was on about. Flashing a 2015 tune onto a pre-2015 ECU causes issues with canbus comms, therefore it is likely that a 2015 ECU causes the same issues. If you still have working sensors it'd be easier (read cheaper) to swap the required sensors over rather than replace all the parts needed from a 2015

[John Rambo]

Originally Posted by FRS Justin

I assume they reset the code and it came back. Before dumping 700 in a ecu I would check to make sure the harness doesn't have a short or the sensor is bad.
Did you have that code before the engine blew or after the swap. Either way I don't think that was the reason for your motor giving up the ghost. when things fail like that (cam sensor) they go back to a factory default that is designed to save a motor not finish it off. If you bypassed the factory ecu and it had no codes its in the electrical system has to be. I hate seeing you having to dump that kind of cash on a ecu..

I don't really see how the sensor would be bad or the harness would have a short if when they bypassed the factory ecu it worked fine... I think they used some sort of scanner to verify that the particular sensor was returning the proper data, Randy said that they were making adjustments to the tune and they were working fine so maybe that's what they did.

But I don't know if it's what caused my motor to go either, but they keep saying it might have been the cause and that I could have had a bad ECU all along and their tune was fine but the ECU was bad. The thing is, I'd never seen that code before, and from what I understand not many people have.

Originally Posted by Kodename47

Here you go:
http://www.ft86club.com/forums/showt...light=ZA1JD00G

This is what I was on about. Flashing a 2015 tune onto a pre-2015 ECU causes issues with canbus comms, therefore it is likely that a 2015 ECU causes the same issues. If you still have working sensors it'd be easier (read cheaper) to swap the required sensors over rather than replace all the parts needed from a 2015

Okay, I'm still confused about this. So you are saying that a 2015 tune on a pre-2015 ECU causes problems, but in my car, they just used my 2013 ECU with a 2013 tune and got a P0011, and then they used a 2015 ECU with a 2015 tune and the car started in limp mode and is not communicating with the gauge cluster, even though it works fine otherwise. What sensors would I have to swap over in order to use either ECU?

Edit: Okay, I read the thread a second time and I think maybe if they flashed my 2015 ECU with a 2013 tune it might do the trick. Or, if they permanently disable whichever code that was mentioned in the thread. Idk how expensive it would be to do this because the 2015 ECU has not been flashed with ECUtek which is all Evasive tunes with and I don't want to have to pay for a license just to patch it... Even if it might be cheaper, since there isn't a guarantee it would work. Thoughts? Is there a way I can flash the 2013 tune on it or permanently disable a CEL on the cheap? If I can get them to try this it's worth a shot

Edit again: Maybe I'll ask them after the weekend if they could try the sensor from the old motor if they hadn't already?

[cookiesowns]

Did the new motor come with the proper "2015" cam position and crank position sensors ? Pretty sure those are different on the 2015 motor

The new 2015 block is quite a bit different than the 2013, in a good way as well. You will need a 2015 ECU and the proper sensors on the 2015 motor along with a proper 2015 tune which for the US market should be the D00C

I'm not 100% sure if the DI ECU is different though.

Start with the 2015 ECU pull with a stock ROm that came with that ECU and see where you get.

EDIT: just read you already tried it. In that case I think you may need a new gauge cluster. What is the code that's being thrown for the can bus communication error with the gauge cluster ?

Side note, maybe convince evasive to hook you up with the Motec from the race car and make big power later down the road ?

[steve99]

Originally Posted by John Rambo

I don't really see how the sensor would be bad or the harness would have a short if when they bypassed the factory ecu it worked fine... I think they used some sort of scanner to verify that the particular sensor was returning the proper data, Randy said that they were making adjustments to the tune and they were working fine so maybe that's what they did.

But I don't know if it's what caused my motor to go either, but they keep saying it might have been the cause and that I could have had a bad ECU all along and their tune was fine but the ECU was bad. The thing is, I'd never seen that code before, and from what I understand not many people have.


Okay, I'm still confused about this. So you are saying that a 2015 tune on a pre-2015 ECU causes problems, but in my car, they just used my 2013 ECU with a 2013 tune and got a P0011, and then they used a 2015 ECU with a 2015 tune and the car started in limp mode and is not communicating with the gauge cluster, even though it works fine otherwise. What sensors would I have to swap over in order to use either ECU?

Edit: Okay, I read the thread a second time and I think maybe if they flashed my 2015 ECU with a 2013 tune it might do the trick. Or, if they permanently disable whichever code that was mentioned in the thread. Idk how expensive it would be to do this because the 2015 ECU has not been flashed with ECUtek which is all Evasive tunes with and I don't want to have to pay for a license just to patch it... Even if it might be cheaper, since there isn't a guarantee it would work. Thoughts? Is there a way I can flash the 2013 tune on it or permanently disable a CEL on the cheap? If I can get them to try this it's worth a shot

Edit again: Maybe I'll ask them after the weekend if they could try the sensor from the old motor if they hadn't already?

OK

I dont know for certain the the 2015 ECU is hardware identical to the 2013 ECU but i suspect it is.

correct a 2015 ROM in a 2013 or 2015 ECU will not work in a 2013 car as the 2015 ROM(tune) expects to see something different in the dash and in the alternator (yep alternator is controlled by ecu)

ROMs from calid 700C to B01C are all compatable then after that something changed in dash or dash firmware and possibly alternator model and the newer ROM calids like D00C/F00C will not work in older cars.

Its very possible that if you flash a 2013 ROM likely a B01C into the 2015 ECU hardware it will work with your 2013 car.

but put that old rom in a 2015 car with updated dash and it wont work.

[steve99]

Originally Posted by John Rambo

I believe they used my stock (2013) harness, stock (2013) ecu, and reflashed. I was told my brz starts fine and everything, just a P0011 code. I had never seen this code ever, so they think the ECU threw the code unnecessarily, pulled timing and then boom. They can't get it to go away, but their motec ecu has the car running perfect.
Like I said they don't think this is a physical problem, they think the ECU is bad. The 2015 ECU didn't work for some reason, so I'm going to have to return it. They think a new 2013 one will solve the issue.

Edit:sorry for the double post

Any replacement stock ECU (new or used) will need to be security coded into the imobiliser system. You cannot just swap in replacement ECU.

A dealer will need to re-code the replacement ECU into the car.

MOTEC ecu bypass the security i believe

The ECU/Imobiliser-authentication unit/Dash are part of a security set if you change any of those components security recoding is necessary.

This is totally separate to flashing a tune or rom

[FRS Justin]

Originally Posted by cookiesowns

Did the new motor come with the proper "2015" cam position and crank position sensors ? Pretty sure those are different on the 2015 motor

The new 2015 block is quite a bit different than the 2013, in a good way as well. You will need a 2015 ECU and the proper sensors on the 2015 motor along with a proper 2015 tune which for the US market should be the D00C

I'm not 100% sure if the DI ECU is different though.

Start with the 2015 ECU pull with a stock ROm that came with that ECU and see where you get.

EDIT: just read you already tried it. In that case I think you may need a new gauge cluster. What is the code that's being thrown for the can bus communication error with the gauge cluster ?

Side note, maybe convince evasive to hook you up with the Motec from the race car and make big power later down the road ?

What changed on the block from 2013 to 2015?


Also I checked all the part numbers on 2013 and 2015 crankshaft sensor, cam sensors, and knock sensors they are all the same number. So NO changes in sensors


The only changes to the motor that I know about were the valves in 2014
I also ran the block and short block numbers and they are the same in 2013 and 2014

[steve99]

Originally Posted by John Rambo

I don't really see how the sensor would be bad or the harness would have a short if when they bypassed the factory ecu it worked fine... I think they used some sort of scanner to verify that the particular sensor was returning the proper data, Randy said that they were making adjustments to the tune and they were working fine so maybe that's what they did.

But I don't know if it's what caused my motor to go either, but they keep saying it might have been the cause and that I could have had a bad ECU all along and their tune was fine but the ECU was bad. The thing is, I'd never seen that code before, and from what I understand not many people have.


Okay, I'm still confused about this. So you are saying that a 2015 tune on a pre-2015 ECU causes problems, but in my car, they just used my 2013 ECU with a 2013 tune and got a P0011, and then they used a 2015 ECU with a 2015 tune and the car started in limp mode and is not communicating with the gauge cluster, even though it works fine otherwise. What sensors would I have to swap over in order to use either ECU?

Edit: Okay, I read the thread a second time and I think maybe if they flashed my 2015 ECU with a 2013 tune it might do the trick. Or, if they permanently disable whichever code that was mentioned in the thread. Idk how expensive it would be to do this because the 2015 ECU has not been flashed with ECUtek which is all Evasive tunes with and I don't want to have to pay for a license just to patch it... Even if it might be cheaper, since there isn't a guarantee it would work. Thoughts? Is there a way I can flash the 2013 tune on it or permanently disable a CEL on the cheap? If I can get them to try this it's worth a shot

Edit again: Maybe I'll ask them after the weekend if they could try the sensor from the old motor if they hadn't already?

2015 ECU firmware wont work with 2013 car dash/alternator it will likey throw U0155 and another code related to alternator control start pulse which i have forgotten, car will go into limp mode will not rev over 4000rpm.

flash the 2013 ROM firmware into the 2015 ECU

or get a 2013 ECU and firmware

MOTEC ECU may not apply the same tolerances or checks/tests on the cam position sensors as the Stock ECU firmware does hence it does not flag the P0011 cam position sensor code

P0011 is a known code that has occured often , it can be as simple as re-shimming the cam position sensors but may be the actuator or cam sprocket assembly or ECU

02-132-12 : DTCs Relating to the AVCS (Active Valve Control System)
11-130-13R : Difficulty Starting, Rough Idle, Cam Position, Misfire

I think the P0011 code is genuine you just need to find the cause ECU cam position sensor or clearance shimming required, new cam actuator or new cam sprocket assembly as per TSB's above

[John Rambo]

Originally Posted by steve99

2015 ECU firmware wont work with 2013 car dash/alternator it will likey throw U0155 and another code related to alternator control start pulse which i have forgotten, car will go into limp mode will not rev over 4000rpm.

flash the 2013 ROM firmware into the 2015 ECU

or get a 2013 ECU and firmware

MOTEC ECU may not apply the same tolerances or checks/tests on the cam position sensors as the Stock ECU firmware does hence it does not flag the P0011 cam position sensor code

P0011 is a known code that has occured often , it can be as simple as re-shimming the cam position sensors but may be the actuator or cam sprocket assembly or ECU

02-132-12 : DTCs Relating to the AVCS (Active Valve Control System)
11-130-13R : Difficulty Starting, Rough Idle, Cam Position, Misfire

I think the P0011 code is genuine you just need to find the cause ECU cam position sensor or clearance shimming required, new cam actuator or new cam sprocket assembly as per TSB's above

I was also thinking the motec might not apply the same checks as the factory ECU...
But in those TSB's, they only say it affects 2013 BRZ's, but my engine is a 2015. And the one that has P0011 in it says to replace the ECM if installing and testing new mechanical parts has already been done. Assuming the 2015 motor is fine, which it may very well not be since it's a junkyard motor, wouldn't the next logical step be to replace the ECM?

I may have them flash my 2015 ECU with a 2013 tune first before I buy a new one. I think that might work if you are right in suspecting the 2015 and 2013 ECU's are identical. I don't know how cheap this will be however since I would need to puchase another ECUtek license... and then what if the ECU still doesn't work... advice please?

[steve99]

Originally Posted by John Rambo

I was also thinking the motec might not apply the same checks as the factory ECU...
But in those TSB's, they only say it affects 2013 BRZ's, but my engine is a 2015. And the one that has P0011 in it says to replace the ECM if installing and testing new mechanical parts has already been done. Assuming the 2015 motor is fine, which it may very well not be since it's a junkyard motor, wouldn't the next logical step be to replace the ECM?

I may have them flash my 2015 ECU with a 2013 tune first before I buy a new one. I think that might work if you are right in suspecting the 2015 and 2013 ECU's are identical. I don't know how cheap this will be however since I would need to puchase another ECUtek license... and then what if the ECU still doesn't work... advice please?

Flash the ecu with tactrix adapter if they have one no licence required no locks no seed key changes ect and you can easily flash it back to original

C Series
ZA1JA700C ,900C, A00C ,A01C , B00C all compatible with ZA1JB01C
ZA1JD00C for late 2014/2015 cars only
ZA1JF00C for late 2015 cars


Most of the stock rooms are at end of tactrix link below.

you wont be able to use the "stock" roms that come with ecutek as they are encrypted for ecutek. The un-encrypted roms are attached to tactrix post link below http://www.ft86club.com/forums/showthread.php?t=62332

Did not realise it was full 2015 motor thought you rebuilt 2013 motor the 2015 firmware in ecu still won't work due dash unless you swap out dash and immobiliser from the 2015 as well and probably a 2015 alternator

It's possible the 2015 motor has updated cam actuators or sensors that may cause the cam cel code it's all a bit unknown

[CSG Mike]

sent you a PM OP.

[John Rambo]

So, I bought a new ECU (2013) from Subaru to use in my car, and had them program the immobilizer to my keys.

Same exact problem as the 2015 ECU: Code U0155 came up. Car idles fine but is in limp mode.

At this point the dealer, evasive, and I are all confused. A brand new 2013 ECU should not have problem communicating with the cluster. Anyone have any ideas?
This is a timeline of events up to now, as Randy from Evasive documented in an email:

Replacement engine went in. Car had a bad idle at start up, but no CEL. (Note: originally Randy told me there was a P0011 code...)

We figured out the cam sensor was causing a bad idle. Cam Sensor was slow to read and not showing the correct values. We swapped sensors and cam actuator which did nothing.

We believed it could of been a bad ECU which we found out Subaru had a few problems with the 1st gen BRZs.

So we decided to swap ECUs with our Motec System. So we can test if the ECU was causing the car to idle bad. The car ran perfect on start up with the Motec system installed. Cam Sensor read correctly and was showing the correct values this time.

So at this point everything is pointing to the ECU is bad.

You gave us a (Used 2015 ECU) and got it programmed at Subaru in your 2013.

Car runs perfect at idle but was in limp mode. It wouldn’t pass 4k and CEL U0155 came up. Lost comm with cluster

Decided to try a (New 2013 ECU)

Car runs perfect at idle but was in limp mode. It wouldn’t pass 4k and CEL U0155 came up. Lost comm with cluster

At this point I have no idea what it can be. Hopefully Subaru forgot to do a procedure on doing the new ECU programming which can fix this. I will have a better answer on Friday.

[Kodename47]

What Calibration is on the ECU?

[steve99]

Originally Posted by John Rambo

So, I bought a new ECU (2013) from Subaru to use in my car, and had them program the immobilizer to my keys.

Same exact problem as the 2015 ECU: Code U0155 came up. Car idles fine but is in limp mode.

At this point the dealer, evasive, and I are all confused. A brand new 2013 ECU should not have problem communicating with the cluster. Anyone have any ideas?
This is a timeline of events up to now, as Randy from Evasive documented in an email:

What was your Original ECU Calid If it was ZA1JB01C or earlier you can run ZA1JB01C code. Dont try to run a later calid like ZA1JD00C or later as it wont work with the 2013 Dash cluster.

Read the calid from the ECU the dealer may have stuffed up and it may have D00C or later calid

U0155 can also be caused by devices plugged into the OBD port glitching or over loading the CAN BUSS.

remove everything from obd port, remove battery terminal press brake to reset ecu, reconnect battery and start with nothing plugged in obd port, do you still get check engine light ?

If you disable U0155 in the rom DTC codes it wont go into limp mode anymore, but thats a dodgy fix, you need to find the cause.

[John Rambo]

Originally Posted by steve99

What was your Original ECU Calid If it was ZA1JB01C or earlier you can run ZA1JB01C code. Dont try to run a later calid like ZA1JD00C or later as it wont work with the 2013 Dash cluster.

Read the calid from the ECU the dealer may have stuffed up and it may have D00C or later calid

U0155 can also be caused by devices plugged into the OBD port glitching or over loading the CAN BUSS.

remove everything from obd port, remove battery terminal press brake to reset ecu, reconnect battery and start with nothing plugged in obd port, do you still get check engine light ?

If you disable U0155 in the rom DTC codes it wont go into limp mode anymore, but thats a dodgy fix, you need to find the cause.

I'll find out from Subaru what calid the ECU has, but I would assume they loaded the one for my vin number.

Subaru is really confused, and they're telling me to buy a new gauge cluster???? Please someons tell me I don't have to do this, slowly going broke and insane