When I have some time, I'll figure out what the required runtime DLL's are and build a package to suppliment this program and fix the problems once and for all.. Unfortunately you guys will have to muddle through this for a day or two. I also e-mailed the author of the program with a few suggestions and other things.

 

Even better news.. I have been conversing with the author of the software, and he has granted me guardianship of the source code. So I can iron out the glitches in the packaging and the app, and update it to .NET 2.0, and be able to officially continue the development and support of the application on Aktivematrix.

 

That is awesome news. Good work.

 

OBDII software has always worked with $5 rs232 level converters for US Evo8. They are good for the CEL codes and other US OBDII standard codes, but for logging they are waay too slow.There is hundreds of obdii software that works with OBDII for US vehicles. None of these programs will work for JDMs (Asian Imports)... Only EvoScan works on JDM vehicles, like Evo4/5/6/7/8/9 and Australian Lancers.

 

True, its not intended to do logging.. just resetting CEL codes for OBD-II end EOBD.. I can already reset the CEL using the MUT protocol, only wasn't able to get useful snapshot or CEL info on USDM ECU's..

The issue has been finding an app that supported that type of cable, and worked with the Openport cable. Nearly every app out there is using a chipset that is designed to insulate the programmer from directly communicating with the ECU at the line level. For ISO (Asian/German/chrysler cars) its just a matter of communication with a line converter.. BUt other cars use PWM or other communication methods (ALDL) which are not in any way similar to RS232 communications. THese devices do the work, and make writing code easier. But they are functionally different than the Openport cable.

The big problem most of us have (for OBD-II and EOBD) is dealing with the CEL/MIL light, and snapshot data, and the continuous and noncontinuous tests that are required to function and complete sucessfully in order to pass an inspection. It does us no good to have a cable to reflash and log, if we can't also do diagnosis and testing in a similar manner that our inspection stations use.

 

On a sidenote, I ordered a MUT tool so I can get the rest of the protocol info for communicating with the other devices in the ECU, I know Evo4Mad has this information already and is working on doing some of this stuff in Evoscan, so hopefully he has something that can do some of this stuff soon, but the Immobilizer unit is the one I'm interested in..

 

Malibu.

I registered on activematrix a lil while back and still no registration email can you help out ?

Dan

 

I sent out activation E-mails to all of the inactive accounts.. Anyone with an account that didn't get activated, and doesnt get this e-mail, *NEEDS* to check the spam folder, and junk mail folder..

 

Got it, and downloaded etc. Now I am trying to figure out how to get it to connect.

 

This wont work with a serial to USB adapter huh?

 

It works with your tactrix cable. I got it to work. On a side note I wonder how the obd2 scanner is calculating load. It has a load calculation which was reading identical to evoscan at idle and was there without even putting any vehicle information in.

 

I cant get it to connect. Laughing at myself for failing to realize that the tactrix cable is USB. .... lol

But yeah my PC doesnt show my tactrix cable on a comport.

 

Me neither it shows up in device manager as a USB device

 

On my PC when I look at my portsthe Openport 1.3 yada yada yada comes up under the USB stuff . It doesnt give me a "comm port" etc

 

sweet deal jack...