Thread: Can’t connect to the ECU – Help please!

Can anybody help me please?... So I bought one of them el cheapo consult from china. I wanted to see all data/gauges via laptop out of my genuinely paid JWT ECU (VE program, Stock VE MAF, VE Injectors, among other customs petitions I made when I requested the chip) When the consult arrived I rushed to the car to connect it, only to find that none of the softwares I used could connect to the ECU! (Conzult free; ECUTalk; Calumsult; etc.) The only software that found something was OBD Scantech, founded it when performing the “ECU FINDER” button in Advanced. It found two things @ FF FF E7 (I suppose this is the ECU) and at FF FF DC (Airbag module I think) . Can anyone help me please? How do I connect to the ECU to see live data?
BTW, tried the same combo on a Mexican GA16DNE B13 and it worked perfectly. I even dumped the rom so the setup (Interface/Serial adaptor/Software/Laptop) it’s working properly. Also tested the JWT consult port with a Blitz R-Vit type II (Specifically to OBD 1 Nissans) and get all data correctly displayed... HELP!!

TIA

Que alguien me ayude por favor!!!! Seriously Hasn't anybody deal with this before? You know the consult thingy it's boxy, it's big, it's gray and it definitively looks painful to shove... Ayude al Chileno en distress please

^^^^^
Longest BUMP ever

What OS is your computer using?

Try Nissan Datascan for a logging program. (i believe its free)

Also your computer needs some software to be able to communicate serial data.

Did the consult cable come with software?

I have never used a JWT ECU so im not sure if the problem is in their software.

For all of my data logging I use a Innovate SSI-4. It is a 4 channel + 1 for innovate wide bands. Comes with all the cables you need and the latest version of log works. You can get them for about 100+shipping.

Those consult units from china work very well, are very well made, there have been several revisions tru the years from through hole PCB's to SMT, never had a problem with one yet and I have tried several (more than 5). The only issue I have had was that one unit the led never lit up and I opened it and found the led was soldered in wrong polarity, switched it and that was it.

The fact that ecu finder sees some valid adresses means the interface is working. Is the car an auto or used to be an auto and the auto ecu is still wired in?

Also I see u have a P11 in Chile, this may be a complication, for instance, I have a JDM P11 '98 that has the OBD1 port(grey 14pin). I can connect to and see all the 4 consult adressable ecus (original) on board (engine, ABS, TCM and A/C) with the same chinese unit.

Now if I take and put in a USDM ecu B13(91-93) like what I expect your JWT is, I cannot see or connect to that ECU from the consult port (have tried the chinese, blazt, homemade cables using datascan, calumsult, obdscantech), I can connect to that same ECU out of the car with a cut harness plug wired up with power and a consult plug.

So I have surmised that one or all of the other units are causing problems communicating with the engine ecu, maybe its daisy chained or something. I do not have a wiring diagram for the car and I have never gotten around to tracing the wires by hand.

Also there is one other possibility, it seems that the newer ecus do not require the CLK signal, but the B13 ecu must have it, if the CLK is not wired through to the engine ecu, you will never see that ECU because it will never initialise via consult.

If you have or can get a cut consult plug from a scrapyard etc, wire it in directly at the ECU harness plug and see if you can communicate there. You just need the 5 pins, +12v/gnd/TX/RX/CLK

you can see how to wire it up at plms developments or maybe here or the old forum.

Are you on the right COM port?

Hes on the wrong comp port i bet, and missing a driver or 2. Just because you have the consult program, have u isntalled one for the unit itself? I know mine took the consult driver, and then a driver just for the cable/unit. And my china one works nice and fine.

If he was on the wrong com port "ecu finder" alerts you and says invald comport. There is also an auto scan where it finds the valid com port for you. It is basically fool proof.

If the interface was not working he would find no available nodes.

He said the interface works on another car. That is another subtle hint that the pc/cable/software package is working as it should.

^ Well hes just fucked then now isnt it. Ive seen it switch com ports on me before when plugged into different cars, always something u should check even if its supposed to "auto" find.

Thanks yoshoto,

After reading what you posted, I think you might be right. When I bought the Blitz it didn't work at all, after relocating one pin on the blitz unit, I made it work. On my particular car the "Clock" signal it's bridged close to the ECU with the "Check" signal so I think if a separate those two I might get it working. I'll study a b13 wiring and try to replicate it, thanks to everybody who tried to help. Oh and danfiveten, I don't think I am what you said (fucked), after all I just want to dump my ROM so I can have a base for my Nemu board when I get it.

I'll report the results
Thanks again

Naw i know your not fucked, but people like yoshomitoda da do dee shoudl know to keep your mind open, computers will switch stuff like com ports, and just because it shouldnt, doesnt mean that it wont and you should keep your mind open for the sitiuation instead of saying nah that cant be it. My dad works I.T. and has seen some weird shit happen with cables. Just because one is working on one pc, hes had it where they switch com ports when plugging devices into others. Always keep a open mind is what im trying to say.