Timing still reading +1 in 909
Moderator: Matt
Timing still reading +1 in 909
I've noticed that the timing still reads +1 degree compared to what should be the real value. It does it on the live consult display but I havnet payed attention to the logger window.
i wasn't aware of this problem before.
do you get on the consult display what you get on the RAM trace window? latest version has decimal display now
$0041 ; IGN TIMING
if so then this is what the ECU reports to use. Are you using a timing light to get the value from the engine?
the logging uses the same data structure as what the guages window reports
you can use CONSULT_TIMING_OFFSET= in the address file if the raw ECU reported value is offset by 1
do you get on the consult display what you get on the RAM trace window? latest version has decimal display now
$0041 ; IGN TIMING
if so then this is what the ECU reports to use. Are you using a timing light to get the value from the engine?
the logging uses the same data structure as what the guages window reports
you can use CONSULT_TIMING_OFFSET= in the address file if the raw ECU reported value is offset by 1
-
- Posts: 112
- Joined: Wed May 03, 2006 5:51 pm
- Location: Id, USA
Did you try adjusting the timing offset setting in the address file?
Its a sort of final trim for the timing advance logging/monitoring, Matt added it for those ecus that do not use a common timing advance consult stream correction.
One example would be the ka24e which is 30 degrees different (compared to most with native consult capabilities).
Bump that value up or down (? not sure atm), 1, and then save your .adr.
Its a sort of final trim for the timing advance logging/monitoring, Matt added it for those ecus that do not use a common timing advance consult stream correction.
One example would be the ka24e which is 30 degrees different (compared to most with native consult capabilities).
Bump that value up or down (? not sure atm), 1, and then save your .adr.
just had a look through the code....
CONSULT_TIMING_OFFSET
TIMING_MAP_OFFSET
if not specified in the address file got assigned INVALID_ADDR (-1) from my address parser function. for these particular values, it should then be assigned 0 when this is detected. that explains the offset
i've fixed it now and will be updated in the next version
use CONSULT_TIMING_OFFSET=0 for workaround for now
CONSULT_TIMING_OFFSET
TIMING_MAP_OFFSET
if not specified in the address file got assigned INVALID_ADDR (-1) from my address parser function. for these particular values, it should then be assigned 0 when this is detected. that explains the offset
i've fixed it now and will be updated in the next version
use CONSULT_TIMING_OFFSET=0 for workaround for now