openecu.org

by **Spiider** » Mon Apr 04, 2005 11:50 am

Order placed, thanks very much.

by **cboles** » Mon Apr 04, 2005 12:40 pm

Turns out there were some problems with signup emails of the tactrix site too. All of that should be fixed now. If you already signed up on that site, don't worry - your sign in was captured even if you didn't receive a mail.

Colby

by **cboles** » Mon Apr 04, 2005 1:14 pm

I've put two versions of the OpenPort on the site now. One includes the 12V programming voltage pin (the "WRX" version) and one does not (the "generic " version). This way you can be sure you are ordering what you need.

Colby

by **yarikoptic** » Mon Apr 04, 2005 2:06 pm

cboles wrote:I've put two versions of the OpenPort on the site now. One includes the 12V programming voltage pin (the "WRX" version) and one does not (the "generic " version).

I can just order WRX and rip off 11th pin to get 'generic' version, is that correct? (I better go with WRX for future possible use and use it on my 95 Legacy because pin 11 is loose on it)

BTW - that is sad that such experimental interface box is 'glued', ie nobody can take the shell off and "adjust" it in case if it is necessary using soldering iron. If you glued the parts together just so it has 'market' appearance, may be you better go with version 'Loose shell' which wouldn't be glued hard and someone who wants to get inside the interface can just wrap it with scotch tape to bring pieces together or smth like that... Then I would be able even to put "scew-in" pin #11 or tiny jumper so interface could be used on WRX and elsewhere safely

by **cboles** » Mon Apr 04, 2005 2:49 pm

I debated making the 12V ECU voltage pin controllable by software, but in the end decided it was too risky as the state could be unknown upon initialization, people make programming mistakes, etc. Even with the case unglued, it is not a casual affair to open the packaging. The OBDII connector portion of the case is attached last by press fitting it over the pins and the other two pieces of the case clamshell. If you attempt to pull the connector off, you end up stressing the right angle header quite a bit. It's a bit hard to visualize without all of the pieces in front of you. You can see the populated board at.

http://forums.openecu.org/ezdloads.php

I could send you a board + case that you could assemble your self once you had added the switch... there is already a error jumper wire on the board for the 12V programming voltage, so it may be possible to wire a switch in its place and bring it out the USB connector hole. Things are incredibly tight in there though. It might be a lot easier to pull pin 11 from your Legacy.

by **yarikoptic** » Mon Apr 04, 2005 4:24 pm

cboles wrote:I could send you a board + case that you could assemble your self one you had added the switch... there is already a error jumper wire on the board for the 12V programming voltage, so it may be possible to wire a switch in its place and bring it out the USB connector hole. Things are incredibly tight in there though. It might be a lot easier to pull pin 11 from your Legacy.

Sounds great! Placing an order (couldn't locate the "jumper wire" on the picture... may be it is just on the opposite side? :-)

). I will place the note to send me open case just don't lock it up and don't glue :-)

Thank you in advance

by **Imp Guerra** » Tue Apr 12, 2005 6:41 pm

95 Legacy is full ODB-II ?

the only '95 US-market Subaru car was equipted with obd-ii protocol and j1962 connector

it is Legacy
only Wagon
only with 2.2 engine
first obd-ii model

all other subaru-obd
since 96 for US
since 2001 Europe

by **yarikoptic** » Tue Apr 12, 2005 6:54 pm

Imp Guerra wrote:
95 Legacy is full ODB-II ?

the only '95 US-market Subaru car was equipted with obd-ii protocol and j1962 connector
it is Legacy
only Wagon
only with 2.2 engine
first obd-ii model

yeap - it is mine ;-)

is there a restriction on color? it is dark blue then :-)

I know that mine has OBD-II because I stopped by at Autozone a few times to read out codes using their code-reader.

it has pin 11 (or pin 6 in Subaru notation following the schematics I previousely posted) used for SSM clocking so I just desingaged it for now from the socket (I would it simpler than mangling beautiful new OBDII interface I got :-)

)

I've tried current interface blindly using posted in the software section C code and it didn't do anything (ofcause I fixed the device name to be /dev/ttyUSB0) - it was stall waiting for something. So I assume that it doesn't to SSM over K-line but only over that dedicated for that pins 4 and 5.

Now I just need to find time and tweak freediag to perform regular K-line handshake (instead of L-line) at 5 baud and then do regular 10400 bot OBD-II interaction. I assume that colby's interface should be capable of that :-)

What is the other software which does traditional ISO OBD-II with handshake over K line without using ELM chip? I assume it should work with this interface or am I mixing up something?

PS. Do you still need ECU diagram for Impresa?

by **Imp Guerra** » Tue Apr 12, 2005 7:22 pm

What is the other software which does traditional ISO OBD-II with handshake over K line without using ELM chip? I assume it should work with this interface or am I mixing up something?

