I know it's not ECUFlash specific ... but I like you guys.

So, I spend a while Sunday learning about the DLL definition files and taking the time to set up my own so I could understand it better.

I only set up the basic things I thought I might need to graph along with my power runs ... AFR, Boost, etc.

For some reason, the Load data isn't graphing properly at all. It shows up fine in the left column where you can view values, but it graphs like in the 10k range. The load might be 260 but it graphs as 11500 or something. It's not a direct x10 multiplier or anything.

This is the load code ... (I log corrected and uncorrected load, noted as T and F)

I've tried using different IDs and different names and descriptions to no avail. This is kind of important to me as I'm currently working on some product development and need to show changes in the load values between the products.

I'm attaching the full file as well ... thanks for any help.

EDIT :: New file in post 13 ...

EDIT AGAIN :: Even more fleshed out in post 22 ... I've made some changes since and I'll try to post them soon.

 

Anyone ... Beuler? Beuler?

 

Just found this post from Razor ...

[Column]
Name=2Byte Load
Description=LoadMUT2Byte
ColumnTitle=LoadMUT2Byte
DataItemID=25
Type=1
ColumnDecimalPlaces=2
Display DecimalPlaces=2

This is pretty much the same thing I have aside from the DataItemID and the ColumnDecimalPlaces. Will these values cause the issues I'm having? Again, the values show up fine in the left column but graph incorrectly. I get no errors and the load curves are correct ... just not the actual values graphed.

 

Customise / Options / Data Item Definitions /

Select the 2byte load and under "Display Properities" on the right there is a "Scaling Factor" input box.

I have mine set a 0.1 for 2byte load, so 278 load is 27.8 when graphed.

 

Also, if you need a data item to graph that has negative values, such as WGDC correction or load error you can assign it an offset like:

Name=LoadError
Description=LoadError
ColumnTitle=LoadError
DataItemID=54
Type=1
ColumnDecimalPlaces=4
DisplayDecimalPlaces=2
Offset=50

 

I get that much, but my load doesn't graph anything close to the real vlaue ... it's WAY off. and it's not off in any basic fashion ... it's like it's being multiplied by 19.8 or something off the wall like that.

I'll post screens this evening and also try your suggestions.

 

Even when you set the scaling factor I mentioned in post #4?

 

I haven't tried ... I'm not at my tuning box right now. At the 9-5 ... =( I'll try it.

 

I'm sure it's the scaling factor.

 

You hit the nail on the head Bryan ... scaling was set to seemingly random values. One was 74 and the other was 55. It makes no sense. But, they seem to be fixed now. Thanks!

 

Look in the help file for the data type translations or something like that. I ran into this over the weekend rebuilding my laptop after the HD died.

Data lab log uses their own propietary data ID (dataItemID). That's the bad news.

The good news is that there appears to be quite a few dataitems to choose from and several generic id's that can be used for raw input.

It's also possible to enter a formulas like we use for calculated load using raw data from the log file.

I don't have the laptop in front of me or I could provide more detailed info.

 

Nice, I will await my beer in the mail.

 

I made some corrections to override the default scaling values that were throwing my graphs off ...

See attached.

 

Dang touring good stuff man, nice def for DLL

 

I'll probably make some more changes this evening ... I want to make the definition more universal, so I'd like to make the 2-byte Load F entry also show the normal 2-byte if 2-byte load F doesn't exist. I got the idea last night while browsing the help file, but didn't get a chance to implement it.

If I could figure out how to calculate values based on other logged values in DLL, I would calculate IDC% and compressor lb/min in DLL and not in EvoScan for better resolution in the log. Anyone have input?