weird a01c calibration issues
 

wantring to know if anyone has had issues pertaining to the a01c calibration, I know that openflash used base b01c calibration for this ecu but when attempting to tune romraider isn't reading the calibration right and anything logical just doesn't make sense, this is the first one I seen like this and is being quite the pita so hoping someone may have some insight into it.
car is boosted and needs a tune but nothing makes sense so it is difficult to get it done, I have included and orig file from the ecu which is new and a couple other files if someone would like to look at it, thanks in advance

Look at the thrre calibration id strings insde eom with hex editor


If they are all same ie all A01C then its a real A01C. If the last one is different then that indicates the real base rom id


Oft tues use may differnt base roms

I am aware of this, but even if is the case using oft tunes, what's the deal with being unable to make any sense of the original file or it running weird on the new ecm with codes p062d and p1235 popping in ? this throwing me off every single car I have tuned has never been like this, it seems straight bonkers

yes this is a new OEM ecm from Toyota, what's also weird is using a matco scan tool, it wont accept a new vin either so idk wtf is going on at this point, the oft did however pull the base even with no vin :iono:

another thing was the original was a00c

Ok had a look at the roms the oft turbo SC A01C is a genuine A01C so you need to use a romraider genunine A01C definition


This rom appears to be set up for a fairly low boost turbo or SC like 8psi, im guessing, judfing by srock injector scaling and the pi\di tables



The other mod A01C is rearly a B01C rom made to look like an A01C


Also it way incomplete as far a setting up for a turbo is concerbed load limits are not set ,its got 700 cc jnjectors scaled but pi\di ratios dont suit



Fuel tables not rescaled for load


Load will truncate at 1.7 likely not enough maf flow limit too low
Seriously dont use that ot your likely to blow stuff up


The two cel codes your getting appear to be hardware issues


If your trying to use either of those roms with an oft married to an A00C car it wont lad as oft wants to see a rom that looks like an A00C

had to put a new ecm in, orig ecm coding came as a00c the new ecm when connected to the oft identified as a01c so I am assuming this would now be correct. I cant see how its scaled for 700 as in romraider it doesn't show anything that says 700 usually it reads out and can be edited but the rom is all weird such as the maf scale table as well. :iono: would Toyota be able to update the car to say something readable like b01c? or later? the injectors are new as is the ecm so idk or understand a hardware issue :iono:

If the tavles in romraider look weird or incorrect, strange numbers symbols or strange axis on tables then you definitin is incorrect and not matched to the rom your editing.


Romraider looks at the calid at 8000 hex in any rom and just gries to match that. Its very easily confused by oft rom calid changes. Editing a rom with incorrect definition will at best cause unusuall wngine behaviour and can also get the ecu into a locked up state


Each time you flash a rom its a complelty new rom. The old one is erased first.


From what your sating i think you problems are matching definions to your calid adjusted roms

so would it be a situation that can be resolved by having Toyota flash the updated factory calibration? or can it be updated via tactrix?

thanks for all input thus far this has been a pita

By having the correct definition file for the ROM.

As kodename47 said.


getting dealer to reflash wont help


it appears to be a tune to definition matching issue, you cannot rely on def or tune names to determine if they match, you need to break out the hex editor and check tunes and find correct defs based on the modified calids in tune

darn it, even if its a stock flash to put it back the way it came from the factory?

I really don't like to mess with hex editing :bonk:
@Kodename47 if they update it to a bo1c or newer I have the def for the file, is this what you are implying?

hex editor was mentioned less with need to use it, more with 'double-check what actual calids in binary blob are, not just first from those (possibly changed) that flashing software might misreport'. Hex editor just as one of means to check for those calids in binary firmware file.

But also definitely, as tune definitions tell at which address which value tables reside and as that is specific to tune version, it's of utter importance to have definition table to match tune editted/flashed, to not have wonders that changing some table alters some random code in firmware image, instead of altering table that wished.

none of this sounds good, and the fact it throws 2 codes after a new ecu that should just be a stock calibration on it is bothersome, is it possible the body control module is having an issue?

also a note about the original ecu which don't know if this would be helpful or not but.

it was attempted to flash a calibration using tactrix, it flashed but then was basically dead, and when we tried to go back it wouldn't even connect. so I am worried if maybe the tactrix messed up something else in the car

@1quickchic here you go:
Because of this if you have a genuine A01C definition it will not read the top one correctly. If you have a OFT definition the bottom 2 will read incorrect. Flashing using the wrong Ecuflash ID can brick the ECU, as you found. You cannot have 2 A01C definitions in Romraider, so you need to find a way around it. If you're flashing using Tactrix then best avoid using a cal ID hacked tune, or correct the 2 addresses back to B01C. This is simple to do, just download HxD off the internet and have a look.