OpenECU - New pages [en]

EvoXRecovery

Cboles — Mon, 19 Jan 2009 08:20:15 GMT

Cboles: /* Connecting to the ECU */

==Evo X Flash Recovery==

===Summary===
Newer Mitsubishi CAN ECUs based on the M32R processor have an alternate reflash recovery mode which can still be accomplished via the OBD port. If you have one of these ECUs that is for some reason unresponsive via CAN, you can use the method described here to reflash it and regain functionality.

===What is needed===
* Openport 2.0 interface cable
* EcuFlash software
* A special wiring connection to the OBD port (described below)

===Connecting to the ECU===
In order to allow the Openport 2.0 to connect to the ECU in the recovery mode, a special additional connection must be made between the cable and the OBD port. This connection can be accomplished in several ways:

* '''Using an OBD breakout box:''' This method requires the least work and is non-invasive, but carries the most expense. Using an OBD breakout box in-line with the Openport 2.0 and the vehicle, a banana plug jumper wire is placed between OBD pins 8 and 12 on the breakout box. To use this method, nothing must be plugged into the 2.5mm jack on the Openport 2.0.[[Image:evoxrecovery_breakout.jpg]]
* '''Relocating the OBD pin:''' Unmount the OBD connector from the body of the vehicle and carefully eject the OBD pin 8 socket / wire and relocate it to pin 12. The Openport 2.0 can now be plugged directly on to the OBD connector for recovery any time. To use this method, nothing must be plugged into the 2.5mm jack on the Openport 2.0.
* '''Making a temporary connection:''' Plug the Mitsubishi reflash connector (used for Evo 7/8/9 vehicles) into the Openport 2.0. Place a stripped end of hookup wire into the one populated pin socket on the connector. Connect this wire to the OBD pin 8 wire on the backside of the OBD connector using some form of splicing / "vampire" connector. Make sure the connection is reliable and will not disconnect or have intermittent contact during the reflash. Connect the Openport 2.0 to the OBD connector.

===Reflashing the ECU===
Once you have made this special connection, plug the Openport 2.0 to your computer and start the EcuFlash software. In the File->Options control panel, check the Flashing->Flash Recovery Mode option. Load the stock rom file for the vehicle into EcuFlash. Select Ecu->Write to ECU from the menus and follow the instructions to complete the flashing process. The erase and flashing can take some time, so be patient. The program may appear stalled early on while it is erasing the flash which takes 10-20 seconds.

===After You Are Done===
Once the flash is complete, remember to turn off the recovery mode option in the Options menu. You should now be able to connect to your ECU via CAN once again and resume your original flashing work.

J2534

Cboles — Wed, 10 Sep 2008 22:48:21 GMT

Cboles:

