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

Is this the cable type you have, its the one i spliced together.

^^^^
LOL Exactly the same setup, even the RS-232 adapter

If you unplug and plug back in a USB-Serial adaptor it may assign a different port, that is known, because its a VCP and not an actual port. All cables that use such VCP's will specify to find what is the assigned port using device manager. If your PC or laptop has a com port it will always be COM1 by default, if it has more than one like older PC's it would be COM1, COM2 etc. You can set this in bios to be a different default but that will remain fixed at what u set it to. Newer windows OS's allow you to set the comport in device manager.

Comports are not kangaroos, they do not "Jump around".

There is more than one IT professional on this here planet. I guarantee that what I KNOW about IT is more than whatever you have heard from your daddy.

As I said before and if you read his first post again slowly, or have your daddy read it to you, he was able to see two consult nodes.

" 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)"

This means the cable is working as it should and something else is wrong, not comports or missing drivers.

So don't let tales of jumping comports, leaping leprechaun's or other mythical beasts your daddy told you at bedtime, prevent you from looking objectively at the facts the OP has posted.

Oh yoshoto, got a tiney lil but hole that cant take a lil lickin now do we....awww. Ill end this hear with not continuing it. Weird things happen in the it world, i used to be it before i got tired of it from growing up with dealing with it and helping my old man at work as a kid. So bite it. This lil bitch war ends after my period, so get back on topic. It may come from my "daddy" but my "daddy" pulls 100k hell i think more now a year and maintains computer systems for a entire hospital and several clinics and has seen some weird ass freaky shit happen, so i trust what he says on things more than someone i dont even know nor care to now. Its just like with cars, people say OH that cant happen, and then guess what, it just fucking did. Its called unpredictability, the improbable and impossible can happen and surprise the shit out of you. Now shut the fuck up and lets go back on topic because your the one egging me on now.

Make sure its plugged in really tight to, mine if it wasnt pushed on super fucking tight would have a few issues sometimes as well.

The USB - Serial adapter might be bad. I had one EXACTLY like that off Ebay and it didn't work for whatever reason. I tried a different looking USB-Serial cable and it worked. I think some of them are wired wrong or just bad. Try a different cable.

-G

Hmmm, well its obvious now that you are afflicted by trisomy 21 and on top of that you've got your period, not the best combination I guess. Come back to us and chat when u stop bleeding. You'll still have an odd number of chromosomes but at least the hormones won't be an issue.

I'd like to hear how the jumping comports, weird ass shit and all the other halloween creatures account for him connecting to other consult devices but not the engine ecu. Once you can explain that logically, not fairy tales and ghost stories, I will be willing to listen, until then we can go on calling each other names.

Seems like "ur daddee" is practicing voodoo IT, only things I have seen are Hardware failures, software bugs and incompatible software/hardware. Really simple stuff. I guess that's why he works so hard and gets paid so little.

Their is a voodo thing and ghost and ghoulies, its called spyware. Its been known to switch settings and shit on machines. Hell its even likely possible that a nistune and shit could hold a virus from a computer that was infected with something that could be messing with shit. You never know. Hate people who know their 100% right when they have no real idea. Talk shit about my dad if you want, but hes got more collecers cars and shit than youll ever have in your dreams. Its why hes not into se-r's, he makes real money so he can have real toys.

Thanks Yoshoto, my problem's solved now. Here's the update:
It seems that on newer models OBD I, the CLK signal cable is joined with the "Check" cable. Probably this is made to simplify the wire harness/save costs.


This is the diagram for my particular model, as you can see CLK signal i's bridged with the "Check" pin even before the F17 Connector. I couldn't find the actual join but I managed to access the correct cable. That's what's been messing with the connection ECU<-> Interface.



As per Yoshoto's suggestion, I sourced a used consult plug and used one of the pins to make a direct connection from ECU pin 14 to DDL pin 9.
Results? I just dumped my 23710-3VE33 rom and can see all live data.

Now another problem arise... I don't know if I should start another thread or just keep it on this one. How the hell do I get to see the dumped ROM? I know JWT roms ares supposed to be encripted and all but I can't even see some other roms I've dumped (Nissan OEM) I'm guessing my limitation is on the XDF files. B13RT.XDF on TunerProRT doesn't work for none of them. How do you make an XDF file? I've searched here and there but I haven't been able to find the way to do it.

Thanks to everybody who posted to help.

glad it wasn't the evil spirits, witch doctors and exorcists aren't easy to come by these days.

jwt roms are "encrypted" on the chip, basically they mixed up some address lines and I think they even jump between an upper and lower 32k rom so 0000 to 7FFF and then 8000 to FFFF, they have jumpers on the boards too so that each ecu is not the same, so basically there are a few differnt flavours of the encryption. If you do a rom dump you would have the right thing. If you try to read the chip using say an eprom programmer you will get garbage, because JWT boards have the decryption system built in when you access the rom tru a consult dump you get the right data.

once you are using the correct xdf for the US b13 91~93 or try the one for the 94 b13 too because there is some difference, then you will be set.

use calumsult if you have any doubt of the rom dump itself.

I have never got datascan to run on fast speed, only slow, fast always locks up, and slow takes forever, that is in my experience but others must be using it or they would have fixed it by now.

Thanks again man, Glad I wasn't f*cked too... I'm gonna try what you said. The ROM was dumped using Datascan. Calumsult took too much, but I'm gonna let it finish to see If I can access the data.