periodic_adv_conn & BLE MESH

[joey]

HI

I am using the nRF54L15. Is it possible to integrate BLE Mesh functionality into the periodic_adv_conn example? This would allow the device to both receive data reported from a periodic_sync_connnode and route data with other periodic_adv_connnodes for data relaying and uploading.

Thanks!

[Hung Bui]

Hi, 

joey said:

So, is it feasible to establish a connection as long as the response slot is set with an appropriate interval

Yes, in that case it will not disturb the periodic advertising activity. I made a blog here a while ago, this could be useful for you: 
Periodic Advertising with Responses (PAwR): A practical guide
Connection v2 is touched briefly at section 3.3 

[joey]

joey said:

That's essentially correct. However, the 70 bytes refer to the data generated at the application layer, not the data after Bluetooth protocol encapsulation. Upon receiving and parsing out these 70 bytes, the advertiser forwards them directly without any processing. Each advertiser has approximately 500 nodes

Regarding the BLE+Zigbee solution, what are the evaluation conclusions?

Hung Bui said:

Yes, in that case it will not disturb the periodic advertising activity. I made a blog here a while ago, this could be useful for you: 
Periodic Advertising with Responses (PAwR): A practical guide
Connection v2 is touched briefly at section 3.3 

Thanks, I'll try it.​

[Hung Bui]

Hi, 

joey said:

Regarding the BLE+Zigbee solution, what are the evaluation conclusions?

Could you explain what you meant ? It's at production level as far as I know. Most of our Matter samples have BLE + Thread (802.15.4) support. 

[joey]

Hung Bui said:

Please give the exact number of byte to be transmitted from PAwR advertiser to PC and the interval so that we can calculate the throughput.

you mentioned earlier that you need my data reporting status to assess whether the Zigbee throughput is suitable for this type of application

[Hung Bui]

Hi, 
Yes but your throughput is really low as far as I understand. 
You are talking about 70 bytes * 500 nodes / hours = 9.7 bytes/s It should be fine with both Bluetooth mesh and Zigbee.