Yes you can but I would wait until all the bugs get worked out first....

 

sorry didnt read the thread. I just got on here and posted.

Ok thanks

 

That would be going in the wrong direction if more midrange torque is what you're wanting.

 

Thanks. I'll be making a trip to my tuner's to get them dialled in first thing tomorrow morning. Will post new power/torque charts when I'm done.

With a -4/-1 setting, I wonder if I will lose any power up high *ponder*

 

No, that should actually prolong the power a bit at the expense of a bit of midrange response.

 

I am away on business till this weekend, I'll see if I can get it all sorted out then

 

Off Topic: Have a safe trip

 

Stay out of trouble

 

me 3

 

I've been trying to get in touch with Hamish, but he appears quite busy at the moment. Until I come up with another solution, at this point I cannot support the EvoScan 1.3M with the EcuFlash software since buying the cable from Hamish does nothing to support the development of EcuFlash. I'm trying to figure out a solution to this, as I would like to keep the EcuFlash software freely distributed yet keep the project funded. I am also unsure as to the specifics of his cable design, but all of the OpenPort designs are copyright Tactrix Inc., even though I do make the schematics public for informational reasons.

Colby

 

I have the Version .97 but have never received any updates or e-mails? Is there any way to check and make sure your on the mailing list? I know the e-mail hasn't gone out yet for the new version but you'd think I would have received something in the last 7 months or so.

 

So thought I'd give EvoScan .98 a try today.

Hooked up the cable, with the OBDII connector only, not the white flash plug because of the problems I've read other people having with version .98. Clicked the log button and the software begins logging, but quits shortly after. It then appears to continuously retry it's connection.

During it's brief logging session, the values that it logs are obviously not correct. Attached is a example of the short log that was captured with the car sitting idle in the driveway.

Just for example, the RPM value jumps around from 0 to 7750, the coolant goes from 273 to -2285, and the knock count goes from 0 to 248! Obviously this isn't right.

I have read that the version of release .98 that's out isn't completely bug free yet, but I thought I'd post this to possibly help evo4mad track some of them down.

Version .97 still logs just fine, so I'm pretty sure it's not a hardware/software install problem.

This is a 2006 USDM Evo IX GSR with ECUID 88590015 and the 1.3M cable.

 

thats weird - i would dbl check your cable is in correctly..

 

Checked it, plus version .97 logs perfectly. So I don't think it's a cable issue.

 

I'll have to talk to Hamish about this, but I think he got bit by the same bug I came across in my code due to how the drivers changed recently. If he started with the same FTDI driver and FTDI sample project code as I did, there was a flow control value that was not really honored in the earlier driver, which is now. It caused all sorts of performance problems for me.