Mesh SDK Architecture?

RE: Mesh SDK Architecture?

Hung Bui — Mon, 06 Nov 2017 15:34:20 GMT

Timeslot is the mechanism where you request the softdevice's scheduler to guarantee a period of time that you can access all the peripheral blocked by the softdevice, such as Radio, Flash, Timer 0.

You can have a look at the softdevice device specification for more information, look for "Multiprotocol Support" chapter.

What you described in your application, advertising, scanning, serial TX. It was all executed by calling the softdevice API, correct ?

How often do you advertise ? How did you configure scan parameter (scan window, scan interval) ?

RE: Mesh SDK Architecture?

ManuGira — Mon, 06 Nov 2017 09:54:32 GMT

Hi Hung Bui,

I'm not sure to understand what is the timeslot mechanism. Does it refers to the hopping behavior between TX and RX?

I'm developping an application where a client node needs to perform 3 tasks alternatively:

advertising
scanning
serial tx.

But most of the published packets sent by the other nodes never arrive to the client. I think this is because the client does't spend enough time for scanning.

Should I understand from your comment that it is not yet possible to manage the time spent for scanning VS advertising VS serial tx ?

RE: Mesh SDK Architecture?

Hung Bui — Tue, 17 Oct 2017 09:14:06 GMT

Hi Godmode,

We don't discuss the roadmap and future product on this forum. Please contact our Sale representative for these questions. Let me know if you don't have contact to your regional Nordic's Sale representative.

RE: Mesh SDK Architecture?

godmode — Mon, 16 Oct 2017 15:31:35 GMT

What is the estimated time to market for beta and final release of Mesh SDK? Any new progress?

RE: Mesh SDK Architecture?

Hung Bui — Thu, 12 Oct 2017 11:58:22 GMT

Hi Ian,

Our Bluetooth Mesh stack and SDK are still underdevelopment and remains in alpha phase. It can be changed.

We do use the BLE stack in the SDK. You need to flash S132 or S140 to be able to run Mesh example.

But Bluetooth Mesh technology is not part of BLE technology or as application layer or profile layer of a BLE stack. If you have a look here. You can find that Bluetooth Mesh only share the two lowest layer: Link layer and physical layer with BLE.

Anything above that is different.

So there is no point integrate Mesh into current BLE stack.

We are using our BLE stack in Mesh SDK just to support (in the future) GATT bearer and to use the timeslot mechanism supported in the BLE Stack. Also it would be easier to integrate Mesh into current BLE application and vise versa, for instant the beacon example in Mesh SDK.