the soft is OBDtool v.1.2.6.0.
it does not need any serial number or so
works with any of ISO-9141 cars
using single bi-directional line

Check DTC, Clear DTC, Live-Data, Data-Logging.

Do u need a copy ?

Then go

http://www.obdtool.org

find SUPPORT and in OBD-II section find
there is zipped installation copy

by **yarikoptic** » Tue Apr 12, 2005 8:01 pm

Imp Guerra wrote:
the soft is OBDtool v.1.2.6.0.
it does not need any serial number or so
works with any of ISO-9141 cars
using single bi-directional line

Great - thanx! I will give it a try whenever it downloads (narod.ru is as slow as usually :-)

)

I would prefer linux software though ;-)

but if obdtool does its job, then I will have at least something working to start from ;-)

by **Imp Guerra** » Wed Apr 13, 2005 3:15 am

i do not know any linux based apps for k-adapter to be compatible with ISO9141,
but there are some for ELM-chip i guess

and why'd u buy elm323 and solder an adaptor for yourself
323 costs only 16.5CAD in Toronto
but here in russia within soldered PCB and enclosure it some what much expencive

more over with elm323 u can use scantool app in my russian translation

, do quotermiles tests, 0-60mph test an so on

by **yarikoptic** » Wed Apr 13, 2005 9:26 pm

Thank you alot - that worked... That is just a summary though :-)

First I've tried to run it on my favourite super-mobile 2-3lb VAIO with ancient 300HZ Celeron running XP... Well... it didn't quite work. I had to force FTDI driver to occupy COM4 instead of default 5 because software didn't have even that option and changing in config file to 5 seems to didn't help. Anyways -- it just didn't work. when I started up software it was trying to communicated but was complaining about not received response message and it even was crashing when I was switching to trouble codes section.

So I demolished swap partition on my other Linux-only laptop (big brother - 5lb :-)

) and made it dual boot with native for it W2k. This time obd1260 worked there like a charm -- FTDI drivers set up for COM3 and software managed to communicate right away. I could already monitor parameters. Now I just need to wait for another occasion of my "stall problem" and see if there is any freese frame data etc.

Also, because it worked using the software you recommended, I'm confident that I should be able to use freediag to do the same :-)

Why I didn't get ELM interface? well...

ELM interface is nice but as any hardware controller, it is too rigid solution. I would prefer open source software solution to the hardware solution whenever they are equivalently powerful because I can always tweak software and figure out why it doesn't work whenever with hardware it might not be even possible.

ELM chip has pretty simple interface, may be someone should write a wrapper for our interface which would implement the same protocol as ELM chip, then it must be possible to use any ELM designed software to interface with a car. Or am I missing something?

by **yarikoptic** » Thu Apr 14, 2005 5:33 am

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

by **Imp Guerra** » Thu Apr 14, 2005 6:15 am

obdtool1260 works. and previously it was the only solution to read US market cars for free. there was time when elm. autoenginity, ozen did not exist at all. the choice was wether VE by A.Pepper (obd-2.com) or obd1260.
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.
according to implementation of elm (or ozen) chip into the Open plug: What for ? SSM protocol with diag app by XYZ gives you quite much than generic obd-II protocol. (when we speak about subaru only). If you have nissan or honda - you also can find specialized apps and use them. Generic OBD-II is very much "generic". It is not for tuning of any kind, just to read DTC, repair the foulty part and clear DTC.

What is FTDI driver and where to download it ?
I have heard about ftdi, they produce usb-com adpts.
what driver do u use to choose "com" 1-4 from usb port ?
cos when i installed Gembird usb-com the choice was only from COM-5 that was unsupported by majority of diag apps.

by **yarikoptic** » Thu Apr 14, 2005 8:06 am

the interface from obd-2.com was the one I considered :-)

there is even seems to be some discount... anyways - it seems that there is some free version available:
Free complete working copy of the VE1 OBD-2 browser
I will check what is there and if it works with Colby's interface

FTDI drivers I took following Colby's link from
http://forums.openecu.org/viewtopic.php?t=16
but I believe it is specific for the USB->Serial chip he is using in the interface
and it allows to choose which com port to occupy in the properties of Serial USB port driver

Indeed SSM is better than a generic OBD-II but I wanted first to get at least something. And in my car SSM seems to be performed not over K-line but rather over pins 4 and 5... I'm not sure if it is possible to adjust interface to perform SSM as well...

There is a guy who used LPT port to interface with SSM over these lines
http://www.graphics.cornell.edu/~v/bcbfscan/
but I didn't try it and he hasn't replied yet on request if he would mind releasing the source code

openecu.org

OpenPort 1.0 now available for sale!

Two versions of OpenPort now available

Re: Two versions of OpenPort now available

Who is online