Page 1 of 1

2007 BMW 335i possible alternate way of getting data?

Posted: Mon Oct 05, 2015 9:13 pm
by Jeff_335i
I've been trying to get OBD data collection to work with my 03/2007 production date BMW 335i (E92 chassis) for quite a while. I have an OBDLink MX Bluetooth dongle that works fine with the OBDLink application and shows reading about 5 PIDs/second on average. However it always shows the low data rate error when trying to use it with HLT.

I've tried everything I was able to find in these forums, changing settings, excluding PIDs, etc. I see my car is listed in the "problem cars" thread here, but that is also pretty old.

One thing I was thinking is that my car has a piggyback tuner attached to the ECU that is wired into it pretty extensively, and it collects data from the CAN bus directly and can display real-time data at a very fast rate via Bluetooth and an Android or iOS app. I was wondering if there might be an opportunity for HLT and the developer of the tuner app to get together and make it so that HLT can fetch data that way instead of via OBD. Obviously I'm not a programmer but I believe the data from the tuner is easily accessible because the guy that wrote the phone app did it in only a few days of free time.

Re: 2007 BMW 335i possible alternate way of getting data?

Posted: Mon Oct 05, 2015 9:43 pm
by Harry
ASL's RaceCapturePro/MK II does exactly this and is supported by Harry's LapTimer for Android. For iOS a WiFi bridge is required but not available yet.

On your BMW and OBDLink MX, please try the following setting:

LapTimer ‣ Settings ‣ Expert Settings ‣ OBD Tweaks / Adaptive Timing ‣ Enabled (instead of Optimized)
LapTimer ‣ Settings ‣ Expert Settings ‣ OBD Tweaks / Reply Timeout ‣ 0.4

- Harry

Re: 2007 BMW 335i possible alternate way of getting data?

Posted: Mon Oct 05, 2015 10:50 pm
by Jeff_335i
I tried the following settings:

Adaptive Timing: Optimized, Enabled, Aggressive - none seem to make a difference.
Reply Timeout: tried 0.4, 0.5, 1.0, 1.02 - seemed like 1.0 and 1.02 allowed it to briefly connect at 1 Hz for a few seconds.
Default Protocol: Automatic or ISO 14230-4 KWP, makes no difference
Ignore NO DATA/NAK: checked
Request Sequence Pause: 0.010
Sequential Requests (BT1): checked or unchecked, no difference
CAN Multi Requests (ELM327): Off or 3 PIDs/adaptive, no difference
Auto Exclude PIDs: unchecked

So far I hve never had a successful connection that actually shows any OBD data in HLT. It always just says "Connected" or "Connected at 0 Hz"