The 'Test' tab is an ECU simulator that injects messages to test the application.

The 'Vehicle Information' tab shall provide you with at least the VIN# when you click the 'Get Data' button.

(This still needs to be tested and I haven't gotten around to trigger a DTC yet on my car, so it may still show some quirks)

The 'DTC Handling' tab allows you to list the DTC:s that are active.

The 'Freeze Frame' box will only be useful if the ECU has logged any Freeze Frame data, but it works in the same way as the 'Current Data' box except that the data ends up under the 'Freeze Frame' tab.

Snapshot data can be taken by checking the desired checkboxes and clicking on the 'Get Data' button.

and that can be plotted by using the interval setting and 'Start' button in the 'Plot Current Data' box after you have checked the applicable checkboxes.

Underlined PIDs defines dynamic data that varies over time like coolant temperature, engine rpm etc.

The answer shall then enable the checkboxes for the supported PIDs. By clicking on the 'Get PIDs' button in the 'Current Data' box the application will send a message to the ECU in the car and ask which PIDs it supports. It will display a lot of disabled checkboxes.

The 'Config' and 'Filter' tabs shall already be filled in with data that works.

This will open a new window with a lot of tabs.

Default is protocol ISO15765, 500kbps and no flags.

On the first page select Vehicle 'Subaru' and Interface 'Tactrix Openport Driver' and click on 'Open'.

Connect your Tactrix OpenPort 2.0 dongle.

Unzip the downloaded ZIP file into an empty directory.

You can run the program without connecting it to your car as long as you have a Tactrix dongle. What's new is that I have made improvements to make it easier to use by automatically filling in some of the data.

More info on extended OBD PID:s and other OBD features.

Wishlist (what I would like to get to extend the app): NEW! - Now there is a simulator available too: įor best support you should either have a 2008 (or later) vehicle running the ISO15765 protocol.įor other vehicles an ELM 327 (or compatible) dongle works best. Now I want someone to try it out and come back with comments on how to improve it. There is support for one other dongle, but I doubt that anyone here has access to that. I have made a program that communicates with the Tactrix OpenPort 2.0 dongle and communicates over the CAN Bus.

Tactrix openport 2.0