OP
OP
Something like that - and before you ask let me tell you it's hardware authenticated (tied to the laptop you install it on) 
Technical Anyone had any success with an ELM323/327 interface
- Thread starter Argonought
- Start date
-
- Tags
- ecu elm323 elm327 maf
Currently reading:
Technical Anyone had any success with an ELM323/327 interface
then im in the same situation as you. interface detected, atsi 'ok', atfi 'error'
lets hope they make fast progress. did they tell you what protocol the car uses?
so this means that the software needs to be configured to turn the garbage results into readable figures and that is what current software seems to do.
lets hope they make fast progress. did they tell you what protocol the car uses?
so this means that the software needs to be configured to turn the garbage results into readable figures and that is what current software seems to do.
If I were you I'd ditch the ELM altogether. The ELM in theory should be able to connect without any software at all. You can use hyperterminal. The KWP2000/ISO14whateveritis interpretation is done on a PIC processor in the cable itself (which im sure you all already know). So if that chip cant talk to your ecu your stuffed.
There is some little known software called unidiag, this apparantly can talk to the edc15c7 ecu that is present in some Stilo JTD's using a definition file for the edc15c5 which is used in the Alfa 166. This works with a "dumb" cable, something without an interpreter chip, and the protocol interpretation is done on the computer itself, rather than the cable.
Ive had it working with my Punto HGT Euro2 and up until now nothing would talk to it. I built a very simple cable to do this (cost about 60pence) plus the price of the OBD connector.
It might be worth looking up the particular model of your ECU to see if it uses both a K and an L line, as AFAIK most fiats 97-2001 (pre OBD2) just used the K line.
Regards
There is some little known software called unidiag, this apparantly can talk to the edc15c7 ecu that is present in some Stilo JTD's using a definition file for the edc15c5 which is used in the Alfa 166. This works with a "dumb" cable, something without an interpreter chip, and the protocol interpretation is done on the computer itself, rather than the cable.
Ive had it working with my Punto HGT Euro2 and up until now nothing would talk to it. I built a very simple cable to do this (cost about 60pence) plus the price of the OBD connector.
It might be worth looking up the particular model of your ECU to see if it uses both a K and an L line, as AFAIK most fiats 97-2001 (pre OBD2) just used the K line.
Regards
OP
OP
To be honest mate I'm pretty much through with ideas of this and that might work
but if someone has an idea they've tried and know it works then great - lets hear more about it What's important is we have a solution to this at last (at least in terms of reading/clearing codes) so that's where I'm sticking for now
OP
OP
That's right Frank (although it's more a case of talking with different codes which are not part of OBDII rather than actually converting anything). In the end it's all down to the software so as it works on mine then it must work with your 05 JTD.
You'd then have proof your JTD is NOT OBDII complaint which would take some explaining :chin:
I'm really puzzled by this - I was able to connect a generic ebay 323 USB unit to my 04 JTD and all the outputs appeared to be correct.
My device is currently on loan to stilosporting, but as soon as it comes back (no hurry) I'll set it up again and re-check. I'll closely detail all the settings and outputs, and report them here with screenshots etc.
My device is currently on loan to stilosporting, but as soon as it comes back (no hurry) I'll set it up again and re-check. I'll closely detail all the settings and outputs, and report them here with screenshots etc.
It's not the year your car was registered in the UK but the year your car was built that is the deciding factor as to whether you have EOBD (OBD2) or Fiat's own OBD
For instance, i have a 1999 Bravo which is Fiat OBD1 if you like and if you try to talk to that using OBD2 you'll just get eng temp 215, a bit of fuel trim bank info and that's about all. Pretty much the same output as people trying to connect their pre OBD2 JTD's. To get a PC to talk to Fiat OBD1 I think you'd need to wire up your own interface plug and possibly go back to basics with commands and some fancy circuitry to "wake up" the ECU to give out its information.
The information is in there, in the ECU, but without the right connections and software, it's not going to talk to you
Could have a look here in the Cinquecento section
https://www.fiatforum.com/cinq-sei-technical/32328-6f-16f-cinque-sei-ecu-reader-project.html
For instance, i have a 1999 Bravo which is Fiat OBD1 if you like and if you try to talk to that using OBD2 you'll just get eng temp 215, a bit of fuel trim bank info and that's about all. Pretty much the same output as people trying to connect their pre OBD2 JTD's. To get a PC to talk to Fiat OBD1 I think you'd need to wire up your own interface plug and possibly go back to basics with commands and some fancy circuitry to "wake up" the ECU to give out its information.
The information is in there, in the ECU, but without the right connections and software, it's not going to talk to you
Could have a look here in the Cinquecento section
https://www.fiatforum.com/cinq-sei-technical/32328-6f-16f-cinque-sei-ecu-reader-project.html
Last edited:
The protocol used isnt the same as the Cinq/Sei 16F ECU, as this actually outputs some code at 1200baud when you switch the ignition on, then switch to 7812.5bps I think.
the 97-2001 Fiats use KWP2000 but do not have an L line. The INIT command is sent down the K Line at 5 baud(slow init), then comms resumes at 10,400baud. ELM interfaces INIT down the L line then do the 10,400bps comms down the K line. AFAIK the ELM sends a 0x33 as the wake up command but most of these fiats you are talking about will want a 0x10 command.
There are Fiat technical documents floating around that explain it all.
Ive had a simple interface going with a few different fiats, using some some software called unidiag or KWP2000 test, you can get it from the authors yahoo group. Its free. http://autos.groups.yahoo.com/group/unidiag/ You can also write definition files for different cars so its pretty customisable!
Ive had it working with a 03 stilo JTD, Fiat Punto HGT W REG '00 and a '00 reg Punto sporting.
The only thing is it doesnt work with the elm interpreter cable, it only works with a simple level shifter cable. The design I used was designed by someone called will hoult (http://forzavx.com/gecu/monitor/tutorial-monitor.html), costs about £1 to build + the price of the connector - I just merged the K & L Lines together so all the comms happened down K Line,.
I know you want definative answers but there really isnt much about for cars of this era - nothing was properly standardised. Ive been messing around scratching my head for months, just to get where I am, which is no where near a ELM type solution
Dan
the 97-2001 Fiats use KWP2000 but do not have an L line. The INIT command is sent down the K Line at 5 baud(slow init), then comms resumes at 10,400baud. ELM interfaces INIT down the L line then do the 10,400bps comms down the K line. AFAIK the ELM sends a 0x33 as the wake up command but most of these fiats you are talking about will want a 0x10 command.
There are Fiat technical documents floating around that explain it all.
Ive had a simple interface going with a few different fiats, using some some software called unidiag or KWP2000 test, you can get it from the authors yahoo group. Its free. http://autos.groups.yahoo.com/group/unidiag/ You can also write definition files for different cars so its pretty customisable!
Ive had it working with a 03 stilo JTD, Fiat Punto HGT W REG '00 and a '00 reg Punto sporting.
The only thing is it doesnt work with the elm interpreter cable, it only works with a simple level shifter cable. The design I used was designed by someone called will hoult (http://forzavx.com/gecu/monitor/tutorial-monitor.html), costs about £1 to build + the price of the connector - I just merged the K & L Lines together so all the comms happened down K Line,.
I know you want definative answers but there really isnt much about for cars of this era - nothing was properly standardised. Ive been messing around scratching my head for months, just to get where I am, which is no where near a ELM type solution
Dan
Last edited:
thank you for your input.
hopefully we will find a solution.
hopefully we will find a solution.
Just got an ELM327 for my 53 plate Stilo JTD 115 and it works fine as far as I can tell (I'm using proscan with it which autodetected the car instantly). Can read error codes, show coolant temp, engine rpm, air intake temp, and loas of other stuff! Really pleased with it!!
If anyone needs any configuration information or anything else I am happy to help, or if anyone in the Whitley Bay area wants to test to see if it works then just pm me.
P.S. Does anyone know if the horsepower tests work using proscan as mine shows bang on 115 just want to know if it calculated them correctly and if the 0-60 speed tests work.
If anyone needs any configuration information or anything else I am happy to help, or if anyone in the Whitley Bay area wants to test to see if it works then just pm me.
P.S. Does anyone know if the horsepower tests work using proscan as mine shows bang on 115 just want to know if it calculated them correctly and if the 0-60 speed tests work.
OP
OP
What version of ProScan are you using?
how do you fancy a road trip? lol
im near pontefract but would like to try it out on my jtd so could meet you halfway somewhere? will of course pay for an non/alcoholic beverage
my thoughts are though that it wont work but it is worth a try.
Version 5.3
how do you fancy a road trip? lol
im near pontefract but would like to try it out on my jtd so could meet you halfway somewhere? will of course pay for an non/alcoholic beverage
my thoughts are though that it wont work but it is worth a try.
Might be passing your way on my way to Norfolk on Friday night it will probably be around 6:30ish, could meet up at Ferrybridge.
do you have an update on the gendan software?
the one day i cant make it lol. might be done for that time but cant guarantee it
what day are you coming back?
Sunday evening but not sure what time yet.
OP
OP
Nothing yet - can still only read/clear fault codes.
OP
OP
For something to do have just tried this on mime :idea:
The ProScan software does indeed connect first time and reports OBDII compliance but be warned it may be lying.
On mine it states NO faults codes (wrong) and also reports water temp of 415°F which is standard nonsense reading to indicate lack of compliance.
Fortunately the Gendan software, on the same laptop, is able to read the correct fault codes.
how frustrating is this!!!! :bang:
