Peugeot Forums banner

1 - 11 of 11 Posts

·
Registered
Joined
·
182 Posts
Discussion Starter #1
Is there anyone or someway to connect to the ECU on the older type Peugeot using the small cheap-o bluetooth ODB2 diag readers.

From what I understand its about the protocols but if you are in hyperterminal connected to the Com port is there no way the AT commands will comunicated with it.

I know there is AT commands for the ELM327
https://cdn.sparkfun.com/assets/c/8/e/3/4/521fade6757b7fd2768b4574.pdf

Do they just not work becuase they dont have the protocol? Do they really need it? anyone wise on this stuff? If so what set of communication do they use?

more related reading.
https://en.wikipedia.org/wiki/OBD-II_PIDs
https://www.elmelectronics.com/wp-content/uploads/2017/01/Prog_Parameters.pdf
https://www.elmelectronics.com/wp-content/uploads/2016/07/ELM327DS.pdf
https://forum.arduino.cc/index.php?topic=435701.0
https://burakalakusen.wordpress.com/2011/07/27/to-get-obd2-data-via-elm327-c/
Peugeot Partner (2006) and ELM327 - MP3Car.com
https://theksmith.com/software/hack-vehicle-bus-cheap-easy-part-1/
How to interface with your car’s ECU through OBD2 and Python | Brian Hemeryck
ELM327 & Hyperterminal - MP3Car.com
Peugeot OBD II diagnostic connector pinout diagram @ pinoutguide.com
Peugeot (106, 206, 207, 306, 307, 308, 3008, 5008) compatible ELM 327 and OBD2
https://www.autoitscript.com/forum/topic/128546-serial-port-com-port-udf/
https://www.scantool.net/forum/index.php?topic=4632.0

The reason I ask is becuase I want to make my own program just to read fault codes.

Thinking Autoit as its easy
https://www.autoitscript.com/forum/topic/128546-serial-port-com-port-udf/

Anyone?
 

·
Registered
Joined
·
14,567 Posts
Peugeots use a different protocol to other manufacturers thats the main reason other stuff cant read them well.

It is the car thats the problem really not the diagnostic gear
 

·
Registered
Joined
·
182 Posts
Discussion Starter #3 (Edited)
Peugeots use a different protocol to other manufacturers thats the main reason other stuff cant read them well.

It is the car thats the problem really not the diagnostic gear
from what I am reading during the AT command in hyerterminal you have to tell the ELM327 what protocol to use. OK so on scantool site I found someone using this protocol on a 307 and said it works but failed to say what year car his was :(

kwp2000 protocol (ISO)

From what I know diesels extra only started following ODBII after 2004 or something like that...

Right now my suspiction is triggered with some software called "engine check LE" there is a setting what allows you to force connect to the ECU.

But sadly it only says what the battery voltage is, It seems to be reading something as it looks to be reading fault codes but comes back with notthing

I am wondering if the software just does not know how to interpet the data and displays nill.

Perhaps it does not come back with hex code?

Never the less I really want to test this and see if anyone else has had a go?

PS. it may be the diag gear too it seems if they dont have the protocols on them, but again on another site the guy said they had to lower the broad rate of the com port and on another site it said to be using "KWP SLOW" as a protocol?

ISO14230-4 (KWP2000)
ISO14230-4 KWP (5 baud init, 10.4 Kbaud) IS IT THIS ONE?
ISO14230-4 KWP (fast init, 10.4 Kbaud)
 

·
Registered
Joined
·
14,567 Posts
Thats my point peugeots are hard to read its not worth the fight when planet is easily available and when looking at diesels you NEED to see live data as codes dont tell you enough
 

·
Registered
Joined
·
182 Posts
Discussion Starter #5 (Edited)
Thats my point peugeots are hard to read its not worth the fight when planet is easily available and when looking at diesels you NEED to see live data as codes dont tell you enough
acording to the elm327 there is a option to read live data.
It shows you what buttons you pushng extra. So the function might be there. Just how to manipulate. ;)
Anyhow just want fault codes, no intention on building some huge program.

