View Single Post
Old 03-12-2018, 04:56 PM   #4
steve99
Banned
 
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,996
Thanks: 1,035
Thanked 4,994 Times in 2,984 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
Quote:
Originally Posted by tomm.brz View Post
Steve what are the differences between D00G and F10g , and the earlier a01g/a02g?
why cant earlier car that have a02g update to d00g?



Their is sometimes hardware or firmware changes to car that are not obvious


700G A00G A01G all compatible with A02G, but if you try to run D00G in early car will throw a couple of cel code the Dash cluster communications and alternator from memory ,I tried it :-)

I assume that they made some mods to alternator control and dash cluster firmware.


strange thing is you can run A01G/A02G in all cars up to F20P so its backwards compatible, but not forwards compatible.


However if you try to run A01G/2G in a K00P or K00G then it locks out security , again I found this the hard way. flashing original rom back doent fix it car still wont start, needed to do ecu resync procedure to get car going.


moral of story is subaru/Toyota don't tell you about changes or compatibility so safest option is to run same calid in car as original unless you can find a TSB that specifically states the update is compatible. Or you are pretty confident with ECU flashing and have spare ECU and appropriate flash tools and willing to risk problems to find out if the firmware is compatible.


Ecutek will no longer let you force write roms id that ecutek thinks is incompatible, and oft will only flash same calid as stock.


Tactrix/ecuflash will flash anything you tell it no questions asked.


its possible to bypass those safety features but be prepared for issues if you do.


all the ECU are same processor and all roms are same size, but the software operation can be different and sensors on cars may be different.
steve99 is offline   Reply With Quote
The Following User Says Thank You to steve99 For This Useful Post:
tomm.brz (03-12-2018)