Originally Posted by
yoshoto
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.
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
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.