Jump to content
LegacyGT.com

Software for Tactrix OpenPort 2.0


ehsnils

Recommended Posts

I have made a program that communicates with the Tactrix OpenPort 2.0 dongle and communicates over the CAN Bus. There is support for one other dongle, but I doubt that anyone here has access to that.

 

Now I want someone to try it out and come back with comments on how to improve it.

 

Latest version here: http://www.bedug.com/pics/Subaru/CanMiner_1.5.612.zip

 

NEW! - Now there is a simulator available too: http://www.bedug.com/pics/Subaru/ObdSimulator_1.0.612.zip

 

For best support you should either have a 2008 (or later) vehicle running the ISO15765 protocol.

For other vehicles an ELM 327 (or compatible) dongle works best.

 

Wishlist (what I would like to get to extend the app):

 

  • More info on extended OBD PID:s and other OBD features.
  • Data for other vehicles than Subaru.

 

A few screendumps:

http://www.bedug.com/pics/Subaru/CanMiner/Screenshot1.png

 

http://www.bedug.com/pics/Subaru/CanMiner/Mass%20Air%20Flow.png

 

http://www.bedug.com/pics/Subaru/CanMiner/Manifold%20Absolute%20Pressure.png

 

Gauges panel:

http://www.bedug.com/pics/Subaru/CanMiner/Gauges1.png

 

Large size gauge panel:

http://www.bedug.com/pics/Subaru/CanMiner/Gauges2.png

453747.png
Link to comment
Share on other sites

  • Replies 65
  • Created
  • Last Reply

I have now updated the application. Same link as in first post.

 

What's new is that I have made improvements to make it easier to use by automatically filling in some of the data.

 

You can run the program without connecting it to your car as long as you have a Tactrix dongle.

 

To get started:

 

  • Unzip the downloaded ZIP file into an empty directory.
  • Run the EXE-file.
  • Connect your Tactrix OpenPort 2.0 dongle.
  • On the first page select Vehicle "Subaru" and Interface "Tactrix Openport Driver" and click on "Open".
  • Default is protocol ISO15765, 500kbps and no flags. This works with my car at least! :)
  • Click on the Connect button.
  • Click on the OBD-II button. This will open a new window with a lot of tabs.
  • The "Config" and "Filter" tabs shall already be filled in with data that works.
  • Start with the "Vehicle Data" tab. It will display a lot of disabled checkboxes. 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. The answer shall then enable the checkboxes for the supported PIDs.
  • Underlined PIDs defines dynamic data that varies over time like coolant temperature, engine rpm etc. 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.
  • Snapshot data can be taken by checking the desired checkboxes and clicking on the "Get Data" button.
  • 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.
  • The "DTC Handling" tab allows you to list the DTC:s that are active. (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 "Vehicle Information" tab shall provide you with at least the VIN# when you click the "Get Data" button.
  • The "Test" tab is an ECU simulator that injects messages to test the application.

This shall work with at least any Subie with CAN bus in the OBD connector.

 

 

For further information about what I'm babbling about I suggest that you also look at: http://en.wikipedia.org/wiki/OBD-II_PIDs and http://subdiesel.wordpress.com/ (It seems to me that the persons running that site has stopped working, but there is at least some good info there.)

 

 

 

Anyway - if you have some knowledge that you want to share please post it here.

453747.png
Link to comment
Share on other sites

and, it is time to buy a tactrix cable to help with development, and should buy you a beer for all your hard work

 

this feels to my cretin mind like we are getting closer to correcting the fuel economy display when larger injectors are installed

 

maybe more than a beer is in order

Link to comment
Share on other sites

Now I have updated the application, and any information you can find is still welcome!

 

A lot of effort has been put into the configuration part.

 

New link: http://www.bedug.com/pics/Subaru/CanMiner_1.0.83.zip

 

It's now installing as a "normal" Windows application.

 

What's still missing:

 

  • Documentation - no user manual is written yet.
  • SSM Support (it will come)
  • Not tested on anything else than a CAN bus vehicle yet.

You don't need any hardware to access the config pages so anyone interested can take a look there and come back with suggestions.

453747.png
Link to comment
Share on other sites

During my digs around the internet I encountered this: http://www.hptuners.com/forum/showthread.php?p=302975#post302975

 

That site seems to contain some goodies in general for tuning too.

 

B.t.w. I also would like to see a list of devices supporting J2534, and possibly get the J2534 implementation DLL for each of them so I can add them to the supported devices of the application.

453747.png
Link to comment
Share on other sites

Now I have made another update to the application:

 

http://www.bedug.com/pics/Subaru/CanMiner_1.0.112.zip

 

Changes:

 

  • The CAN logger is able to create ASC files that can be loaded into Vector Canalyzer - useful for those that are has access to Canalyzer. It's not fully tested, but as they say "what can possibly go wrong?" and it's in this case the file format that may have a glitch or two.
  • Support for Extended OBD PID:s. On newer cars there are a few of those too.
  • Support for reading SSM data through the 0xA8 mode.
  • Support for SSM init and the responding capability bytes.
    If anyone has a more detailed list of the capability byte mapping than I have I would be happy to receive that info.
  • The Filter tab has received a bug fix or two.
  • Documentation is provided!
  • The plot routine has been improved, but it needs more work. At least now the X-axis is presented at zero on the Y-axis so the temperature graphs makes sense.
  • The plot routine is now also supporting three zones red, yellow and blue to allow the presentation to show when a value leaves the comfort zone. However this needs to be configured to work, only the engine coolant is configured with guesstimated values.
  • Data format can be entered for each unit on an item (PID), formats are whatever C# accepts for numeric values and are used in the output in the snapshot view.
  • Support for most of the ECU error responses and causes. Usually a pop-up is displayed when such a response is received.

 

 

Limitations:

 

  • If you check too many of the SSM items the API (or ECU) won't accept the request since the request will be too large.

453747.png
Link to comment
Share on other sites

Maybe just update the first post with the revision history & latest rev... I almost downloaded from there.

 

I'm typing from my tuning laptop, so I'll download & play with it at my next opportunity & give you feedback. I'm no beta tester, but I know what I like.

Tits mcgee
Link to comment
Share on other sites

No, they are using KWP2000.

 

 

  • ISO9141 for all up to 2002.
  • 2003,2004 has either ISO9141 or KWP2000
  • 2005 has KWP2000
  • CAN from 2006 and on.

But ISO9141 and KWP2000 are very similar so it's not as bad as it looks.

 

 

I'm still scratching my head over ISO9141/KWP2000 though... This 5 baud init sequence seems to fail for some reason.

453747.png
Link to comment
Share on other sites

See below:

To get started:

  • Unzip the downloaded ZIP file into an empty directory.
  • Run the EXE-file. <~~ When I ran the program file, it popped up with a dialog box that said it couldn't load a preferences file, and then the program continued to load. I didn't see these error/notification the 2nd time I opened the program.
  • Connect your Tactrix OpenPort 2.0 dongle. OK
  • On the first page select Vehicle "Subaru" and Interface "Tactrix Openport Driver" and click on "Open". OK
  • Default is protocol ISO15765, 500kbps and no flags. This works with my car at least! :)OK
  • Click on the Connect button. OK
  • Click on the OBD-II button. This will open a new window with a lot of tabs. OK
  • The "Config" and "Filter" tabs shall already be filled in with data that works. OK
  • Start with the "Vehicle Data" tab. It will display a lot of disabled checkboxes. 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. The answer shall then enable the checkboxes for the supported PIDs. This didn't work for me. Clicking "Get PIDs" resulted in a short delay while (I presume) the message was sent, but nothing came back in the form of checked boxes.

