Hi all....
My name is SKOLS and i'm French. My car is an AUDI S3 8P 2007 BHZ.

First of all, let me apologize but i 'don't speak german. So, i write in english.

Since few years, i work on Kline and CAN protocole, and i (a friend and me) make a little device (Arduino DUE) to read OBD values...
Here is our prototype in action :

https://youtu.be/vj1QaD8p9HI

The GOAL was to put it in the MK4 cluster....and it's in progress.

Now, with the new technologies, i'm looking in the ANDROID/IOS direction....
I've got a chiness 2DIN ANDROID HU in my S3, and i use TORQUE with an ELM, since 2 weeks............and just for the fun..........it's a toy, nothing else, because of generic PIDs.

While searching, i found the BT5 TORQUE compatibility very interesting, but i've few questions about this:

- Is it working well? Any issues?
- Is it possible to READ another ECU than 01-ENGINE? (I guess the BT5 can, but i don't think TORQUE is coded for)
- When the BT5 connected to a measure block (only one, so 4 values), how many fps can i hope to make LOGS?
(for ex, VCDS make about 19 fps for a MB, in turbo mode)


Another question:
If i make my own ANDROID app, is it possible to start on the WBH protocole, or must i make my own protocole? Is there a restriction with the copyright?


Thank's a lot for your interest.
Best regards.

As I know Torque can only use ECU 01. WBH BT5 can use mostly every ECU. The best way will be to test it first with a normal PC
How fast it will be I did not meassure because I think this is useless. The speed is dedicated to the used diagnostic protocol and it's fast enough for everything.
You can make what you want with the WBH BT5. If you write a App for the WBH BT5 you are welcome. You are free to use the WBH commands for everything. If you are ready with your App let us know it - you will be the first one and we can promote it a little bit.

_________________

Alles folgende ist Teil der Antwort und wird oben nicht noch mal explizit wiederholt:

Sieh' in die FAQ! Schaue in die Fahrzeugliste, ob Dein Fahrzeug vorhanden ist. Trage Deine Erfahrungen dort ein und hilf so anderen Nutzern!

Ich freue mich über Infos mit Herstellernummern zu VAG Steuergeräten mit CAN TP 1.6/2.0 oder UDS Protokoll wenn die Pinbelegung (Diagnoseleitungen und Spannungsversorgung) bekannt ist.

Nutze PGP für Deine Emails! (PDF lesen)

Dieser Beitrag kann Werbung enthalten.

Thank's Florian....

As you saw, i've just order a BT5 this day....now,n i had to play with it to undersatand all the commands.

The speed is for me a very usefull data because i want to make a multi-logs functions......i'll see what the BT5 can do on this side.

Thank's a lot for your interest.
SKOLS

Florian, do you receive my account from the BANK?

Well.....my BT5 is here.....very quick ship, thank's a lot.

This said, i've some issues with it.

Fisrt :
- i put the BT5 in my AUDI S3 2007 BHZ MED9.1 (TP2.0).
- i follow the steps for terminal connection (SENA Bterm)
- i follow the steps for TORQUE setup
- i read the "WBH diag" pdf, and the BT5 pdf

Well, first problem : i can connect to the BT5, but according to SENA Bterm, there's a DATA error when i ask "atd01" command. In fact, ECU seem to be connected but no DATA are received.....

Here are some Screenshot :

As you can see, ECU seem to be connected, but BT5 can't get any DATA.

So, to be sure that it wasn't an App or Android issue, i try the same thing on my SEAT LEON TDI 110 2005 (EDC15P KWP1281 i guess).
And it work without any issues...it's very very slow, but it work.

Florian, can you confirm that BT5 is TP2.0 ready?
It seem to be not......

Say: CAN TP 2.0 with 500 Kbit.
Normally there must be follow information about the ECU. Becaue they are missing there must be an communication problem. This can happen to some ECUs. Try other ECUs (numbers) with ATDxx
If there is a data error, Torque can not display any information.

_________________

Alles folgende ist Teil der Antwort und wird oben nicht noch mal explizit wiederholt:

Sieh' in die FAQ! Schaue in die Fahrzeugliste, ob Dein Fahrzeug vorhanden ist. Trage Deine Erfahrungen dort ein und hilf so anderen Nutzern!

Ich freue mich über Infos mit Herstellernummern zu VAG Steuergeräten mit CAN TP 1.6/2.0 oder UDS Protokoll wenn die Pinbelegung (Diagnoseleitungen und Spannungsversorgung) bekannt ist.

Nutze PGP für Deine Emails! (PDF lesen)

Dieser Beitrag kann Werbung enthalten.

I've ever try ATD17 (screenshot 2), with the same result.....i'll try the others, with no hopes...

This said, I'don't think that the problem come from TORQUE because SENA Bterm doesn't show any DATA too......and it get DATA from my EDC15P....

So, if i understand, it's possible that the BT5 can never read my MED9.1?
I'm sick...

I've just try to connect to ABS ECU, with ATD03 command.....

CONNECT 6.3 ----> cluster lights are flashing ----> DATA ERROR.... so the ECU received the command, but can't get any DATA.

There's something wrong with the TP 2.0 comm....

Another test to suggest?

TP 2.0 will be supported but sometimes there will be communication problems. We are sorry but there is no solution if it does not work on your car. Did you test it on another car?

_________________

Alles folgende ist Teil der Antwort und wird oben nicht noch mal explizit wiederholt:

Sieh' in die FAQ! Schaue in die Fahrzeugliste, ob Dein Fahrzeug vorhanden ist. Trage Deine Erfahrungen dort ein und hilf so anderen Nutzern!

Ich freue mich über Infos mit Herstellernummern zu VAG Steuergeräten mit CAN TP 1.6/2.0 oder UDS Protokoll wenn die Pinbelegung (Diagnoseleitungen und Spannungsversorgung) bekannt ist.

Nutze PGP für Deine Emails! (PDF lesen)

Dieser Beitrag kann Werbung enthalten.

Yes i try it on a GOLF GTI mk5, am 2006, with the same ECU MED9.1.......same issues, connected but no DATA.....

I also try with Windows XP + WBH pro 1.3 (only one in english):

Here are the screenshots









Look at the dialogue box in the bottom, it's written KWP1281....!!!
Is it normal?

Well, i try with the last update of WBH....

I get this :



So it's detecting the TP 2.0 but get NO DATA from the ECU....

Well....

Here is what i've got:




The HARDWARE:
- a 12V power supply
- a MED 9.1 TP 2.0 ECU, with all the documentation
- a WBH BT5 brand new (lol)
- an ARDUINO DUE with CANbus chip, abble to sniff any data (NOTE: i've ever sniff TP 2.0 protocol so i know how to communicate)
- an XP computer with a BT dongle
- a NEXUS 7 2013
- an ANDROID HU 4.4.4 KK RK3188, with official TORQUE pro
- a lot of motivation ( )

I'm ready to work!!!!
But i need you, Florian.....i can't acess to the WBH code without you.

BR

Are you sure the ECU did not use UDS? or K-Line because the Pinout has one port for it.
My MED 9.5.1 supports TP 2.0 and it works
Can you tell me one or more VAG OEM numbers for MED 9.1 so I can probably buy one?

_________________

Alles folgende ist Teil der Antwort und wird oben nicht noch mal explizit wiederholt:

Sieh' in die FAQ! Schaue in die Fahrzeugliste, ob Dein Fahrzeug vorhanden ist. Trage Deine Erfahrungen dort ein und hilf so anderen Nutzern!

Ich freue mich über Infos mit Herstellernummern zu VAG Steuergeräten mit CAN TP 1.6/2.0 oder UDS Protokoll wenn die Pinbelegung (Diagnoseleitungen und Spannungsversorgung) bekannt ist.

Nutze PGP für Deine Emails! (PDF lesen)

Dieser Beitrag kann Werbung enthalten.

Yes fore sure : my ECU is a 8P0 907 115 H
But all ECU's with xxx 907 115 x use the same protocol.

About TP 2.0, i'm pretty sure that the MED9.1 use it, refer to BOSCH Funktiosrahmen document (if you need it, just ask).
I'm sure that it's not Kline because my VCDS use CAN pins for the diagnose com.....



I've some sniff of the CAN connections, if it help....
Let me know if i can make some test for you, some sniff, or anything else.....


Here's how VCDS connect to the 01 - ENGINE ECU and open a diag session (i filter the propulsion ID to be more readable)

ID: 0x200 Len: 7 Data: 0x01 0xC0 0x00 0x10 0x00 0x03 0x01
ID: 0x201 Len: 7 Data: 0x00 0xD0 0x00 0x03 0x40 0x07 0x01
ID: 0x740 Len: 6 Data: 0xA0 0x0F 0x8A 0xFF 0x32 0xFF
ID: 0x300 Len: 6 Data: 0xA1 0x0F 0x8A 0xFF 0x4A 0xFF
ID: 0x740 Len: 5 Data: 0x10 0x00 0x02 0x10 0x89
ID: 0x300 Len: 1 Data: 0xB1
ID: 0x300 Len: 5 Data: 0x10 0x00 0x02 0x50 0x89
ID: 0x740 Len: 1 Data: 0xB1
ID: 0x740 Len: 5 Data: 0x11 0x00 0x02 0x1A 0x9B
ID: 0x300 Len: 1 Data: 0xB2
ID: 0x300 Len: 8 Data: 0x21 0x00 0x30 0x5A 0x9B 0x38 0x50 0x30
ID: 0x300 Len: 8 Data: 0x22 0x39 0x30 0x37 0x31 0x31 0x35 0x48
ID: 0x300 Len: 8 Data: 0x23 0x20 0x20 0x30 0x30 0x34 0x30 0x10
ID: 0x300 Len: 8 Data: 0x24 0x00 0x00 0x00 0x00 0x00 0x00 0x00 ------> 8P0 907 115H, 0040, R4/V4 TFSI
ID: 0x300 Len: 8 Data: 0x25 0x18 0xAA 0x32 0x2E 0x30 0x6C 0x20
ID: 0x300 Len: 8 Data: 0x26 0x52 0x34 0x2F 0x34 0x56 0x20 0x54
ID: 0x300 Len: 8 Data: 0x27 0x46 0x53 0x49 0x20 0x20 0x20 0x20
ID: 0x300 Len: 2 Data: 0x18 0x20
ID: 0x740 Len: 1 Data: 0xB9
ID: 0x740 Len: 7 Data: 0x12 0x00 0x04 0x31 0xB8 0x00 0x00
ID: 0x300 Len: 1 Data: 0xB3
ID: 0x300 Len: 8 Data: 0x29 0x00 0x12 0x71 0xB8 0x01 0x01 0x01
ID: 0x300 Len: 8 Data: 0x2A 0x03 0x01 0x02 0x01 0x06 0x01 0x07
ID: 0x300 Len: 7 Data: 0x1B 0x01 0x08 0x01 0x0D 0x01 0x18
ID: 0x740 Len: 1 Data: 0xBC
ID: 0x740 Len: 5 Data: 0x13 0x00 0x02 0x1A 0x9A
ID: 0x300 Len: 1 Data: 0xB4
ID: 0x300 Len: 8 Data: 0x2C 0x00 0x17 0x5A 0x9A 0x00 0x00 0x00
ID: 0x300 Len: 8 Data: 0x2D 0x00 0x18 0xAA 0x30 0x30 0x34 0x30
ID: 0x300 Len: 8 Data: 0x2E 0x10 0x09 0x01 0x03 0x00 0x03 0x18 -----> Workshop Code + Softcoding
ID: 0x300 Len: 5 Data: 0x1F 0x0F 0x01 0x60 0xFF
ID: 0x740 Len: 1 Data: 0xB0
ID: 0x740 Len: 1 Data: 0xA3
ID: 0x300 Len: 6 Data: 0xA1 0x0F 0x8A 0xFF 0x4A 0xFF
ID: 0x740 Len: 5 Data: 0x14 0x00 0x02 0x1A 0x91
ID: 0x300 Len: 1 Data: 0xB5
ID: 0x300 Len: 8 Data: 0x20 0x00 0x11 0x5A 0x91 0x0E 0x38 0x50
ID: 0x300 Len: 8 Data: 0x21 0x30 0x39 0x30 0x37 0x31 0x31 0x35
ID: 0x300 Len: 6 Data: 0x12 0x42 0x20 0x20 0x20 0xFF
ID: 0x740 Len: 1 Data: 0xB3