EvoScan v0.98 Now with Power & Torque Graphing - Map Tracing completed also!
Mar 7, 2007, 12:26 PM
#347
Registered User
Join Date: Jan 2005
Location: scarsdale,NY - lima,OH
Posts: 845
Likes: 0
Received 0 Likes
on
0 Posts
Ok thanks
Mar 7, 2007, 12:49 PM
#349
Evolving Member
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*
With a -4/-1 setting, I wonder if I will lose any power up high *ponder*
Mar 9, 2007, 08:45 AM
#355
Newbie
iTrader: (3)
Join Date: Dec 2005
Location: Seattle, WA
Posts: 87
Likes: 0
Received 0 Likes
on
0 Posts
Yes they are 100% compatable, and will continue to be, I even kept the same USB PID so that you can use the same installed drivers. Which is especially important for Mobile device drivers, ya don't want two sets of drivers taking up memory. The EvoScan 1.4E cable is a low cost solution and contains no boot flash circuits, The EvoScan 1.3M is the same design as the openport 1.3M and supports the boot flash connector.
Colby
Mar 9, 2007, 10:43 AM
#356
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.
Mar 11, 2007, 07:11 PM
#357
Evolving Member
iTrader: (3)
Join Date: Mar 2005
Location: Grand Rapids, MI
Posts: 222
Likes: 0
Received 0 Likes
on
0 Posts
EvoScan .98 issue
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.
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.
Last edited by RedV; Mar 11, 2007 at 07:22 PM.
Mar 11, 2007, 08:35 PM
#360
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.
Last edited by MalibuJack; Mar 11, 2007 at 08:39 PM.