updated log variables

Report bugs/problems with ecuEdit

updated log variables

Postby BarryC » Wed Dec 23, 2009 7:31 pm

bought this software a good while ago could never get it to log reliably
downloaded latest version and OMG its a very powerfull tool

am having some difficulty getting it to log my LM2
it will connect to it but the logger reads 22.3 when the LM2 reads 20.9 ???

anyway here are some updates for the logging parameter lists as some are a wee bit innacurate

fuel trims should be logged as %
([value]*0.1961)-25

also it is very handy to be able to log knocksum

here are the variables

Knocksum #26

afrmap (14.7*128)/[value]
BarryC
 
Posts: 7
Joined: Mon Feb 12, 2007 12:58 pm

Re: updated log variables

Postby epifan » Thu Dec 24, 2009 11:38 am

BarryC wrote:am having some difficulty getting it to log my LM2
it will connect to it but the logger reads 22.3 when the LM2 reads 20.9 ???

Hmmm, 22.3 seems to be Max AFR value of LM2. How did you connect ecuEdit to LM2? Using Innovate SDK connection? Did you calibrate LM2 in Innovate utils?

BarryC wrote:anyway here are some updates for the logging parameter lists as some are a wee bit innacurate

fuel trims should be logged as %
([value]*0.1961)-25

also it is very handy to be able to log knocksum

here are the variables

Knocksum #26

afrmap (14.7*128)/[value]

Here is link for fixed defs: http://www.epifansoft.com/download/logdefs_evo.xml. Copy it to XMLDefs folder.
"Knocksum" is named as Knock Retard in ecuEdit defs.

Regards
epifan
Site Admin
 
Posts: 825
Joined: Thu Jul 13, 2006 3:17 pm

Re: updated log variables

Postby BarryC » Thu Dec 24, 2009 4:02 pm

epifan wrote:
BarryC wrote:am having some difficulty getting it to log my LM2
it will connect to it but the logger reads 22.3 when the LM2 reads 20.9 ???

Hmmm, 22.3 seems to be Max AFR value of LM2. How did you connect ecuEdit to LM2? Using Innovate SDK connection? Did you calibrate LM2 in Innovate utils?

BarryC wrote:anyway here are some updates for the logging parameter lists as some are a wee bit innacurate

fuel trims should be logged as %
([value]*0.1961)-25

also it is very handy to be able to log knocksum

here are the variables

Knocksum #26

afrmap (14.7*128)/[value]

Here is link for fixed defs: http://www.epifansoft.com/download/logdefs_evo.xml. Copy it to XMLDefs folder.
"Knocksum" is named as Knock Retard in ecuEdit defs.

Regards



yep connected via SDK connected via LM2 unit
thanks for the updated defs
BarryC
 
Posts: 7
Joined: Mon Feb 12, 2007 12:58 pm


Return to Troubleshooting

Who is online

Users browsing this forum: No registered users and 1 guest

cron