OpenPort 1.0 now available for sale!

[Spiider]

Pin 4 and 5 are both ground. No way anything is being communicated over those lines.

All communication is done over pin 7 (K-line) and pin 9 for what I think are the "line end" feed.

Edited for typo on pin number.

[yarikoptic]

Pin 4 and 5 are both ground. No way anything is being communicated over those lines.

oops - sorry - I mixed up with Subaru inverted pin notation again as described on the picture earlier in this thread. So they are pins 12 and 13 in J1962 as you've mentioned before .

All communication is done over pin 11 (K-line) and pin 9 for what I think are the "line end" feed.

hm... I thought K-line is pin 7 (or 10 in Subaru numbering) and anyway pin 9 (or 8 in Subaru) is not ingaged on mine.

[Spiider]

Ooops, you are right.

Pin 4 = ground
Pin 7 = k-line
Pin 9 = line ends
Pin 11 = 12v regulated power for erasing/flashing

[Imp Guerra]

bcbfscan
is for
BC and BF legacies (BC & BF is the chassis codes)
it want work with your car
100%

it works with legacy turbo 92-94
but there are no such models in US and canadian market

it is not interface and with such "schematic" lpt-port is in very unsecure position and it is high possibility to completely burn it in pc.

BTW - I couldn't find a word on baumtools.com about this tool believed to be their... So what is its story?

it is their soft, no doubt.
an VWtool also (on the same basis)

about Subaru and OBD-II J1962-connector notation.
To be not confused I think we should use only standardize OBD-II j1962 pin enumeration, not subaru or other notation.

For ISO-9141-x and for KWP-2000 :

4;5 - Ground
7 - K-line
9,11,12,13 - OEM
16 - VCC +12volt

[bofh]

This place has some new software.
http://www.palmerperformance.com/

I was in on the beta with my elm interface, and it seemd quite good. My beta expired, however, so I can't test it on the new one. It does, however, support non-elm based scanners.

[Imp Guerra]

It does, however, support non-elm based scanners

so
are there 2 or more protocols ?
one is for ELM translation and the other is for pure ISO, like VE by OBD-2.com

i have found new soft at

http://www.myscantool.com

it does quoter miles.
but i cannot try it becouse of some "bugs" that do not allow the app to start and communicate with my elm-chip.
May be some one helps me with "de-bugging" that app ?

unfort, i cannot "debug" apps by myself

[yarikoptic]

bcbfscan
is for BC and BF legacies (BC & BF is the chassis codes)
it want work with your car 100%

it works with legacy turbo 92-94
but there are no such models in US and canadian market

well... check the thread were originally it was discussed

http://bbs.legacycentral.org/viewtopic. ... sc&start=0

There:

Update: It should now support non-turbo models too! Give it a try, everyone!

Also most of the subaru owners on that site are from the states... so I Would assume that the tool (3 wires + software) would work on most of old subaru's were for SSM there were 12,13 pins ingaged. That would be my wild guess

it is not interface and with such "schematic" lpt-port is in very unsecure position and it is high possibility to completely burn it in pc.

Yeah... it can... so in the ideal case I would like to get a proper interface for it... but just to check if it works, probably simple wires would suffice...

[yarikoptic]

VE also works with K-line. But only with ISO, and you are to know the serial key to the app.
VE is great soft.

today I've tried that free copy from obd-2.com and it didn't connect to ECU under any circumstances although right serial port was selected. Also I was confused a lot by the available settings such as that com port speeds 19.2, 36K etc. So it sounded like for some chiped interface (I don't know at which baud rate ELM is working but may be for it?)
So is VE really a pure ISO K-line only capable? I dunno :-/
I wish it connected -- it seems that it has maany nice features and infromation

[NeverLies]

You may not connect to any car with the sofware available on obd-2.com. It may only works with interface sold on this site

I've bought one interface to test it and in this case, it perfectly worked.. but you can't use it for SSM or for OBD on a standard interface

[Imp Guerra]

You may not connect to any car with the sofware available on obd-2.com. It may only works with interface sold on this site

more than 2 years I have worked with various VE versions and my self-made K-line-adaptor.
With K-line-adpt it realy works, but only with ISO 9141 protocol and KWP-2000
For VPW, PWM it needs dumped chip.

today I've tried that free copy from obd-2.com

and who said you that it is "free" ?

I won't connect without serial.

More over new versions of the soft works with CAN pca82c251 chip.
I consider VE (Car Code) to be the best OBD-II diag soft.
I wish I have original adpt for it.
But now we produce our ISO+KWP+VPW+PWM+CAN adaptors with ozen-2600 chip.

[NeverLies]

Colby, you have made your interface in order to have a regulated +12V on pin 11.

Looking at the HC916 documentation, the Vpfe must be between VDD-0,5V and 5.5V (so should be 5V regulated) for reading operation and 12V operation for flashing/erasing.

Have you been able to dump ECU code with your interface ? what connection have you used so ?

[Spiider]

He has done the 12v regulated on pin 11, trust me on that one.

Mine is a little low at 11.67v but will work fine once we have some software to reflash. You need 12v +/- 0.5v for a reliable flash.

[NeverLies]

Yes, I known it for refash operation but does we have to take care of this reading voltage as we can see in the documentation ?

[cboles]

It's up to the flashing software in the kernel you download to determine that the voltage is adequate and the the flash is correctly erased and programmed. Does that answer your question?

[NeverLies]

Will see