Kiwi 3 OBD Refresh Issue with BMW

[Dubbedown]

I am running v24.8.2.186 Grand Prix Edition on iOS. I’ve used Kiwi 3 successfully many years ago but I’ve had difficulties in recent weeks on 2 different cars. First was ‘06 BMW Z4 M coupe and the other is a ‘15 BMW F10 550i. Sensor list shows successful connection but whenever I am about to race, the OBD refresh rate shows as RED: “The OBD sensor does not receive data at an expected rate. Please check compatibility between…”

I’ve gone as far as

- forgetting (i.e. remove) existing Bluetooth car audio connections
- closing any other apps in background so only lap timer is running
- reinstalling the app to ensure I was using default settings

The only external device I have are LE Bluetooth GPS antennas. One of my cars has the Apex unit, other car has RaceBox mini. I’ve also ruled out any issues with hardware; device works fine for car diagnostic apps. In general, my experience is very similar to this user here:

viewtopic.php?t=5674

I would really love to get this resolved before my next track day. Are there any settings I can tweak so the Kiwi can connect/transmit data?

IMG_7572.png (1.34 MiB) Viewed 7982 times

[Dubbedown]

Harry any idea how I can fix the above?

[Harry]

The snapshot is showing there is communication (including specific PIDs), but obviously communication is not stable and incomplete.

Two possible reasons:
#1 The optimized communication applied by LapTimer doesn't work with the OBD gateway. One thing you can try is setting LapTimer ‣ Administration ‣ Settings ‣ Expert Settings ‣ OBD Tweaks / Adaptive Timing to Enabled instead of Optimized. You can limit the ECUs addressed by selecting ECM instead of ALL too.
#2 There is still some other communication going on. In case another app or device contacts the Kiwi in parallel to LapTimer, the above result is expected. Try to simplify your setup, turn off / do not use other BT devices, uninstall other OBD and BT LE apps etc.

- Harry

[Dubbedown]

The snapshot is showing there is communication (including specific PIDs), but obviously communication is not stable and incomplete.

Two possible reasons:
#1 The optimized communication applied by LapTimer doesn't work with the OBD gateway. One thing you can try is setting LapTimer ‣ Administration ‣ Settings ‣ Expert Settings ‣ OBD Tweaks / Adaptive Timing to Enabled instead of Optimized. You can limit the ECUs addressed by selecting ECM instead of ALL too.
#2 There is still some other communication going on. In case another app or device contacts the Kiwi in parallel to LapTimer, the above result is expected. Try to simplify your setup, turn off / do not use other BT devices, uninstall other OBD and BT LE apps etc.

- Harry

I tried changing those 2 settings (Enabled and ECM) but still same outcome. Only other BT device was Racebox GPS.

Weird thing is when I used to track regularly (pre-Covid so few years ago), I never had issues with the Kiwi. But I don’t know if it’s a particular Kiwi firmware update, change to iOS settings, or laptimer app but I’ve not been able to get Kiwi working anymore. It works fine with other diagnostic apps however.

Harry can you recommend any other obd device for iOS that is still available? Many on your comparability list have been discontinued for some time now.

[Harry]

OBDLink CX or MX+. But I doubt it is a problem with LapTimer and the Kiwi 3. Try without Racebox please, it may use up all bandwidth.

Harry

[Dubbedown]

OBDLink CX or MX+. But I doubt it is a problem with LapTimer and the Kiwi 3. Try without Racebox please, it may use up all bandwidth.

Harry

Even without Racebox I am encountering the same issues. Though I am certain I eliminated any other BT devices (by ‘forgetting’ the connection), does the existence of searchable BT devices in background cause bandwidth issues? Or is there a way in laptimer settings to limit only user defined devices (e.g. “Kiwi” and “Racebox” only)?

[Harry]

Bluetooth devices can “advertise” their services, usually after setting them to be ready for pairing or (for BT LE), simply broadcasting availability of services. Both operations reduce the bandwidth available, the former considerable. I recall I have seen in car stereos advertising constantly and creating issues. You can try by pulling their fuse.

[Dubbedown]

Bluetooth devices can “advertise” their services, usually after setting them to be ready for pairing or (for BT LE), simply broadcasting availability of services. Both operations reduce the bandwidth available, the former considerable. I recall I have seen in car stereos advertising constantly and creating issues. You can try by pulling their fuse.

Harry I guess what I failed to appreciate is that multiple BTLE devices may interfere with each other. Till now I was only concerned with not doubling up on Wi-Fi devices for purposes of my GoPro.

ideally I’d like to connect to 1) external gps, 2) obd and 3) GoPro 4. What combo of gps and obd devices would you then recommend? Perhaps I should dig up old bad elm lightning gps unit and stick to kiwi 3?

[Harry]

Bandwidth used for GPS multiplies with update rate. A device with 25 Hz will use a lot of bandwidth. OBD will get slower when bandwidth is low. Can't say for the GoPro.

[Dubbedown]

So Wi-Fi aside is it better to have 2 LE devices or 1 LE and 1 MFi for OBD and GPS (assuming 10hz)?