Tutorial for DA 14861 WEARABLE

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at https://www.dialog-semiconductor.com/support . We’ll be fixing bugs / optimising the searching and tagging over the coming days.
13 posts / 0 new
Last post
ksalgado
Offline
Last seen: 1 year 1 month ago
Joined: 2019-09-13 13:30
Tutorial for DA 14861 WEARABLE

Hi,

i would like to use the DA 14861 wearable version. I would like to ask if there is a tutorial such as, https://www.dialog-semiconductor.com/products/connectivity/bluetooth-low-energy/smartbond-da14680-and-da14681, but for the Wearable development kit specifically. Generally, i would lke to ask some hints about experimenting on this dk in terms of software. specifically, the development tools for the wearable, because i see in the site that there are tools such as Smartsnippets Studio and toolbox and it is not very clear to me what is need for this. finally, my experimentation with the dk is to switch off/on sensors or components of the wearable and calculate the energy consumptions. Are there any tutorials for something like this ?

Thank you in advance

Device: 
PM_Dialog
Offline
Last seen: 5 months 2 weeks ago
Staff
Joined: 2018-02-08 11:03
Hi ksalgado,

Hi ksalgado,

Thanks for your question online! Unfortunately, there isn’t any available tutorial for the DA14681 Wearable development kit specifically. Generally, all the available tutorials in DA14680/681 product page can be followed in every DA1468x based project. We don’t have any dedicated tutorial for any of our reference application designs. In the DA14681 Wearable DK support page you will find all the available documentation you need.

Regarding the tools, you should use the SmartSnippets Studio to build and debug any DA1468x related project. The SmartSnippets Toolbox contains useful tools to assist you with key development activities such as flash programming, power measurement and profiling etc. Please check the user manuals:

Regarding the power consumption measurements, I would recommend you first reading the AN-B-037 application note. Link is provided below:

https://www.dialog-semiconductor.com/sites/default/files/an-b-037_da1468x_power_measurements_v1.5.pdf

Thanks, PM_Dialog

ksalgado
Offline
Last seen: 1 year 1 month ago
Joined: 2019-09-13 13:30
Im a little confused. Some of

Im a little confused. Some of the UM-B-057 elements are not available in the wearable sdk. for example pxp _reporter etc. Isn't important to use the appropriate SDK depending on the DK ? Also, the components are not the same e.g in the wearable version there is no jtag. Is there something more about the wearable version to be more familiar with the wearable programming. I would like to see how to make a program where for e.g every 10 seconds the bluetooth component wakes up etc

Thanks 

PM_Dialog
Offline
Last seen: 5 months 2 weeks ago
Staff
Joined: 2018-02-08 11:03
Hi ksalgado,

Hi ksalgado,

The DA14681 Wearable development kit is a reference application design based on the DA1468x SDK. This project should be taken as a reference and it is designed to run with the dedicated development kit. The pxp_reporter is an SDK example which is included with the SDK. Generally, we provide some BLE and non-BLE examples which come with the SDK.

The DA14681 Wearable DK doesn’t contain JTAG. To do so, you should use an additional board named Communication Interface Board (CIB). Please read section 12.4 Connection with CIB from the user manual. I found a past forum thread that you had created before couple of months and I had provided you some guidelines:

https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-hardware-device-reference-designs/da-14681

Regarding your last question, can you please share more inputs? Do you want to stop advertising and wake up the chip periodically every 10 sec? In which project are you referring to? In the wearable project? Keep in mind that the device will go into sleep mode between advertising or connection intervals.

Thanks, PM_Dialog

ksalgado
Offline
Last seen: 1 year 1 month ago
Joined: 2019-09-13 13:30
Well i will try to explain

Well i will try to explain better from the beginning. Firstly, i have the wearable DK. In order to use it, first i installed Smartisnippet. Then i imported the wearable SDK. As far here am i right (i mean the above steps are correct?)? Then i try to experiment with the device, specifically to make a program that e.g will enable and disable some modules such as the heart sensor etc. This can be in intervals for example some sensors will wake up every 10 seconds while others in 30 seconds. In this phase i want to learn how to use and program it, and start with very simple things. How should i start?

Thank you very much and sorry if it feels that i am asking very basic questions, 

ksalgado
Offline
Last seen: 1 year 1 month ago
Joined: 2019-09-13 13:30
Are there any recommendations

Are there any recommendations ?

 

PM_Dialog
Offline
Last seen: 5 months 2 weeks ago
Staff
Joined: 2018-02-08 11:03
Hi ksalgado,

