PLX Kiwi "does not receive data at an expected rate."

[Hubs996]

I recently purchased a PLX Kiwi wireless and tried it out at Watkins Glen a few weeks ago. Something isn't quite right, and I hope someone can help me figure out a solution.

HLT Grand Prix Edition v19.0.8
iPhone 5c, iOS 8.4, 15GB available memory
Dual SkyPro 10Hz Bluetooth GPS
PLX Kiwi wireless OBD II

The car is a 2000 Porsche 911.

When ready to head out for the track, and getting HLT into "Timer" mode, I get an error warning:
System Status, Not Ready, OBD Update Rate
"The OBD sensor does not receive data at an expected rate. Please check compatibility between car, OBD dongle, and LapTimer."

I went with it anyway, and here is a sample of the data (I have also attached an Excel file):



You can see at row 9 (lap time 0.61s) the data from the OBD sensor "freeze." The OBD data were frozen for about 5 seconds, then throughout the session the data intermittently recorded and froze (there's another long freeze starting at 16s). Here is the overlaid video:

https://www.youtube.com/watch?v=j6y-0r6RW-Q

In a later session I tried putting the iPhone in airplane mode, but that did not seem to make any difference.

Any ideas on how to get the Kiwi and HLT on the same page???

[Harry]

Please check the "Debugging OBD Connections" post in the FAQ sub forum. When sending the log, please add a reference to this thread or "2000 911 / Kiwi disconnects"

[Harry]

Thanks for sending the log.

First of all, please do not expect high update rates for your 911 in general. The early busses / OBD II gateways where quite slow and you will probably get not beyond 2 Hz (i.e. 10 PIDs/s) anyway.

What I found is the request for 0900 does not work correctly for your car. This adds additional waiting times every few seconds. This in turn will make an averaged update rate slightly above 0 only:

Code: Select all

00399258360 +   10ms ---------  mode: 9 pid: 0x00 [PID01-20] (index: 15)
00399258360          Tx: "30 39 30 30 0D '0900\r'" (5)
00399259540 + 1180ms Rx: "4E 4F 20 44 41 54 41 0D 0D 3E 'NO DATA\r\r>'" (10)
00399259540          ---------  mode: 9 pid: 0x20 [PID21-40] (index: 16)
00399259540          Tx: "30 39 32 30 0D '0920\r'" (5)
00399260720 + 1180ms Rx: "4E 4F 20 44 41 54 41 0D 0D 3E 'NO DATA\r\r>'" (10)
00399260720          ---------  mode: 9 pid: 0x40 [PID41-60] (index: 17)
00399260720          Tx: "30 39 34 30 0D '0940\r'" (5)
00399261900 + 1180ms Rx: "4E 4F 20 44 41 54 41 0D 0D 3E 'NO DATA\r\r>'" (10)
00399261900          ---------  mode: 1 pid: 0x01 [DTCCNT] (index: 18)
00399261900          Tx: "30 31 30 31 20 31 0D '0101 1\r'" (7)
00399262080 +  180ms Rx: "34 31 30 31 30 30 30 37 36 44 30 30 0D 0D 3E '410100076D00\r\r>'" (15)
00399262080          ---------  mode: 9 pid: 0x02 [VIN] (index: 19)
00399262080          Tx: "30 39 30 32 0D '0902\r'" (5)
00399263260 + 1180ms Rx: "4E 4F 20 44 41 54 41 0D 0D 3E 'NO DATA\r\r>'" (10)
00399263260          Tx: "41 54 52 56 0D 'ATRV\r'" (5)
00399263330 +   70ms Rx: "31 33 2E 38 56 0D 0D 3E '13.8V\r\r>'" (8)

To work around, please add the following string to LapTimer ‣ Administration ‣ Settings ‣ Expert Settings ‣ OBD Tweaks / Exclude PIDs:

Code: Select all

0900092009400902

With 0902 disabled (because it is not available anyway), LapTimer will not be able to receive the vehicle identification number and consequently will not switch to this car automatically. This is usually not an issue, just make sure you select your 911 manually once (e.g. in Timer ‣ Status).

I haven't tested the effect, please let me know if the workaround works or not. In case it does not, please send another log with the named PIDs excluded.

- Harry

[Hubs996]

Harry,

Thanks for the quick reply. I've entered that number in Lap Timer on the line for Exclude PIDs, so it now appears as . . .

Exclude PIDs (e.g. 0140) 0900092009400...

I also did the same thing in GPS/OBD Buddy.

I'll update you when I get a chance. My next time on a track is August 7. If I can figure out anything before then I will let you know.

Best,

Mark

[Harry]

You do not need to be on track. Just bring up the Engine View and check the update rate while driving.

- Harry

[Hubs996]

When I first started it the display was back and forth between 1 Hz and 2 Hz. After a few seconds it seemed to hold pretty steady at 2 Hz. System status showed green for the OBD sensor, and no error message about unexpected rates. Can't wait to try it out on the track!

[Harry]

Ok, that's fine!

[Hubs996]

Well, I'm back with a similar problem, but different hardware. Going back to 2015, I never did get the Kiwi to work properly. But, I've got some new toys now . . .

I have HLT running on an iPhone SE that I got earlier this week. I have IOS version 13.5.1. HLT is version 23.0.11. For the first time I am trying to run a fairly new Kiwi3 OBD dongle. My car was out of commission for a while, and I have not tried the Kiwi3 with HLT. The car is the same: 2000 Porsche 911.

Anyway, I was trying to test this all out in my garage today, and I get the same error message about not receiving data at an expected rate. That string you gave me still shows in the Exclude PIDs setting. Any ideas?

[Hubs996]

OK, I see a page with some trouble-shooting information. I will try that first.

[Harry]

Please keep in mind that a 2000 Porsche will utilize a pre-CAN bus. These busses are slow and not as stable as those in modern cars. The gross rate you should see is 1 or 2 Hz (which means 5 to 7 PIDs/s).

- Harry