Issues with DLL graphing Load%
you can actually have DLL do all the conversions and let evoscan just record the raw data.
the problem with that is DLL doesn't use the same XML parser as evoscan, so some experimentation would be needed to get the fomulas correct.
the problem with that is DLL doesn't use the same XML parser as evoscan, so some experimentation would be needed to get the fomulas correct.
Now that I'm writing this, I think i did stumble on the way to calculate values ... it was just written differently than I expected so i didn't realize it.
There is an explanation of a way to add calculations for different scales, such as F to C or psi to bar. I should be able to use that same method to get the IDC% and lb/min values. Sweet!
EDIT :: I'm not sure IDC% will be possible based on what I read ... it is calculated based on RPM and IPW and I only remember the DLL text talking about calculating from a single value.
It's explained as creating a new entry by modifying an existing one and I was thinking more of creating a new entry and referencing another.
I'll make the changes tonight ...
There is an explanation of a way to add calculations for different scales, such as F to C or psi to bar. I should be able to use that same method to get the IDC% and lb/min values. Sweet!
EDIT :: I'm not sure IDC% will be possible based on what I read ... it is calculated based on RPM and IPW and I only remember the DLL text talking about calculating from a single value.
It's explained as creating a new entry by modifying an existing one and I was thinking more of creating a new entry and referencing another.
I'll make the changes tonight ...
Last edited by TouringBubble; Mar 19, 2008 at 08:48 AM.
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?
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?
you can already do it with EvoScan/Mitsulogger/Excel ... JohnBradley was kind enough to give us the calculations ...
First, calculate g/rev ... [2-byteLoad]/95.
Then, calculate lb/min from that ... ([g/rev]*[RPM])/454
But, there again, thats calculating from 2 logged values and I'm not sure it's possible in DLL. I'll give it a try though ...
Anyone want to post the help file up here? I'm at work and don't have the file with me ...
First, calculate g/rev ... [2-byteLoad]/95.
Then, calculate lb/min from that ... ([g/rev]*[RPM])/454
But, there again, thats calculating from 2 logged values and I'm not sure it's possible in DLL. I'll give it a try though ...
Anyone want to post the help file up here? I'm at work and don't have the file with me ...
If you select the help option from the menu in DLL it sends you to a local HTML file. I can't find that file online.
With the lb/min, it's ultimately based on load, which is based on airflow which is affected by elevation. So, technically, elevation is considered.
Calculating HP based on airflow is very consistent, but may not be accurate at higher RPM where the turbo starts to heat everything up. I'm still on the fence as to which method is best ... RPM/time or airflow ...
With the lb/min, it's ultimately based on load, which is based on airflow which is affected by elevation. So, technically, elevation is considered.
Calculating HP based on airflow is very consistent, but may not be accurate at higher RPM where the turbo starts to heat everything up. I'm still on the fence as to which method is best ... RPM/time or airflow ...
Okay ... so here is probably the last file I'll post. I couldn't find a way to build completely calculated values, so you'll have to log IDC%, g/rev and lb/min w/ EvoScan. I did add them to the DLL definition though, along with Boost Error.
This definition should be able to handle most of your graphing needs ...
This definition should be able to handle most of your graphing needs ...
Some people were asking recently about DLL definitions ... so here is my current definition file. If you have issues, please verify that the ColumnTitle values match your EvoScan columns exactly.
Thread
Thread Starter
Forum
Replies
Last Post
richardjh
09+ Ralliart Engine/Turbo/Drivetrain
68
Jan 16, 2013 06:58 PM



