Problems updating form ZA1JA01G to ZA1JD00G ROM - fixed disable U0155 code in rom

[steve99]

Originally Posted by Td-d

I think that's if - did not come through when I ran the script on the RR definition to convert to Ecuflash. I've edited and uploaded to Github.

Thanks I will test it out tomorrow

[steve99]

Ok tried again with corrected definitions. Flashes fine no errors car runs logging ok but in limp home mode and U0155 can-buss communications error cannot clear.

Soon as you flash back older rom all good.

looks like D00G roms not compatable with A01G.

Anyone else tried
if someone has a D00G rom can you send it to me or a A02G thanks

[elBarto]

Can the dealer flash a (official) 2015 D00G update on a A0xG car?
I will pay happily the bill if they can do it without any troubles.
It would be easy then, flash back to stock, dealer update, mod it

[Td-d]

Interested to hear from Shiv whether they have managed -I don't see why there would be a major difference between d00c and D00G (with D00c having been flashed already no problem)


Sent from my iPhone using Tapatalk

[Fizz]

@steve99 what improvements does the latest ZA1JD00G have over the A01G rom? Any benefits in updating to the new rom?

[steve99]

Originally Posted by Fizz

@steve99 what improvements does the latest ZA1JD00G have over the A01G rom? Any benefits in updating to the new rom?

I dont know as yet i have not been able to get car runnig on a stock d00g , i can load it and car runs idles ok but still get cel light and stuck in limp home mode due can buss error, everything works though its weird.

hoping someone else will load a d00g and see it they get same problems or its just related to my car. They may have update software in the body control computr or traction computer in 2015 cars and it not talking properly to my 2014

[AP756]

Tell me if I'm wrong. I suppose that the display cluster also is driven by ECU. If tyre pressure seems to be a problem you will go in limp mode and the display tries to throw an error. Your car definitive has no tyre pressure sensors and no matchingg display...

