User topics relating to software that logs data from ECUs

Moderator: Freon


Postby MalibuJack » Thu Nov 02, 2006 12:59 pm

Yep.. You heard right..


In the process of writing some code to use our openport cable to read and reset CEL codes, I got some base code to work, and realized how frustrating it was reinventing the wheel. So I did some research and spent a few days trying different scan tool programs.. I found one that works with the cable! AND ITS FREE!

Its a program called OBD Scan Tech, it supports a device called the "Jeff Protocol Converter" which is basically functionally identical to the Tactrix Openport cable without the reflash capabilities..

1) You need to be running the most current version of ECUFlash and Drivers, this is because the most current version creates a serial (com) port for your cable, this is REQUIRED to get this to work.

2) Go into computer management, look under devices, under ports, see what COMx port your tactrix cable is listed under, this is necessary for configuring the software

3) Install your copy of OBD Scan Tech (OBD II GENERIC version!) and under settings, set the interface to JEFF PROTOCOL CONVERTER and set the com port setting to the value you found earlier in the device manager.

Thats it.. When you connect you can now use your Tactrix cable as a regular OBD-II scan tool..

Okay.. Now your asking, What good is this?

1) Read and reset CEL codes

2) Check diagnostic data

3) Check the freeze frame info

4) check the continuous and noncontinuous monitors (so you can see if you'll pass an inspection)

This basically completes your toolkit of useful tools for the Tactrix cable to make it a fully fleged Scan tool!
Posts: 128
Joined: Tue Apr 25, 2006 12:10 pm
Location: Royse City, TX

Postby MalibuJack » Thu Nov 02, 2006 10:11 pm

BTW This should work with both the Mitsubishi and Subaru Openport 1.2 cable, or an earlier cable with the VCP driver installed.

Generic OBD-II (ISO9141-2) is the same for both cars..

In fact, this program and the cable should work on most cars that use the ISO type protocol (though you don't hook up the reflash wire/plug) which means most late chrysler, asian, german, EOBD, etc, cars...

The cable is functionally the same as the Jeff Noxon hobby OBD interface for this purpose..
Posts: 128
Joined: Tue Apr 25, 2006 12:10 pm
Location: Royse City, TX

Postby MalibuJack » Thu Nov 02, 2006 10:13 pm

Oh, and for you linux/OSX guys (That means you Donour ;)) The OpenDiag Linux tool works fine with the openport cable if you make it with the JEFF interface..
Posts: 128
Joined: Tue Apr 25, 2006 12:10 pm
Location: Royse City, TX

Postby New2Scoobs » Fri Nov 03, 2006 5:49 am

Does it let you reset DTC's/ECU too?
Posts: 60
Joined: Fri Nov 04, 2005 5:55 am

Postby MalibuJack » Fri Nov 03, 2006 6:27 am

Yep, I have verified that it will read and reset DTC's, (the Cel light) also view and reset snapshot info..
Posts: 128
Joined: Tue Apr 25, 2006 12:10 pm
Location: Royse City, TX

Postby merchgod » Fri Nov 03, 2006 8:36 am

Nice find.
Posts: 243
Joined: Fri Sep 29, 2006 10:17 am

Postby wrx_aruba » Wed Nov 08, 2006 3:34 pm

very nice indeed...

User avatar
Posts: 34
Joined: Mon Aug 14, 2006 10:21 am

Postby MalibuJack » Wed Nov 08, 2006 6:37 pm

I have another update..

I have assumed the support of the current app on my website, plus he graciously provided me with the sourcecode to update it and enhance it for future versions of the application. This will allow direct support of the tactrix cable and some other fixes (initially) to make it easier to configure.

In the future, the app will run under the .NET 2.0 framework and probably share the same plugin architecture with Mitsulogger 2.0.

The plan is to create the framework for logger 2.0, the base module plugin has the OBD-II capabilities, and the MUT logger will be part of the application (as a plugin) this will allow direct logger support for several native logging protocols for other ECU's that are much faster than OBD-II

This will ultimately make the application alot more flexible and interoperate with more types of ECU's, and OBD type cables.
Posts: 128
Joined: Tue Apr 25, 2006 12:10 pm
Location: Royse City, TX

Postby disque71 » Wed Nov 15, 2006 4:28 pm

tried installing the software and it gave me an error when i clicked on the installer .exe file. anyone have this same issue?
Posts: 16
Joined: Sat May 06, 2006 1:31 pm

Postby Fitz » Fri Nov 24, 2006 3:05 pm

disque71 wrote:tried installing the software and it gave me an error when i clicked on the installer .exe file. anyone have this same issue?

I don't think there is an installer. The link looked like an .rar file to me. .rar is a compression format. I don't believe that WinZip understands it, but WinRAR and StuffIt do.

Posts: 29
Joined: Mon Nov 20, 2006 5:42 pm

I'm actually surprised it works!

Postby Fitz » Fri Nov 24, 2006 11:06 pm

I could be missing something, but it seems like sheer luck that this application works with the OpenPort 1.2/1.3 cables.

On the "Jeff" interface, RTS is connected to the L line, but on the Open Port 1.3 schematic, RTS toggles an A/B switch that determines if RX/TX is connected to K or L (the other line being connected to DTR).

I suspect that the application just uses the K line, setting the baud rate to 10.4K and using break to send the 5 baud ECU address to kick off 9141-2 communication.

Posts: 29
Joined: Mon Nov 20, 2006 5:42 pm

Postby MalibuJack » Sat Nov 25, 2006 2:32 am

Its not "Sheer luck"

the openport cable is functionally similar to the Jeff cable with the exception of the ability to trigger bootstrap for reflashing.

OBD-II only uses that one line, the slow init is done by using a break signal and its the common method for doing this type of communications using this sort of protocol converter. Since its less complicated than swapping the lines, doing an init, and then switching and waiting at the OBD-II baud rate for a reply.

There are very few apps written that use a simple RS232 protocol converter (Opto-isolated) but apps that can do this, should work with the open-port cable using the current drivers that assign a com port to the cable.

The only two I've gotten to work were this program, and the opendiag project app.

There are other cables (VAG-COM) that are functionally similar to these, but their apps don't work because their too application/car specific.
Posts: 128
Joined: Tue Apr 25, 2006 12:10 pm
Location: Royse City, TX

Postby Fitz » Sat Nov 25, 2006 10:07 am

I think that there is some confusion. 'How many lines' in OBD-II (SAE J1978) depends on the physical layer, which varies between make and model. In this case we are talking about ISO 9141-2.

Per the 9141-2 spec, ECU's can implement a one line interface (K) or a two line interface (K and L). K is always the bi-directional line for communication, L is uni-directional and is only used for ECU addressing.

Section 6 is the 9141-2 spec, "Initialization of vehicle prior to serial communication" and Section 4, "Specific configurations" seem clear. For initialization the tester should simultaneously broadcast an address of 33h on the K and L lines at 5 b/s.

Both the "Jeff" interface and the OpenPort 1.2/1.3 appear capable of doing this. There is no "switching" required. You can generate the slow 5 baud byte transmission on the K line using break and the L line by toggling a handshaking line (on OpenPort 1.3 you can use the D2XX interface to actually set the baud rate down to 5 b/s instead of using breaks and host based timeing). However, if the ScanTech tool did this, it would not work with OpenPort 1.3 cables - because the interfaces use different handshaking lines to access the L line. Toggling the RTS line to signal L on a 'Jeff' interface would disrupt communication on the K line on a 1.3 cable (since RTS is used for selecting DTR/RX-TX usage on 1.3 cables). Disrupting the K line would make communication with single wire ECUs fail.

On 1.2 interfaces, toggling RTS would toggle the Subaru specific Vpp line. I don't know if this would effect single wire communiation, but it is not something I would normally want to do adhoc. So, yes, I consider it a stroke of good fortune that the interfaces are similiar in their handling of K and that the Scan Tech app does not attempt to utlize L. Especially with OpenPort 1.3 cables, which have provisions to make L bi-directional (alternate, manufacturer specific, uses of L are allowed under the spec) and uses additional control lines on the USB->Serial chip for control.

But even with a rudimentary convertor there is some luck involved. For example, the simple choice of sourcing or syncing opto isolators in the HW design would determine rather or not the software needs to invert bytes being transmitted via RS-232.

But a little luck does not diminish the efforts of the original programmer. That person simply set out to support Jeff Noxon's design.

Posts: 29
Joined: Mon Nov 20, 2006 5:42 pm

Help - couldn't get it to work. :(

Postby Penphoe » Wed Mar 26, 2008 10:19 pm

I too found this software, however I couldn't get it to work! :(

The version of OBD Scan Tech that I have is 0.77. I was able to get it to connect to my wife's CRV, however it wouldn't/couldn't connect to my LGT!

I have a Tactrix 1.3 cable and I can connect to my car using ECUFlash and ECUExplorer.

Here's part of the connection log. Any help would be much appreciated!

Code: Select all
************************START OF CONNECTING************************"
"MARCH, 26 2008"
"(9:53:04 PM)     SET PORT:  1"
"(9:53:04 PM)     OPEN PORT"
"(9:53:08 PM)     DELAY:  4000 mS"
"(9:53:08 PM)     SET BAUD RATE:  10400"
"(9:53:08 PM)     CLEAR BUFFER"
"(9:53:08 PM)     SENDING:  START BIT"
"(9:53:08 PM)     TIME ELAPSE:  0.2"
"(9:53:08 PM)     SENDING:  BIT 1"
"(9:53:09 PM)     TIME ELAPSE:  0.2"
"(9:53:09 PM)     SENDING:  BIT 2"
"(9:53:09 PM)     TIME ELAPSE:  0.2"
"(9:53:09 PM)     SENDING:  BIT 3"
"(9:53:09 PM)     TIME ELAPSE:  0.2"
"(9:53:09 PM)     SENDING:  BIT 4"
"(9:53:09 PM)     TIME ELAPSE:  0.2"
"(9:53:09 PM)     SENDING:  BIT 5"
"(9:53:09 PM)     TIME ELAPSE:  0.2"
"(9:53:09 PM)     SENDING:  BIT 6"
"(9:53:10 PM)     TIME ELAPSE:  0.2"
"(9:53:10 PM)     SENDING:  BIT 7"
"(9:53:10 PM)     TIME ELAPSE:  0.2"
"(9:53:10 PM)     SENDING:  BIT 8"
"(9:53:10 PM)     TIME ELAPSE:  0.2"
"(9:53:10 PM)     SENDING:  STOP BIT"
"(9:53:10 PM)     TIME ELAPSE:  0.2"
"(9:53:10 PM)     SET MANUAL DELAY:  230"
"(9:53:10 PM)     INCOMING BUFFER:  00"
"(9:53:10 PM)     INCOMING BUFFER:  00"
"(9:53:10 PM)     INCOMING BUFFER:  00"
"(9:53:16 PM)     Trying ISO - 14230 (FAST)"
"(9:53:16 PM)     SETBAUD 200"
"(9:53:16 PM)     CLEAR BUFFER"
"(9:53:16 PM)     INITIALIZING ECU:  F0"
"(9:53:16 PM)     DELAY:  250 mS"
"(9:53:16 PM)     SETBAUD 10400"
"(9:53:16 PM)     START COMMUNICATION REQUEST:  C1 33 F1 81 66"
"(9:53:17 PM)     DELAY:  250 mS"
"(9:53:17 PM)     DATA RECEIVED:  F0C133F18166"
"(9:53:30 PM)     USER CANCELED"
"************************END OF CONNECTING************************"

Posts: 2
Joined: Sun Mar 09, 2008 9:57 pm
Location: Burnaby

Postby LGT-3-6 » Thu Apr 03, 2008 10:15 pm

It's the cable and/or driver I believe, I haven't seen anyone with a OpenPort 1.3 get it to work.
Posts: 50
Joined: Fri Jun 03, 2005 1:12 pm


Return to Data Logging Software

Who is online

Users browsing this forum: No registered users and 1 guest