EDC15 has a special TP which seems very similar to KWP2000 but there are some differences.

1. Send a 3 byte message to id 0x214(apperently is the ecu id in this protocol, had to disassemble the flash to find this, not listed in the FR) for channel setup
  --> 0x214 3 0x01 0xC0 0xA1
  <-- 0x201 3 0x01 0xD0 0xA1

0x01- engine
0xc0- channel setup command(TPCI1 byte, like in KWP2000)
0xA1- offset from 0x700 for channel(means 0x7A1 will be id for comms)


2. Send 6 byte message to id 0x7A1 for timing parameters. ECU replies on 0x7A1 with it's timing parameters
 
  -->7A1 6 0xA0 0x0F 0x8A 0xFF 0x32 0xFF
  <--7A1 6 0xA1 0x01 0x94 0x83 0x82 0xD4

3. now, when I send startDiagSession command, there is no response. no ACK or anything at all.

Am i missing something? Or could it be that this TP is not mant for diag? I'm still trying to trace the disassembly but its getting harder with so  many possible responses!

regards
Nihal

I don't think there's any tool implementing this protocol...

I did some more experiments
After the 214 id init, if i send-
7A1 0xA0

Without any timing paramters, the ecu still acks with-

7A1 0xA1 0x94 0x83 0x82 0xD4

I did read on another site that some of the parameters are fixed in TP1.6, so maybe you are correct in assuming this is TP1.6.
Do you have any info about this protocol? I couldnt find much, jazdw.net only mentions it as similar but fixed parameters...

Thanks

Hi
What interface can communicate with protocol canbus to edc15 ?

check this book here

https://books.google.de/books?id=iv1VDZLKkDIC&pg=PA100&lpg=PA100&dq=TP+1.6&source=bl&ots=0SwUenEd6B&sig=3KIdmqXyfh77VcV7LBnoYg4jvi0&hl=de&sa=X&ved=0ahUKEwjs15KUupnaAhWBLVAKHXL5DjQQ6AEILjAA#v=onepage&q=TP%201.6&f=false

seems its TP1.6