will do, THX!

 

I'd be interested to see any .csv or whatever files you are dumping from this interface

 

me too!

 

Spoken like a true idiot :-)

 

Its been a while since I've used the software (only really use it for diagnosis & curiosity), but I think I took a few logs of some runs. I'll try dig them up when I get home. However, given the slow logging speed, reading anything more than 3 or 4 parameters at a time doesn't really graph nicely (too few data points per second).

If you want any specific sets of data, let me know what readings (ie boost & rpm, or injector on\off time & rpm etc) and I'll get them this weekend.

 

Very cool project.

I'd be interested to see these channels on a datalog:
RPM, Manifold Pressure, MOP Voltage, and Ignition timing.

To get around the slow logging rate, you could run the car in a high gear (3rd, 4th, 5th ... safety first, though!!!) so that it doesn't accelerate as quickly.
I'd log this myself but have changed the car's setup to the point that the stock ECU won't run happily.

 

BTW, I believe I saw that Greddy has an FD adapter for their "informeter touch" which is the data readout thing for OBD-2 ports. It plugs into the underhood diag port then to the display.

Would be cool, but a pretty pricey setup.

Dale

 

ok guys, those of you that have successfully built a working interface, please upload a video, if possible, of in it operation. I think I may have damaged it somehow. Are any lights supposed to be on when it's plugged in cause when mine is connected, even before I access it on the laptop, which I'm having issues with, both the red and green led's are lit!Or is there a way to test the unit to make sure it's functioning properly even without connnecting it to the vehicle

 

If I remember correctly, both LEDs were lit when it was powered up & not transferring any data. They will flash when there is data being transferred.

What part are you having problems with? Have you been able to connect it to the car & test it? I assume you have the drivers & software installed correctly?

 

If thats the case then, Maybe something was incorrect with the computer i was using, I'll try again. The thing that had me confused mostly, was the leds being on when I connected everything. I didnt get any data from the ecu but maybe it's not the interface.
My overall problem is that, even though she starts and idles perfectly, when I put it in gear to back out of my driveway or move forward, seem like I'm getting fuel-cut. There isn't enough power to move the vehicle. Hoping the interface will show me a bad sensor or whatever is out of spec, if there is anything.

 

this is crazy, i've built components from schematics hundreds of times and I'm pretty sure that i built this correctly but for some reason, with two different computers, i cant seem to get any data transfer. should the leds on the transmit side of the interface ( the computer talking) flash, if the interface is not connected; cause mine is not flashing? its like the program is not seeing the interface. The ecu sees it cause the check engine light is on when it's plugged in

 

do i need a driver for this usb-serial cable?

 

Damn man, want someone to come over and log the data for ya?

 

sure, or just bring a cable that works. I appears that the usb serial cable isnt being seen by the laptop, thats why its not communicating. I've been trying to load the drivers but the computer still wont see it.

 

Incase Windows didn't install the correct drivers, try the ones from the actual manufacturer here:
http://www.ftdichip.com/Drivers/CDM/CDM20600.exe

To make sure the cable is working properly, install the drivers first, then do the following:

Plug the cable in (it doesn't have to be connected to the car or even the circuit board).
Open device manager, and look under the Ports section:


You should have something simlilar to the above picture, but probably with a different COM number. To double check, unplug the cable and it will dissapear from the list.

If it is appearing in the list correctly, then the cable is working.

Now when you run the program, make sure that you select the same COM port that you saw in the device manager. Click 'Open' to connect. I can't remeber if the data starts reading automatically, or if you need to tick/untick the auto-read box. Either way, have a fiddle, it's been a while since I wrote/used it.

 

I will make you a video showing how I get my data..

Teaser: http://www.youtube.com/watch?v=G691Z_nh2KM&fmt=22
(Not everyone will understand ...yes its really the FD3S ECU)

 

you guys ROCK!!!!! This is awesome!!! i really appreciate your help on this. The only thing is that I did find the driver for the cable. That exact same one, but Im pretty sure that its the cable thats screwed up. Im going to get another one and then give it a try. I dont know how, when, or why the cable took a crap but it did. ONCE AGAIN, YOU GUYS ARE THE BEST!!!!! thank You
BTW, The video above, is that the program thats listed as the zip file on page 1 of this thread?

 

No, its the disassembly / output from the processor.
In other words.. thats the firmware on the processor in its running state.

 

comprendo! I thought it looked a bit more resolute than that program i opened up. You could probably get a megasquirt ems to function properly with an FD then huh!?!?!

 

Probably but I dont have much interest in Mega..whatever :-)
I'm very interested in rewriting the firmware to do other things better suited for racing or something along those lines.

 

how about a control system for a hydrogen powered rotary?

 

I dont follow ...?

We dont have any hydro fueling stations in these parts. Maybe closer to the city?

 

dont need any when you have an on demand system installed on the vehicle. made from water as you drive!!!

 

I can't believe I'm even typing this but dude.. it was a joke!
A simple ECU change doesn't cut it.

 

Just trying to pick the mind of someone that obviously knows how to do something I dont, nevermind, may I ask if theres something in the firmware or that would cause the "CEL" to freeze on with the O2 sensor unplugged instead of storing or blinking a code?