EvoScan v0.98 Now with Power & Torque Graphing - Map Tracing completed also!
Mar 6, 2007, 11:37 AM
#318
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
Wait till the final copy before worrying, after that PM him
I am sure he isnt trying to rip anyone off I was just wondering if maybe anyone talked to him and knew something that I didnt i.e. He was busy making more cables to send out
Mar 6, 2007, 12:03 PM
#319
Evolving Member
@jfitzpat
If you can somehow add EvoScan or Mitsulogger to the list of supported logs that DLL can read from, I'd buy DLL here and now without a second thought. The only thing holding me back right now is that I have not been able to get DLL to work with my EvoScan or Mistulogger logs.
If you have that in your roadmap somewhere, do let me/us know!
If you can somehow add EvoScan or Mitsulogger to the list of supported logs that DLL can read from, I'd buy DLL here and now without a second thought. The only thing holding me back right now is that I have not been able to get DLL to work with my EvoScan or Mistulogger logs.
If you have that in your roadmap somewhere, do let me/us know!
Mar 6, 2007, 12:11 PM
#320
Data Log Lab already supports Mitsulogger and Evoscan, The author of the software is not jfitzpat, the DLL website is www.dataloglab.com
DLL has a universal data importer tool, you supply a definition file, which I have provided with Mitsulogger (I am under the impression he will include definitions for our apps in his future releases)
You have to go into configuration settings and set the data definition file to the log format you want to import. I definitely feel should be some improvement in selecting definition files and importing, but it works as I use it.
The reason Glenn (the author of DLL) created the universal tool is because it takes quite some time and effort to create specific importers for each log type, and Mitsulogger/Evoscan are so incredibly flexible that its not realistic for him to create a static importer.. Every few days we find new ways of logging and representing items in the Mitsubishi ECU. The definition file allows you to add new items as they turn up, and are needed (if their needed)
Its really a matter of editing a file to load our data logs.
DLL has a universal data importer tool, you supply a definition file, which I have provided with Mitsulogger (I am under the impression he will include definitions for our apps in his future releases)
You have to go into configuration settings and set the data definition file to the log format you want to import. I definitely feel should be some improvement in selecting definition files and importing, but it works as I use it.
The reason Glenn (the author of DLL) created the universal tool is because it takes quite some time and effort to create specific importers for each log type, and Mitsulogger/Evoscan are so incredibly flexible that its not realistic for him to create a static importer.. Every few days we find new ways of logging and representing items in the Mitsubishi ECU. The definition file allows you to add new items as they turn up, and are needed (if their needed)
Its really a matter of editing a file to load our data logs.
Mar 6, 2007, 12:39 PM
#321
Account Disabled
iTrader: (38)
Join Date: Aug 2005
Location: Virginia Beach, Virginia
Posts: 9,319
Likes: 0
Received 1 Like
on
1 Post
I fired up DLL last night and ran an evoscan file through and without any correction saw ~ 350awhp, does that sound realistic for my mods? I'm tuning by NB02 and Knock and feel like I'm leaving a little on the table because I probably don't have a perfectly smooth a/f. I did a few g-tech runs and it showed 12.8 @ 111.4 with a bogged 2.0 60'
I ran it through here http://home.neo.rr.com/jturrin/calchp1.htm and had similar results based on the trap speed. for what it's worth I've tested the g-tech against my local track and found that on average it's 1 tenth fast and 1.5mph fast so I plugged in 12.9 and 110mph and got ~ 350awhp
I ran it through here http://home.neo.rr.com/jturrin/calchp1.htm and had similar results based on the trap speed. for what it's worth I've tested the g-tech against my local track and found that on average it's 1 tenth fast and 1.5mph fast so I plugged in 12.9 and 110mph and got ~ 350awhp
Mar 6, 2007, 01:11 PM
#323
Mar 6, 2007, 04:34 PM
#325
Account Disabled
iTrader: (38)
Join Date: Aug 2005
Location: Virginia Beach, Virginia
Posts: 9,319
Likes: 0
Received 1 Like
on
1 Post
with data log lab (DLL) http://www.dataloglab.com you can click on the beginning of the rpm curve and it will tell you that position, then click on the end of the curve and get that postion, then when you display the power graphs plug those numbers in and it focus on the area between those numbers.
I use the TPS in the graph view to determine where to start and stop the hp run
I use the TPS in the graph view to determine where to start and stop the hp run
Last edited by Mellon Racing; Mar 7, 2007 at 04:52 AM.
Mar 6, 2007, 04:53 PM
#326
Evolving Member
Join Date: Dec 2006
Posts: 276
Likes: 0
Received 0 Likes
on
0 Posts
The last maintanence release of LW-2 has also included a Tactrix cable plug-in so you can log MUT, SSM, and OBDII into logworks as well.
All Others - Again, I am not the DLL guy, I was just commenting that in my own experience, soaring HP is typically a problem with bad data (not part of the pull) being put into the slope computation or no SAE correction (static dyno calc instead of moving road calc). And, later noted that how RPM is smoothed can really impact readings as well.
-jjf
Mar 7, 2007, 06:24 AM
#330
Evolving Member
Data Log Lab already supports Mitsulogger and Evoscan, The author of the software is not jfitzpat, the DLL website is www.dataloglab.com
DLL has a universal data importer tool, you supply a definition file, which I have provided with Mitsulogger (I am under the impression he will include definitions for our apps in his future releases)
You have to go into configuration settings and set the data definition file to the log format you want to import. I definitely feel should be some improvement in selecting definition files and importing, but it works as I use it.
The reason Glenn (the author of DLL) created the universal tool is because it takes quite some time and effort to create specific importers for each log type, and Mitsulogger/Evoscan are so incredibly flexible that its not realistic for him to create a static importer.. Every few days we find new ways of logging and representing items in the Mitsubishi ECU. The definition file allows you to add new items as they turn up, and are needed (if their needed)
Its really a matter of editing a file to load our data logs.
DLL has a universal data importer tool, you supply a definition file, which I have provided with Mitsulogger (I am under the impression he will include definitions for our apps in his future releases)
You have to go into configuration settings and set the data definition file to the log format you want to import. I definitely feel should be some improvement in selecting definition files and importing, but it works as I use it.
The reason Glenn (the author of DLL) created the universal tool is because it takes quite some time and effort to create specific importers for each log type, and Mitsulogger/Evoscan are so incredibly flexible that its not realistic for him to create a static importer.. Every few days we find new ways of logging and representing items in the Mitsubishi ECU. The definition file allows you to add new items as they turn up, and are needed (if their needed)
Its really a matter of editing a file to load our data logs.
I thought I missed something when I looked into the Mitsulogger 1.5 Alpha directory and could not find a .CAR file. I just popped by AktiveMatrix to download the file again and still could not find any definition file to use in DLL.
Sorry to be a bother, but could you provide steps to import Mitsulogger files into DLL for analysis? I'm at my wits end here