Tits mcgee
Link to comment
Share on other sites

OK, I just wanted to check. Anyway - the first warning was expected, it's just the user preference to remember which vehicle that you selected last time and some other minor data.

 

There's a log in the first window under a separate tab, that may provide some clues too. The default message flags shall have the ISO15765_FRAME_PAD checked, and the address under the Config tab shall be either 0x07df or 0x07e0.

 

So far I have at least realized that the OBD-II standard is a flock of protocols that are tricky to get to work.

453747.png
Link to comment
Share on other sites

For data, check out RomRaider's ecu_defs.xml, it covers 4th Gen LGTs.

 

 

For code, have you see this? http://ssm.codeplex.com/

 

I have seen the link and looked at that code. May still be something useful there.

 

And from what I understand the RomRaider data is more for information within the ROM, not so much what can be inspected on the fly in the car.

 

What I would like to see is a list of extended PID:s (Mode 0x22) that are supported by Subaru.

 

Thanks anyway. Back to scratching my head over odd things in protocols! :p

453747.png
Link to comment
Share on other sites

No, they are using KWP2000.

 

 

  • ISO9141 for all up to 2002.
  • 2003,2004 has either ISO9141 or KWP2000
  • 2005 has KWP2000
  • CAN from 2006 and on.

But ISO9141 and KWP2000 are very similar so it's not as bad as it looks.

 

 

I'm still scratching my head over ISO9141/KWP2000 though... This 5 baud init sequence seems to fail for some reason.

 

So I'm guessing that this software won't be able to grab the "freeze frame" data on a USDM2005 Outback XT.

 

EDIT: Also, can this work with an Access Port serial cable or does it need to be a Tactrix cable? I'd really like to be able to get my own freeze frame data because the last time the dealer did it they flashed my ECU and rendered my AP a $600 lump of coal.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.




×
×
  • Create New...

Important Information

Terms of Use