Today I went for a drive and made a long log with Logworks/Ecuflash. The xml formulas that I created WORK. I logged the following:

Timing
Airflow (new formula added to xml)
Knock Sum (new formula added to xml)
TPS
Injector pulse width

And My LMA-2/LM-1 logged
Boost
AFR
RPM

After I did the log, I then applied the LoadAF formula to get the Load (unit used is measure).

I attached the logworks log for those who have the program and would like to see it. I also attached the xml file that has formulas

Here are two screen shoots with markers showing the parameters measured.




This one had sustained knock in it the car was still cold. It is good though since I know that the KS formula works

 

Sweet! I can't wait to use this over the weekend, too. Finally I can have my boost and AFR logged in the same log with everything else.

How was the sample rate compared to EvoScan or Mitsulogger?


Eric

 

It should be the same.. But I haven't tried it yet, my package just showed today.

 

Be sure to download the latest LW from our site. It is compatible with a lot more flavors of the cables and a lot more ECUs (I've been getting trace files via email for a week . Also, just drop me a note if you want to experiment with being a virtual device for LogWorks with your own stuff. The LW2VDev control is an indentical subset of the 'official' control coming out with LogWorks3. The only difference is that you can't register bit channels (since LW 2 doesn't support them).

Support isn't 'official' for Virtual Devices until LW3, but I'd be happy to answer your questions.

As far as sample rate, I can only really log 2-3 channels via ISO 9141 on my wife's Lexus before it gets to 'steppy' for me, but nj1266's log he posted on our forum looked pretty darn good.

Enjoy and let me know if there is anything I can answer.

-jjf

 

The only downside I see to this logging is that we cannot use Dataloglab to make power graphs. I wonder if MJ can create something to make the *.dif files that Logworks saves in to work with DLL.

 

If there's an export function its probably easier.. In reality, once I have time to work with it I'll see what I can do to make things more seamless.

If DIF files are documented, we could actually request that the author of DLL add support for it.

 

FWIW you can do fairly complex computations, complete with a prompt for user input, in the LogWorks calculator. For example, here is a calculation that user "vigge" submitted for volumetric efficiency:

****************
# Estimated volymetric efficiency % based on RPM, MAP, MAF, MAT, Engine
# displacement. Displacement input in cubic inches.

?i RPM channel = RPM{RPM}[RPM]
?i MAP channel = MAP{kPA}[MAP]
?i MAF channel = MAF{g/s}[Airmass]
?i MAT channel = MAT{C}[Intake temp]
?Engine displacenment = DIS[139]

# MAT in Farenheit
MATF = (5/9) * (MAT- 32)

# Boost in PSI

MAPP = ((MAP - 100) / 100)/0.0689475729

# airmass flow in lb/min

MAFL = (MAF*60)/453.6

# VE

MC(VE;%) = (100*MAFL)/(RPM/2*DIS/(639.6*(460+MATF))*(MAPP+14.7))

********************************

Similarly, here would be a simple torque/power (us measurements) from RPM (with a known gear ratio):

#Creates Torque and hp from RPM only
#for US measurements (hp and lbft)
#
#- requires user input of vehicle weight (lb)
#- gear ratio
#- Final drive ratio
#- tire diameter (inches)

?Vehicle weight in lb = m
?Tire diameter in inch = td
?Gear ratio of run = gear_ratio
?Final drive ratio = finaldrive
?i Name of RPM channel = rpm

a = slope(RPM) * pi * td * 4.3153245 * 10^-5/(gear_ratio * finaldrive)
#acceleration in g

F = m * a
R = td/24 #tire radius in ft

trq = F * R / (gear_ratio * finaldrive)
MC(torque;lbft) = trq
MC(power;hp) = trq * rpm/5252

***************************************

Of course, MJ is welcome to import DIF files. I'd also be glad to send what is nec. to get his charting working as a LogWorks plug-in as well (dynamic charting, like viritual channels, will all be open source and documented for the upcoming version, though I'm happy to give what previews and help that I can to developers now).

-jjf

 

I'll stay in touch, at the moment bit channels aren't really needed because of how poorly documented the MUT requests currently are..

However the virtual device and activeX control will be how I implement support for it.. If its a bi-directional communication so I can retrieve data it would be cool too, kinda makes the answer in the previous post more realistic.

ISO9141 is SLOW, the fact that each request and response are several bytes, plus the 10k baud speed, makes it unrealistic to do any practical logging. That is why MUT logging is so popular, as the rate is at 15kbaud, and each request is 1 byte, and each response is (currently) 2 bytes, no error checking or checksums, only an echo of the request, and the data response, so its significantly faster.

 

Logworks exports logs in DIF or MDF. I have not figured out what to use to read MDF files. The MDF is better since it exports the log in as many session as you have in it. I wonder if Excel can read an MDF file???

 

Probably not..

That power calculation is pretty cool, since MUT can log rpm and speed, you can actually calculate gear ratio easily and incorporate it so you won't have to always calculate your pulls in a particular gear.

 

What would the formula for the Math Trace window be given the following:

Weight=3438 lbs
Tire diameter=25.326 inch
3rd gear ratio=1.407
Final drive ratio=4.529

 

You should be able to determine the gear ratio at any given time by using the vehicle speed, therefore not needing to know gear your in.

 

Right. I need to log speed AND RPM to use the hp/tq formul in logworks. I did not log speed in this log. I will do a log today with all the needed parameters and report back on the hp/tq calculations.

This is shaping up to be a great logging tool. Only ONE program to log, view, trace, and calculate power

 

That's what the formula ask you. The '?' are params in a pop up dialog, the '?i' gives you a combo box of channels.

Note: To get a good slope calculation you really are going to want to right click on the RPM channel and smooth it first. You'll also get the most accurate power calculations if you use the selection tool and mark the wide open throttle portion of a gear run.

MJ is correct, you can calculate drive ratio from speed. The formula was just a simple example, RPM only, but could easily be extended.

Glad to hear you are getting some use out of it.

-jjf

 

I think I already know the answer to this question but I have to ask anyway. can we record all this data using the LM-1 and then DL it to our laptops or does the laptop have to be present in the car just like when you log with EVOScan?