Two ways: Search for the tyre pressure table and alter the allowed pressure range. Or search for the routine transporting the alert and just enter a "no fault" jump address (don't allow reaction to alert).

My way to pay your help on top of those beers

Bye for now Fred

[steve99]

Originally Posted by AP756

Tell me if I'm wrong. I suppose that the display cluster also is driven by ECU. If tyre pressure seems to be a problem you will go in limp mode and the display tries to throw an error. Your car definitive has no tyre pressure sensors and no matchingg display...

Two ways: Search for the tyre pressure table and alter the allowed pressure range. Or search for the routine transporting the alert and just enter a "no fault" jump address (don't allow reaction to alert).

My way to pay your help on top of those beers

Bye for now Fred

We don't have tyre pressure monitoring or sensors, ROM was pulled from another australian BRZ but 2015 model

I believe the display cluster is driven from the Body Control unit.

Everything on my car worked ie display/dash no traction/VSC lights just the U0155 code/CEL and limp home mode evident by unable to rev beyond about 4000 rpm.

[AP756]

Originally Posted by steve99

We don't have tyre pressure monitoring or sensors, ROM was pulled from another australian BRZ but 2015 model

I believe the display cluster is driven from the Body Control unit.

Everything on my car worked ie display/dash no traction/VSC lights just the U0155 code/CEL and limp home mode evident by unable to rev beyond about 4000 rpm.

From 2015 on tyre pressure warnings are mandatory all over EU => Toyota had to upgrade their wiring loom => the ECU had to be adapted and the routines for tyre pressure warning had to be implemented => for countries where no tyre pressure warning is delivered this feature will be coded out using the tables in ROM (where you set any default equipment codes, might be in Body Control Unit).

My assumption: Due to the fact that Toyota won't make a wiring loom for every different need they produce one "universal wiring loom" with minimum effort/costs. So I believe all wires and code for this feature are in your (Australian 2015) wiring loom/ ROM too and we just don't know how to disable that sensor-less feature...

Viewed from other side: No tyre pressure sensors => no signal to process => this fault is permanent, so you can't delete => because it's a safety feature speed and revs are limited to make sure the driver recognizes something is wrong => limp mode. Flashing back to A01G the ECU, wires and sensors match again => no further problem => no limp mode.

How to solve: Hopefully someone will come around with an EU 2015 D00G ROM. Compare D00G with and D00G without tyre pressure warning side by side you will find the differences and probably you'll be able to work out a solution (where to set/reset the tyre pressure flag, if this is set in the ECU of course). Well, it's a slave work to do so, but it might be an attempt... Having some new documentation might be a big help too.

Sorry to bother you with an old, but instrucive story: Had a car some years ago which failed to start (no starter motor). Mechanically all was sound. After a long investigation with a couple of people and numerous laptops someone came around and suggested to check equipment codes. He was right! The car was AT but the codes said MT. Nobody was able to press the non existent clutch for getting the "clearance" to start the engine! After correcting the codes the "ghost was gone".

My two cents and bye for now Fred

[steve99]

Originally Posted by AP756

From 2015 on tyre pressure warnings are mandatory all over EU => Toyota had to upgrade their wiring loom => the ECU had to be adapted and the routines for tyre pressure warning had to be implemented => for countries where no tyre pressure warning is delivered this feature will be coded out using the tables in ROM (where you set any default equipment codes, might be in Body Control Unit).

My assumption: Due to the fact that Toyota won't make a wiring loom for every different need they produce one "universal wiring loom" with minimum effort/costs. So I believe all wires and code for this feature are in your (Australian 2015) wiring loom/ ROM too and we just don't know how to disable that sensor-less feature...

Viewed from other side: No tyre pressure sensors => no signal to process => this fault is permanent, so you can't delete => because it's a safety feature speed and revs are limited to make sure the driver recognizes something is wrong => limp mode. Flashing back to A01G the ECU, wires and sensors match again => no further problem => no limp mode.

How to solve: Hopefully someone will come around with an EU 2015 D00G ROM. Compare D00G with and D00G without tyre pressure warning side by side you will find the differences and probably you'll be able to work out a solution (where to set/reset the tyre pressure flag, if this is set in the ECU of course). Well, it's a slave work to do so, but it might be an attempt... Having some new documentation might be a big help too.

Sorry to bother you with an old, but instrucive story: Had a car some years ago which failed to start (no starter motor). Mechanically all was sound. After a long investigation with a couple of people and numerous laptops someone came around and suggested to check equipment codes. He was right! The car was AT but the codes said MT. Nobody was able to press the non existent clutch for getting the "clearance" to start the engine! After correcting the codes the "ghost was gone".

My two cents and bye for now Fred

Sounds possible that this could be problem.

would have thought it would be coded out of australian rom but maybe its still looking for some response from another module that has updated firmware.

Will see if tdd can find the tire pressure tables in rom and see if it can be disabled

[steve99]

OK more tests.

Flashed D00G rom with Open Flash Tablet just to check nothig weird with flashing with Tactrix/Ecuflash.

Same result CEL light code U0155.
Car runs fine everything ok dash works but in limp home mode.

Connected TechStream Toyota diagnostic software.

confirms Code U0155
Clear DTC with techstream, does not clear, current alarm
Further info is Engine ECU lost communications with Instrument Panel Cluster (IPC)

However everything on Instrument panel works ie speedo tachometer fuel/temp guages lights ect

Run diagnostic check on Can-buss all ok no errors.

Run diagnostic on Engine ECU says no comms with Instrument panel/cluster

Run diagnostic on Instrument panel/cluster no errors reported all ok

Appears something has changed with Instrument panel cluster either software or hardware and D00G rom has some sort of problem communicating with Instrument cluster.

It possible it could be Tire pressure monitoring related but no other systems reported errors to Techstream re TPMS errors ect.


For @AP756 checked Tire Pressure monitoring system with Techstream says not fitted to my car. ECU reported no errors trying to access TPMS.

Just for a laugh disconnected battery for 10 minutes to reset everything still same issues.

Appears to be Genuine Incompatibility @Td-d any ideas ??

[Td-d]

Hmm.. not off hand, not - and since it was not a TSB, there's no information on what's been updated.

I'll try and do a compare between the the A01G and this D00G, since if it throws any light on it. You could just disable the U0155, but then again, the A01G calibration is working fine for you.

[steve99]

Originally Posted by Td-d

Hmm.. not off hand, not - and since it was not a TSB, there's no information on what's been updated.

I'll try and do a compare between the the A01G and this D00G, since if it throws any light on it. You could just disable the U0155, but then again, the A01G calibration is working fine for you.

I will give disabling U0155 a go

[steve99]

@Td-d

Something weird again

Went to disable U0155 in D00G ROM.

Looked in Def file I have for D00G (ecuflash) and U0155 defined. However it does not show up when I open ROM in Ecuflash, also a couple of others missing is that a 32bitbase problem ??



<table name="(P2103) THROTTLE ACTUATOR CIRCUIT HIGH" address="11e2c4" />

<table name="(P2109) TPS A MINIMUM STOP PERF" address="11e288" />

<table name="(P2122) TPS D CIRCUIT LOW INPUT" address="11e30c" />

<table name="(P2123) TPS D CIRCUIT HIGH INPUT" address="11e318" />

<table name="(P2127) TPS E CIRCUIT LOW INPUT" address="11e2f4" />

<table name="(P2128) TPS E CIRCUIT HIGH INPUT" address="11e300" />

<table name="(P2135) TPS A/B VOLTAGE" address="11e324" />

<table name="(P2138) TPS D/E VOLTAGE" address="11e2e8" />

<table name="(U0073) CAN COMMUNICATION BUS A OFF" address="11e4c8" />

<table name="(U0101) CAN LOST COMMUNICATION WITH TCM" address="11e4a4" />

<table name="(U0122) CAN LOST COMMUNICATION WITH VDC" address="11e4bc" />

<table name="(U0155) LOST COMMUNICATION WITH INSTRUMENT PANEL CLUSTER (IPC) CONTROL MODULE" address="11e600" />

<table name="(U0402) CAN INVALID DATA RECEIVED FROM TCM" address="11e498" />

<table name="(U0416) CAN INVALID DATA RECEIVED FROM VDC" address="11e4b0" />

<table name="(U0423) INVALID DATA RECEIVED FROM INSTRUMENT PANEL CLUSTER CONTROL MODULE" address="11e5f4" />