I will see what I can connect and read tomorrow. But I fear..... ZEROOoooooo :lol:
 

·
Registered
Joined
·
182 Posts
Discussion Starter #6
So had the odb2 in and used android terminal app. I get to speak with the odb2 device. Connected there fine but any commands to the ECU come back with error.

This makes me wonder if the data pin configuration is some place else. Power seems fine.

Will need to do more investigation
 

·
Registered
Joined
·
182 Posts
Discussion Starter #7 (Edited)
Ok

So after much research it seems the blue tooth dongles CAN communicate on PIN7 K-line.

This document explains what each pin does in the older peugeots
(I have a 307 2.0 HDI diesel 2001)

http://www.evoscan.com/technical-vehicle-manuals/132-peugeot-obd-ii?format=pdf

But as you can see the cheap chinese bluetooth dont use all the pins and some pins are one protocol and other diffeent. What this means is that only pin 7 on the dongle actualy connectes, this is OK as you only need one pin to read the busline aparently. But only Engine and transmission diagnostic the rest is not possible.

Attention! "Bad" Bluetooth adapters! - Page 4 - Bluetooth / WiFi OBD-II adapters - OBD Car Doctor Forum: ELM327 WiFi adapter, ELM327



Pin 7 - Engine and transmission diagnostic

some more on the cheap dongles
http://www.fadvisor.net/blog/2015/02/inside-a-fake-elm-327/

As you can see pin 4,5 are ground and 16 is power. this is why the odb device works as its correct.
on another side the voltage AT check does work and it will show 12.3 volts when the car is off and 14v when running.
 

·
Registered
Joined
·
182 Posts
Discussion Starter #8 (Edited)
So after more searching it seems the protocol in quistion is KWP or KWP2000
the ISO are named ISO 9141-2 / ISO 14230-4 K-line and operate on VAN bus not CAN

So while most AT commands will work on the bluetooth dongle once you connected... the problem comes when you want to talk to the ECU.

In most it seems you have to pack a header and send it to the ECU and wait for a response. Something like this

Here is a good AT documemt
https://www.scantool.net/downloads/98/stn1100-frpm.pdf

I found allot of awnsers here but lacked allot more
Raspberry Pi Car-puter – Ant's Blog
Use google translate
Toyota Corolla E11 Diagnose über OBD
ODB II » Tech Toy Hacks
http://tunertools.com/prodimages/obdpros/manuals/obdpro_datasheet.pdf
 

·
Registered
Joined
·
182 Posts
Discussion Starter #9
I did manage to find that allot of cars and older ones DO WORK IN TORQUE PRO. It meant putting a custom initiation in the vechale profile
But sadly none work on my 307

Read below google translate from a russian site
Настройка подключения ELM 327 к старым автомобилям | Специализированный магазин электроники по низким ценам

"Configuring the connection to the ELM 327 old cars
July 13, 2016 Aleksei Eremenko
Solve connectivity problems some cars

Some cars are not 100% compatible with the OBD2, but Torque program can contact them if ELM327 adapter is configured in a certain way.

The problem lies in the small difference OBD2 protocol used for car diagnostics.

This problem is eliminated by the addition of the initialization string in Torgue programs.

And so, the initialization string to manually ELM327 adapter to connect to such vehicles. If you can not connect to the vehicle control unit in automatic mode, you may need to enter the initialization string.

So, let's see how to make ELM327 adapter to work with us to correct initialization string.

1. First you need to find the initialization string in the list below.

2. Go to the Torque program and create a new profile.

3. In the settings you set up a profile at the bottom, we write our initialization string, click the Save button.

stroki_inicializacii_3stroki_inicializacii_4

For the majority of right-hand drive Toyota prescribe string enough: ATSH8213F1 ATIB96 ATIIA13

Initialization strings ELM327:

Toyota Celica ZZT230

ATIB 96 \ n ATIIA 13 \ n ATSH8113F1 \ n ATSP A4 \ n ATSW00

Toyota Caldina 1998

