Hi all,

I've got an 05 RRS with pin 2 of the FBH already wired to pin 7 on the OBD-II port and I have a cheap and cheerful (£5) OBD-II interface which is *supposed* to support K-line on pin 7 as ISO 9141-2 or 14230-4.

The OBD-II interface is *said* to use protocol auto-detection and works fine for the CAN and ScanXL reads the cars values like RPM etc.

But for the FBH, I've tried manually changing the protocol to K-line 9141-2, 14230-4 and 14230-4 Fast Init. (ATSP3, ATSP4 and ATSP5) but the Webasto software can't find the device - I tried setting it for W-Bus and auto-detection.

Has anyone managed to one of these adapters to talk to the FBH while connected to the OBD-II port? Am I missing something?

Thanks!

'tang.

Currently the technical side of OBD is a bit over my head so afraid can't answer your question directly. I have a IID Tool which can purge air from the FBH, prime it and fire the thing up regardless of the ambient temp. But if all you need is the FBH functionality - not worth the expense.

Just for fun I too have a cheapo OBD interface (Elm 327 Chinese knock-off) but it must be the deluxe model (it was £7)
with bluetooth connectivity so using an android tablet and the Torque app to read values and use as a toy showing boost pressure and other boy racer essentials

Have you looked on the Torque forum and wiki pages? There is information there about adding to the things that the adapter can do - but I haven't managed to figure it all out yet. Might mean more to you as clearly your technical knowledge is much more advanced than mine in this area
 2008 MY Java Black TDV8 HSE

Will give Torque site a read tonight - there's loads of information but not sure how much is applicable.

Am I imagining reading somewhere that to connect to the FBH via K-Line the unit must be powered (key turned) but the engine not running?

'tang

If you search the Disco3 website for Elm 327 you'll find a discussion of the same problem you are having with connectivity. Apparently you need a VAG OBD cable - whatever the hell that is.

A D3 owner (Matt Green) also wrote a plug-in for Torque aimed at the FBH which is free on the android app website. I think a few people reported getting it to work so may be worth a look.

Good luck. 2008 MY Java Black TDV8 HSE

Cheers for the added info.

Yeah, a VAG OBD (VW & Audi OBD) cable is a simple KKL interface that most ELM-clones are supposed to support under ISO 9141-2 and 14230-4/KW2000.

I'll go back out when cooler for another try and see what happens. Will check the Torque/D3 Webasto from Matt too.

Thanks!

Ok, I have an answer. It can't be done.

The Webasto is talking it's own raw protocol. The ELM327-clone is trying to read it as ISO 9141-2 or 14230-4/KW2000 packets to send to the PC. The Webasto app doesn't understand these chopped up packets and therefore doesn't work.

Seems the ELM327 doesn't have a raw pass-through option to send the K-line data straight to the PC serial port so we have to use KKL cables...

Pity

'tang.

I've just re-read my last post and I think it needs a better explanation for anyone else who comes across this.

The ELM327/STN1110 units can use K/L communications but only under the ISO 9141-2 or 14230-4/KW2000 protocols. If any data received on these lines does not conform to those protocols then it is discarded. The ELM/STN units convert any valid data into standard packets to be sent to the upstream device (PC etc).

The W-Line from the Webasto FBH uses the same signal levels as the K/L protocols BUT does NOT conform to the ISO/KW protocol standards as it is a propitiatory protocol used by Webasto.

The ELM/STN units see the communication from the FBH as unrecognised/invalid and therefore it does not work.

The only way to communicate with the FBH over W-Line is to pass the data to the upstream device as a raw stream which the ELM/STN units can't do (seems the latest chips can do CAN RAW but not any others as yet).

The only option is to purchase a KKL interface such as those used by the VAG OBD interfaces which you can find on your favourite auction site.

Hope this helps someone else...

Paddi wrote:

Currently the technical side of OBD is a bit over my head so afraid can't answer your question directly. I have a IID Tool which can purge air from the FBH, prime it and fire the thing up regardless of the ambient temp. But if all you need is the FBH functionality - not worth the expense.

RRSTDV8 wrote:

Paddi wrote:

Currently the technical side of OBD is a bit over my head so afraid can't answer your question directly. I have a IID Tool which can purge air from the FBH, prime it and fire the thing up regardless of the ambient temp. But if all you need is the FBH functionality - not worth the expense.

Which version of IID Tool firmware are you running for that functionality?

The current beta version 2008 MY Java Black TDV8 HSE

Is that the one that will become 2.18? Mine is on 2.17.3 (I think) but I haven't used it since I upgraded it. 2012 SDV6 - it's missing a couple of cylinders
2008 TDV8 - it was a labour of love and is much missed

Think the current beta is something like v2.18.09 (can't recall the last digit). The nice man at Gap updated it especially for me so that I can see the live values for the TC and solenoids 1 to 4 in the gearbox.

Great service  2008 MY Java Black TDV8 HSE

Ah, that makes sense. I saw on the website that the FBH features were to be expanded in ver 2.18. I'm looking forward to the next upgrade  2012 SDV6 - it's missing a couple of cylinders
2008 TDV8 - it was a labour of love and is much missed

The update, if it includes all the beta functionality, will be significantly more powerful with the gearbox reset, FBH, more live values and some reflashing. I was sceptical at first but am now a convert.

The bluetooth enabled modules are on the way too - will be great.

Might be time to invest in a proper power supply or we will have people 'bricking' their ECUs when the reflashing functions are used. The CTEK one looks good - but oops we are getting way....
 2008 MY Java Black TDV8 HSE