Virtual Dyno - Standalone Software
i have vista. works for me. i really like how it pulls the correct part of the log for me. no more cut and paste? sold!
oh. and saving a profile is nice so i don't have to re-enter my info EVERY time.
oh. and saving a profile is nice so i don't have to re-enter my info EVERY time.
Thread Starter
Evolved Member
iTrader: (1)
Joined: Oct 2008
Posts: 692
Likes: 1
From: Kansas City, KS
Im going to hold of on using the new installer a bit ... I need to add some to it and its not a major advantage. Its just going to cut the installer to about half the size and be a lot faster installing. Just got to get that tested first. Ohh and did I mention its easier on me building a release
Thread Starter
Evolved Member
iTrader: (1)
Joined: Oct 2008
Posts: 692
Likes: 1
From: Kansas City, KS
I started off using just a .NET setup project. I found out in the next version of Visual Studio they are doing away with those so I had to find an alternative. I started using InstallShield and people were complaining of write permission issues on the installation directory. So I went to using Nullsofts (NSIS). I have a beta of the installer built with it but its not released yet. Its fairly simple and VERY customizable. It is probably the most customizable of the three. Ive still got some things to add to it but I think its going to be the simplest install for the user and the quickest, and it has the smallest footprint (611k vs 1500k).
DSMLink (and now ECMLink) log in a binary format that I don't believe Tom and Dave ever formally documented anywhere. You can peruse the source code for DSMLink v2, which might give you an idea of the V2 format:
http://www.ecmtuning.com/downloads/i...s_2_5_full.exe
(Once unzipped, you'll want to look in dsmlinksrc.jar; you'll probably want to start with com.ecmtuning.dsmlink.data.Dataset and friends.)
I believe they changed the format with V3, however, and I don't believe they have any plans to release the source for V3 after all the work they put into it.
http://www.ecmtuning.com/downloads/i...s_2_5_full.exe
(Once unzipped, you'll want to look in dsmlinksrc.jar; you'll probably want to start with com.ecmtuning.dsmlink.data.Dataset and friends.)
I believe they changed the format with V3, however, and I don't believe they have any plans to release the source for V3 after all the work they put into it.
Thread Starter
Evolved Member
iTrader: (1)
Joined: Oct 2008
Posts: 692
Likes: 1
From: Kansas City, KS
ehh the way I view it is if they want to leave their logs in their own format thats their business. If they want to their users to be able to use software like mine they can easily add an export function to save it in CSV or just plain text format. every other logger does.
heres a chart from some baseline tuning i did on my 90 eclipse
mods:
wiseco 9:1 HD pistons
manley Hbeam rods
buschur stg3 head/arp L19's
bone stock fuel system, exhaust and IC
turbo is what looks like a 16g, has a 1.87" compressor inlet ID
i'd say sounds about right. now its time to uncork this puppy
mods:
wiseco 9:1 HD pistons
manley Hbeam rods
buschur stg3 head/arp L19's
bone stock fuel system, exhaust and IC
turbo is what looks like a 16g, has a 1.87" compressor inlet ID
i'd say sounds about right. now its time to uncork this puppy

heres a chart from some baseline tuning i did on my 90 eclipse
mods:
wiseco 9:1 HD pistons
manley Hbeam rods
buschur stg3 head/arp L19's
bone stock fuel system, exhaust and IC
turbo is what looks like a 16g, has a 1.87" compressor inlet ID
i'd say sounds about right. now its time to uncork this puppy
mods:
wiseco 9:1 HD pistons
manley Hbeam rods
buschur stg3 head/arp L19's
bone stock fuel system, exhaust and IC
turbo is what looks like a 16g, has a 1.87" compressor inlet ID
i'd say sounds about right. now its time to uncork this puppy








its perfect
mid-high 11's is perfectly fine. its dying past 6200 because i need to uncork it, stock exhaust/intercooler FTL! not for long tho