Since we are in the waiting for a logging software, I figured I would search the net for the numerous OBD-II software apps out there. There are a ton of freeware, shareware, etc, so I thought I would check some out to see if I could get some rudimentary logging of timing, fuel trims, etc, in the meantime.

However, most of these apps are looking for a COM port and Colby designed the 1.3M with drivers that don't create a virutal COM port for the USB cable anymore. He mentioned that he uses a more direct driver (ftd2xx.sys) for the communications.

Does anyone know of any OBD-II software that we can presently use with the 1.3M to get some logging while we wait for a better solution to be developed?


Thanks,
Eric

 

Buy a decent OBDII scan tool or pocket logger

 

Yeah but it doesnt log knock? Thats what im hoping for in the near future is a good datalogging tool that will log knock like the 1G dsms loggers do....

but like my dad always told me "wish in one hand...s*** in the other"

 

Try Innovate or PLX widebands

 

I have already requested that the logging software that is being worked on can monitor knock retard, sometimes called knock correction. DSMLink did this and it looks like the logging software created on OpenECU for the Subarus does this.

But, no aftermarket device can log knock retard unless it can read the stock ECU code. Knock retard is calculated by the stock ECU. That's what I am looking for. Knock voltage is useless to me, which is what most aftermarket gadgets try to log.

The stock ECU already uses it's own algorithms to calculate how much knock retard to apply. That's all I need to know. DSMLink allowed me to set it so that the MIL would illuminate over a certain amount of knock retard, in degrees. That way, if you're in a hard run or pull and the MIL illuminates, you can get out of it, before you cause too much damage. Hopefully, something like that can come out of the developments with ECUFlash.

My original questions above wasn't to monitor knock, though. You can't monitor knock retard via OBD-II. I can use timing to monitor knock retard in a round-about way.


Eric

 

That doesnt help me....they dont log knock, im looking for something that logs knock as l2r99gst has stated. Thats how my friend tunes his 1G and thats how I want to tune the evo....I just wouldnt be comfortable doing a tune and yet not be able to monitor knock. This is why I was thinkng of going the dsmlink route? but that was until ecuflash was released...

Basically as of now this great new tuning software is no good to me until a good datalogging tool is released as well....I will wait and see what happens in the coming months, maybe a breakthrough will happen with logging the evo ecu?..... but eventhough I cant use it, it def. gives a bright future to diy tuners out there

 

I use the TurboXS Tuner Pro, the Tuner Pro has several inputs, one of them is a pretty good knock sensor that you can bolt on near the stock sensor. I have found the triggers and thresholds set up in it mirror pretty closely my ECU's reaction to knock.. Plus it has an audible output so you can listen to the sensor directly.

 

Check my postings on OpenECU regarding this. It is possible to load VCP drivers for the 1.3M, it's just that you will have to switch them back to flash. If you are competent enough to switch drivers back and forth - have at it - I uploaded a zip file with a driver package for this there. In the long run, any logging software I write will use the direct driver, and so it won't be an issue.

 

Thanks, Colby.

Eric

 

"any logging software I write will use the direct driver, and so it won't be an issue"
when do you forsee this happening colby?

 

+1...and which freeware obd2 loggers do you guys recommend?

 

I have lots of ideas, but haven't really started. I can't say when it will be done, but it will definitely NOT be done for a couple of months. It is on my mind though. I have built a lot of data-acq / logging / visualization systems in the past for medical and scientific applications, so I know some good ways to implement these things. I'm looking towards a very thorough solution that will allow integrated logging from multiple disparate devices.

 

Once again - after working with the softwear for a full weekend - thanks man for making such a great flashing application

Your a very talented guy, I can really appreciate what you have created after paying huge sums for inferior products and having to work harder to use them.

 

 

There is code sitting in a project called freediag that should work at this point. I've been playing with it for the last few days, but most of the time went into getting around annoyances with my Mac. However, it's not really an application yet. It's more like a bunch of libraries.

But that's only for OBD-II. The main problem with obd is that it's slow. If we can log using the mitsubishi MUT protocol, we can get data much faster. There is a guy on the openecu forums who's been looking into it, but it's still in the early stages I think.

donour