VeePeak Custom BTLE OBD2 Adapter Troubleshooting

[agentdax5]

Has anyone successfully used a VeePeak BTLE OBD2 adapter?

* Harry's LapTimer GP Edition
* VeePeak OBDCheck BTLE OBD2 adapter https://www.amazon.com/gp/product/B073X ... UTF8&psc=1
* iPhone 6S Plus running iOS 12.1.4

I have used this adapter with TrackAddict in the past but want to migrate over the LapTimer.

I sniffed the UUIDs using LightBlue and I can successfully get it connected as a Custom BTLE device but the update rate is too slow at 0.0Hz

I believe that my Read and/or Write UUIDs are wrong. I have tried basically every combination of UUIDs from sniffing via various apps with no luck. I also tried using the FFF* UUIDs with the BTLE base id as described in this post: viewtopic.php?f=6&t=4607

Screenshots of sniff results: https://imgur.com/a/pWK0zu9

[Harry]

Please post the Custom OBD Expert Settings you have set. I will check this against VEEPEAK’s interface. LapTimer v23 will come with predefined VEEPEAK Settings.

Harry

[agentdax5]

Here are the combinations I have tried. All of them connect to the adapter but stop there.

Code: Select all

Peripheral Name : VEEPEAK
Service UUID    : 49535343-FE7D-4AE5-8FA9-9FAFD205E455
Read UUID       : 49535343-6DAA-4D02-ABF6-19569ACA69FE
Write UUID      : 49535343-ACA3-481C-91EC-D85E28A60318

Peripheral Name : VEEPEAK
Service UUID    : 49535343-FE7D-4AE5-8FA9-9FAFD205E455
Read UUID       : FFF1
Write UUID      : FFF2

Peripheral Name : VEEPEAK
Service UUID    : 49535343-FE7D-4AE5-8FA9-9FAFD205E455
Read UUID       : 0000FFF1-0000-1000-8000-00805F9B34FB
Write UUID      : 0000FFF2-0000-1000-8000-00805F9B34FB

Peripheral Name : VEEPEAK
Service UUID    : FFF0
Read UUID       : FFF1
Write UUID      : FFF2

Peripheral Name : VEEPEAK
Service UUID    : 0000FFF0-0000-1000-8000-00805F9B34FB
Read UUID       : 0000FFF1-0000-1000-8000-00805F9B34FB
Write UUID      : 0000FFF2-0000-1000-8000-00805F9B34FB

[Harry]

I know the correct UUIDs I wanted to see what you have entered in LapTimer. I’ll post the settings later when in office.

Harry

[Harry]

Code: Select all

LapTimer ‣ Administration ‣ Settings ‣ Expert Settings
    ‣ Custom OBD Adapter
        ‣ ELM327 Type ‣ Request/Reply
    ‣ Custom BTLE OBD Adapter
        ‣ Peripheral Name ‣ VEEPEAK
        ‣ Service UUID ‣ FFF0
        ‣ Read Characteristic UUID ‣ FFF1
        ‣ Write Characteristic UUID ‣ FFF2

[agentdax5]

I tried those before but I just ran outside to try again and no luck.

Here are some screenshots: https://imgur.com/a/WdUNKTx

[Harry]

So it is a problem between car and adapter or the way LapTimer is accessing it. See Debugging OBD Connections in the FAQ section.

- Harry

[crazyxzer0]

Hi Harry,

I emailed you with information as well since I am having the same issue with the settings you posted.

[Harry]

Hello,

As LapTimer v23 will come with native VEEPEAK support, I will not work on supporting it using the Custom OBD BTLE Expert Setting in v22. Thanks for your understanding, I want to concentrate on finalizing v23.

- Harry

[crazyxzer0]

Thanks Harry!

Is Beta V23 working with VEEPEAK? I'm heading to a trackday 4/20 and would love to use it