ATIB96 \ nATIIA13 \ nATSH8113F1 \ nATSP4 \ nATSW00

Toyota Fielder 2005

ATIB96 \ nATIIA13 \ nATSH8113F1 \ nATAL

Toyota Vitz 01.2002

ATSH8213F1 \ n ATIB96 \ n ATIIA13

Toyota Hilux Pick Up 2006

ATIB10 \ nATIIA10 \ nATSH8110F0 \ nATSPA5 \ nATSW00

Toyota Mark 2, Toyota Aristo 161

ATIB96 \ nATIIA13 \ nATSH8113F1 \ nATAL

ATIB96 \ nATIIA13 \ nATSH8213F1 \ nATE0 \ nATAL

ATIB96 \ nATIIA13 \ nATSH8113F1 \ nATSP4 \ nATSW00

Toyota Japan for the domestic market ISO9141

ATSP3 \ nATAL \ nATIIA33 \ nATIB10 \ nATSH686AF1 \ nATST32 \ nATSW00

Toyota for the domestic market in Japan Common

ATIB96 \ nATIIA13 \ nATSH8113F1 \ nATSPA4 \ nATSW00

Toyota Japan for the domestic market 10400baud

ATIB10 \ nATIIA13 \ nATSH8013F1 \ nATSPA4 \ nATSW00

Toyota for the Japanese domestic market CAN mode21

ATSP6 \ nATAL \ nATSH7E0 \ nATCRA7E8 \ nATST32 \ nATSW00

Toyota GT86

ATSP6 \ nATAL \ nATSH7E0

Toyota Nadia / Harrier for the domestic market in Japan

ATIB10 \ nATIIA13 \ nATSH8013F1 \ nATSPA4 \ nATSW00

ATIB96 \ nATIIA13 \ nATSH8213F1 \ nATSPA5 \ nATSW00

Toyota Sienta 1NZ-FE (CVT)

atspa4 \ atib96 \ atiia13 \ atsh8113f1 \ atst32 \ atsw00

Toyota Allex 2002 1nz-fe 4WD automatic transmission

atspa4 \ natib96 \ natiia13 \ natsh8113f1 \ natst32 \ natsw00

Toyota Passo KGC1 (1KR-FE)

atsp5 \ natsh8110f0 \ natfi

Nissan for the domestic market in Japan

ATSP5 \ nATAL \ nATIB10 \ nATSH8110FC \ nATST32 \ nATSW00

VAZ January

ATSP5 \ nATAL \ nATIB10 \ nATSH8110F1 \ nATST32 \ nATSW00

VAZ January 5.1.1

ATSP5 \ nATIB10 \ nATSH8110F1 \ nATST10 \ nATSW00

VAZ January 7.2 Euro 2

atal \ natsp5 \ natib10 \ natsh8110f1 \ natst32 \ natsw00 \ atfi

VAZ Bosch MP7

ATSP5 \ nATAL \ nATIB10 \ nATSH8111F1 \ nATST32 \ nATSW00 \ nATFI

VAZ Bosch 797

ATFI \ nATAL \ n

Volkswagen Caddy 1.9I 2006 diesel (KWP2000)

atsp5 \ natib10 \ natsh8110f1 \ natst10 \ natsw00

Renault Scenic RX4 2002 Diesel

atsp5 \ atal \ atib10 \ atsh817af1 \ atst32 \ atsw00

GREATWALL Delphi MT20U2_EOBD

atal \ natib10 \ natsp5 \ natsh8111f1 \ natst10 \ natsw00

SSANGYONG KYRON ISO 14230

ATSP5 \ nATAL \ nATIB10 \ nATSH8110F1 \ nATST32 \ nATSW00

SsangYong 2.3 MSE gasoline (Kyron, Rexton, Action, Musso , Korando)

atsp5 \ natib10 \ natsh8101f3 \ natst32 \ natsw00

Daihatsu Terios Kid 2002

ATIB10 \ nATIIA10 \ nATSH8110F0 \ nATSPA5 \ nATSW00

