Sorry about the repost, but I think it might get some more attention here.

Plans: http://mmcdlogger.sourceforge.net/ecu-rs232.jpg
Software:http://mmcdlogger.sourceforge.net/

I have come accross some plans for a pre OBD2 mitsubishi diagnostics cable, just wondering if anyone has tried it before? It seems that you hook it upto a palm pilot and run the software, I was thinking i could run a palm emulator on a laptop.

Sorry to be a nublet here, but would this be a cable that plugs into that...well plug above the fusebox that reads all the engine info?

You think your a noob, I thought emulater was a flightless aussie bird that didnt arrive on time. Think about it .............. ok its late. lol

Tell us more about this cable????:)

']Sorry to be a nublet here, but would this be a cable that plugs into that...well plug above the fusebox that reads all the engine info?

It is that cable, plugs in there and to the Palm handheld to display your engine info on the Palm's screen.

Only issue I can see is either the Palm emulator on the desktop or notebook machine does not include the necessary connectivity of a physical Palm handheld. The cable looks like a standard serial cable. If both of those check out then you may just be able to read it all out on the notebook.

Interesting idea for sure.

']Sorry to be a nublet here, but would this be a cable that plugs into that...well plug above the fusebox that reads all the engine info?

Yes, aparently the ECU outputs a standard serial connection so it should be as simple as soldering on 2-3 wires.

It is possible to read the data on the laptop it self, but I don't have that software. The emulator should be able to use the computers serial port for communication.

if it works it should be able to tell us a lot about the engine (including fault codes), see the sourceforge web page for more information.

EDIT: parts were dispatched today, should have them in a week or two + a day or so to build the cable and test it.

Huh, a reg and a 233, who'da thunk it...
Main issue I'm seeing is most laptops don't have serial ports anymore, should be possible to convert to USB, but I don't know much about that yet.

Wonder what the difference is between a 233 and a 232, if any...
Also, if going to USB, whether the 233 is an unnecessary step...
</thinking_out_loud>

232 doesn't have capacitors in the chip, a 233 does....

Cable is made, it's pretty messy at the moment, can't wait to get my hands on a laptop to test it (I would use my car pc, but it's currently getting an upgrade)

After 7 years!
What happened to this exercise Mrmacomouto??

After 7 years!
What happened to this exercise Mrmacomouto??

Not sure what happened here but check out http://www.evoscan.com/

Evoscan and the appropriate data logger cable (serial to usb cable really - with the right plug on the cars end!) would be nice.
But was just interested in the DIY approach to marry some sort of readout (PC, tablet, dedicated LCD display) with a data cable.
The thread by ac1167 is interesting http://www.aussiemagna.com/forums/showthread.php?t=104871
I already have a FTDI RS232 breadboard (for reflashing my NASBOX to OpenWRT!) and might just see what responses I can get with a terminal program like Putty .

I have a simple homebrew serial to Mitsubishi interface box that I've been using in that other thread while I've been interrogating the various ECUs in my TS. It has a 9-pin serial connector on one end and a pair of screw down terminals at the other, that you can hook up a pair of aligator clips to the OBD plug under the dash. In the box is the necessary hardware to do the RS232 <-> Mitsubishi logic conversion. You will need a laptop that has a 9-pin serial interface to use it, although you could probably get away with a USB-serial adaptor. Any serial comms software that allows you to send hex codes can be used (Realterm, Putty, TerraTerm, Br@y's Terminal etc) provided you can set the baud rate to a custom value. Handy thing about it is that it's powered from the laptop serial port, so you don't need to have a separate plug pack or extra wiring off the car electrics to make it work.

I'll post details in the next few days if you're interested?

Anyone else out there over 50 and thinking about the "good" old days of ignition points and carbies....?
And AM radio.

@ ac1176
I am definitely interested in looking at the diagnostics parameters that are presented at the OBD1 plug.
Have a nice looking Verada KS, but considering its book value I tend towards DIY servicing.

By Mitsu logic conversion are you talking about mismatched voltage levels for the I/O data pins?

Came across these bits of free software for the PC viz, "Mitsulogger" (early version of evoscan?) and TunerPro.
I'll have to search AMC to see if anyone has played with these.

@ KS95Dave
Over 50 too, but no need to dream having a Sigma GJ with the old time mechanics.

Anyone else out there over 50 and thinking about the "good" old days of ignition points and carbies....?
And AM radio.

The bad old days, when a 80 KW engine got 18 MPG, if you drove sedately, and at times the points would weld shut and you would be swapping them out on the side of the road, and guessing at the gap and ignition timing because the feeler gauges and timing light were at home? You mean those days?

I bet I'm older than you. My first car radio had valves in it!

By Mitsu logic conversion are you talking about mismatched voltage levels for the I/O data pins?

Came across these bits of free software for the PC viz, "Mitsulogger" (early version of evoscan?) and TunerPro. I'll have to search AMC to see if anyone has played with these.

Yes, Mitsubishi comms requires 0-12V, whereas RS232 is -7.5V to +7.5V. Baud rate is non-standard too, not something you're likely to come across in most terminal programs.

Circuit is basically the one shown here (http://mmcdlogger.sourceforge.net/) built up on some stripboard, but with its own on-board power supply derived from the RS232 laptop port.

No idea if the various abandonware Mitsubishi logging programs will work with the above interface, but can't hurt to try. None of them support the other ECUs in the car, only the engine. Most of them are written for people wanting to tweak their Lancer Evo's. From my own experiments some of the request codes used did not align with the Magna V6 ECU readouts, or the scaling factors were incorrect. Don't have access to a 4cyl car to try it out on another type of ECU.

@ ac1176
Thanks.
So it looks like I need a voltage level shifter on the output of the FT232R chip (USB to TTL serial).
The MAX233 or maybe a simple Transistor/FET cct.

Did notice the "abandon ware" was mostly all about the Evo's, hence one of the reasons for my interest in your other thread.

@ MadMax - I bet we are very happy to loose that kind of bet!

@MadMax
18MPG perhaps, but petrol was 15 cents/litre in 1977, I could guess a points gap well enough to get home, and timing was often done by advancing it up until it pinged, stop, get out with your 7/16" spanner, retard it a little, repeat, repeat, repeat until right.
Unless you have a crank angle sensor or idle stepper motor or oxygen sensor or ____ (insert applicable obscure electronic device) in your toolbox these days you are coming home on a towtruck.

My first car (a Cooper S on 10:1 compression) would run-on after you turned it off (and then stop run-on backwards!) so you had to ease the clutch out in-gear to stall it as you turned the key to off.
Tell the kids of today and they wooon't believe you....
KSD
PS these days your radio would have 16 valves!