GR Yaris brake system error in a secondary collision

Rastislav Kokavec

New member
Joined
Aug 8, 2023
Messages
1
Reaction score
0
Hi, i would like to ask some informations abou problems with my GR yaris
My car have 500km
After 400 kilomters car show this type of fault brake system error in a secondary collision. Today is 6 months in toyota servis a they are no possible to find problem a make my car good
We have this types od fault codes P030100, P030200, P03000, P030027
Have you same problems or some informations abou this ?
Thank you
 
Welcome Rastislav. As far as I know P030100, P030027 etc. are engine related (engine has random misfire), codes for the brake system start with P05. If possible give us some more information: Are these errors permanent, when do they happen (accelerating with light or full throttle etc,)? The more information the more help will come.

Bye for now Fred
 
I have exactly the same problem here in Australia. My car has 12,000klm and I get the same codes and a CEL & Visit your dealer. & the Secondary Brake message. & sometimes a TRC light. Those codes are all about random misfires being detected ( as Fred says above). The secondary collision message is triggered by the misfire codes, I think.

My engine & ECM are stock. No tuning box and stock air filter box.

My dealer is working hard but so far they cannot find the problem either.
We have checked all the grounding points in the engine bay, all the hose connections from the air filter box to the turbo to the intercooler to the throttle body and the vacuum hoses.

We have changed:
Coil packs
spark plugs
MAF sensor
Both MAP sensors
crankshaft angle sensor
Intake camshaft sensor
Pumped out the fuel tank & removed all fuel. It was clean. Added fresh fuel.

I cannot feel any misfire, the car idles fine and drives fine. Knock correction value is low (13) when it should be higher (24).

It is like fake phantom misfires logged by the ECM.
 
I had a brake override fault message and a secondary brake collision message sometimes with the TRC light on. It was caused by a faulty boost control solenoid which makes no logical sense but you can forget logic if are dealing with a Denso ECU.
 
Car electronics can be mysterious. Especially cars with CAN bus system tend to broadcast stupid and incomplete messages across the car, ECU (not limited to Denso) misinterpretes this and the car will report bullshit... Yes, boost control sensor can be one of the reasons that makes CAN going crazy...

Bye for now Fred
 
I had a brake override fault message and a secondary brake collision message sometimes with the TRC light on. It was caused by a faulty boost control solenoid which makes no logical sense but you can forget logic if are dealing with a Denso ECU.
Thank you. Was that the MAP boost & temperature sensor at the manifold? Or a different part?
I have replaced both MAP sensors on my car.
 
Different part, located near the oil filler cap.

Boost Control Solenoid .webp
 
Hi, i would like to ask some informations abou problems with my GR yaris
My car have 500km
After 400 kilomters car show this type of fault brake system error in a secondary collision. Today is 6 months in toyota servis a they are no possible to find problem a make my car good
We have this types od fault codes P030100, P030200, P03000, P030027
Have you same problems or some informations abou this ?
Thank you
More news:
I have proved that these codes in my car and the random misfire counts (which are not real misfires) are caused by the knock sensor detecting a noise.
While it is detecting "misfire counts", the counts stop and show zero if I put my foot on the clutch & select 1st gear to stop the gearbox input shaft & clutch plate turning.
The counts start again as soon as I let it idle in neutral with my foot off the clutch.
The problem happens when the input shaft & clutch plate are turning.

I am thinking that the clutch plate is bent and it is causing the input shaft to wobble and make a noise.

The gearbox is coming out tomorrow to examine the clutch.

I will reply again when we find the problem.

PROBLEM SOLVED:
 
Last edited:
Back
Top