Engine code reader pre OBD II

magg · Post by **magg** » Sat Jan 15, 2011 8:41 pm

Strange number but if it works who cares As I said don't known what vwrx software does & no mention of a setting that I can find on his webpage. Will have another look & perhaps send him an e-mail for clarification.

fredsub · Post by **fredsub** » Sat Jan 15, 2011 10:08 pm

Suparoo wrote:1953 is the SSM baud rate, which is rather unusual, but apparently guys have got it to work using the next closest, 1800.

I dont know if it is possible to change the baud rate to something custom?

suggest this is why your FDTI chip does not work, I've got one, perhaps an older version chip, but it only works at standard baud rates, anything a bit off
doesn't work well if at all.

Standard MAX232 based converter with a real serial port works no problem.
It sucks that real serial ports are no longer included in notebooks.

magg · Post by **magg** » Mon Jan 17, 2011 6:24 pm

Pick up replacement oscilloscope tomorrow morning and then can see what is going on. Have tried ecuExplorer & vwrx software, neither work, even sent ssm initialization word direct to ecu without success. Need oscilloscope!

Gannon · Post by **Gannon** » Mon Jan 17, 2011 8:02 pm

Sweet.

I'll look into another form of serial connection, like a max232

magg · Post by **magg** » Tue Jan 18, 2011 9:06 pm

Have oscilloscope, another long story but now in business. Only had time so far to confirm data coming out of the serial port when vwrx or ecuExplorer software is running. Rates look similar but detailed analysis to follow. Think the big issue is my interace inverts the data, my mistake. Need to re-engineer the interface & try again.

Gannon · Post by **Gannon** » Thu Jan 20, 2011 7:07 pm

Did a little bit of internet browsing and came across these sites.

This is information about using OpenECU software and OpenPort cables with the intention of reflashing the ECU rom.

OpenPort 1.2 FAQ

ozLiberty.com/ECU Interrogation

www.myrollingroad.com/OpenPort Cable Version 1.3

Openport 1.3 schematic.pdf

www.myrollingroad.com/Openport cable
Openport schematic.pdf
www.myrollingroad.com/OpenPort 1.3 project 4 mitsubishi carisma

It isnt possible to reflash an NA ECU but it will give us more of an idea how the data interface works

magg · Post by **magg** » Fri Jan 21, 2011 9:48 am

Going to use max232 as the easiest method of getting TTL to RS232 comms, have used it for comms on my programmable delco ecu. Had already looked at the openport cable schematics etc but have not found one that supports ODB II pins 12/13 ie no SSM capability. The more I read, the more I get confused but I think SSM is simple TTL/RS232. OpenPort & other cables appear to assume OBD II capability.

My impending 4 day break will delay the build but expect MAX232 chip will work as indicated by fredsub. You may have issues with USB, the guys using a delco ecu but with USB had problems. This is where my comments regarding virtual ports came from.

An alternative is to get a late model oz or US ecu that runs OBD II & is compatible with our engines, probably most. Would have full programming capability too.

fredsub · Post by **fredsub** » Fri Jan 21, 2011 10:16 pm

here's my circuit..

sorry the image isn't that good, if you want a better one, pm me a email address and i can send pdf.

i see the openport one has opto-isolators. Not really required if using from
a battery operated notebook - does no harm either.
Though if using a mains powered desktop machine, its very very advisable.

some useful comments can be found here also
http://www.rslibertyclub.org/forums/sho ... data+cable

http://www.rslibertyclub.org/forums/sho ... hp?t=65874

Gannon · Post by **Gannon** » Sat Jan 22, 2011 7:18 am

So how is the max232 chip different to the ttl-232-usb FTDI?

I have read that other people have had success with the FTDI adapter, why cant I?

Id use the max232 circuit, but my laptop doesnt have a hardware serial port

fredsub · Post by **fredsub** » Sat Jan 22, 2011 9:45 pm

That is the wrong question:)

How is FTDI chip different to 8250 and its superseding chips 16550 etc - ie the actual asynchronous TX/RX hardware and how its interrupt wired to the computer. Note: USB has no actual hardware interrupt for the pheriperal, its a pseudo based on USB protocol.

