As title, here is the link:

http://cgi.ebay.co.uk/ws/eBayISAPI.d...=STRK:MEWAX:IT

 

It probably won't work since your classic (if its V4 and below) will only understand the Subaru proprietary SSMI protocol and not OBD2. Get the proper SSMI cable from evoscan.com. There are a few free alternatives to the Evoscan software for logging like Revscan.

Edit: On second thought, maybe it might work in conjunction with a VAG-COM cable. You would have to experiment and see.

 

i have one of these cables but am yet to try it, i will try tonight to to see if it works.

 

Thanks for your input.

I was going to say it has to be worth a try at that price.

 

yeah, although the postage is that slow your car would have rotted away before you get it.

 

U should just do a manual test with the engine check light and the two connector under dash I done for the first time over the weekend and was just so easy ... I have a 95 wrx the two connectors put the car in diagnostics mode and the check light flashes basically the long flashes come first each 1 = 10 then after the short flashes =1 eg 3 x long flashes and 2 short = error code 32 ... I just recorded it on my phone and then went over it inside just to confirm I read it right then googled the Subaru error code I was given fixed it discon battery for 1 hr that resets ecu then fire her up and no more error ... I cannot stress how easy it is .... There is a sequence basically open car connect the two cables , keys in , turn on ( don't start car ) just make sure u have the cam pointed at check engine light when u turn on then after 2 secs it will start flashing away .. Se if u can remember the first sequence as if u see it again it's repeating and that mean u have seen all the errors so if u have 2 errors it will show 1 then 2 and back to 1 then 2 ect .. Anyhow when u have seen enough turn ignition off disconnect the two wires and go look at ur cam to see what codes u have ... Think that's is anymore help just message me ... Or google it ..... Simpilllss

 

Thanks anyway but I already know about the test connectors but they only show error codes (even that, not always).
The reason for looking at a cable is to be able to connect and monitor real time what's happening in the engine.