Technical Anyone had any success with an ELM323/327 interface

Currently reading:
Technical Anyone had any success with an ELM323/327 interface

Seraph, you seem to be well into serial comms. (y)

Have you tried the ATFI command as mentioned in posts #17 & #27 yet ?

I had a go with the ATFI settings in the first place, but it wont even connect...and I've tried porting to see that it is connected (and it isn't).
ironically, the first time I installed it, windows gave me some ATFI only drivers... So i'm thinking the interpretation is slightly off... I might give the www a bit of a scan for some better or customer drivers, but then it doesn't explain why the only car with a problem is the JTD.
 
Last edited:
I tried a while ago to get my JTD to connect to a laptop, but without success. I thought they used CAN bus though, not ISO. There is some information on the net. A few posts on www.canhack.de about stilo's, but it is in mostly in german, but can be translated.
 
Last edited:
I had a go with the ATFI settings in the first place, but it wont even connect...and I've tried porting to see that it is connected (and it isn't).
ironically, the first time I installed it, windows gave me some ATFI only drivers... So i'm thinking the interpretation is slightly off... I might give the www a bit of a scan for some better or customer drivers, but then it doesn't explain why the only car with a problem is the JTD.
ATFI is simply a command (in ASCII) you give to the ECU. If should reply "BUS INIT: OK" (see post #17)

Of course if you can't connect to the ECU then it also means you can't 'talk' to it :(

It seems Frank's problem might be different to mine as I CAN talk to the ECU. The problem is the ECU replies "NO DATA" to almost everything and what DATA it does provide is rubbish :bang:
 
Last edited:
ATFI is simply a command (in ASCII) you give to the ECU. If should reply "BUS INIT: OK" (see post #17)

Of course if you can't connect to the ECU then it also means you can't 'talk' to it :(

It seems Frank's problem might be different to mine as I CAN talk to the ECU. The problem is the ECU replies "NO DATA" to almost everything and what DATA it does provide is rubbish :bang:

i think your getting confused with my issue and what we are trying.

when we use auto detect then it communicates but with gibberish or 'no data'. (exactly the same issue as you) then when we trial other connection types it wont connect.

after looking on the net i have found about 5 different conversations about the jtd not working correctly with these types of interfaces. the down side is no-one yet has given a good answer or found a solution.

so it looks like it is the stilo jtd across the range not just mine and yours. :(
 
I tried a while ago to get my JTD to connect to a laptop, but without success. I thought they used CAN bus though, not ISO. There is some information on the net. A few posts on www.canhack.de about stilo's, but it is in mostly in german, but can be translated.

the CAN-network in the Stilo is not used for OBD2 purposes - so with a obd2 interface you will only be able to connect to the K-line of the motor-ecu using the KWP2000 protocol.
However it is possible to do some (non-OBD) diagnosis on the other CAN-nodes on the network but you will need the proper hard-and software plus the right codes to achieve this.

yellowstilo
 
ATFI is simply a command (in ASCII) you give to the ECU. If should reply "BUS INIT: OK" (see post #17)

Of course if you can't connect to the ECU then it also means you can't 'talk' to it :(

It seems Frank's problem might be different to mine as I CAN talk to the ECU. The problem is the ECU replies "NO DATA" to almost everything and what DATA it does provide is rubbish :bang:
OK, might have overstated this a bit.

I can certainly talk to the ELM interface OK (with "ATZ") but if I ask the ELM interface to connect to the ECU with ATSI (10.4k baud Slow Interface) or ATFI (Fast Interface) then in both cases I get "BUS INIT: ERROR".

In other words it would seem the ELM interface can't talk to the ECU after all.

I've tried both an ELM323 and ELM327 and both fail so guess it can't be the interface (or at least very unlikely :chin:)
 
If it's any help they have found the same problems in France, they can read eng temp static at 215 and rpm is the figure divided by 4 but that's all.
They reckon that for Stilo diesels pre 2004 you're "cooked" for OBD
Someone believes older models didn't change til 2004 but the newer style models may have it at 2003. They have a lot of diesels over there as you can imagine

Make of it what you will but it might stop somebody going mad
 
Last edited:
If it's any help they have found the same problems in France, they can read eng temp static at 215 and rpm is the figure divided by 4 but that's all.
Spot on Decks, this is EXACTLY what I can read (y)

It's totally weird. I can't seem to initialize the ECU bus but I CAN read some data (as above) :bang:

I think you'll find they can also read airflow via the MAF sensor but very difficult to know just how reliable these reading are :(
 
totally bizzare considering most software are listing the punto 1.9 diesel and the alfa 147 diesel as compatabile. they and the stilo are rather similar
 
ok more info on the obd-diag 4000

modes / protocols

ISO9141-2
KWP2000 slow init
KWP2000 fast init
PWM
VPWM
CAN 11bit/250kB
CAN 11bit/500kB
CAN 29bit/250kB
CAN 29bit/500kB
K/L transit mode
KK/L transit mode

99.99 euro from www.obd-diag.de/

what do we think??? it was this tool that listed the punto jtdM 2005 as compatible?
 
I have an OBD-Diag 4000. I dont think they are very good. Lots of compatibility issues. I have not got it to work on any Citroen or Fiat cars yet. Ford / Mazda, VAG (not can bus) and Vauxhall seems to be OK though. CAN bus seems to be compatible with nothing.
Very limited support/ help, except if you speak german.
 
Back
Top