Timing still reading +1 in 909

Discuss software bugs and related problems here.

Moderator: Matt

Post Reply
Stinky
Site Admin
 

Posts: 266
Joined: Thu Jan 26, 2006 1:43 am
Location: Tampa, Florida USA
Contact:

Timing still reading +1 in 909

Post by Stinky »

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.
Matt
Site Admin
 

Posts: 8961
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Post by Matt »

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
Stinky
Site Admin
 

Posts: 266
Joined: Thu Jan 26, 2006 1:43 am
Location: Tampa, Florida USA
Contact:

Post by Stinky »

Matt,
Just checked the ram address. The ram address is showing the correct value but the consult and logging windows are reporting the timing +1.
GZ@hybridka
 

Posts: 112
Joined: Wed May 03, 2006 5:51 pm
Location: Id, USA

Post by GZ@hybridka »

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.
Stinky
Site Admin
 

Posts: 266
Joined: Thu Jan 26, 2006 1:43 am
Location: Tampa, Florida USA
Contact:

Post by Stinky »

I havent tried it yet. While it will probably work I think it's also important to find out why the offset has been introduced. The offset has only appeared in recent releases so it would be interesting to know why and fix it.
Matt
Site Admin
 

Posts: 8961
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Post by Matt »

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
Matt
Site Admin
 

Posts: 8961
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Post by Matt »

version is up. see how it goes now
Post Reply