Tactrix Openport 2.0 Software Download

Tactrix Openport 2.0 Software Download:

The OpenPort 2.0 is our newest tuning tool hardware that is capable of communicating with most OBDII compliant vehicles using a standard J2534 interface. Combined with our EcuFlash software, the OpenPort 2.0 is capable of reflashing a large number of newer Subaru and Mitsubishi vehicles, and support for other cars is in progress.

We include a USB cable with each OpenPort, which is all the hardware you’ll need unless you have one of the few vehicles that require a separate reflash adapter. For Subaru you’ll only need a reflash adapter for the 2001 through 2005 WRX, but not STi, unless you’re working on an early non USDM STi in which case you made need one of our WRX adapters. No other Subaru vehicles require reflash adapters including Forester, Baja, Legacy, or naturally aspirated Impreza models. For Mitsubishi, you’ll need the adapter for most pre CAN vehicles which include the 5-9 Evo. Choose the adapter you need from the ‘Reflash Adapters’ drop down list on the right side of this page.

Tactrix Openport 2.0 Car List:

Drivers
— bug fixes —

Fixed Openport 1.3 driver INF file section naming error which was preventing this driver from installing correctly
Fixed MSVC compiler library issue which made J2534 DLL incompatible with Windows XP
Changed driver signing certificates back to SHA1 from SHA256 for compatibility with pre-Win8 OS versions until MS release SHA256 kernel mode signing updates for these

EcuFlash
— features —

File dialogs offer all ROM types by default
Added SH boot mode support for SH725XX processors. User Boot MAT is still not supported yet pending read support for this area.
adding clarification to message indicating nothing was written due to no differences in ROM images.
support for 2015 WRX with Hitachi ECU
support for OEM reflashing of BRZ
mitsucan heuristically determines correct checksum area size
Allow for other responses in wrx02 bootloader init sequence (possibly for ecutek’d ECUs)
Update checker now looks at build numbers to notify you of incremental improvements that don’t have a new minor version change

— bug fixes —

added additional delays when communicating with Mitsubishi bootloaders to avoid the ECU occasionally not receiving bytes
fixed MSVC compiler library issue which made EcuFlash incompatible with Windows XP
fix bug where reading response from kernel could report “msg buffer too small” when it was not
get Evo X recovery mode write back in ECU menu options
Fix bug where vehicle type dialog selects first item if you do not interact with tree view, even though another item is shown as selected.
Fix problems with FTP uploads of unknown ROMs
Problems with failed readEcuIdentification requests in CAN Mitsubishis are ignored in case they are not supported in the current mode.
Fixed problem with non-ASCII (e.g. Cyrillic) filenames
Fix bug where patches and some other metadata was not appearing in metadata view

J2534 DLL
— features —

DLL no longer uses Qt to make smaller and more portable, uses boost library instead
OSX support coming shortly

— bug fixes —

fix bug where startMsgFilter was looking for the wrong synchronization stamp
fix wait condition problems in port to boost library causing communication problems with driver
report ERR_TIMEOUT in more places where waits fail
fix missing ExtraDataIndex values when dequeing rx messages

Firmware
— new features —

change voltage / pin enable logic to allow more than one OEM pin to be set to the same voltage
add more Subaru seed-key tables
ISO: add beginnings of a ISO9141 “max msg len” J2534 custom parameter to allow chopping up of continuous ISO9141 stream to cut down on latency and potential message size overflow.
logging: add length limit to UDS requests (will break into multiple requests)
logging: add logical not function
logging: reduce SSM retry time by half
logging: improve error reporting
logging: disallow params that start with a number
logging: add mode23 UDS logging option “mode23uds”
logging: add option to sort PIDs “sortpids = 1” for channel (mode23 logging needs this to work well as it tries to optimize sequential byte reads)
do additional range validation on many J2534 parameters

— bug fixes —

CAN: only send additional flow control frames if ISO15765_BS is not 0
CAN: complete missing implementation of ISO15765_BS and ISO15765_BS_TX which are needed to limit the number of continuing CAN messages sent between waiting for additional flow control (FC) messages from the other party.
CAN: return CAN_29BIT_ID flag on appropriate read results (was being masked by accident)

Download links :

• Tactrix Openport 2.0 Drivers + J2534 DLL – Tactrix Setup
• ECUFlash 1.44.4870 for Windows XP / Vista / 7 / 8 / 10
• EcuFlash 1.38 for OSX 10.4+