Xiao Sense BLE ISSUE - ZephyrOS

[vgarcive]

Hi Everyone,

I am trying to develop a simple application with the XIAO BLE Sense device, the idea is to send a BLE message when something hits the device. To achieve this, I wanted to configure the BLE to notify the event after connecting with the master. I problem I have is very simple but I cant figure out how to solve it, the problem is that I always have to Enable notifications on my phone in order to receive the notification, How can I change that to receive the message without the need to enable anything on the phone?? Thanks!!

First of all, let me summarize what I am using and what program I have uploaded to the device:

• Hardware:
  • Xiao BLE Sense.
• Software:
  • Visual Studio Code.
  • nRF Connect for VS Code Extension Pack (latest version).
  • nRF Connect SDK Toolchain v2.5.2
  • nRF Connect SDK v2.5.2
  • Zephyr OS.

I have used the Zephyr Example for BLE and I have the following piece of code:

/* Accel readings Service Declaration and Registration */
BT_GATT_SERVICE_DEFINE(accel_service,
BT_GATT_PRIMARY_SERVICE(BT_UUID_ACCELSERVICE),
BT_GATT_CHARACTERISTIC(BT_UUID_ACCELSERVICE_RX,
			       BT_GATT_CHRC_WRITE | BT_GATT_CHRC_WRITE_WITHOUT_RESP,
			       BT_GATT_PERM_READ | BT_GATT_PERM_WRITE, 
                   NULL, on_receive, NULL),
BT_GATT_CHARACTERISTIC(BT_UUID_ACCELSERVICE_TX,
			       BT_GATT_CHRC_NOTIFY,
			       BT_GATT_PERM_READ ,//BT_GATT_PERM_READ,
                   NULL, NULL, NULL),
BT_GATT_CCC(on_cccd_changed,
        BT_GATT_PERM_READ | BT_GATT_PERM_WRITE),
);

int bt_ready(void) {
    return perform_bt_ready();
}

int my_service_init(void)
{
    int err = 0;
   
    memset(&data_rx, 0, MAX_TRANSMIT_SIZE);
    memset(&data_tx, 0, MAX_TRANSMIT_SIZE);
    
    return err;
}

void my_service_send(const uint8_t *data, uint16_t len)
{
    /* 
    The attribute for the TX characteristic is used with bt_gatt_is_subscribed 
    to check whether notification has been enabled by the peer or not.
    Attribute table: 0 = Service, 1 = Primary service, 2 = RX, 3 = TX, 4 = CCC.
    */
    const struct bt_gatt_attr *attr = &accel_service.attrs[3]; 

    struct bt_gatt_notify_params params = 
    {
        .uuid   = BT_UUID_ACCELSERVICE_TX,
        .attr   = attr,
        .data   = data,
        .len    = len,
        .func   = on_sent
    };

    // Check whether notifications are enabled or not
    if(bt_gatt_is_subscribed(my_connection, attr, BT_GATT_CCC_NOTIFY)) 
    {
        // Send the notification
	    if(bt_gatt_notify_cb(my_connection, &params))
        {
            printk("Error, unable to send notification\n");
        }
    }
    else
    {
        printk("Warning, notification not enabled on the selected attribute\n");
    }
}  

Thanks beforehand, sorry for the inconveniences and looking forward to hearing from you.

Kind regards.

[Hieu]

Hi vgarcive,

There is an old DevZone case on this topic and the answer is still valid now:
RE: How to enable notification on the peripheral side?

If you really need the notification working without having to be re-enabled from the client, you can use bonding. Note that when you have a dedicated phone app for your application, enabling notification is just one line of code, and a moment in real time, not user-recognizable at all.

A more convoluted solution is to have the Server on the Central, and the Client on the Peripheral. That way, the data from the Peripheral is sent with a Write instead, not requiring Notification enabling. This approach is very rarely used and doesn't bring any big benefit though.

Hieu

[Akshay Mehta]

 Hi Hieu ,

Not sure if you already got a solution or not. You can checkout our sample library for XIAO nRF52840. Let us know if you face any issues on our slack channel.

Best,

Akshay 

[Hieu]

Hi Akshay,

I am not the one with question in this thread but thank you for trying to help. I am sure the topic creator, vgarcive, has received notification of your response.

However, I have looked at the links you provided and would like to have some feedback.

The presentation of the library and links made it possible to see your answer as suspicious.

Firstly, please do not distribute library in .zip file on GitHub. It is not clear what the zip file contains. You should publish the source code along documentation, no matter how brief.

Secondly, as you are referring people to a Slack channel. I would like to ask you to give a few words about what the channel is about, and who are there.

My apology if you are trying to help and my words discourage you. That isn't the intention. Please take my reply as suggestions to make your contribution better received.

Best regards,

Hieu

[Akshay Mehta]

Hi Hieu ,

Thanks for a prompt reply! The contents are listed here (on Github and the README file also has the notion link). However we will publish the sources for samples and object files for OTAinfo libraries.

The Slack channel is to support users who wish to use OTAinfo library. It is created by OTAinfo, Inc.  

Best,

Akshay