Hi ksalgado,

Yes, you are correct. You should import the wearable project into SmartSnippets Studio. It’s not a straight-forward implementation to start your own application. If you check the source code, you will find that many libraries should be imported. My recommendation would be to interact with the existing application code and start enabling/disabling some peripheral modules. The wrbl_app_defs.h header file includes definitions for the underlying software modules used by the Wearable Application. Also please check the wrbl_prof_Default.h which includes configuration attributes for the operation of the default - full feature list. For example, in 12.2.1.9 Gyroscope Sensor Settings section of the um-b-076 user manual, you will find all the gyroscope sensor configurations. You can define the ACCELEROMETER_SENSOR macro to SENSOR_NONE for disabling the accelerometer sensor. In general, I would strongly recommend you not modifying the source code. There are couple of definitions described in UM-B-076 DA14681 Wearable Development Kit Software Manual for interacting with the all peripheral modules/sensors.

If you are interested in starting a new project or modifying the existing one, you should read the  UM-B-085 DA14681 Wearable Development Kit API user manual. This document describes the API specifications of software modules of the application running on the Dialog DA14681 Wearable Development Kit. This manual intends to assist software developers who implement applications using the DA14681 Wearable Development Kit.  Keep in mind that Wearable reference application is obsolete, and it is supported as it is provided in our support portal.

Thanks, PM_Dialog

ksalgado
Offline
Last seen: 1 year 1 month ago
Joined: 2019-09-13 13:30
Thank you for the answer it

Thank you for the answer it was very helpful. I would like to ask in the example 12.2.1.9 while you set it in disable you cannot change it unless you compile it again, isn't it. Im asking this because i would like to make it more dynamic. As i told before i would like to do something for 10 seconds the gyroscope is disable in the macro but then to be enabled etc. In the way you explained, you predefine in the beggining if it will enabled from the beggining and this cannot be changed, isn't it?

 

Thank you in advance

PM_Dialog
Offline
Last seen: 5 months 2 weeks ago
Staff
Joined: 2018-02-08 11:03
Hi ksalgado,

Hi ksalgado,

The macro definitions are static, so you will need to build the source code every time. If you want to make it more dynamic, this is up to you and you should override many source code functionalities. I would not recommend it, as it not straight-forward and the wearable application code is supported as it is provided in our support website.

In case you have a sensor related project in your university, you can also move into DA14585 IoT Multi-Sensor Development Kit.

https://www.dialog-semiconductor.com/products/da14585-iot-multi-sensor-development-kit

Thanks, PM_Dialog

DanielHouston
Offline
Last seen: 1 year 9 months ago
Joined: 2020-10-28 11:58
Yes, I have my university

Yes, I have my university project on DA14585 IoT Multi-Sensor Development Kit. Thanks for the link  https://www.dialog-semiconductor.com/products/da14585-iot-multi-sensor-development-kit https://writemyessay.onl

ksalgado
Offline
Last seen: 1 year 1 month ago
Joined: 2019-09-13 13:30
Hi,

Hi,

searching on the  UM-B-085 DA14681 Wearable Development Kit API, i found the bmi160_set_sensor_state(). Would you recomend to use it for the dynamic change of states for example from ACC_SUSPEND to Normal? If yes, should i change something else? Where would you recommend me to implement this ? E.g in main.c it will not work, so where shoult i put it?

ksalgado
Offline
Last seen: 1 year 1 month ago
Joined: 2019-09-13 13:30
Hi are any recommendations? I

Hi are any recommendations? I am asking as, there is no tutorial and the API describes only the inputs and the outputs, and no where should these fucntion should be used.

 

PM_Dialog
Offline
Last seen: 5 months 2 weeks ago
Staff
Joined: 2018-02-08 11:03
Hi ksalgado,

Hi ksalgado,

If you search into the source code, you will see that the bmi160_set_sensor_state() is called in sc_impl_bmi160_and_bmm150.c file. As you can see, there is a whole mechanism that handles and control all the sensors’ states. To do so, calling the bmi160_set_sensor_state() in the main function, will not change the accelerometer state. Why don’t you use the Wearable mobile application to manually controlling the sensors? As I have already mentioned, changing the source code of the Wearable kit is not a straight-forward. The ACC_SUSPEND state is set in the following functions : sc_impl_power_state_set_step_bmi160_and_bmm150(), sc_impl_power_state_set_acc_bmi160_and_bmm150().

Thanks, PM_Dialog