EvoScan v0.98 Now with Power & Torque Graphing - Map Tracing completed also!
Wow I was so excited I just spent the last 10 mins scouring the website looking for a download link for .98...then I realized you said that it wouldn't be out till the 28th 
That's how excited I am!!! 
That's how excited I am!!!
To say that the code isn't obfuscated really isn't all that useful, I really have no interest in reverse engineering someone elses code even though I have been indirectly accused of it several times. Heck I wish I would have noticed that before I spent weeks working on mine before I got something that worked with a single requestID using information posted on OpenECU and Opendiag, and some third party assistance. Prior to the log analyzer I wrote, I had no experience with VB.NET and wrote almost everything in VB6.
I only purchased the program because of the promise of source code I had no interest in making any changes except for things I needed to support my own car.
Ya know, I do understand why the source wasn't released though. Part of the problem with open source is some projects frequently split off into new features based on code that is no longer compatible with the core. Also, VB.NET projects don't lend themselves very well to group development using something like sourceforge.
I wish I never had to develop my own program, but it was because there was no intention of adding the features I was looking for at the time, I didn't want .NET 1.1, and I didn't want the gauge features.
You should release the information on the different protocols and other info, as that would benefit the community and I personally think its something everyone can benefit from.
You did originally claim the charge was to cover the cost of your third party gage components.. If thats the case, why didn't you invest in the new updated components? .NET 1.1 is considered depricated and microsoft has urged developers to migrate away from it if possible.
I'm looking forward to the features you've announced.. Many are similar to things I had planned that may no longer be necessary to work on.
But my ultimate problem was if people were promised source code, then you should have made it available. This was made in writing, and would constitute a breach of contract. But besides all of that, if people had the source, they would be contributing new code snippets and other good bits to you. I took a very modular approach so I could potentially do that if I lose interest in continuing development.
Anyway, I'll end it here, because its really not appropriate for this thread, and for as critical as I am, I do think what your doing is a great service for the community, I just think it would have been better served to share what you have learned with the community.
I only purchased the program because of the promise of source code I had no interest in making any changes except for things I needed to support my own car.
Ya know, I do understand why the source wasn't released though. Part of the problem with open source is some projects frequently split off into new features based on code that is no longer compatible with the core. Also, VB.NET projects don't lend themselves very well to group development using something like sourceforge.
I wish I never had to develop my own program, but it was because there was no intention of adding the features I was looking for at the time, I didn't want .NET 1.1, and I didn't want the gauge features.
You should release the information on the different protocols and other info, as that would benefit the community and I personally think its something everyone can benefit from.
You did originally claim the charge was to cover the cost of your third party gage components.. If thats the case, why didn't you invest in the new updated components? .NET 1.1 is considered depricated and microsoft has urged developers to migrate away from it if possible.
I'm looking forward to the features you've announced.. Many are similar to things I had planned that may no longer be necessary to work on.
But my ultimate problem was if people were promised source code, then you should have made it available. This was made in writing, and would constitute a breach of contract. But besides all of that, if people had the source, they would be contributing new code snippets and other good bits to you. I took a very modular approach so I could potentially do that if I lose interest in continuing development.
Anyway, I'll end it here, because its really not appropriate for this thread, and for as critical as I am, I do think what your doing is a great service for the community, I just think it would have been better served to share what you have learned with the community.
Ahhhhh, Maliboobie...you need some love, bro? Seriously, it's people like me that REALLY appreciate what is given, purposed, and shared within this community to make life easier and more enjoyable for all of us. Tuning takes enough extensive thought and when given the right tools makes it's that much easier and accurate for the end-user to provide positive results. The best analogy I can think of is...do I want tools from Wallymart or Snap-On? No contest...thanks again to you and the Kiwi!
s. I've been cursed with no option but snap-on at work the past 8 years. I have also seen some tools up to and even better than snap-on at WalMart. Furthermore WalMart provides me with the MeOH that my car depends on at still, $0.97/12oz
But going forward most people are going to have the newer versions of .Net either because they upgraded to Vista or because windows updated pushed it out to the machine. Either way going forward you should include the required runtime at installation time
.
.Anything you compile on .NET is transformed into CLR code so I don't understand what was the point in pointing this out?
. To be clear not attacking here but trying to understand your reasoning?
Last edited by codgi; Feb 24, 2007 at 04:59 PM.
The problem with this is that for both .NET and Java it is possible for someone to take the code in the intermediary language and easily reverse engineer it to get the original source code.
For .NET the solution for this was to "obfuscate" the produced program. All this means is that another program is run on the final product so that any attempts to reverse engineer the product will be harder (i.e you'll end up with very cryptic hard to read code).
When I saw this thread the other night I did too think with the correct tools the source probably doesn't need to be available to someone with enough time to sit down and prod it (never bothered looking cause I just don't have the time/need to do it).
MJ is correct in the end though (as usual it appears
)...but what is done is done.
I think the original idea was to include DTC functions but I dont think they work as of yet. I use Scantech and it works great. Search this forum for Scantech and you should find the link MJ posted for it. It works great and also lets you see actual OBDII values and freeze frame data.
Yep, the functionality for clearing and reading DTC's isn't working for the USDM Evo8 and 9.. However I think he might have mentioned that he was able to resolve that in this upcoming version.
Thread Starter
Former Sponsor
iTrader: (4)
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
geez, I already said I was going to be at the racetrack all day yesterday, yesterdays emails haven't been cleared yet why dont you just PM me, instead of slagging me off on here about "$25 bucks for nothing". nice.
EvoScan v0.98 is the bomb man! EvoScan saved my engine from death twice yesterday, I was driving the evo pretty hard, and all off a sudden my knock sensor alarms went crazy on the back straight. I lifted off the throttle straight away Afterwards I checked the A/F ratios and they were in fact too lean, so I fulled the tank up with petrol cause it was basically empty and the AFRs came back to normal, and no more knock. And then in the heat of the afternoon, my coolant temp >95Celsius alarm started going off.. turned out my headgasket became leaky due to running 24Psi through the poor engine. called it a day.. tonight I will analyse the logs through the torque and power graphs to ensure everything is working properly before releasing tomorrow.
why dont you just PM me, instead of slagging me off on here about "$25 bucks for nothing". nice.EvoScan v0.98 is the bomb man! EvoScan saved my engine from death twice yesterday, I was driving the evo pretty hard, and all off a sudden my knock sensor alarms went crazy on the back straight. I lifted off the throttle straight away
Afterwards I checked the A/F ratios and they were in fact too lean, so I fulled the tank up with petrol cause it was basically empty and the AFRs came back to normal, and no more knock. And then in the heat of the afternoon, my coolant temp >95Celsius alarm started going off.. turned out my headgasket became leaky due to running 24Psi through the poor engine. called it a day.. tonight I will analyse the logs through the torque and power graphs to ensure everything is working properly before releasing tomorrow.