I'm a little disapointed your reporting problems - I assume you have purchased a recent USB/rs232 ? so it hasn't much changed in 4years, hmmm

the max232 is only a level translator and the FTDI has one integrated.
Fortunately my notebooks are Toshiba's, got actual real serial port.But it would be good to have a netbook size m/c with serial port, but none are in existence:mad:

adamjgs · Post by **adamjgs** » Fri Feb 18, 2011 2:58 pm

Hi folks,

I realise this thread hasn't been touched for a few weeks now, but did anyone end up having any luck making a DIY interface for non-OBDII Subarus?

I only have this to offer - Suparoo, what model is your FTDI chip? It seems from the photo that it might be an FT232BL. I notice that other cables listed as being compatible with SSMII are using the FT232RQ chip. I wish I knew enough about all this to be able to tell whether their differences are significant here. Another issue might be the degree to which the FTDI chip itself is programmable - perhaps it needs some customisation in order to work with SSMII?

The reason I ask is that I'm trying to make an interface to suit my non-OBDII compliant MY02 Outback, so I'm thinking of using your approach but with the FT232RQ chip instead (http://shop.4dsystems.com.au/usb-to-ser ... -2002.html). Any help would be much appreciated.

Adam

Stig · Post by **Stig** » Fri Jan 25, 2013 7:04 pm

Hi Guys,
it seems you guys solved the obd2 compliance issue IS it or is it no compliant to obd2

if i dont have that sensor on the air box means 100% non obd2.?
i realley need to hear it as im stubborn as and i keep hoping.

my car is a 1/99 build liberty gen3 wagon with a NA ej251 motor,
for the record does NOT have that sensor coming out of airbox, IT does have pin 7 on obd2 plug

so what you guys want is
SSM Baud Rate 1953 ssm asyncronous serial com for communicating in ssm i belive

i dont know if you guys seen this

http://www.alcyone.org.uk/ssm/index.html

my pin settings are on the obd2 plug on car

pin:
16 always +12v
15na
14 na
13 is there ecm to ssm apparenly
12 ssm ssm to ecm
11 ssm pulse
10 na
9 na
8 pin is there but unsure to what
7pin k-line apparently, not sure what it does on mine yet
6 na
5 signal ground
4 Ground
3na
2na
1na

ill add info as i find it ,would be nice to see some definate answers out there as its all a bit hazy with fact answers for us AU Subaru drivers and OBD2 support, has subaru done a dirty on us? send us old parts back in 98/99/2000 ? lol

Thanks
Stig

Gannon · Post by **Gannon** » Sat Jan 26, 2013 7:57 am

There were no Gen3 (1998 - 2003) 2.5L Liberty/Outbacks that had OBDII in Australia, nor did they have an IAT sensor.
The Gen3 H6 and twin turbo B4 had both OBDII and an IAT sensor.

I havent had time to play with SSM since this thread, but it is on my long term list of projects

NachaLuva · Post by **NachaLuva** » Sat Jan 26, 2013 12:55 pm

Gannon wrote: it is on my long term list of projects

Dont ya hate those lists...I have one too...& its getting longer!

RSR 555 · Post by **RSR 555** » Tue Feb 12, 2013 1:32 pm

Gannon wrote:I havent had time to play with SSM since this thread, but it is on my long term list of projects

Damn.. I was going to ask how it was going. Would love to hear solved solution.

alisoncc · Post by **alisoncc** » Fri Apr 05, 2013 9:52 am

Need to pick up a low cost OBD II code reader ASAP. A while back tried an Autel MS509, which seemd to work intermittently, now looking at the AL519 off ebay for $120. Apparently item located in Melbourne. Anyone had any success with this unit?

Driving a MY04 Gen04 Outback. Apparently there were some issues with pre-2006 subbies and OBDII in Oz. Looked at a few of the code reader variants, need something stand-alone to chuck in the glove compartment and retrieve when necessary, rather than all the other possibilities. Any advice appreciated.

The AUSubaru.com.au Forums

Engine code reader pre OBD II

its a shame to see this die