Multilink: accuracy scheduling

RE: Multilink: accuracy scheduling

Sigurd — Wed, 01 Jul 2020 15:51:13 GMT

[quote userid="51855" url="~/f/nordic-q-a/62013/multilink-accuracy-scheduling/254087"]If for example, now only one or two devices are on the air. Can I somehow reserve a place in the temporary layout of the stack? To create a new connection at the time I need.[/quote]

A best-fit algorithm is used to find which free time space should be used when creating a new connection. This is explained and illustrated in the Scheduling Initiator timing chapter in the SDS. See this link.

RE: Multilink: accuracy scheduling

CheMax — Tue, 09 Jun 2020 15:25:33 GMT

Hi,

I apologize for the long wait.

[quote userid="73427" url="~/f/nordic-q-a/62013/multilink-accuracy-scheduling/253332"]A1& A2. Could you explain what you mean with redundancy manual positioning? I didn't quite understood the question.[/quote]

I will try to explain in more detail.

I want to ensure a strict sequence of sensor connections in order to maximize the effective use of radio. Ideally, if I get the connections in the following order: yellow, green, blue (as in the picture above).This is not difficult to do at the application level if all three devices are already on and ready to go. Ok.

Now about the difficult. If for example, now only one or two devices are on the air. Can I somehow reserve a place in the temporary layout of the stack? To create a new connection at the time I need.

Best regards, Max

RE: Multilink: accuracy scheduling

Marjeris Romero — Thu, 04 Jun 2020 14:18:48 GMT

Hi Max,

A1& A2. Could you explain what you mean with redundancy manual positioning? I didn't quite understood the question.

A3. For changing the connection event length you should set the right value for NRF_SDH_BLE_GAP_EVENT_LENGTH for both master and slave. You could also enable connection event length extention. The connection event length doesn't need to be matched between master and slave devices, but it's recommended that all connection have intervals that have a common factor, see more information in https://infocenter.nordicsemi.com/topic/sds_s132/SDS/s1xx/multilink_scheduling/suggested_intervals_windows_s132.html?cp=4_6_2_0_14_9

A4. If the NRF_SDH_BLE_GAPP_EVENT_LENGTH is too low, then yes you should enable connection event length extension.

A5. yes, if you use PA/LNA, there is a own configuration you can use, see this blogpost for more information: https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/pa-lna-support-in-s132

Best regards,

Marjeris