chromebook cannot receive notification from nRF51822 using s110 v6.0

[irarykim]

Environment:

BLE Slave Module: nRF51822, s110 v6.0, based on UART over BLE application example

Chromebook: ASUS C101P, Chrome os 70.03538.110 (32 bit)

I have a BLE slave module(nRF51822, s110 v6.0, based on UART over BLE application example) which is working well with Android, iOS, S120 v1.0.

Below is a capture image from Master Control Panel software for this slave module.

As it is shown, this module uses Nordic UART over BLE service with TX and RX characteristics.

For Tx characteristic(Slave -> Master), it uses notification type.

 (you can see if you click this image icon)

Recently I wanted use a ASUS Chomebook (70.03538.110 (32 bit)) for paring and communicating with this Slave Module.

The app is the same app worked well on Android devices.

This app is based on "nRF UART v2.0" which is provided by Nordic semiconductor.

But I found Chromebook doesn't catch notification event.

It catches if I debug step-by-step, but when I run the program, it misses the notification event.

Does anyone have similar experience or any suggestion?

Thank you!

[Mttrinh]

Hi,

Master Control Panel is really old and I would suggest you to use nRF Connect for Desktop instead. Can you try and see if the same issue occurs with nRF Connect?

[irarykim]

Hi, Mttrinh,

My Slave Module is working well with this Master Control Panel, tx and rx. The problem is chromebook , not windows pc.

[Mttrinh]

I'm not too familiar with Chromebook but it can run Android applications, right? 

Can you try with nRF Connect for Android? Or nRF Toolbox? 

The nRF Toolbox is a container app that stores your Nordic Semiconductor apps for BLE in one location, including nRF UART.

[irarykim]

Hi, Mttrinh, 

Thanks for your hint.

nRF Connect works fine on Chromebook!

I will debug according to this clue.

I will add reply after test .

[irarykim]

Mttrinh

According to Mttrinh's suggestion, I tried  nRF Connect for Android, and Chromebook worked perfectly. There was a bug in the firmware of my BLE. Chromebook is innocent!