Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB

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)
-   -   OFT log - adv multiplier = 0 (https://www.ft86club.com/forums/showthread.php?t=126500)

madcatjf 03-29-2018 05:27 AM

OFT log - adv multiplier = 0
 
Hello,

I recently got a OFT and flashed my ECU with stage 2 EL tune file. I did 2 third gear pull yesterday and logged them. When I see my log files, the adv multiplier is always 0. I have 2 questions.
1) adv multiplier = IAM ?
2) adv multiplier = 0, is that normal?

Spuds 03-29-2018 05:49 AM

Quote:

Originally Posted by madcatjf (Post 3065192)
Hello,

I recently got a OFT and flashed my ECU with stage 2 EL tune file. I did 2 third gear pull yesterday and logged them. When I see my log files, the adv multiplier is always 0. I have 2 questions.
1) adv multiplier = IAM ?
2) adv multiplier = 0, is that normal?

1) Yes, if you are referring to IAM as Ignition Advance Multiplier as some people do. IAM can also be the Initial Advance Multiplier which is the maximum value the Advance Multiplier will be when starting the car. The latter is a value in the tune file.

2) No. Likely a mistake in the logging. If you flash your ecu again does it start at 1 or .7? If so, your ECU is detecting a lot of knock and reducing timing (logging good, engine bad). If after flashing the adv multiplier starts at 0, then you definitely have a logging issue (logging bad, engine ???).

Hope that helps.

Boomerang 03-29-2018 06:34 AM

Quote:

Originally Posted by madcatjf (Post 3065192)
Hello,

I recently got a OFT and flashed my ECU with stage 2 EL tune file. I did 2 third gear pull yesterday and logged them. When I see my log files, the adv multiplier is always 0. I have 2 questions.
1) adv multiplier = IAM ?
2) adv multiplier = 0, is that normal?


logging issue, what is your CAL ID?

madcatjf 03-29-2018 10:29 AM

ZA1JA03N


Quote:

Originally Posted by Boomerang (Post 3065199)
logging issue, what is your CAL ID?


madcatjf 03-29-2018 10:32 AM

Thanks, so you suggest me to flash my ecu again, then to log afterwards to see if this value starts with 0.7 or 1?


Quote:

Originally Posted by Spuds (Post 3065195)
1) Yes, if you are referring to IAM as Ignition Advance Multiplier as some people do. IAM can also be the Initial Advance Multiplier which is the maximum value the Advance Multiplier will be when starting the car. The latter is a value in the tune file.

2) No. Likely a mistake in the logging. If you flash your ecu again does it start at 1 or .7? If so, your ECU is detecting a lot of knock and reducing timing (logging good, engine bad). If after flashing the adv multiplier starts at 0, then you definitely have a logging issue (logging bad, engine ???).

Hope that helps.


Spuds 03-29-2018 11:37 AM

Quote:

Originally Posted by madcatjf (Post 3065231)
Thanks, so you suggest me to flash my ecu again, then to log afterwards to see if this value starts with 0.7 or 1?

Yes, that will determine if you actually have a logging problem or some other problem. I think it will start at 0, which means you have a logging problem.

madcatjf 04-01-2018 07:56 AM

Spuds, I flashed again the tune and run diagnostic again, adv multiplier is still 0. But I run diagnostic on my friend's car (2013 BRZ), it shows adv multiplier 1. :(


Quote:

Originally Posted by Spuds (Post 3065243)
Yes, that will determine if you actually have a logging problem or some other problem. I think it will start at 0, which means you have a logging problem.


steve99 04-01-2018 09:31 AM

Quote:

Originally Posted by madcatjf (Post 3066456)
Spuds, I flashed again the tune and run diagnostic again, adv multiplier is still 0. But I run diagnostic on my friend's car (2013 BRZ), it shows adv multiplier 1. :(


Your friends car may ne different calibration id .


If iam is 0 and car is driving ok its definitely logging problem.

Spuds 04-01-2018 10:51 AM

Quote:

Originally Posted by madcatjf (Post 3066456)
Spuds, I flashed again the tune and run diagnostic again, adv multiplier is still 0. But I run diagnostic on my friend's car (2013 BRZ), it shows adv multiplier 1. :(

Quote:

Originally Posted by steve99 (Post 3066469)
Your friends car may ne different calibration id .


If iam is 0 and car is driving ok its definitely logging problem.


As steve99 said, that proves that the CALID for your car is not logging advance multiplier correctly. CALID is usually different between model years, so that is why your friend's car is logging correctly. (I didn't think that was clear when steve99 said it :thumbsup:)

Fixing it requires a software update to the tablet. You might want to try and contact Openflash with what you found.

