Hi Florian and forum users

I just made 2 pcs controller with WBH PRO 2.0 using as start point the circuit provided in WBH PRO 2.0 datasheet.
L interface is made according with WBH PRO 2.0 datasheet.
For K interface I use 2 versions:
1. using LM339 according with:


and



2. using 33199 according with:
http://itbrainpower.net/obd/MC33199.pdf

PCB used is modified Bluetooth:
http://www.obd2-shop.eu/pcbwbhdiagprobt-p-110.html

USB translation is made using FT232RL. The communication with PC is just fine (ATZ return boot string).

Problem came when I tried to connect to VW ECU! Car model used for test is VW Golf5, (1KABBUDX0)/2005/1390cm3/gasoline/59kW/Eu model.
On ATD01 and ATD17 the controller return error. I used several connection params(ATBDT, ATIBT). Also, I used your software and direct terminal connection. Same result.
On same car I succeed OBD connection using ELM327 oem and ST1100(ODBLinkSX) using ISO14230 KWP(5baud ini, 10.4 bouds - so call slow). I suppose, from this reason, this VW5 is KW2000 compatible.
My goal is to obtain some supplementary data from ECU17 that are unavailable under OBD Mode01 (as fuel level).

Can you help with some info, hints regarding interfacing with OBD? Can be some issues that was fixed in 2.1 version of WBH PRO?

Also, can someone help with some info regarding connection to VW service protocol (again, I only need to read some data from ECU17, as fuel level) when car support only CAN (I found this on VW6 FSI-2009 1.8L-i think ), using as interface ELM327 (After initial protocol selection and connection, how we can select service protocol, and how to address/select ECU17)

Thank you in advance,

Dragos Iosub
R&D Software Solutions srl

Maybe the LM339 is not fast enough? I did not check it out.



OBD II and VAG protocol is not the same. Maybe the car use CAN for VAG protocol.
There are some fixes in 2.1 for KW2000. Maybe they improve the possibility for a connect.

_________________

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.

Hi Florian,

Thank you for your answer.


Actually, I used BA10339F from Rohm. In data sheet is reported with Response time(typical) 1.3us. This means that override 200KHz bandwith (reported for LM33199) and ISO transients time = 400ms for L9637D. KW2000 use 10.4 KHz, if I understand right.


This Golf5 did not support CAN (CAN pins are in 0V).



I would like to order 2 more WBH PRO (2.1), 2xSMD-Adapter MC33290 - L9637, 2x Bluetooth PCB and 2xL9637 (I'l make the order on site and payment in this night). Can you prepare for me, in order to ship them tomorrow morning?

Thank you,

Dragos

About VAG over CAN... Can be used some initialization strings (send as raw can) in order to activeate service protocol, and after that to access some ECU? Thank you again.

Hi Florin,

I would like to complete the order, mentioned on previous post.

At this moment, is available only "rest of the world" shipment option. Please enable all shipment options in shop, for delivery to Romania (unfortunately for some peoples, Romania is part of EU ).

Thank you and BR,

Dragos

Hi Florian,

Golf 5(1K/MID) / 2004 2.0tdi 1868cm3

Using MC33199 interface, after atd01 received:
CONNECT: 5.2
x0101
½}çÎïvÀŽï'Óµ"›ãü,ÿ™…)
ÏnG£e»ãLÍ;];õ<øÁýyæ°éiZÞ•lçÉþŽÔÍJñ½·›þÇ
ƒšk¦«G-ú¶÷çÿ$·nÿÖýj{¡£È3«kƒ/
Ÿ1nô½&wÙþµÍÍ+ºÖ,­$ÉùpC‚Ë{6®Ø{ú²Ãý‡×¾èœ¢N¾ìõ½û
÷ÑÞNx0101

this block received after "CONNECT: 5.2" repeating several times. after that:
DATA ERROR

I tried several ATIBT /ATBDT combination. Also ATN. Same result. In addition, any data saved(ATIBT/ATBDT or ATN) came back at default state.. Looks like buffer overflow in ECU identification algorithm or is something related to electrical interface!!???
Florian, did you succeed to implement the ISO interface with MC33199?

I look forward for your reply,

Dragos

Maybe a baud rate problem. Do you choose the right one? Or the KL Interface is build incorrect.
Or the ECU is not supported.

_________________

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.

Hi Florian,

Meanwhile, on more tests, two times the ECU01(I think this is always supported ) respond sending back id data, but this happen from 30->40 tests!

Tests was made with ATN0 and ATN5. Same rate 10.4Kbauds used on connection made with ELM327 with success.

Regarding KW electric level interface: I will check again with L9737 included in last order .

My concern is related to settings reset (ATBDT and ATIBT fall back to default values). This is the reason I ordered 2.1 version for WBH.

I will came back with feedback after new test made with new interface made with WBH2.1 and L9737 (related to your schema from WBH2.1 data-sheet).

BR,

Dragos

ELM327 is OBD II. WBH-Diag not. So you can not compare it.

Try many combinations of IBT and BDT. It's a hard job. But some ECUs never will work fine. It's a pitty.

_________________

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.

Hi Florian,

One more question please!

How do you recommend to implement the electrical interface with L9637? Like in your MC33290 <-> L9637 adapter drawing (without ISO L interface connections on L9637), or like in WBH PRO 2.1 data sheet reference schematics (including ISO L interface on L9637... -> L interface used as second receiver line??!!! I think)?

Thank you in advance. BR,

Dragos

Hi Florian,

New test, new issues! Can you tell me what means "CONNECT:5.3" received after ATD01 (VW Golf5, (1KABBUDX0)/2005/1390cm3/gasoline/59kW/Eu model). After that I received ERROR? In datasheet CONNECT must be only 5.1 or 5.2.

I used WBH2.1 with L9637 (connected as in BT02 interface reference-without L line connections).

Thank you,

Dragos

This is the best way


It's for KW2031 fast or slow init.

_________________

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.