Fiat Pre-OBD

ATSH 8110F1

Mitsubishi MUT

ATSP0 \ nATAL \ nATIB10 \ n

Tiggo Delphi MT20U

ATSP5 \ nATAL \ nATIB10 \ nATSH8111F1 \ nATST32 \ nATSW00

Chery Tiggo Delphi system 2.0L / 2.4L ( 4G63 / 4G64)

atal \ natsp5 \ natib10 \ natsh8011f1 \ natst10 \ natsw00

Delphi MR240

ATSP5 \ nATAL \ nATSH8111F1 \ nATWM8111F13E

Siemens ACR167 KWP

ATSP5 \ nATAL \ nATSH8111F1 \ n81 \ n

Sirius D42

ATSP5 \ nATAL \ nATIB10 \ nATSH8211f1 \ nATST32 \ nATSW00 \ nATFI

UAZ 1797

ATSP5 \ nATAL \ nATSH8110F1 \ nATFI

UAZ Patriot Bosch m17.9.7

ATZ \ nATSP5 \ nATIB10 \ nATSH8110F1 \ nATSW00

Opel KWP2000

ATSP5 \ nATAL

OPEL Vectra Simtec 56.5

ATSP5 \ nATSH8111F1 \ nATSW00

ABS MK70 (Geely and others. Car with unit)

atal \ natsp4 \ natiia83 \ natsh8128f1 \ natst10 \ natsw00

Lifan Solano ABS (Mando)

ATSP5 \ nATSH8028F1 \ nATWM8028F1021081 \ nATFI

Lifan Solano ABS (Wanxiang)

ATSP5 \ nATSH8128F1 \ nATWM8028F1021080 \ nATFI

BYD F3

ATSP5 \ nATSH8111F1 \ nATSW00

BYD F3 ABS

atsp5 \ natsh8128f1 \ natfi

Dacia Logan 1.4 2007

ATSP5 \ nATSH817AF1"
 

·
Registered
Joined
·
182 Posts
Discussion Starter #10
another site surgested these but it also did not work in torque pro


307 OBD Bluetooh - ForoCoches

tell you how it is done in Torque pro (for other programs, you're worth the same heading but I do not know the steps you have to follow).

1º Open torque, press the "menu" key of our device and click on "Vehicle profile".

2º Click on "Create new profile"

3º You go filling all the data, you can invent all but the last ones , which are the ones that I'm going to tell you.

4º We marked " Use alternative OBD header "

5º In protocol we chose "Automatic - Thorough protocol"

6º In the last field we write this AS IS: ATSP5 \ n ATSH 8110F1 it is very important to respect capital letters, lowercase letters and all the characters !!!
If you do not have that string you can try ATSP5 ATSH 8111F1 or ATSP5 ATSH 8112F1
 

·
Registered
Joined
·
182 Posts
Discussion Starter #11 (Edited)
So of i went and installed ODB bluetooth Terminal on my phone and started the AT commands



https://play.google.com/store/apps/details?id=com.app.elm327terminal

The app is nice and connects to the ODB device over bluetooth.
I issed commands and all fine.
Set protocol 5 and all still good.

I then issued a command ATSH811A80

the header 81 1A 80

this is how a OPEL would respond
Format 81 (Start Comms, as per below)
1A ecuID followed by 1 byte:
80 - complete table.
1A 80 response:
5a 80 [3-21]VIN [22-37]ECUhardwareno [38-57]sysSupplierECUSW [58-72]Engine [73-79]repairshopCode [80-89]progDate [90-97]vehManECUID
5A 90 91 92 93 94 98 9f

acording to Raspberry Pi Car-puter – Ant's Blog

But all I get back from the ECU is >ok

>ok

nothing else?

So now my search will lead me to finding out how the peugoet talks to the ECU as many people say the KWP2000 is rather large and varies from vendor to vendor.

Well its something... last time all I got back from the ECU was error, and thats becuase it does not comply to standard PID's.. well that is what it seems at the moment.
 
1 - 11 of 11 Posts
Top