madcatjf 04-01-2018 10:59 AM

Thanks, @Spuds, @steve99. My car is 2015 and my friend's car is 2013, I noticed that the cal IDs are different, but I am sure I used the right tune file with my cal ID. I think I will send an email to Shiv about my issue to see if they are aware of it.

steve99 04-01-2018 11:54 AM

Quote:

Originally Posted by madcatjf (Post 3066490)
Thanks, @Spuds, @steve99. My car is 2015 and my friend's car is 2013, I noticed that the cal IDs are different, but I am sure I used the right tune file with my cal ID. I think I will send an email to Shiv about my issue to see if they are aware of it.


each calid will require different ecu logging ram addresses. You will have used correct file, oft wont load incompatable tunes (unless you do a bit of hacking).


Shive will likely send you one of the new V4 tunes for your calid this will correct the logging issues

madcatjf 04-01-2018 12:14 PM

Steve99, when I flashed my car, I used the file "Stg2 EL A03N" which Shiv sent me. I am from China and the CAL ID of my car is ZA1JA03N. I am afraid that there is no V4 tune file for my region.


Quote:

Originally Posted by steve99 (Post 3066504)
each calid will require different ecu logging ram addresses. You will have used correct file, oft wont load incompatable tunes (unless you do a bit of hacking).


Shive will likely send you one of the new V4 tunes for your calid this will correct the logging issues


fminicooper 03-15-2020 11:58 PM

Thanks to this post I learnt about logging issues. I have exactly same problem.

I updated the OpenFlash Manager.
Uploaded latest OTS Maps.
Re flashed with new map.

Problem solved. Logging correctly.

NicFromTheNorth 07-15-2020 03:42 PM

Hi, new member here!

I am experiencing a similar issue with ZA1JF00C. Some parameters do not log properly. For example, VVTi is all over the place and IAM is always 0. Also, when I load my base tune file in RomRaider using the .xml definition file that OFT supplied to me all I get is errors.

I found a .xml definition file on the RomRaider forum that works perfectly with my base tune file, and I can see all the maps correctly.

I am reluctant to troubleshoot by loading a tune I received from OFT into my car as the map addresses are clearly different than in my original tune. So aside from the fix described above, does anyone have a suggestion? My OpenFlash Manager completed all the automatic updates.

steve99 07-17-2020 02:39 AM

Quote:

Originally Posted by NicFromTheNorth (Post 3349471)
Hi, new member here!

I am experiencing a similar issue with ZA1JF00C. Some parameters do not log properly. For example, VVTi is all over the place and IAM is always 0. Also, when I load my base tune file in RomRaider using the .xml definition file that OFT supplied to me all I get is errors.

I found a .xml definition file on the RomRaider forum that works perfectly with my base tune file, and I can see all the maps correctly.

I am reluctant to troubleshoot by loading a tune I received from OFT into my car as the map addresses are clearly different than in my original tune. So aside from the fix described above, does anyone have a suggestion? My OpenFlash Manager completed all the automatic updates.




OFT wont log correctly till you flash an OFT version 4 tune from there website

NicFromTheNorth 07-19-2020 07:43 PM

Thank you @steve99.

What confuses me is how the ECU will know where to fetch the maps in the OFT V4 tune, given that the map memory addresses are different than in my original tune file. I assume the flashing process does not only load the tune file, but also modifies something else in the ECU such that it retrieves the maps from the proper locations in the V4 tune file. Is this assumption correct?

steve99 07-20-2020 03:02 AM

Quote:

Originally Posted by NicFromTheNorth (Post 3350550)
Thank you @steve99.

What confuses me is how the ECU will know where to fetch the maps in the OFT V4 tune, given that the map memory addresses are different than in my original tune file. I assume the flashing process does not only load the tune file, but also modifies something else in the ECU such that it retrieves the maps from the proper locations in the V4 tune file. Is this assumption correct?


a lot of oft tunes are based on a different calid to your stock calid. this is why tuned roms log correctly and some stock ones dont

Kodename47 07-21-2020 09:27 AM

Quote:

Originally Posted by NicFromTheNorth (Post 3350550)
What confuses me is how the ECU will know where to fetch the maps in the OFT V4 tune, given that the map memory addresses are different than in my original tune file. I assume the flashing process does not only load the tune file, but also modifies something else in the ECU such that it retrieves the maps from the proper locations in the V4 tune file. Is this assumption correct?

The ROM file is the new software for the ECU and only this is flashed - These replace one area on the ECU but the IDs that it use are different depending on the Calibration ID. How it does this doesn't really matter.


All times are GMT -4. The time now is 12:42 PM.

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.