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.htmlUSB 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