Version 4.3.4 ignition timing issues
Posted: Thu Oct 10, 2024 5:23 pm
HONDA CRZ, 2011 CVT
Version 4.3.4
No ecu relevant mods
Stock ECU
Serial: FP-CRZ-US-70125
Calibration and two datalogs will be attached.
Issue: Incorrect ignition timing. ECU not following ignition timing in the tables. If the table is set to 4, for example, the ECU will be using 30+ timing advance. If the ECU is supposed to be using 25 ignition timing, it’s 0 for some reason. I noticed the issue briefly after modifying the WOT low lambda adjustment while using live tuning. I noticed the issue yesterday for the first time but did not save the datalog. Uploading a slightly different calibration fixes the issue immediately. I will report if the issue eventually occurs on this functional calibration as well.
The ‘before’ datalog will show the car starting off normal and at the end is when I noticed the issue. The second catalog is me starting a new the datalog and driving with the issue present, keeping my car in high RPM to prevent knock. The car was not turned off in between, I just started a new datalog to make the beginning of the issue more obvious.
The issue may have been occurring for the last two weeks at a lower severity, as I’ve noticed knock randomly appearing in weird spots.
Version 4.3.4
No ecu relevant mods
Stock ECU
Serial: FP-CRZ-US-70125
Calibration and two datalogs will be attached.
Issue: Incorrect ignition timing. ECU not following ignition timing in the tables. If the table is set to 4, for example, the ECU will be using 30+ timing advance. If the ECU is supposed to be using 25 ignition timing, it’s 0 for some reason. I noticed the issue briefly after modifying the WOT low lambda adjustment while using live tuning. I noticed the issue yesterday for the first time but did not save the datalog. Uploading a slightly different calibration fixes the issue immediately. I will report if the issue eventually occurs on this functional calibration as well.
The ‘before’ datalog will show the car starting off normal and at the end is when I noticed the issue. The second catalog is me starting a new the datalog and driving with the issue present, keeping my car in high RPM to prevent knock. The car was not turned off in between, I just started a new datalog to make the beginning of the issue more obvious.
The issue may have been occurring for the last two weeks at a lower severity, as I’ve noticed knock randomly appearing in weird spots.