Announcement

Collapse
No announcement yet.

Peugeot Partner (2006) and ELM327

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Peugeot Partner (2006) and ELM327

    I have a homemade ELM327 scanner I have successfully used with several cars. I want to use it with a Peugeot Partner (2006) to read vehicle speed, RPM, etc, but I can't find the way. I have tried ScanMaster-ELM and the only way I found for it to connect to the ECU is to press the "Alfa" button of the start tab and in the opened dialog then select "Engine" and then "Connect". If I connect this way I can only read trouble codes, but I can't read RPM, speed, etc.

    Using a Serial Port Sniffer, I read the commands used to connect and I have emulated it myself using Hyperterminal. I can connect this way:

    Code:
    Tx: ATSP5
    Rx: OK
    Tx: ATSH8110F1
    Rx: OK
    Tx: ATWM8110F13E
    Rx: OK
    Tx: 81
    Rx: BUS INIT: OK
    Rx: 83 F1 10 C1 D0 8F A4
    From this point I don't know how to read data. Using the standard commands (like 0100) gives me only strange data, for example:

    Code:
    Tx: 0100
    Rx: 83 F1 10 7F 81 12 93
    Tx: 0101
    Rx: 83 F1 10 7F 01 11 15
    Tx: 0102
    Rx: 83 F1 10 7F 01 11 15
    Tx: 0103
    Rx: 83 F1 10 7F  01 11 15
    Is there a way to read RPM, speed, etc.? Any suggestions?

    Thanks in advance.

  • #2
    Sending EOBD commands to the ecu at address 10 (engine with peugeot protocol) has no use.
    The engine ecu responds with a NAK (Negative acknowledgement) because it does not have a clue what you mean.

    A 2006 model should be EOBD-compliant. Which pins are present in the diagnostic connector?

    Comment


    • #3
      This is the connector:

      Click image for larger version

Name:	31012012096.jpg
Views:	1
Size:	59.6 KB
ID:	2283655

      Populated pins are:
      1 - Vendor option
      4 - Chassis GND
      5 - Signal GND
      7 - ISO 9141-2 K-Line
      11 - Vendor option
      13 - Vendor option
      16 - Battery Power

      Comment


      • #4
        I have investigated a bit about KWP2000 protocol, and if I'm not wrong the comand to read variables using this protocol is 21 XX -Read Data by Local Identifier- (and also maybe 22 XX -Read Data by Identifier-). The problem is that I have not found good documentation for the XX codes.

        I have tried entering every command from 21 00 to 21 7F and all I get is a "Sub Function not supported" negative response (7F XX 12).

        Some "Record Local Identifier" values (0xA0-0xDF) output data I don't know how to interpret besides the first two bytes. The same happens with "Dynamically Defined Local Identifiers" values (0xF0-0xF9). Examples of these readings:

        Code:
        >21A0
        61 A0 01 C7 F0 FF FF FF FC C0 F0 FF EF F7 FF FF FF FE EF FB FF 09 02 00 00 01
        
        >2101
        7F 21 12
        
        >21A2
        7F 21 12
        
        >21A2
        7F 21 12
        
        >21A3
        61 A3 64
        
        >21F0
        61 F0 00 00 00 00 04 2C 19 05 06 02 48 01 02 19 05 06 FE 00 00 00 01 57 66 23
        
        >21F1
        61 F1 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 5C A2 4D
        
        >21F2
        7F 21 12

        Comment


        • #5
          Peugeot uses the 21 command for its own protocol. That's correct.
          The subfunction is always 80h or larger. The exact definition of the subfunction and its answer cannot be found anywhere.
          You would have to reverse engineer everything yourself.

          For a 2006 model EOBD should work. Either ISO 9141-2 or ISO 14300. That is, if you live inside the European Union and your country requires EOBD.
          What's your engine code? You can find the engine code in position 6 thru 8 of the vin number.

          Comment


          • #6
            Finally I have reverse-engineered the protocol to get the data I need (RPM, speed and throttle position).

            RPM/30 and speed in km/h are found in the response of the "21 C4" command. RPM/30 is in the 3rd byte and speed in km/h is 19th byte.

            Throttle position is in the 11th byte of the response to a "21 C6" command. It goes from 0 to 255 for pedal position 0% to 100%.

            Here in Spain, AFAIK, only vehicles newer than 2010 neet to be EOBD compliant.

            Comment


            • #7
              That's odd. Spain has been a member of the EU a long time now. I think from the beginning.
              EOBD is a European law and it should apply to Spain without any exceptions.
              Do you have any website or link where the date of 2010 can be found?

              Comment


              • #8
                I don't remember where, buy I think I saw it somewhere. Anyway, in this thread, you wrote some 2005 Partner vehicles are not EOBD compliant. You also state 2006 models are EOBD compliant... Maybe this Partner is an early 2006 not EOBD compliant one.

                Comment


                • #9
                  The EOBD rules are very clear on this point. It's not interesting when the vehicle was build, but when it was SOLD.

                  The rules for petrol and diesel are different and for commercial vans (which a Partner is) are also different.
                  The bottom line is that a commercial van of your weight class with a diesel engine sold ON or AFTER 1st. Jan 2006 SHOULD be compliant.
                  However, there are a few problems here. Nobody checks it, to start with.

                  Comment


                  • #10
                    Thanks for help. I didn't know 1st. Jan 2006 was the date. It looks like in this case somebody skipped the tests...

                    Comment


                    • #11
                      Or they sold you a 2005 model that has been in the showroom for a 1/2 year or longer?

                      Comment

                      Working...
                      X