User Tools

Site Tools


v3changelog

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
v3changelog [2014/10/01 09:00]
twdorris [3.28.121 (03/25/2014)]
v3changelog [2018/02/09 16:12]
twdorris [3.34.151 (04/22/2017)]
Line 56: Line 56:
  
  
-===== 3.29.63 (10/01/2014) =====+===== 3.36.73 (02/09/2018) =====
  
  
-  * The "Stop capture"​ action now creates a new auto-named datalog file and writes current stream and configuration data to it if no live datalog file had been established previously. ​ Prior to this releasethe decision ​to create a new auto-named datalog file was only made when the stream was started.  ​But now the user can decide before or after stream has been started whether to auto save or not.  ​The "Start stream"​ -> "Stop stream"​ sequence remains unchanged; as does the "Start capture"​ sequence whether followed by "Stop stream"​ or "Stop capture"​ The only sequence affected ​here is the "Start stream"​ -> "Stop capture"​ sequence ​which now auto-creates a new datalog and dumps all previously memory-based datalog packets to the new file and initializes ​the datalog tab as though ​it had been created using the "Start capture"​ action+  * Added support for post key-on fuel pump prime function. 
-  * "​File->​Open" ​and "​File->​Save ​as" will now default to the last "​accessed"​ directory whether established via "​File->​Save ​as" *or* the auto-log-capture create process.  ​Prior to this releasethe auto-log process did not influence the initial directory where the "​File->​Open"​ or "​File->​Save as" dialog would startleading ​to annoying navigation issues.+ 
 + 
 +===== 3.34.151 (04/​22/​2017) ===== 
 + 
 + 
 +  * Fixed an annoying warning message that really didn't mean anything was actually wrong. 
 + 
 +===== 3.34.150 (04/​22/​2017) ===== 
 + 
 + 
 +  * Added support for 64-bit Linux JVM (should ​auto detect at runtime) 
 +  * Added row-based (left-to-right) ​and column-based (top-to-bottom) interpolation options to tables 
 +  * Added scaling/​multiply option ​to tables and lists 
 + 
 +===== 3.33.115 (11/​27/​2016) ===== 
 + 
 + 
 +  * Apparently 80 psi still wasn't enough… Extended boost field range on FPSEGR and Boost (WGS) tabs from 80 psi to 117 psi. 
 +  * Added airflow and boost-based fuel cut options to the ECU Config→Fuel tab. If you have MAP sensor defined in your ECU Inputs tab, you can specify the pressure at which you'd like fuel cut. If you do not, you can use LoadFactor instead. 
 +  * Extended LoadFactor upper limitIt's impossible to given an exact boost figure ​here, of course, because LoadFactor ​is based on the mass of air going into the cylinder per revolution of the engine ​which varies for the same manifold pressure depending on the volumetric efficiency of your setup. But it's //​roughly// ​ extended from about 70 psi to 140 psi
 +  * This update includes proper application signatures for both Windows ​and MacOS as well as a new installation platform and a new underlying runtime library. Any one of these could cause problems…all three at the same time will surely cause someone some griefSo please report ASAP. [[support@ecmtuning.com?​subject=ECMLink laptop application bugs|support@ecmtuning.com]] 
 +  * New rpm and debian package distributions for Linux. Forewarning…there has been *zero* testing of these two items. We're tossing them up because they come for free with our new install platform. If someone needs them and gets a chance ​to test themplease let us know how it goes! 
 +  * NOTE: Linux installations will require that you already have Java 1.8 installed on your system. Most distributions come with that by default these daysbut just in case… 
 + 
 +===== 3.29.64 (10/​15/​2014) ===== 
 + 
 + 
 +  * Extended boost field range on FPS, EGR and Boost (WGS) tabs from 60psi to 80psi for a few (OK, one) crazy individualsThis could get interesting! 
 + 
 +===== 3.29.63 (10/​01/​2014) ===== 
  
 +  * The "Stop capture"​ action now creates a new auto-named datalog file and writes current stream and configuration data to it if no live datalog file had been established previously. Prior to this release, the decision to create a new auto-named datalog file was only made when the stream was started. But now the user can decide before or after a stream has been started whether to auto save or not. The "Start stream"​ → "Stop stream"​ sequence remains unchanged; as does the "Start capture"​ sequence whether followed by "Stop stream"​ or "Stop capture"​. The only sequence affected here is the "Start stream"​ → "Stop capture"​ sequence which now auto-creates a new datalog and dumps all previously memory-based datalog packets to the new file and initializes the datalog tab as though it had been created using the "Start capture"​ action.
 +  * "​File→Open"​ and "​File→Save as" will now default to the last "​accessed"​ directory whether established via "​File→Save as" *or* the auto-log-capture create process. Prior to this release, the auto-log process did not influence the initial directory where the "​File→Open"​ or "​File→Save as" dialog would start, leading to annoying navigation issues.
  
 ===== 3.28.121 (03/​25/​2014) ===== ===== 3.28.121 (03/​25/​2014) =====
v3changelog.txt · Last modified: 2024/03/15 11:16 (external edit)