Hi I thought I would buy Evoscan to help me set up a HHO unit on my car ?

I have Evoscan Openport 1.3 cable and version 2.5 software but having some difficulties getting it working

I have an NJ 1994 3.0Ltr V6 Petrol Pajero M/T

When I try EFI it does nothing, if I connect to the OBDII it connects and disconnects.

Evoscan settings are standard at 15625 baud rate and set to OBDII
Cable is set to Com1
I select only Engine RPM to log
It keeps connecting - Green and then almost immediately it disconnects with 'No response from ECU'

It then repeats over and over again.... Link Engaged.. Link Disengaged.

Info: Initialize Vehicle ECU...
Info: Initializing At 5 baud...
Info: Initialization Complete...
Info: Waiting for INIT Response...
Info: Connection successful...
Error: No Response from Vehicle ECU
Info: Datalogger Ended.

mitsulogger doest work either

On the Diagnostic Connector...

Pin 16 is 12v

Pins 4 and 5 are earth

Pin 1 is 4.4v but it is also 4.4v at the ECU pin 2 ?

Pin 7 was not working but I have now connected it to ECU Pin 1 and it flashes the codes now as it should

Connecting 1 & 4 does not cause dash lights to flash however if the ECU has an error Engine light stays on longer and Brake and Oil lamp stay illuminated. I can also read the error codes from pin 7

Not sure whether I have a compatibility issue with my car or whether there is something wrong with the diagnostic connector ? Can anyone help ?

schematic is

 

not sure if its true er not but a bud said that he had the 1.3 cable and updated his software when his computer crashed to the 2.5 and now his 1.3 cable wont work. he said he had to get a new cable because the 1.3 cable and 2.5 software wasn't compatible. like i said im not sure if its true er not but thats what he told me

 

I think this is your problem. EvoScan, Mitsulogger do not suport real(virtual) COM ports for ECU logging. Try MutMonitor.

 

Well tried Mutmonitor 1.9 but still no joy

- I also updated to the Tactrix cable and serial port drivers by installing the latest ECU flash

- Ecu flash recommended XP Service Pack 3 because of usb issues.. So I did this as well

- Downloaded Evoscan 2.6b11 and installed over the top of v2.5 as recommended but still no connection established. Evoscan did not want to know about the COM ports so that wasnt an issue.

At this point I will probably give up unless someone else can bless me with some divine wizdom ???

 

for a 1994 vehicle you need to ensure "disable flashing lights" is unticked in EvoScan. and you need to ensure the diagnostic lights are flashing. and you need to be sure its an openport 1.3U cable purchased from EvoScan (http://www.limitless.co.nz/cables)
Otherwise its quite likely you have faulty wiring in your vehicle somewhere, it wouldn't be the first Pajero I've see where the factory forgot to wire it all the way to the vehicle ecu.

 

Thanks Hamish.. Yes I did buy the cable from you. I really do want to get this working.. I even pulled apart half my dash to track down the wiring. There was only one wire plugged into the wrong plug and I fixed that.

Please check out the schematic on my first post.. Aren't there any checks I can do at the ecu end to see if there may be something wrong there ?

 

Guys seeing that I can't get my cable to work I was wondering if you could help with my narrowband O2 sensor.

I am trying to run HHO in my car and have installed an efie unit (as per d17.pdf)

No mater what voltage boost I add the car does not behave any differently. At high boost the reading should be rich which is supposed to make the ecu go lean therefore causing the car to cough and splutter.

My O2 sensor seems to react fine between 0.1 to 0.9 volts and runs up to 0.9v after I rev the motor. I noticed though that the heater resistance is not to spec.

From the schematic I noticed the heater wire continues all the way around to the injectors and so on. I will try to post a copy tonight.


Is it possible that if the heater circuit is not working properly that the ECU will just ignore the o2 sensor alltogether ?

 

Thanks for the offer to help Hamish.. I will add you to my MSN Messenger soon.

I am busy working on modying my MAF signal using a Basic Stamp microprocessor. I have decided to go open loop with the O2 sensor by unpluggin it.

 

Hamish I noticed when I connect pins 1 and 4 the car revs drop. I assume it disables the automatic idle control.

This then allows you to adjust the idle mixture after you have changed the timing

So although 1 and 4 do not make the lights flash, they do have some effect.

Does this help ?



PS...Trying to make a frequency modifier unit is not as easy as I thought. You need to supply enough fuel at all rev ranges as smooth as possible otherwise the car stalls and sputters!!.

 

My Openport 1.3U cable and Evoscan software is for sale if anyone wants to make me an offer ? Still cant get it going and have not used it.


BTW I have completed the MAF frequency modifier board (using a propeller chip)... Can't get any savings from HHO though

With the O2 sensor unplugged I can make the mixture as rich or as lean as I want using an adjustable pot while driving.

Is this of interest to any Mitsubishi owners ?

 

Have you tried going back to EVOSCAN 2.5 and setting the OBDII baudrate to 10400? I see more disconnects when it is higher than that. Your 1994 is one of the weird hybrid in-between years, where Mitsubishi still didn't really have their act together on integrating both OBDII and MUT protocols into their ECU's. We have the same issue here in the states with the 1995/96 2G DSM ECU's, and certain year Stealth/3000GT's. I also think Hamish broke something with the hybrid protocol in v2.6, and have all my 1995 customers back on v2.5.

 

Thanks keydiver, I tried it again with version 2.5 and 10400 baud but still no joy. I even set the timeout to 20,000 but it still would not stay connected.

It says connected and goes green then it restarts. I assume it is not getting any info back from the ECU after the handshake ?

It really looks like a good thing, I would love to get it working but I have no idea how. Still selling it if anyone is interested.

 

Hi I found this response on the pajero forum.. Will this work for me ?

Hi, it's ok. got it working already on my car. here is what i did. iam using an openport 1.3d cable, at first i dismantled the openport cable and check whether there is connectivity between pin 1 and pin 4. visually, the connection is there, i saw pin 1 and pin 4 are soldered together. so i ignore the connection on the obd connector on the vehicle side, since it is already connected on the cable. tried hundred times connecting to the ecu using evoscan 2.6 - no luck at all. after that i was thinking, wtheck, i tried to connect pin 1 and pin 4 on the vehicle side using just a short cable. once i connect the openport 1.3d cable to the vehicle, straight away it flashes CEL, and then i tried to connect again using evoscan and voila! bro, maybe you should try to connect pin 1 and pin 4 on the vehicle obd connector using a short cable, i tried using paperclip, it ain't gonna work, maybe the connection is not that good.

 

Connecting pins 1 and 4 didn't help...