=J2534 Resource Page=
==What is J2534==
*J2534 refers to the document number of the SAE standard for "Recommended Practice for Pass-Thru Vehicle Programming".
*The standard defines a general purpose Windows DLL API and hardware requirements to allow software to communicate on various vehicle busses in a hardware independent way.
*Additional revisions of this standard include J2534-1 and J2534-2. The OpenPort 2.0 J2534 DLL primarily follows the specifications of J2534-1.
==Where can I find J2534 documentation?==
*[http://www.sae.org/servlets/productDetail?PROD_TYP=STD&PROD_CD=J2534/1_200412 The standard can be purchased from the SAE for $59]. The PDF document is copyrighted and DRM protected and thus cannot be distributed.
*Drew Technologies has a some good resources:
**[http://www.drewtech.com/support/j2534/intro.html About PassThru]
**[http://www.drewtech.com/support/j2534/index.html API documentation]
**[http://www.drewtech.com/downloads/Drew%20Technologies%20Tool%20for%20J2534-1%20API%20v1.05.msi Drew Technologies J2534-1 Tool] - allows you to connect to J2534-1 devices such as the OpenPort 2.0 and experiment with the API. This program was written for DrewTech products, and so some J2534 features are disabled in the program even though they are supported with the OpenPort 2.0.
**[http://www.drewtech.com/downloads/dllconnect.zip Sample code for DLL discovery]

Current events

Cboles — Fri, 05 Sep 2008 07:41:31 GMT

Cboles:

== OpenPort 2.0 released ==

The new [http://www.tactrix.com/product_info.php?products_id=40 OpenPort 2.0 hardware] is out in the wild, and we are working frantically to add support for the many new CAN vehicles it will work with. Soon after this first releases, we hope to add logging support as well!

Tactrix:MitsuInit

Cboles — Tue, 02 Sep 2008 18:38:36 GMT

Cboles:

This connector is used to pass the initialization voltage to the ECU on pre-CAN Mitsubishi vehicles. It is only needed during a reflash.

The connector can be [http://www.tactrix.com/product_info.php?products_id=48 purchased seperately here], or is available as part of a [http://www.tactrix.com/product_info.php?products_id=40 complete OpenPort 2.0 kit].
[[Image:openport2_mitsu_adapter_sm.jpg|right]]

Driver Tips

Cboles — Thu, 17 Apr 2008 23:21:04 GMT

Cboles: /* Repairing the driver installation */

== Introduction ==

The drivers for the OpenPort 1.2 and 1.3 are included in the EcuFlash installer and installed automatically. This document mainly serves as a reference for developers and to help diagnose or repair OpenPort driver problems in the case that something goes wrong.

== About the drivers ==

The Openport 1.2 and 1.3 use USB interface chips from FTDI as wells as drivers and DLLs also provided by FTDI. 32-bit and 64-bit versions of these drivers for Windows XP and Windows Vista that are customized for the OpenPort Cable are included in the EcuFlash installer and are installed automatically. In the OS X version of EcuFlash, there are no drivers per se, but a FTDI library is utilized. The Windows drivers are actually a pair of drivers - one providing a direct interface to the OpenPort hardware for programs such as EcuFlash and another that creates a virtual COM port on the system with which the OpenPort hardware can be used generically in conjunction with other OBD programs such as data loggers.

== Files ==

Windows XP / Vista 32-bit

* ftd2xx.sys
* ftd2xx.dll
* ftd2xx.ini

* ftser.sys
* ftser.ini

Windows XP / Vista 64-bit

* ftd2xx.sys
* ftd2xx.dll
* ftd2xx.ini

* ftser.sys
* ftser.ini

OSX x86 / x64

* libtfdi.so

== Examining and verifying proper driver installation ==

Aside from running tests with applications which utilize the OpenPort, it is possible to examine and verify the driver installation in Windows using Device Manager. To run Device Manager from the Start Menu, choose '''Start->Run...''' and type '''devmgmt.msc''' and press enter. In the default "View devices by type" view, the two OpenPort drivers appear in seperate locations, one under "USB serial bus controllers" and the other under COM & LPT ports as shown below.

[[Image:openport_drivers_view_by_type.jpg]]

Alternatively, one can select View->Devices by Connection from within Device Manager and locate the driver pair deep within the USB host controller and hub nodes of your PC as shown below. The exact names and number of instances of these various hardware nodes will vary from computer to computer based on the hardware configuration. The advantage of this method is that it can give you a clearer view of how the OpenPort drivers relate to each other, particularly when more than one OpenPort or other FTDI device is present on the system.

[[Image:openport_drivers_view_by_conn.jpg]]

In either case, both drivers should be present, working and have no exclamation points on top of their icons in the tree view.

== Repairing the driver installation ==

If there appears to be a problem with the driver installation, the best course of action is to attempt to re-install the drivers. Try the following solutions one at a time until you are successful. The solutions are ordered in increasing complexity.

'''1. Reinstall drivers automatically via the EcuFlash installer'''

This is the easiest solution - just try re-running the EcuFlash and see if the drivers appear properly in Device Manager as described in the previous section.

'''2.Uninstall drivers and re-install manually'''

Assuming both drivers are already present but not working, start with the virtual COM port driver in Device Manager (e.g. the node named something like "OpenPort 1.3M (as Serial Port) (COM7)") and right click on it and select "Uninstall". Do the same for the other driver (e.g. the node named something like "OpenPort 1.3M"). Now unplug your OpenPort and then re-plug it in. The OpenPort should be recognized as a new device and you should see a dialog (in Windows XP) like the one below. Proceed as described in the following images:

Select "No, not this time" from this dialog and then choose "Next"

[[Image:fnhw1.jpg]]

Select "Install from a list or specific location (Advanced)" from this dialog and then choose "Next"

[[Image:fnhw2b.jpg]]

Select "Don't search. I will choose the driver to install" from this dialog and then choose "Next"

[[Image:fnhw3.jpg]]

Choose "Have Disk..."

[[Image:fnhw4.jpg]]

Choose "Browse..."

[[Image:fnhw5.jpg]]

Browse for the directory

C:\Program Files\OpenECU\EcuFlash\drivers\x86 (for 32-bit OSes)

or

C:\Program Files\OpenECU\EcuFlash\drivers\x64 (for 64-bit OSes)

or to a similar directory if you have installed EcuFlash somewhere else.

[[Image:fnhw6.jpg]]

Choose "OK"

[[Image:fnhw7.jpg]]

The driver "OpenPort 1.3 Universal" should now appear in the list - choose "Next"

[[Image:fnhw8.jpg]]

You now receive a warning which you can ignore - choose "Continue Anyway"

[[Image:fnhw9.jpg]]

This installation now proceeds...

[[Image:fnhw10.jpg]]

This is the final completion dialog - choose "Finish"

[[Image:fnhw11.jpg]]

Once the first driver installation is complete, after a small delay you should see a second driver installation dialog pop up, like the one you just completed. The is the driver installation for the Virtual COM Port driver. Follow the same procedure as the previous driver and the driver installation should be complete.