openecu.org

I have a cm5a 1997 gsr with a 4g93t and factory ecu. I just received a tactrix mistsubishi openport, which the notebook can see ok but I get no response from the ecu using any software.
Can anyone tell me whether I am out of luck with this car or is there something else I can try.
Also is there a loopback mode or any other way of testing the openport to know it is ok. Or is there a way to be able to connect to it via a terminal program (hyperterminal) to test it using normal keystrokes.

what are you trying to do exactly if its evoscan you need to join the wires to pins 1 and 4 on the obd socket,if its ecuflash gsr doesnt have the white initialization socket .

pic of white socket and obd socket in here
http://forums.openecu.org/viewtopic.php ... highlight=

Initially I am hoping to use ecuexplorer to look at the fault codes and live data and, eventually to read the factory ecu to get the injector data so I can use it to key into an adaptronic after market ecu I have partially running as a base map.
However, at this stage I would like to know that the openport is ok. I am now assuming my lancer isn't odb2 capable which makes perservering with the openport senseless.
My lancer has the odb connector but I can't see a white socket that I can plug the openport white connector into.

neither did my evo4 have the white connector but it has now,run an extra wire it goes to ecu pin 79 ,i think the ecu pinouts are the same as evo4,i have ran a gsr on a e4 ecu before temporarily, il have a look for a pinout diagram and post it up. thegsr like evo4 are not fully obd II compliant but if you join pins 1 and 4 on the obd socket the ecu will flash the error codes via the eng light ,long flashes are tens and short flashes units eg 2 long and 3 short is code 23 . you dont need the white socket for logging with evoscan ,afaik you cant write to these ecus and theres no def file for gsr/evo4 type ecu. it might be possible to use a later evo ecu like evo7 with a few pin changes then you could map it yourself

Since last post I have tried testing the openport interface with the 2000 ce Lancer ecu by setting up the old wiring loom on a bench top.
The engine light comes on, not surprisingly as there is no engine, so some codes should be readable.
This loom has both the white and the odb connectors but reacts the same. no response using any software.
Has anyone used the mitsubishi openport with any non evo mitsubishi's?

I have '95 lancer gsr, which is evo4 shape, I'm able to log the data from ecu without pin1 and pin4 connection, but I'm not sure if I can read fault codes as my o2 sensor is removed and swapped with wideband and I have aftermarket boostcontroller which required factory solenoid removal which I guess would result a fault code too.