Obd-ii Scan Tool Software That Works!
Nov 2, 2006, 01:02 PM
#1
Obd-ii Scan Tool Software That Works!
Yep.. You heard right..
http://www.aktivematrix.com/forum/viewtopic.php?p=957
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!
http://www.aktivematrix.com/forum/viewtopic.php?p=957
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!
Nov 2, 2006, 01:46 PM
#6
Yeah, this was actually the result of a few months of research until I gave up and decided to write my own.. In the process of doing so, I came across the Opendiag project for Linux and Jeff Noxon's simple ISO to Serial adapter which looked strikingly similar (functionally) to the Openport cable minus the RS232-USB chip.. But if the com port driver is installed, any software that works with the JEFF interface will work with the Openport interface..
(This goes vice-versa for Evoscan, which works with the JEFF interface and anything similar if its hooked up to com1 or com2)
I don't think people really appreciate the amount of effort that goes into making a scantool, and how exasperated I was trying to find something that worked. I normally write code as a last resort, and was about a day into writing code that actually worked to read to see if the CEL light was on, and to clear the codes.. Thats as far as I got.. So I was looking for code that functioned similarly that I could use as a basis to save myself time and came across it.
Then I searched all over for software that was compatible with the JEFF interface (FWIW there isn't much), considering how simple the interface is, and how much effort the programming needs to get compared to ELM or mOByDic tools which are very simple for the programmer to utilize, but less flexible..
I found VAG-COM which the early hardware was almost identical, but I never could get it to work with a standard generic OBD-II protocol, it worked with the cable, but couldn't interface with the ECU correctly.
Finally I stumbled across this tool... Not only is it fully functional, but it does everything the more expensive scan tool programs can do (that I consider useful) It doesnt have a desktop dyno or anything like that, but at the sample rates that OBD-II runs at, its not really useful for that anyway......
This really does complete my "toolbox".. I can now reflash the ECU, Log it at high speed (Mitsulogger), log and adjust settings and my wideband (ECU+)...
The ECU+ also reads and resets OBD-II port.. But I frequently forget to switch the cable back and forth and this ended up being easier to on OTHER cars that don't have that luxury.
(This goes vice-versa for Evoscan, which works with the JEFF interface and anything similar if its hooked up to com1 or com2)
I don't think people really appreciate the amount of effort that goes into making a scantool, and how exasperated I was trying to find something that worked. I normally write code as a last resort, and was about a day into writing code that actually worked to read to see if the CEL light was on, and to clear the codes.. Thats as far as I got.. So I was looking for code that functioned similarly that I could use as a basis to save myself time and came across it.
Then I searched all over for software that was compatible with the JEFF interface (FWIW there isn't much), considering how simple the interface is, and how much effort the programming needs to get compared to ELM or mOByDic tools which are very simple for the programmer to utilize, but less flexible..
I found VAG-COM which the early hardware was almost identical, but I never could get it to work with a standard generic OBD-II protocol, it worked with the cable, but couldn't interface with the ECU correctly.
Finally I stumbled across this tool... Not only is it fully functional, but it does everything the more expensive scan tool programs can do (that I consider useful) It doesnt have a desktop dyno or anything like that, but at the sample rates that OBD-II runs at, its not really useful for that anyway......
This really does complete my "toolbox".. I can now reflash the ECU, Log it at high speed (Mitsulogger), log and adjust settings and my wideband (ECU+)...
The ECU+ also reads and resets OBD-II port.. But I frequently forget to switch the cable back and forth and this ended up being easier to on OTHER cars that don't have that luxury.
Nov 2, 2006, 02:42 PM
#7
Evolved Member
iTrader: (19)
Join Date: Oct 2004
Location: CT
Posts: 885
Likes: 0
Received 0 Likes
on
0 Posts
My how times have changed.
I can remember not too long ago when reverse engineering the MUT-II protocol was just an idea and the ROM was only able to be seen by a few--those willing to spend big bucks on the software.
These are good times gentlemen.
Props to those who have worked hard to make this Renaissance happen!
I can remember not too long ago when reverse engineering the MUT-II protocol was just an idea and the ROM was only able to be seen by a few--those willing to spend big bucks on the software.
These are good times gentlemen.
Props to those who have worked hard to make this Renaissance happen!
Trending Topics
Nov 3, 2006, 04:32 AM
#10
Well at first I had a run-time error that wouldn't let me open the program. Got that fixed. Now when I try to connect to the ECU I have another error that pops up. I believe it's a Error "32, or 33" I did have the white connector plugged in so Im not sure if thats the problem or not. Also I had to change my COM port from 6 to 2 (only one avaliable).
Here are my settings:
Port/Device:
Jeff protocol Converter
Auto
COM 2
10 ms
Sequence:
Jeff converter (ALL)
BR3 (ALL)
Connect with 2nd frame (Unchecked)
Am I doing something wrong here? I didnt go back out and try different settings since Im still stuck at work for a while longer (damn late people)
Here are my settings:
Port/Device:
Jeff protocol Converter
Auto
COM 2
10 ms
Sequence:
Jeff converter (ALL)
BR3 (ALL)
Connect with 2nd frame (Unchecked)
Am I doing something wrong here? I didnt go back out and try different settings since Im still stuck at work for a while longer (damn late people)
Nov 3, 2006, 04:42 AM
#11
I disabled all of the non-iso settings in the tabs.. and only enabled the ISO (Slow init) settings and other interface specific sequences..
Also, I left the timeout settings at the default, didn't raise it or lower it since OBD is a bit more picky and has more framing errors..
Also, make sure your COM2 isn't shared by something else that you didn't notice (easy way to check is to run EVOSCAN on com2 instead of FTDI and see if it works normally, if it doesnt then the problem is the port your trying to use or the driver)
Since I know it works for me, and a half dozen others, the issue your having is likely something in your settings. The fact that your getting runtime errors means your missing some of the runtime files required by the software. Another member fixed that by installing the demo nissan scanner software, then the Generic one.. Personally I think thats not the right way, but the author obviously is putting a lower priority on the generic (and free) version of his scanner. I do get a runtime error when I try to load or save a log file, but that must be the only "old style" dll I'm missing.
Also, I left the timeout settings at the default, didn't raise it or lower it since OBD is a bit more picky and has more framing errors..
Also, make sure your COM2 isn't shared by something else that you didn't notice (easy way to check is to run EVOSCAN on com2 instead of FTDI and see if it works normally, if it doesnt then the problem is the port your trying to use or the driver)
Since I know it works for me, and a half dozen others, the issue your having is likely something in your settings. The fact that your getting runtime errors means your missing some of the runtime files required by the software. Another member fixed that by installing the demo nissan scanner software, then the Generic one.. Personally I think thats not the right way, but the author obviously is putting a lower priority on the generic (and free) version of his scanner. I do get a runtime error when I try to load or save a log file, but that must be the only "old style" dll I'm missing.
Nov 3, 2006, 05:02 AM
#12
Originally Posted by MalibuJack
I disabled all of the non-iso settings in the tabs.. and only enabled the ISO (Slow init) settings and other interface specific sequences..
Also, I left the timeout settings at the default, didn't raise it or lower it since OBD is a bit more picky and has more framing errors..
Also, make sure your COM2 isn't shared by something else that you didn't notice (easy way to check is to run EVOSCAN on com2 instead of FTDI and see if it works normally, if it doesnt then the problem is the port your trying to use or the driver)
Since I know it works for me, and a half dozen others, the issue your having is likely something in your settings. The fact that your getting runtime errors means your missing some of the runtime files required by the software. Another member fixed that by installing the demo nissan scanner software, then the Generic one.. Personally I think thats not the right way, but the author obviously is putting a lower priority on the generic (and free) version of his scanner. I do get a runtime error when I try to load or save a log file, but that must be the only "old style" dll I'm missing.
Also, I left the timeout settings at the default, didn't raise it or lower it since OBD is a bit more picky and has more framing errors..
Also, make sure your COM2 isn't shared by something else that you didn't notice (easy way to check is to run EVOSCAN on com2 instead of FTDI and see if it works normally, if it doesnt then the problem is the port your trying to use or the driver)
Since I know it works for me, and a half dozen others, the issue your having is likely something in your settings. The fact that your getting runtime errors means your missing some of the runtime files required by the software. Another member fixed that by installing the demo nissan scanner software, then the Generic one.. Personally I think thats not the right way, but the author obviously is putting a lower priority on the generic (and free) version of his scanner. I do get a runtime error when I try to load or save a log file, but that must be the only "old style" dll I'm missing.
At first I did have the runtime error on initial set-up so I did the Nissan DL also and then the generic version, and it worked. I think it was an OCX file I was missing.
I have it on my work Laptop and got it to work last night pretty quickly. Hit me up on AIM and we'll compare settings.
Nov 3, 2006, 10:08 AM
#15
Ok people.
For those of you getting the Runtime 52 error I think I figured out a solution. If you ended up DL the nissan version like I did, get rid of it. Go into your Add/Remove programs and uninstall everything. Keep your .OSX files just in case. Now delete the generic scan tech files and re-DL.
It should work now. At least it did for me.
For those of you getting the Runtime 52 error I think I figured out a solution. If you ended up DL the nissan version like I did, get rid of it. Go into your Add/Remove programs and uninstall everything. Keep your .OSX files just in case. Now delete the generic scan tech files and re-DL.
It should work now. At least it did for me.