User Tools

Site Tools


v2tov3settings

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

v2tov3settings [2008/12/15 06:53]
twdorris created
v2tov3settings [2012/02/27 16:07] (current)
twdorris
Line 4: Line 4:
 The basic problem is that users looking to upgrade from V2 to V3 want to be able to transfer their old chip settings over to the new setup. ​ There are two issues with this. The basic problem is that users looking to upgrade from V2 to V3 want to be able to transfer their old chip settings over to the new setup. ​ There are two issues with this.
  
-First, the new V3 application does not (at least not yet) read V2 datalogs or V2 .ecu files. ​ So you have no way to load up the old settings in the new application.+First, the new V3 application does not read V2 datalogs or V2 .ecu files. ​ So you have no way to load up the old settings in the new application.
  
 Second, even if the new V3 application did load those files, you still can't save the settings to the new V3 device because nearly every internal configuration record changed in some way with the V3 release. ​ So doing a "Load from disk" followed by a "save all to ECU" would simply be impossible anyway. Second, even if the new V3 application did load those files, you still can't save the settings to the new V3 device because nearly every internal configuration record changed in some way with the V3 release. ​ So doing a "Load from disk" followed by a "save all to ECU" would simply be impossible anyway.
v2tov3settings.txt ยท Last modified: 2012/02/27 16:07 by twdorris