Anyone had any success with an ELM323/327 interface

Im not looking for code reader/cleaner because this I can do with normal softwares... I can connect with all ELM softwares to car and read/clean codes normaly... Problem is reading parameters like rpm, temperature, speed, air flow... I need interface which can do this. For RPM I can build own application which multiply value from OBD by 4. But speed I can't fix because when I have speed 0 show 0 when I drive show 255 also temperature show allways same I dont remeber how but I think show 120°C if car is cold or hot...

That's very interesting

Based on what you just said, your JTD is NOT OBDII compliant (at least based on my testing)

How are you managing to clear codes and what software are you using to do so

Im try connect to OBD trought hyperterminal and send code and wait for answer then Im convert from HEX to DEC and Im receive same values than in any software that Im try(Scan Tool, ScanMaster and a lot of other which I don't remeber now...) All give me same values...

Then Im reproduce Error on engine and check error code and Im see one error, then Im clear code and read again and code has been cleared I think that Im do with Scan Tool. Then Im on local fiat service ask if can find any error code and he didn't find it...

You seem to be making a fair bit of headway on this (have you read the whole thread?)

Any chance of listing the full command list you're using?

Im not read whole thread because there is a lot of post... But in future I will read it...

Yesterday Im delete all my OBD programs and data because Im sell device...
I have only this PID codes:
LINK

I hope that this will help you

Hello,

I build the interface.
Installed the UniDiag program.
Selected the Alfa 166 or so configuration file.
No connection with my Fiat ECU.

Unless I do something wrong I am afraid this is also not the solution for our problems.
For the wrong calculations like RPM, I can make new a program to correct this.
But the one’s like speed, that only give 0x00 or 0xFF there is no solution in that.

Dan,
Any suggestions about possible error I make in connecting via the UniDiag program?
Can you tell us where to find these documents describing the protocol?

Unless there are good suggestions I let it rest a while before I get mad.


Hans.

@Oldman

Do you get any data back at all, any keybytes? When setting up the comms settings make sure the DTR box is checked, this powers the circuit and must be ticked.

Also, check what the logfile says, you will have to scroll to the bottom of the window as it doesnt do this automatically.

My punto hgt works with those settings, i also had to connect tx and rx together and wire them to the kline pin on the odb connector as it doesnt have an L line I believe.

Let me know how you get on and Ill see if I can help.

Regards

Dan

Hi all,

Well, I think my car has a L line.
Splitting the K and L did not work.
So I think I have to build another interface, my third one.
If I get in the mood, next week more news.

Stilo's don't use the L-line.... this was only used until 1997/98 to wake up the ecu - the rest of the communication was done over the K-line.
On the later models from 97/98 onward only the K-line was used for wake-up and communication .

Hi, got my Elm327 today and connected to my 2.0 jtd 2004.Various programs seem to talk to ecu ok but dont tell me much.
So i used the terminal interface it tells me i have 1 fault so i ask what the fault is ie, 03 and i get 43 00 00 00 which seems to me to mean no fault?
I can reset the MIL light but it returns when i start the engine.
When i used monitor mode the airflow and rpm change with the throttle.

I did a scan with wobd and get the following;
Thursday, August 07, 2008 02:56 PM
Header: 686AF1 Mode:01-01 Pid:00-FF Suffix:
X 0100 SEARCHING...
V 0101 81 03 81 00 [....] 2164490496
V 0104 00 [.] 0
V 0105 FF [.] 255
V 010B FF [.] 255
V 010C 00 00 [..] 0
V 010D 00 [.] 0
V 010F FF [.] 255
V 0110 00 18 [..] 24
V 0111 00 00 [..] 0
V 011C 05 [.] 5
Scan Completed
Events(s):256
No Data:245
Invalid:1
Zero:4
Does this mean anything?

I'd recommend you try digimotolite.

It's a free download and should indicate straight away if your JTD is compliant or not (the full version is quite nice too)

Tried Digimotolite no improvement.Does anyone know
exactly how many parameters are in theory readable from the 2.0 jtd in a 2004 ducato.
I found copies of the full fiat ecu specifications but as yet they seem to confirm the commands i am using to obtain info.
Here they are in case anyone needs them.

Useful info but at the end of the day your JTD isn't OBD compliant so all those generic access programs are a waste of time (I presume you've read the whole thread)

Hello,

UniDiag should work with the Stilo JTD (old and new). It does use exactly the same protocol as the Examiner, which is indeed different to the generic OBD protocol.

Kind regards, Sander.

From what have I seen on the service the Examiner conects to the OBD interface next to the fuse box, from inside the car, driver's side. I have found the PINOUT of the OBD connector on andywhittaker.com website and it seems that it also has connections for the CAN Interface.

CAN Protocol Pins
If pins 5, 6, 14 and 16 are populated, the vehicle supports CAN.
Pin # Description
5 Ground
6 Data
14 Data
16 Power

ISO and KWP Protocol Pins
If pins 5, 7, 16 and, optionally, 15 are populated, the vehicle supports ISO or KWP.

Pin # Description
5 Ground
7 Data
15 Data (this pin is optional and may not be present)
16 Power

VPW Protocol Pins
If pins 2, 5 and 16 are populated, the vehicle supports VPW.

Pin # Description
2 Data
5 Ground
16 Power

PWM Protocol Pins
If pins 2, 5, 10 and 16 are populated, the vehicle supports PWM.

Pin # Description
2 Data
5 Ground
10 Data
16 Power

There are some CAN scanners softwares around the internet, but my questions is if this will work with the ELM interface in case i resolder the pins on the OBD interface side.