evoscan
Apr 6, 2009, 08:56 PM
#23
Evolving Member
iTrader: (2)
Join Date: Aug 2008
Location: MA
Posts: 232
Likes: 0
Received 0 Likes
on
0 Posts
Latest update:
You guys should keep an eye on that thread.
I have finished writing the Vista64 bit serial logging code, and I got a few people to test it this week. Its working great on AEM, ZT2, and Innovate widebands for Vista 64 bit now.
If you get disconnect reconnects, thats just because you ticked an item that forces the ecu to disconnect the logging session, I seen that today on an older vehicle when I was logging wastegate duty cycle, I unticked it, then it was all happy again.
I have finished the EvoX datalogging, and the data items are being discovered at the moment, this will take another few days of discovery, if you know vehicles well you can get a copy of the EvoX full log CSV from me and work out which MUTII ids are for what values, I have a few undiscovered ones, the community may figure these out fairly quickly once I release it anyway.
I have retested the OpenPort2.0 datalogging, and its working good.
I am programming Diagnostic codes for the OpenPort2.0 cable at the moment, should only take me another day.
I tested the 1G/OBDI/ALDL (pre 1995 Mitsubishi) still works in EvoScan v2.6 beta10 today. Its still working sweet.
I have tested that the EvoScan ECU Reflashing feature works on Openport 1.3U on evo7/8 (Evo9 reflashing still in beta testing - still 1 more bug), but for openport2.0 you will need to use EcuFlash.
These large advancements may warrant an EvoScan v3.0 release.
If you get disconnect reconnects, thats just because you ticked an item that forces the ecu to disconnect the logging session, I seen that today on an older vehicle when I was logging wastegate duty cycle, I unticked it, then it was all happy again.
I have finished the EvoX datalogging, and the data items are being discovered at the moment, this will take another few days of discovery, if you know vehicles well you can get a copy of the EvoX full log CSV from me and work out which MUTII ids are for what values, I have a few undiscovered ones, the community may figure these out fairly quickly once I release it anyway.
I have retested the OpenPort2.0 datalogging, and its working good.
I am programming Diagnostic codes for the OpenPort2.0 cable at the moment, should only take me another day.
I tested the 1G/OBDI/ALDL (pre 1995 Mitsubishi) still works in EvoScan v2.6 beta10 today. Its still working sweet.
I have tested that the EvoScan ECU Reflashing feature works on Openport 1.3U on evo7/8 (Evo9 reflashing still in beta testing - still 1 more bug), but for openport2.0 you will need to use EcuFlash.
These large advancements may warrant an EvoScan v3.0 release.
Apr 7, 2009, 04:36 PM
#26
Account Disabled
iTrader: (8)
Join Date: Sep 2007
Location: Hayward
Posts: 3,366
Likes: 0
Received 0 Likes
on
0 Posts
if you click on the blue arrow icon next to the quote title it will take you to the original post:
https://www.evolutionm.net/forums/ec...ml#post6903405
https://www.evolutionm.net/forums/ec...ml#post6903405
Apr 7, 2009, 04:40 PM
#27
Evolved Member
Join Date: Dec 2008
Location: MD
Posts: 685
Likes: 0
Received 0 Likes
on
0 Posts
if you click on the blue arrow icon next to the quote title it will take you to the original post:
https://www.evolutionm.net/forums/ec...ml#post6903405
https://www.evolutionm.net/forums/ec...ml#post6903405
