Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB
Page 72 of 79 « First 226268697071 72 73747576 Last »
Show 40 post(s) from this thread on one page

Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB (https://www.ft86club.com/forums/index.php)
-   Software Tuning (https://www.ft86club.com/forums/forumdisplay.php?f=88)
-   -   Tactrix EcuFlash Info for BRZ 86 FRS Rom flash update and logging (https://www.ft86club.com/forums/showthread.php?t=62332)

Compelica 08-26-2021 01:44 PM
@steve99 @Kodename47 do you guys have the RR definition for OFT A01G that has the A/F #3 Learning Limits?

I see the table described in the def, but one of the entries is missing. @Kodename47 I suppose this link below goes to your latest defs but the A/F #3 Learning Limits is not there either.

https://www.ft86club.com/forums/show...&postcount=411

https://i.imgur.com/lbRq3fI.jpg

steve99 08-27-2021 02:14 AM
Quote:
Originally Posted by Compelica (Post 3460206)
@steve99 @Kodename47 do you guys have the RR definition for OFT A01G that has the A/F #3 Learning Limits?

I see the table described in the def, but one of the entries is missing. @Kodename47 I suppose this link below goes to your latest defs but the A/F #3 Learning Limits is not there either.

https://www.ft86club.com/forums/show...&postcount=411

https://i.imgur.com/lbRq3fI.jpg

if you have thise two #af3 parameters just zero those i think the third one in some defs is redundant or a duplicate ecutek only has 2

Compelica 08-27-2021 02:29 AM
Quote:
Originally Posted by steve99 (Post 3460421)
if you have thise two #af3 parameters just zero those i think the third one in some defs is redundant or a duplicate ecutek only has 2
Thanks. For some reason the A/F #3 Learning values are still coming up in OL so was wondering where was that coming from.

https://i.imgur.com/sx8WUMz.png

steve99 08-28-2021 02:55 AM
Quote:
Originally Posted by Compelica (Post 3460422)
Thanks. For some reason the A/F #3 Learning values are still coming up in OL so was wondering where was that coming from.

https://i.imgur.com/sx8WUMz.png

not sure is that ovt v4 based tune ??

Compelica 08-28-2021 03:30 AM
Quote:
Originally Posted by steve99 (Post 3460748)
not sure is that ovt v4 based tune ??
Tune is based on Wayne's, so yes OFT v4. Another forumer was also seeing the same issue.

https://www.ft86club.com/forums/show...41&postcount=5

churchx 08-28-2021 08:38 AM
Compelica: I might be wrong .. but IIRC wayneroms were based on heavily reworked but OFTv3.

Compelica 08-28-2021 11:12 AM
Quote:
Originally Posted by churchx (Post 3460771)
Compelica: I might be wrong .. but IIRC wayneroms were based on heavily reworked but OFTv3.
Just checked - he did mention in his changelog on his site that his recent roms are based off V4.

churchx 08-29-2021 10:27 AM
Compelica: then i might be reading wrong if it is as you say.
when searching on his site for "V4" in one changelog bit:
"Apr 2018 Re-generated all USDM MY12-MY16 roms from A01G/I instead of B01C/D, for compatibility with Openflash V4."
when at same Apr 2018 for Openflash Release History there is bit:
"MY12-MY16 tunes are identical to OTS 3.0."
On which base stock tune something is based on doesn't mean it's similar tuned as OFT v4.

Compelica 08-29-2021 10:53 AM
Quote:
Originally Posted by churchx (Post 3461008)
Compelica: then i might be reading wrong if it is as you say.
when searching on his site for "V4" in one changelog bit:
"Apr 2018 Re-generated all USDM MY12-MY16 roms from A01G/I instead of B01C/D, for compatibility with Openflash V4."
when at same Apr 2018 for Openflash Release History there is bit:
"MY12-MY16 tunes are identical to OTS 3.0."
On which base stock tune something is based on doesn't mean it's similar tuned as OFT v4.
I see your point. Maybe @Wayno himself can clarify (don't see him around the forums often nowadays).

TeeJay.net 09-16-2021 03:55 PM
Does anybody know A01G hex addresses for codes that come before P0011?
The list in Romraider -> Diagnostic Trouble Codes seems to start with P0011. Codes like P000A, P000B, P000B, P000B and P0010 are nowhere to be found.

On GitHub I've found a definition file that says A01G but it's totally different from my A01G definition file I got from Wayno's website and this definition file just throws bunch of errors when I try to open my ROM.

I've also tried to just use these addresses and add them to my definition file like so
HTML Code:
...
<table name="(P000A) CAMSHAFT POSITION A  TIMING SLOW RESPONSE BANK 1" storageaddress="11E138" />
<table name="(P000B) CAMSHAFT POSITION B  TIMING SLOW RESPONSE BANK 1" storageaddress="11E144" />
...
But even with this code added they still don't appear in RomRaider.

steve99 09-19-2021 09:04 PM
Quote:
Originally Posted by TeeJay.net (Post 3466374)
Does anybody know A01G hex addresses for codes that come before P0011?
The list in Romraider -> Diagnostic Trouble Codes seems to start with P0011. Codes like P000A, P000B, P000B, P000B and P0010 are nowhere to be found.

On GitHub I've found a definition file that says A01G but it's totally different from my A01G definition file I got from Wayno's website and this definition file just throws bunch of errors when I try to open my ROM.

I've also tried to just use these addresses and add them to my definition file like so
HTML Code:
...<table name="(P000A) CAMSHAFT POSITION A  TIMING SLOW RESPONSE BANK 1" storageaddress="11E138" /><table name="(P000B) CAMSHAFT POSITION B  TIMING SLOW RESPONSE BANK 1" storageaddress="11E144" /> ...
But even with this code added they still don't appear in RomRaider.
</div>

ok none of the romraider definitions have those codes defined


ecutek has them and its pisdible to disable those codes but they fo indicate you have a real problem and disabking those codes in tune wont fix the hardware issue

makinen 09-19-2021 10:13 PM
1 Attachment(s)
Quote:
Originally Posted by TeeJay.net (Post 3466374)
Does anybody know A01G hex addresses for codes that come before P0011?
The list in Romraider -> Diagnostic Trouble Codes seems to start with P0011. Codes like P000A, P000B, P000B, P000B and P0010 are nowhere to be found.

On GitHub I've found a definition file that says A01G but it's totally different from my A01G definition file I got from Wayno's website and this definition file just throws bunch of errors when I try to open my ROM.

I've also tried to just use these addresses and add them to my definition file like so
HTML Code:
...
<table name="(P000A) CAMSHAFT POSITION A  TIMING SLOW RESPONSE BANK 1" storageaddress="11E138" />
<table name="(P000B) CAMSHAFT POSITION B  TIMING SLOW RESPONSE BANK 1" storageaddress="11E144" />
...
But even with this code added they still don't appear in RomRaider.
Below lines do the trick for A01G.

HTML Code:
    <table name="(P000A) CAMSHAFT POSITION A  TIMING SLOW RESPONSE BANK 1" storageaddress="11C7C4" />
    <table name="(P000B) CAMSHAFT POSITION B  TIMING SLOW RESPONSE BANK 1" storageaddress="11C7D0" />
    <table name="(P000C) CAMSHAFT POSITION A  TIMING SLOW RESPONSE BANK 2" storageaddress="11C7DC" />
    <table name="(P000D) CAMSHAFT POSITION B  TIMING SLOW RESPONSE BANK 2" storageaddress="11C7E8" />
Attachment 205419

And the definition file in the link you've mentioned has weird DTC addresses. I don't know why td-d left those values incorrect, but suggest to use the definition file included in the OFT distributions. Keep in mind that since OFT v4, all definitions for manuals are based on A01G.

TeeJay.net 09-20-2021 09:16 AM
Quote:
Originally Posted by steve99 (Post 3467133)
</div>

ok none of the romraider definitions have those codes defined


ecutek has them and its pisdible to disable those codes but they fo indicate you have a real problem and disabking those codes in tune wont fix the hardware issue
Absolutely, the car needs a new cam sprocket and possibly ECU changed as the service bulletin says and it will get changed soon. I was just exploring the options and found out those codes were not in the definition files unlike all other codes.

Quote:
Originally Posted by makinen (Post 3467143)
Below lines do the trick for A01G.

HTML Code:
    <table name="(P000A) CAMSHAFT POSITION A  TIMING SLOW RESPONSE BANK 1" storageaddress="11C7C4" />
    <table name="(P000B) CAMSHAFT POSITION B  TIMING SLOW RESPONSE BANK 1" storageaddress="11C7D0" />
    <table name="(P000C) CAMSHAFT POSITION A  TIMING SLOW RESPONSE BANK 2" storageaddress="11C7DC" />
    <table name="(P000D) CAMSHAFT POSITION B  TIMING SLOW RESPONSE BANK 2" storageaddress="11C7E8" />
Attachment 205419

And the definition file in the link you've mentioned has weird DTC addresses. I don't know why td-d left those values incorrect, but suggest to use the definition file included in the OFT distributions. Keep in mind that since OFT v4, all definitions for manuals are based on A01G.
Now the P000x codes show up in Romraider, thanks a lot!

oBradyG 09-27-2021 11:02 AM
opening my stock bin in rom raider
 
Im new and trying to learn so 2 questions.

1a. So i got my stock .bin and it wont open in rom raider the CAL id is ZA1JV01D00G i get a bunch of errors trying to open it? do i need compatible DEFs for it to open?

1b. Im trying to look at the stock values cause i want my stock cold start on my stg 2 tune.. is that possible to do by copying the (Idle Speed Targets A-F, Ignition Timing Post Start, and MAF correction before start Neutral and in gear)? or will it mess things up?

Thanks!


All times are GMT -4. The time now is 07:47 AM.
Page 72 of 79 « First 226268697071 72 73747576 Last »
Show 40 post(s) from this thread on one page

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
User Alert System provided by Advanced User Tagging v3.3.0 (Lite) - vBulletin Mods & Addons Copyright © 2026 DragonByte Technologies Ltd.


Garage vBulletin Plugins by Drive Thru Online, Inc.