OFT log - adv multiplier = 0

[madcatjf]

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]

Originally Posted by madcatjf

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]

Originally Posted by madcatjf

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]

ZA1JA03N

Originally Posted by Boomerang

logging issue, what is your CAL ID?

[madcatjf]

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?

Originally Posted by Spuds

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]

Originally Posted by madcatjf

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]

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.

Originally Posted by Spuds

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]

Originally Posted by madcatjf

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]

Originally Posted by madcatjf

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.

Originally Posted by steve99

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 )

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

[madcatjf]

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]

Originally Posted by madcatjf

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]

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.

Originally Posted by steve99

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]

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]

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.