Änderungen in Version 2.8.607 - Bugfix: Trailing spaces in a VIN could lead to an error when saving a log file - fixed Changes in version 2.8.604 (professional only) - Bugfix: Save Logfile could fail when no VIN was reported by vehicle and no VIN was entered into database manually - fixed Changes in version 2.8.603 - Bugfix: Wrong calculation of Mode 6-testlimits could lead to wrong passed/failed indication - fixed Changes in version 2.8.602 - Bugfix: Fuelconsumption could freeze at "--,--" when logging - fixed Changes in version 2.8.601 - New language: Russian - Bugfix: No protocol found when used with Scandevil V. 2.0 - fixed Changes in version 2.8.600 - New language: Turkish - New feature: in the sensor data table and digital displays, thresholds can be entered. When the treshold value is reached a warning will appear. - Improved termination of the program during connection establishment. Changes in version 2.8.515 - Improved functionality of error log function - BUGFIX: Dialog asking for saving unsaved Log Data appeared even when logging was only paused - fixed. Changes in version 2.8.511 - Correction of minor visualization errors Changes in version 2.8.510 - Improved support for ELM interfaces (professional and moDiag expert for ELM) Changes in Version 2.8.500 - Improved termination of the program - on slower systems it could happen, that the program could not be terminated correctly - fixed - Improved resizing of diagrams - when the main-window has been resized during recording a diagram, the diagram did lose the previously recorded values - fixed Changes in Version 2.8.202 - Improved display on systems with low resolution (e.g. netbooks) - Mouse wheel support in all tables - Faster startup - Interface wizard now also tests for interfaces with 19200 baud (e.g. DXM-module) Changes in Version 2.8.104 - Preparation for turkish translation - Corrected display of trouble codes with hexadecimal ciphers - Improved behaviour if PID configuration file is missing Changes in version 2.8.102 BUGFIX: Run-time error 380 could occur on computers with screen resolution set to 800 x 480 - fixed. Changes in version 2.8.101 - New feature: Calculated PID "Volumetric Efficiency [%]" - moDiag determines the volumetric efficiency of the engine from the PIDs "Mass Air Flow" and "Engine Speed"; this can help to diagnose malfunctions of the inlet-/exhaust section of the car (e.g. defective MAF sensor, restrictions or false air) (professional only) - New feature: Single data records can be deleted from the customers/vehicle database (professional only) - Improved connection establishment for vehicles with ISO 9141-2 protocol and critical timeout behaviour - Improved support of multi-frame-messages for mOByDic interfaces with cars using CAN protocol - Unification of expert-Versions for OBD-DIAG/DIAMEX and mOByDic interfaces - Interface wizard now supports mOByDic interfaces too - moDiag now also can be executed from different user accounts than the one it has been installed under - Support of the new Tremex interfaces - Support of Windows 7 64-bit Changes in version 2.7.201 - Improved support for mOByDic-Interfaces with CAN-Protocol (professional only) - Date entries in database with non-german local settings could result in run-time error - fixed (professional only) Changes in version 2.7.105 - Added manufacturer "Isuzu" to the vhicle data base (professional only) - BUG: Wrong entry in the field "registration date" of the vehicle database could lead to a runtime error - fixed (professional only) - BUG: A crash could occur when in the sensor data grid the option "Show only supported data" was deselected and another tab (e.g. Display) was selected - fixed Changes in version 2.7.104 Improvement - additional/redundant function for the enumeration of available COM-ports; Run-time errors when searching for available COM ports with certain USB-to-serial converters should be avoided hereby Changes in version 2.7.102 Bugfix: Wrong serial identification with DIAMEX DX60/61 interfaces could occur - fixed Changes in version 2.7.101 Bugfix: Opening the Configuration dialog could result in Run-Time-Error - fixed Changes in version 2.7.100 - improved support of Bluetooth interfaces - Faster data aquisition - Several internal optimisations - improved Windows 7-compatibility - improved presentation of LPG-adjustment software icons (will automatically change to a list style, when more than 5 softwares are installed to minimize scrolling) Changes in version 2.5.110 (Express, Expert, Professional) - Added function for saving the error-log on the configuration dialog - Bugfix: DTCs which have set a freeze frame and had a code that terminated in "00" could not be displayed - fixed Changes in version 2.5.109 (Expert and Professional) - Admintrative (no changes to 2.5.108) Changes in version 2.5.108 (Expert and Professional) - Bug concerning the output of live sensor data in the report - fixed - Small changes for Windows 7 compatibility - moDiag now is fully Windows 7 compatible Changes in version 2.5.107 (Expert and Professional) - Added multiple diagram views in the sensor data tab Changes in Version 2.5.106 - Improved search for communication protocol with OBD-DIAG interfaces Changes in Version 2.5.105 - Bugfix: Minimizing the program window could result in hang up - fixed Changes in Version 2.5.102 Professional, Expert and Express-Version - Complete support of the new Mode 1-PIDs acc. to SAE J1979-2007-05 for model year 2010 vehicles - Implementation of "calculated" PIDS "Fuel trim #1 - #4" and "Fuel trim S2 B1 - B4" - moDiag now can calculate the resulting fuel trim automatically and visualize it like all other PIDs - Implementation of Mode 9 - Infotype 08 - In-Use-Performance-Counter - Implementation of Mode 9 - Infotype 0A - ECU-name - Expanded Baudrate list for better support of the DXM-Module from OBD-DIAG - Improved visualization of the Readiness-Codes - Improved data logging - the logging can be activated any time during the read out process. - Minor bugfixes