Mesh Gatt Peripheral Role

[Charlie Choi]

Device nrf52832, nrf5_SDK_for_Mesh_v3.2.0_src with nRF5_SDK_15.3.0_59ac345

Hello.

I want to transmit and receive some data between smartphone app and mesh sensor.(almost similar function as light_switch server model)

I made the mesh server has a specific ble name(e.g. SENSOR_ABCD) and wanted to connect to the server while the server is working as a member of mesh network through my own smart phone app.

However, when my app scans and searchs the ble name(SENSOR_ABCD), it appears for very short time and disappears and I cannot connect to it. Actually, I can still see the sensor's BLE address but it doesn't have name. also it's advertisement type is shown as Non-connectable.

It seems that I can find the ble name and can connect to it if there is little mesh packets. But if there are many mesh packets, the name disappears.

What's the reason and what should I do to communicate with mesh server through my smartphone app?

Thank you in advance.

Charlie. 

[Kenneth]

I was thinking the problem could be related to the same gap address is used for connectable and non-connectable here. This may prevent the mobile to connect to the device, so maybe change the gap address before starting connectable advertisement? Something like:

    ble_gap_addr_t gap_addr;
    err_code = sd_ble_gap_addr_get(&gap_addr);
    APP_ERROR_CHECK(err_code);    
    gap_addr.addr[3] = ~gap_addr.addr[3]; // flip the bits when connectable
    err_code = sd_ble_gap_addr_set(&gap_addr);
    APP_ERROR_CHECK(err_code);  

[Charlie Choi]

Hello Kenneth,

Thank you for your advice. I tested per your suggestion and got a good result. i.e. Device name and advertisement type seems stable.

Could you confirm that this alteration of gap address doesn't affect the mesh function?

Thank you.

Charlie.

[Kenneth]

Good to hear that it works, I do not see any reason why this should affect mesh function no.

Kenneth