You work on Data Log Lab? If so then good work! And a to MJ who gave it a lot of exposure with the release of Evoscan and Mitsubishilogger.

 

let me start off by saying that I really appreciate the level of comitment you have on these boards and I appreciate your awesome products. I have tuned with several innovate products in the past but alsways used PLX widebands on my setups using the super expensive NTK L1H1 O2S. it was not until recently that I decided to start using the innovate LC-1 and bosch sensor. I could not be happier with the resolution and sample rate of this setup!! I will never go back!

ok, with that out of the way.... I guess I'm having a hard tme trimming the datalog for just the pull. I'm just now getting used to this particular datalogging software.

also, how are you guys able to calculate injector duty cycle in evoscan? I can't seem to find the feature to add calculations in, other than calculated load, which is already included in the sensor list. (i know how to do all this in logworks2).

CJ

 

jfitzpat, any plans to power/torque calculations into logworks2? I'm sure you can do it now if you know the formula and log the correct parameters. but entering in car weight, drag coeffeciency, gear ratios... ect is what would be the hard part in the formula.

thanks!

CJ

 

if I could actually figure out how to trim this datalog in evosan, I would send it to you for sure! I can highlight what I want, but can't figure out how to trim around it.

CJ

 

There may be an easier way to do this but this is what I've been doing.

Open a log file in Excel and insert a column. Highlight a column by right clicking the column heading LETTER, in this case Y and then left click insert. Now you have a blank column, on line 1 enter the Text 'IDC', and on line 2 press the "=" sign up below your File menu and enter this formula '=(H2*X2)/1200' (remove the quotes). Now I grab the bottom right corner of the new Y2 field (you should get a bold + sign when doing this) and drag straight down to fill in that formula through my entire data log.

 

Thankyou. Oh ... and I wont tell anyone.

 

Yep, I've just been doing the Injector Duty Cycle: IDC (%) = IPW*RPM/1200 calculation like you're showing.

You can edit the requests that are being sent to the ECU in EvoScan but I don't know how you'd do the internal calculations without haveing Evo4Mad add this in.

 

Just open the log file in excel an cut out all of the log entries before 100% TPS and everything after 100% TPS. That will get you your best log.

 

Evo4Mad -

Are the emails for the update still going out?

Should I be concerned if I haven't gotten one yet?

 

I haven't gotten one myself. Let me know what I need to do.

 

Has anyone even talked to Evo4Mad? I havent got an email or the 1.3M cable I paypaled him for at the beginning of last week. I havent been able to contact him by PM or email.

 

I'm not sure how busy he is.. But he's not out to rip anyone off, he's probably resolving some issues with the software and has a few things going on. I do recall he had written that when the new fixed version is ready, he will send out a new mass mailing.

From a hardware standpoint, not sure what is going on with the cables, but like I said earlier, if you ordered it, you will get it.

 

I've posted power/torque based on RPM, power/torque based on RPM with SAE correction, power/torque based on RPM and accell with SAE, and power/torque based on speed/rpm with SAE for LW2 in various threads here and on our forums. You drop them into the trace calculator and the formula puts up a dialog for car specific values.

Laakness, no, I have not worked on DLL. I just knew from my work on/with the stuff above that if you try to measure slope and have a lot of pre/post stuff in the log, HP will typically balloon. Though, now that I think about it, the problem could also be in the RPM smoothing algorythm.

-jjf

 

Off topic, sorry. That particular NTK sensor is very durable, primarily because there is so much material mass at each end of the test chamber. But, on the flip side, it is quite slow, because of the volume of the chamber. It is also very prone to gas pressure errors, again because of chamber volume.

We generally don't use the NTK sensors, because our speciality is measurement speed and high WHP pro racing installs, but if I were to choose one, that isn't a bad way to go if you are worried about heat and contamination.

-jjf

 

He's likely waiting until he's finished finalizing the v0.98 before he sends it out to new customers and post's it on the link for current customers. The 0.98 on the link now is just to keep us off his back until he finishes.

Wait till the final copy before worrying, after that PM him