Mesh with bi-direction communication

RE: Mesh with bi-direction communication

kian79 — Sun, 24 Mar 2019 13:38:54 GMT

Thanks Hung Bui. I got this to work already. But I have other questions about the multi-link-multi-role demo. I will start another thread with more specific questions.

RE: Mesh with bi-direction communication

Hung Bui — Wed, 16 Jan 2019 12:07:38 GMT

Which issue did you have ? I tried here and it worked for me.

RE: Mesh with bi-direction communication

Vroon — Wed, 16 Jan 2019 01:53:27 GMT

Hello Hung Bui,

I checked the update, but I guess PCA10040 still isn't supported. Any idea how to go on about this? I'm having the same issues as Kian.

RE: Mesh with bi-direction communication

Hung Bui — Mon, 14 Jan 2019 09:23:11 GMT

Hi Kian,

I'm so sorry for that. I got the developer updated the project. Please try again.

RE: Mesh with bi-direction communication

kian79 — Sat, 12 Jan 2019 00:55:32 GMT

Hi Hung Bui,

I like to further feedback that the program for ble_peripheral is not working too for pca10040. I like to compile and download the codes onto a Nordic Thingy. I am trying to compile the ble_peripheral project for pca10040 on SES and I am getting this error:

C:\NordicSemi\nRF5_SDK_15.2.0\examples\components\libraries\log\src\nrf_log_backend_rtt.c: No such file or directory

I figured that the components directory is referenced wrongly in the project properties. So rather than changing the user directory in project options -> preprocessor, I just copied and paste the components directory inside the examples directory. I tried compiling again and I am getting another error:

compiler_abstraction.h: No such file or directory

I am not sure how to fix this and if there will be more errors after fixing this. Can Nordic also help to check and fix this project?

I am using SES with the latest SDK15.2 downloaded from Nordic.

RE: Mesh with bi-direction communication

Hung Bui — Fri, 11 Jan 2019 10:12:49 GMT

If you have nRF52840 DK you can use the SES project for it in github and it should work out of the box. Keil project should also work if you include the missing file (in common folder). I would suggest to install SES and have a look inside the project to find the difference to fix the Keil project. It should be only 2 files missing.
You don't have to do anything extra. The programming tutorial is for other application.

RE: Mesh with bi-direction communication

kian79 — Fri, 11 Jan 2019 08:50:28 GMT

Thanks Hung Bui, I will wait for the updated codes on Github.

Alternatively, I have a nRF52840 dongle (PCA10059). Can that work replace the nRF52840DK as an aggregator? If so, do I need to make any changes to the codes?

I read on the nRF52840 dongle programming tutorial, the says the following:

Adjust the linker configuration. Set FLASH_START=0x1000 to place the application right above the MBR. You should also set FLASH_SIZE=0xDF000 to make sure that there is room for the bootloader at the end of the flash. Set RAM_START=0x20000008, as the first 8 bytes are used by the MBR for interrupt forwarding and adjust the size accordingly by setting RAM_SIZE=0x3FFF8.

Do I have the same exact change too?

RE: Mesh with bi-direction communication

Hung Bui — Thu, 10 Jan 2019 14:58:53 GMT

Hi Kian,

When you see Fatal error, you can debug it. You can follow this guide.

However, the issue you are having is related to the fact that we was preparing the demo for PCA10056 (nRF52840 DK) SES and the other projects were not updated. I have reported this internally and it should be fixed most likely by the end of tomorrow. Please try again later.

RE: Mesh with bi-direction communication

kian79 — Thu, 10 Jan 2019 08:31:18 GMT

Hi Hung Bui,

I am trying your suggestion. I have downloaded nRF5_SDK_v15.2.0, downloaded the nrf52-ble-multi-link-multi-role example and followed the instructions on the github page. I do not have nRF52840 PDK, so I am using a nRF52832DK (PCA10040) and I am more familiar with using Keil.

I opened the project in the directory nRF5_SDK_15.2.0\examples\training\ble-multi-link-multi-role\ble_aggregator\pca10040\s132\arm5_no_packs\ble_aggregator_pac10040_s132.uvprojx and tried to compile the project.

I got the error:

..\..\..\main.c(62): error: #5: cannot open source input file "ble_lbs_c_extended.h": No such file or directory

I figured that I have to include the ble_lbs_c_extended.h file, so I went into project options to include this directory: ..\..\..\..\common\ble_lbs_extended

I tried to compile again and now, I am getting this error which I have no idea how to solve:

.\_build\nrf52832_xxaa.axf: Error: L6218E: Undefined symbol ble_lbs_led_color_send (referred from main.o).

Also, I noticed there are a few ble_peripheral directories: ble_peripheral, ble_peripheral_long_range, and ble_peripheral_long_range_color. What is their difference?

I have a Nordic Thingy. Which program should I use?

Can you help? Thank you.

Update:

I commented out a few lines that made a call to the function: ble_lbs_led_color_send:

// First, try to access the devices as a Blinky device
//err_code = ble_lbs_led_color_send(&m_lbs_c[i], colors);
//if(err_code != NRF_SUCCESS)
//{
// If the blinky call fails, assume this is a Thingy device
err_code = ble_thingy_uis_led_set_constant(&m_thingy_uis_c[i], button_action ? r : 0, button_action ? g : 0, button_action ? b : 0);
if (err_code != NRF_SUCCESS &&
err_code != BLE_ERROR_INVALID_CONN_HANDLE &&
err_code != NRF_ERROR_INVALID_STATE)
{
return err_code;
}
//}

The program compiles successfully now. However, when I try to load the program onto the nRF52DK, nothing is happening. I don't see any LED blinking neither can I scan for the aggregrator from the android app. I also used RTT viewer to see the log and saw the following errors:
0> <error> app: Fatal error
0> <warning> app: System reset
0> <error> app: Fatal error

Debugging the program shows that the program go to system reset on the line:

gap_params_init();

RE: Mesh with bi-direction communication

Hung Bui — Wed, 09 Jan 2019 16:25:17 GMT

No, the phone wouldn't support upto 20 links. Normally a phone supports 5-6 links. What I meant is to have a central device that connect to the other 19 devices and also to the phone.

You can have a look at this demo: https://www.youtube.com/watch?v=tbl6Dui-_w4

Source code is here: github.com/.../nrf52-ble-multi-link-multi-role

RE: Mesh with bi-direction communication

kian79 — Wed, 09 Jan 2019 15:21:58 GMT

Hi Hung Bui,

Thank you for the reply. I am only looking at a range of about 50m or less. You mention that the Nordic softdevice supports up to 20 concurrent links. Is this supported by any mobile phone that has BLE? Or different models of phones or mobile OS will affect the number of concurrent links?

Does this then mean that I can have each of these devices running ble_app_uart and have the phone connected to all 20 of them at the same time and exchange information?

RE: Mesh with bi-direction communication

Hung Bui — Wed, 09 Jan 2019 14:34:48 GMT

Hi,

What is the distance between devices and to the phone ? If it's in the RF range with the phone, you don't really Mesh. Our BLE softdevice support up to 20 concurrent links.

If mesh is needed, your application is pretty similar to this demo: https://www.youtube.com/watch?v=XthbU9NP0Yg

The source code is provided here: https://github.com/NordicPlayground/thingy52-mesh-provisioning-demo

It can be configured with our nRF mesh app.

Of course you would need to modify the app and firmware to customize for your application, but it's a good place to start with.