|
Software Tuning Discuss all software tuning topics. |
|
Thread Tools | Search this Thread |
03-02-2020, 07:12 PM | #1 |
Senior Member
Join Date: Jan 2016
Drives: 2013 Panda ft86/FRS
Location: Oklahoma, USA
Posts: 147
Thanks: 22
Thanked 21 Times in 17 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
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 |
03-02-2020, 09:06 PM | #2 | |
Banned
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,998
Thanks: 1,035
Thanked 4,987 Times in 2,981 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
|
Quote:
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 |
|
03-02-2020, 09:35 PM | #3 | |
Senior Member
Join Date: Jan 2016
Drives: 2013 Panda ft86/FRS
Location: Oklahoma, USA
Posts: 147
Thanks: 22
Thanked 21 Times in 17 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
Quote:
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 |
|
03-02-2020, 09:36 PM | #4 |
Senior Member
Join Date: Jan 2016
Drives: 2013 Panda ft86/FRS
Location: Oklahoma, USA
Posts: 147
Thanks: 22
Thanked 21 Times in 17 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
another thing was the original was a00c
|
03-03-2020, 04:30 AM | #5 | |
Banned
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,998
Thanks: 1,035
Thanked 4,987 Times in 2,981 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
|
Quote:
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 Last edited by steve99; 03-03-2020 at 06:54 AM. |
|
03-03-2020, 10:19 AM | #6 | |
Senior Member
Join Date: Jan 2016
Drives: 2013 Panda ft86/FRS
Location: Oklahoma, USA
Posts: 147
Thanks: 22
Thanked 21 Times in 17 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
Quote:
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. 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 |
|
03-03-2020, 05:13 PM | #7 | |
Banned
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,998
Thanks: 1,035
Thanked 4,987 Times in 2,981 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
|
Quote:
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 |
|
03-03-2020, 05:33 PM | #8 | |
Senior Member
Join Date: Jan 2016
Drives: 2013 Panda ft86/FRS
Location: Oklahoma, USA
Posts: 147
Thanks: 22
Thanked 21 Times in 17 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
Quote:
thanks for all input thus far this has been a pita |
|
03-03-2020, 05:35 PM | #9 |
Senior Member
Join Date: Oct 2012
Drives: UK GT86
Location: UK
Posts: 3,040
Thanks: 185
Thanked 1,629 Times in 1,112 Posts
Mentioned: 155 Post(s)
Tagged: 1 Thread(s)
|
By having the correct definition file for the ROM.
__________________
.: Stealth 86 :.
Abbey Motorsport/K47 Tuned Sprintex 210 Supercharger Kodename 47 DJ: Soundcloud / Instagram / Facebook |
03-03-2020, 08:02 PM | #10 |
Banned
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,998
Thanks: 1,035
Thanked 4,987 Times in 2,981 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
|
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 |
03-03-2020, 09:32 PM | #11 | |
Senior Member
Join Date: Jan 2016
Drives: 2013 Panda ft86/FRS
Location: Oklahoma, USA
Posts: 147
Thanks: 22
Thanked 21 Times in 17 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
Quote:
I really don't like to mess with hex editing @Kodename47 if they update it to a bo1c or newer I have the def for the file, is this what you are implying? |
|
03-04-2020, 01:14 AM | #12 |
Senior Member
Join Date: Mar 2015
Drives: 2014 GT86
Location: Latvia, Riga
Posts: 4,333
Thanks: 696
Thanked 2,085 Times in 1,436 Posts
Mentioned: 53 Post(s)
Tagged: 1 Thread(s)
|
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. |
03-04-2020, 01:45 PM | #13 |
Senior Member
Join Date: Jan 2016
Drives: 2013 Panda ft86/FRS
Location: Oklahoma, USA
Posts: 147
Thanks: 22
Thanked 21 Times in 17 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
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 |
03-04-2020, 05:43 PM | #14 |
Senior Member
Join Date: Oct 2012
Drives: UK GT86
Location: UK
Posts: 3,040
Thanks: 185
Thanked 1,629 Times in 1,112 Posts
Mentioned: 155 Post(s)
Tagged: 1 Thread(s)
|
@1quickchic here you go:
Code:
Name: mod1a01c.bin Size: 140000h 8000: ZA1JA01C (suggested calibration code) 100000: ZA1JA01C 11D96D: ZA1JB01C (actual calibration code) This is a ZA1JB01C ROM, hacked to appear as ZA1JA01C for OFT or Ecutek. Please find a genuine ZA1JB01C ROM to flash if using tactrix. Name: OFT_Turbo_SC_A01C.bin Size: 140000h 8000: ZA1JA01C (suggested calibration code) 100000: ZA1JA01C 11D931: ZA1JA01C (actual calibration code) This is a genuine ZA1JA01C ROM. Name: StockpullZA1JA01C.bin Size: 140000h 8000: ZA1JA01C (suggested calibration code) 100000: ZA1JA01C 11D931: ZA1JA01C (actual calibration code) This is a genuine ZA1JA01C ROM.
__________________
.: Stealth 86 :.
Abbey Motorsport/K47 Tuned Sprintex 210 Supercharger Kodename 47 DJ: Soundcloud / Instagram / Facebook |
|
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
A couple of weird issues - fixed? | StraightOuttaCanadaEh | Suspension | Chassis | Brakes -- Sponsored by 949 Racing | 14 | 05-30-2019 08:25 AM |
Weird Bluetooth music issues | kravi | Electronics | Audio | NAV | Infotainment | 3 | 01-18-2016 11:34 AM |
New RPM Calibration TSB... | 5AD86D | Issues | Warranty | Recalls / TSB | 23 | 01-21-2015 10:50 PM |
Weird electrical issues. Need help! | Pneub | Issues | Warranty | Recalls / TSB | 15 | 09-13-2014 12:38 AM |
Weird Blinker Issues | sufu05 | Cosmetic Modification (Interior/Exterior/Lighting) | 0 | 08-06-2013 10:47 AM |