BLE Device name Error[N/A] using example code of [HRS] <KW38 EVB>

[JungkyuHan1]

Hello

I am using the device #KW38 EVB

When I test with two example code; <heart rate sensor>,<blood pressure sensor>, I found some difference of SCAN result.

(I tested with SAMSUNG Galaxy Note 9 phone)

Using <blood pressure sensor> , the [Device Name] in host is always [NXP_BPS]. Exaclty I expected.

BUT, Using <heart rate sensor> , the [Device Name] in host is always [N/A]. I expected [NXP_HRS]. 

I have No idea what makes this diffence. Anybody can explain this and how to fix the fault scanning result?

[EduardoZamora]

Hello @JungkyuHan1

Hope you are doing well.

What SDK version are you using? Please try using the latest SDK version.

By any chance, did you modify the source code of any of those examples?

Have you previously paired the FRDM-KW38 with your mobile device (perhaps using another BLE example project)? If so, please try removing the Bluetooth pairing data/paired devices from your mobile device.

Also, could you please confirm if the same behavior is observed using the IoT Toolbox App?

Regards,
Eduardo.

[JungkyuHan1]

Dear Eduardo. Thankyou for your advise.
<SDK Info>
This is SDK version 2.6.615 manifest file. It describes the content of the FRDM-KW38 and additional settings for tools that support SDK version 2.6.615
ID:SDK_2.x_FRDM-KW38
Name:FRDM-KW38
Timestamp (UTC): 2023-02-23 14:33:08.853680

============================================
I Tested other example projects. Two of the projects <Heart rate sensor/BLE Shell> are shown the same symtom. The others are FINE.

1. Cycling Power Sensor[NXP_CPS]
2. Glucose Sensor[NXP_GLS]
3. Health thermometer[NXP_HTS]
4. Heart Rate Sensor [N/A] <====== Error
5. Proximity reporter[NXP_PXR]
6. Running speed cadence sensor[NXP_RSCS]
7. Wireless uart[NXP_WU]
8. Ble_Shell [N/A] <====== Error

[EduardoZamora · Accepted solution]

Hi,

Did you modify the source code of any of those examples?

What is the android version of your android device? Can you test these applications with a newer android version?

You mention that you tested other projects, and the same issue occurs, could you please confirm if you observed this behavior using the IoT Toolbox App?

Regards,
Eduardo.