Obd-ii Scan Tool Software That Works!
. It seems that my hand held OBD II scanner walked away on me so Id like to get this working
Nov 10, 2006, 06:28 AM
#48
yeah I can understand the confusion.. I do actually use a USB-Serial converter and log the ECU+ at the same time I log with mitsulogger.. Since both use the same timestamps for logging, I can very easily match up my runs and the times if I start both at almost the same time.
Jan 13, 2007, 09:40 AM
#50
Those files should be packaged with the file you downloaded, not every version of windows has those files so I put them all together..
HOWEVER, if you search google, you an find a place to download the runtime files needed. MSCOMM32.OCX is a vb component for the serial ports.
HOWEVER, if you search google, you an find a place to download the runtime files needed. MSCOMM32.OCX is a vb component for the serial ports.
Jan 13, 2007, 09:42 AM
#52
yeah it makes the tactrix cable really flexible.. Once I have some free time I'm going to rewrite it using VB.NET and hopefully make the setup a bit easier.. Its just such a fully featured application that although the original author supplied me with the source code, it will take a complete rewrite to get it all working in VB.NET
Jan 13, 2007, 10:47 AM
#53
Jack and the guys, you're great!
After a lot of stubborness, I was able to launch and run the software with my Tactrix. I had to download MSCOMM32.OCX and then it asked of TABCTL32.OCX which i downloaded as well..
I then fiddled a bit to set the Tactrix to COM1.. First it refused then it succeeded after changing the USB to another socket.. The software worked immediately.
All loggings are working but the software is giving me 'no codes detected' ALTHOUGH the Cel Light on the screen was ON (light green) and i was able to clear the CEL in my car from the software itself!
So do you guys know why it didnt show me any DTC code number? It's only that little glitch remaining! COuld it be our ECU's here are not so much compatible?
Please i appreciate your feedback!
Wael
After a lot of stubborness, I was able to launch and run the software with my Tactrix. I had to download MSCOMM32.OCX and then it asked of TABCTL32.OCX which i downloaded as well..
I then fiddled a bit to set the Tactrix to COM1.. First it refused then it succeeded after changing the USB to another socket.. The software worked immediately.
All loggings are working but the software is giving me 'no codes detected' ALTHOUGH the Cel Light on the screen was ON (light green) and i was able to clear the CEL in my car from the software itself!
So do you guys know why it didnt show me any DTC code number? It's only that little glitch remaining! COuld it be our ECU's here are not so much compatible?
Please i appreciate your feedback!
Wael
Jan 20, 2007, 12:56 AM
#55
Evolving Member
iTrader: (2)
Join Date: Jul 2006
Location: Iceland
Posts: 165
Likes: 0
Received 0 Likes
on
0 Posts
For everyone that get runtime error 52.
I got it untill I downloaded the lates repack of Scantech and EcuFlash 1.29a
Then I started on changing com port setup so that I would have com 1 free.
I am running Win XP pro so I opened up
Start / All Programs / Accessories / System Tools / System Information
There I expand Components / Ports and click Serial.
There you see information about all your serial ports or atleast the names that you need to search in Device Manager.
Next go into Device Manager .. right click My computer on your desktop and click properties .. go to Hardware / Device Manager
For me I needed to change parameters on my ports which were under Modems and Ports
Just fined what you need to change and right click and go to properties
There you should find something like Port Settings / Advanced and hopefully like for me .. you should see Com port numer there ..
this way you should be able to free up Com1
This is atleast what fixed it for me
regards
Gudmundur
I got it untill I downloaded the lates repack of Scantech and EcuFlash 1.29a
Then I started on changing com port setup so that I would have com 1 free.
I am running Win XP pro so I opened up
Start / All Programs / Accessories / System Tools / System Information
There I expand Components / Ports and click Serial.
There you see information about all your serial ports or atleast the names that you need to search in Device Manager.
Next go into Device Manager .. right click My computer on your desktop and click properties .. go to Hardware / Device Manager
For me I needed to change parameters on my ports which were under Modems and Ports
Just fined what you need to change and right click and go to properties
There you should find something like Port Settings / Advanced and hopefully like for me .. you should see Com port numer there ..
this way you should be able to free up Com1
This is atleast what fixed it for me
regards
Gudmundur
Jan 20, 2007, 06:40 AM
#56
I forgot to mention I posted a repack on my website awhile back that included most if not all of the missing OCX and DLL files you guys had complained about with the version on the original website. I assumed support for the software so he hasn't mirrored any recent changes.
I have to admit, this software can be a little hard to get running initially, it supports several different interfaces and can take some trial and error. But its the only fully functional OBD-II diagnostic software that works with the Tactrix cable, and that makes it worthwhile to spend the time to get working until I can rewrite the software (actually I'll be starting from scratch but using his code for reference for OBD-II stuff)
The biggest bear to deal with is its current limitation to com1-com4, as it seems like the tactrix cable always turns up as com5-com18 or something stupid. I do have a version that was updated by the original author just before he sent me the code that supports higher com ports so you don't have to remap yours. I didn't really see alot of value in putting it in the repack, but if enough of you guys are having trouble, I'll put it up.
I have to admit, this software can be a little hard to get running initially, it supports several different interfaces and can take some trial and error. But its the only fully functional OBD-II diagnostic software that works with the Tactrix cable, and that makes it worthwhile to spend the time to get working until I can rewrite the software (actually I'll be starting from scratch but using his code for reference for OBD-II stuff)
The biggest bear to deal with is its current limitation to com1-com4, as it seems like the tactrix cable always turns up as com5-com18 or something stupid. I do have a version that was updated by the original author just before he sent me the code that supports higher com ports so you don't have to remap yours. I didn't really see alot of value in putting it in the repack, but if enough of you guys are having trouble, I'll put it up.
May 22, 2008, 07:03 PM
#59
Evolved Member
iTrader: (16)
Join Date: Apr 2006
Location: Twin Cities, MN
Posts: 888
Likes: 0
Received 0 Likes
on
0 Posts
Wow, way to bring back an old thread! Now I complete my computer logging/reflashing/diagnosis software! I suppose some people still don't know about this software.
