This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Mesh proxy light switch client, current consumption with the Power Profile kit (PPK)

Hello, I currently using the proxy light switch exemple of the mesh SDK 2.0.1 in this configuration : 

I search to have the less current consumption in the mesh client .

With the Power Profile Kit of nordic I have this result :

 

With a lot of pic comsuption approximately every 10-30 ms. This measure is take when the Client is connected with a serveur( GATT conection) . (The devices are provisonned,  I can light-up the servers leds.)

This is my configuration :

#define MIN_CONN_INTERVAL MSEC_TO_UNITS(250, UNIT_1_25_MS)
#define MAX_CONN_INTERVAL MSEC_TO_UNITS(1000, UNIT_1_25_MS)

(same value for the client and the server)

I don't understand my measure.

I would like to know why the pic isn't every 250ms ( or between 250-100ms). And how I can have less energy comsuption.

Thanks in advance

Axel Collet

Parents
  • Hi,

    I suspect that this is a misunderstanding due to our bad naming of the light switch examples of nRF5 SDK for Mesh version 2.0.1.

    There are five projects in the light_switch example: Client, provisioner, proxy_client, proxy_server and server. All of those are "normal" Bluetooth Mesh nodes. The proxy_client and proxy_server have both enables the proxy feature, which means they both operate as "proxy servers" according to the Bluetooth Mesh specification.

    The project named "proxy_client" is better described as "light switch client with proxy feature", or "light switch client with proxy server". So it is the "light switch" model that is client or server, not the proxy feature.

    With that in mind, seeing that the node uses ADV bearer close to 100 % of the time, high power consumption should be expected.

    We are working on libraries and applications both for iOS and Android, for the client connecting to the node with GATT proxy feature, but at the moment we have not released those. This means at the moment we provide neither examples nor tools for proxy client. Only for proxy server.

    Please note that the use case for the proxy feature is for legacy devices to participate in a Bluetooth Mesh network (primarily targeted at smartphones). It is not for low power operation. For that, you need the friend feature and low power nodes, which we have scheduled for implementation later this year. For more information about planned features and schedules, please contact our sales representative for your area. If you do not know who that is then please ask in a private ticket.

    Regards,
    Terje

Reply
  • Hi,

    I suspect that this is a misunderstanding due to our bad naming of the light switch examples of nRF5 SDK for Mesh version 2.0.1.

    There are five projects in the light_switch example: Client, provisioner, proxy_client, proxy_server and server. All of those are "normal" Bluetooth Mesh nodes. The proxy_client and proxy_server have both enables the proxy feature, which means they both operate as "proxy servers" according to the Bluetooth Mesh specification.

    The project named "proxy_client" is better described as "light switch client with proxy feature", or "light switch client with proxy server". So it is the "light switch" model that is client or server, not the proxy feature.

    With that in mind, seeing that the node uses ADV bearer close to 100 % of the time, high power consumption should be expected.

    We are working on libraries and applications both for iOS and Android, for the client connecting to the node with GATT proxy feature, but at the moment we have not released those. This means at the moment we provide neither examples nor tools for proxy client. Only for proxy server.

    Please note that the use case for the proxy feature is for legacy devices to participate in a Bluetooth Mesh network (primarily targeted at smartphones). It is not for low power operation. For that, you need the friend feature and low power nodes, which we have scheduled for implementation later this year. For more information about planned features and schedules, please contact our sales representative for your area. If you do not know who that is then please ask in a private ticket.

    Regards,
    Terje

Children
No Data
Related