Multiecuscan 2.7.1 RELEASED!

[yani]

Hi,


I released Multiecuscan 2.7.2 on 03/03/2011 to fix a PROXI Procedure bug in Multiecuscan 2.7 and 2.7.1.



I released Multiecuscan 2.7.1 today to fix the "crash" on connection bug in Multiecuscan 2.7.
I also improved the support for Bluetooth OBDKey interfaces and fixed the error codes for ABS Teves MK20/70.

Multiecuscan 2.7 Interface and functionality improvements. The main changes are:

- Fixed a problem with Remote Control programming
- Fixed the RPM calculation in Bosch Motronic ME7.3H4
- Support for TRW MY05, AUTOLIV MY06, AUTOLIV MY07 and SIEMENS MY06 Airbags (Grande Punto, Punto Evo, 500, QUBO, MITO)
- Support for Hitachi MPI Injection (pre-98 vehicles)
- Support for Bosch Monomotronic MA1.7.3 Injection
- Added [Recent] option for vehicle selection
- Added search when typing for vehicle selection
- Added "tool-tips" for the buttons. The messages for the tool-tips can be modified/translated from the language files.
- Added Select All/Select None buttons on Parameters screen
- Added monitoring of error codes in Parameters and Graph screens and recording of the error codes in the generated CSV logs.
- Fixed a problem with the scaling on the graph screen.
- Added current values display on a graph when the user clicks on it with the mouse.
- Improved PROXI procedure support
- Added more configuration options for PROXI procedure (Stilo, Punto, 147)
- Added command-line switch /t=XX where XX is a template number. This switch causes the program to connect to last ECU and load the selected template. (So, when you run "Multiecuscan2 /t=1" then the program will start, connect to the last ECU, go to Parameters screen and load template 1.)
- Added interface auto-selection. You can define up to 4 interfaces in Settings. Then when you click "Connect" the program will first check which of the interfaces is connected to the computer and will use that interface for connection to the vehicle. If there is only 1 interface defined in Settings then the program works without auto-selection.
- Added interface lookup function in Settings. This function will automatically identify the type of interface, port and port speed of your interface(s). The interface has to be powered (connected to vehicle).
- Added full support for the USB OBDKey 1.40 interface which is in official production now. This interface cannot be used for Fiat Grande Punto, Alfa MITO and Fiat 500 yet.
- Added support for the Bluetooth OBDKey 1.40 interface. There are still some stability issues with the Bluetooth interface, so the USB unit is recommended.
- Added "PLEASE CONNECT ADAPTER XX" messages before connecting to ECU. For the users who do not use adapter cables the message can be disabled from Settings.

Please, I need someone with USB OBDKey interface and Alfa 147 or Stilo with automatic climate control to test the PROXI Alignment function and send me a report. I need to know if the PROXI function will work properly on these two vehicles or not with OBDKey interface. The procedure always fails for Alfa 147 Instrument Cluster and Stilo Climate Control nodes when using ELM interface.

Yani

[EnIgMa]

wow.
great great job Yani!!

[mattydr67]

This is very good news.
Good luck

[dusan147]

......Added monitoring of error codes in Parameters and Graph screens and recording of the error codes in the generated CSV logs.........

Thanks Yani...

[Bravo-JTD]

- Added [Recent] option for vehicle selection
- Added search when typing for vehicle selection
- Added monitoring of error codes in Parameters and Graph screens and recording of the error codes in the generated CSV logs.
- Added interface auto-selection. You can define up to 4 interfaces in Settings. Then when you click "Connect" the program will first check which of the interfaces is connected to the computer and will use that interface for connection to the vehicle. If there is only 1 interface defined in Settings then the program works without auto-selection.
Added interface lookup function in Settings. This function will automatically identify the type of interface, port and port speed of your interface(s). The interface has to be powered (connected to vehicle).
...
Very, very useful. Thank you Yani

[frank37]

Hi Yani,

I have a problem and a question.

1. At a resolution of 800x600 Tablet PC, I have the text boxes to the far right, see first picture.

2. Sub-parameter is the right yellow box, the text can only be in English, we translate into several languages.
The same is also Actuator, yellow in the right window.

It would be nice if you could still change this.

Fantastic software from you.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Greetings
Frank

[bas]

The procedure always fails for Alfa 147 Instrument Cluster and Stilo Climate Control nodes when using ELM interface.

So in practice it is not working if I have A/C?

BAS

[yani]

The procedure always fails for Alfa 147 Instrument Cluster and Stilo Climate Control nodes when using ELM interface.

So in practice it is not working if I have A/C?

BAS

It is working for all other modules. The AC ECU does not need to be programmed (PROXI Aligned) unless it is replaced or retrofitted. So, even if the procedure fail, it will program properly the rest of the ECUs.

[ototest]

Thank you dear Yani ,,
We will try for support you lovely.. Regards.

[Shadeyman]

Hello Yani.

I have an Elm interface, and I've replaced my automatic climate control unit in my Stilo. Proxi-alignment failed. I've already sent you my log file via PM.
I also have a VAG-Com interface it works well, but not as functional as the Elm.
OBDKey is next on my shopping list.
If there's anything I can do to help please let me know.