HowTo: Identify Diagnostic Cables by PinOuts.
Connected pin 1 to pin 15 on the cable side.
AYC connects and logs = however the data is not changing ie doesnot makes sense - turning wheel doesnot chenge the angle etc.
ABS - is not able to establish a continuing connection - no logged data
Engine on - but car was not moving. I haven't tried the actuators.
AYC connects and logs = however the data is not changing ie doesnot makes sense - turning wheel doesnot chenge the angle etc.
ABS - is not able to establish a continuing connection - no logged data
Engine on - but car was not moving. I haven't tried the actuators.
Thread Starter
Former Sponsor
iTrader: (4)
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
nope, it works perfect I have had hundreds of success reports.. I never said connect pin 1 to 15 on the cable side, thats absurd, you are basically connecting pin 15 to ground by doing that, thats the last thing I said to do. I said to put pin 1 on the vehicle side into pin15 slot on the vehicle side.
Thread Starter
Former Sponsor
iTrader: (4)
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
yep perfect... you've got it.... on the latest cables, I hope I dont confuse anyone, but how the evoscan cables now are - they have pin1 disconnected from ground on the cable, and instead pin15 and pin1 are connected. So only do this if you have continuity between pins 1 and 4 on your cable side. those that have continuity between pin 1 and 15 on the cable side then you I have already done for you, and you don't have to do anything except perhaps remove the subaru pin9, which interferes with mitsubishi diagnostics and should be removed from the cable side.
I cannot get the pins out of my car's OBD connector even removing the grey holder and then trying to get it out with watchmaker's screwdrivers. This is why I have tried by connecting pin 1 to 9 (9 and 15 are connected in my Tactrix cable - they continuity test and it shows on the wiring diagram). I will get the ecuids for AYC and ABS and post them. I had to cut the connection to pin 9, but again this made no difference so I've resoldered it again. I could log TPS through request ID 1C on the AYC so something is working...
Am I wasting time trying to get this to work with a Tactrix cable? If your cable will fix this I'm happy to order one, but no point if I just get the same problem. Or is your cable just twiddling the same K & L lines as Tactrix with the L line moved to pin 1?
Am I wasting time trying to get this to work with a Tactrix cable? If your cable will fix this I'm happy to order one, but no point if I just get the same problem. Or is your cable just twiddling the same K & L lines as Tactrix with the L line moved to pin 1?
Last edited by jcsbanks; Jul 23, 2008 at 01:28 PM.
AYC ecuid is 6201
I get "Error: Index was outside the bounds of the array" if I try to log TPS on 1C, but I can do it from the custom requests.
ABS:
Info: Initialize Vehicle ECU...
Info: ECU ID: B063
Info: Connection successful...
[Immediately followed by...]
Info: Datalogger Ended.
I know this isn't an open source project, but I'm completely in the dark to debug this as I don't know how the hell it all works apart from studying the wiring diagrams.
I get "Error: Index was outside the bounds of the array" if I try to log TPS on 1C, but I can do it from the custom requests.
ABS:
Info: Initialize Vehicle ECU...
Info: ECU ID: B063
Info: Connection successful...
[Immediately followed by...]
Info: Datalogger Ended.
I know this isn't an open source project, but I'm completely in the dark to debug this as I don't know how the hell it all works apart from studying the wiring diagrams.
nope, it works perfect I have had hundreds of success reports.. I never said connect pin 1 to 15 on the cable side, thats absurd, you are basically connecting pin 15 to ground by doing that, thats the last thing I said to do. I said to put pin 1 on the vehicle side into pin15 slot on the vehicle side.
the same scenario - AYC connects and logs - but the values do not change
ABS the same behaviour as with john - connects and immediatelly disconnects.
the ecu ids are the same as john is mentioning - (but I have a EDM Evo 8 vs his Evo 9) so I am surprised they show the same ID.
Thread Starter
Former Sponsor
iTrader: (4)
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
Thread Starter
Former Sponsor
iTrader: (4)
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
Thread Starter
Former Sponsor
iTrader: (4)
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
you've got it right, my cable is twidlling the same K & L lines as Tactrix with the L line moved to pin 1. (my cable has L Line connected to both pin1 and pin15)
mitsubishi pin 9 ETACS is a 5volt TTL line, so putting the 12-14volt L line(subaru pin9) onto it is not the best idea, but doesn't harm anything.
I am looking at supporting the older TTL ecus used in the EVO8/9 by creating a new cable with pin9 as a TTL line.
mitsubishi pin 9 ETACS is a 5volt TTL line, so putting the 12-14volt L line(subaru pin9) onto it is not the best idea, but doesn't harm anything.
I am looking at supporting the older TTL ecus used in the EVO8/9 by creating a new cable with pin9 as a TTL line.
Thread Starter
Former Sponsor
iTrader: (4)
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
There is no point you wasting your time debugging sourcecode, I can fix it easy as, now that you have posted the results. I'll take a look at it this afternoon. to see any reason why you are getting what you are both getting.
AYC ecuid is 6201
I get "Error: Index was outside the bounds of the array" if I try to log TPS on 1C, but I can do it from the custom requests.
ABS:
Info: Initialize Vehicle ECU...
Info: ECU ID: B063
Info: Connection successful...
[Immediately followed by...]
Info: Datalogger Ended.
I know this isn't an open source project, but I'm completely in the dark to debug this as I don't know how the hell it all works apart from studying the wiring diagrams.
I get "Error: Index was outside the bounds of the array" if I try to log TPS on 1C, but I can do it from the custom requests.
ABS:
Info: Initialize Vehicle ECU...
Info: ECU ID: B063
Info: Connection successful...
[Immediately followed by...]
Info: Datalogger Ended.
I know this isn't an open source project, but I'm completely in the dark to debug this as I don't know how the hell it all works apart from studying the wiring diagrams.
Thread Starter
Former Sponsor
iTrader: (4)
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
maybe on the vehicle side make sure you only have the orginal pins 1/4/5/7/16 connected up and nothing else.
the other lines might be interferred with by the Subaru pins on the openport cable.
there are other ecus on the other pins like ETACs that can interrupt pin1 for all the ecus.
the other lines might be interferred with by the Subaru pins on the openport cable.
there are other ecus on the other pins like ETACs that can interrupt pin1 for all the ecus.


