<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MPSL timslot sample: sender and receiver</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/118732/mpsl-timslot-sample-sender-and-receiver</link><description>Can some one describe how this is supposed to work: 
 https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/mpsl/timeslot/README.html 
 I would have expected to see some sender and receiver code. 
 Can I run this on 2 different boards? and exchange</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 11 Apr 2025 13:11:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/118732/mpsl-timslot-sample-sender-and-receiver" /><item><title>RE: MPSL timslot sample: sender and receiver</title><link>https://devzone.nordicsemi.com/thread/531537?ContentTypeID=1</link><pubDate>Fri, 11 Apr 2025 13:11:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e6de8c95-2340-4541-ab77-fad490ee4d96</guid><dc:creator>SwRa</dc:creator><description>&lt;p&gt;Hi Klaus,&lt;/p&gt;
&lt;p&gt;T&lt;span style="font-family:inherit;font-size:inherit;"&gt;he MPSL (Multi-Protocol Service Layer) timeslot functionality is different from a typical sender/receiver communication example. The timeslot API allows developers to implement their own 2.4 GHz proprietary protocol that can run concurrently with other protocols using MPSL. It essentially gives your application access to the radio and other restricted peripherals during defined time intervals (timeslots).&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:inherit;font-size:inherit;"&gt;I suggest that you refer the timeslot documentation here:&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrfxlib/mpsl/doc/timeslot.html"&gt;https://docs.nordicsemi.com/bundle/ncs-latest/page/nrfxlib/mpsl/doc/timeslot.html&lt;/a&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-family:inherit;font-size:inherit;"&gt;1. The code snippet you shared with bt_data_cb is from Bluetooth API and not the Timeslot API. These are different mechanisms. When using MPSL timeslots, you need to implement your own radio protocol handling (configure, receive, etc.) within the timeslot callback.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-family:inherit;font-size:inherit;"&gt;2. The timeslot will be scheduled at the next available time that doesn&amp;#39;t conflict with higher-priority activities. If there&amp;#39;s a conflict with a higher-priority event (like critical BLE packets), your request might be canceled. See here:&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrfxlib/softdevice_controller/doc/scheduling.html#timeslot_api_timing"&gt;https://docs.nordicsemi.com/bundle/ncs-latest/page/nrfxlib/softdevice_controller/doc/scheduling.html#timeslot_api_timing&lt;/a&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-family:inherit;font-size:inherit;"&gt;Best Regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="font-family:inherit;font-size:inherit;"&gt;Swathy&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MPSL timslot sample: sender and receiver</title><link>https://devzone.nordicsemi.com/thread/522011?ContentTypeID=1</link><pubDate>Fri, 07 Feb 2025 15:36:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:22baaf02-55bc-447c-9280-74ec0679de32</guid><dc:creator>klaus1234</dc:creator><description>&lt;div style="background-color:#ffffff;color:#000000;font-family:Consolas, &amp;#39;Courier New&amp;#39;, monospace;font-size:14px;font-weight:normal;line-height:19px;white-space:pre;"&gt;
&lt;div&gt;&lt;span style="color:#000000;"&gt;&lt;span style="color:#001080;"&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;div style="background-color:#ffffff;color:#000000;font-family:Consolas, &amp;#39;Courier New&amp;#39;, monospace;font-size:14px;font-weight:normal;line-height:19px;white-space:pre;"&gt;&lt;br /&gt;Two further questions:&lt;br /&gt;&lt;br /&gt;1: on the receiver side, how do I get the received bytes in the time slot?&lt;br /&gt;&lt;br /&gt;static struct bt_data_cb eeg_cb = {&lt;br /&gt; .received = bt_receive_cb,&lt;br /&gt; .send_enabled = bt_send_enabled_cb,&lt;br /&gt;};&lt;br /&gt;in .received call back?&lt;/div&gt;
&lt;div style="background-color:#ffffff;color:#000000;font-family:Consolas, &amp;#39;Courier New&amp;#39;, monospace;font-size:14px;font-weight:normal;line-height:19px;white-space:pre;"&gt;&lt;/div&gt;
&lt;div style="background-color:#ffffff;color:#000000;font-family:Consolas, &amp;#39;Courier New&amp;#39;, monospace;font-size:14px;font-weight:normal;line-height:19px;white-space:pre;"&gt;2. in case I have a BLE connection and I reserve the earliest timeslot(MPSL),&lt;/div&gt;
&lt;div style="background-color:#ffffff;color:#000000;font-family:Consolas, &amp;#39;Courier New&amp;#39;, monospace;font-size:14px;font-weight:normal;line-height:19px;white-space:pre;"&gt;will this be at the begining of the next connection interval?&lt;/div&gt;
&lt;div style="background-color:#ffffff;color:#000000;font-family:Consolas, &amp;#39;Courier New&amp;#39;, monospace;font-size:14px;font-weight:normal;line-height:19px;white-space:pre;"&gt;Or is the whole connection interval thing bypassed, and it will be the next available&lt;/div&gt;
&lt;div style="background-color:#ffffff;color:#000000;font-family:Consolas, &amp;#39;Courier New&amp;#39;, monospace;font-size:14px;font-weight:normal;line-height:19px;white-space:pre;"&gt;time slot, regarding what BLE is doing?&lt;/div&gt;
&lt;div style="background-color:#ffffff;color:#000000;font-family:Consolas, &amp;#39;Courier New&amp;#39;, monospace;font-size:14px;font-weight:normal;line-height:19px;white-space:pre;"&gt;Thanks&lt;/div&gt;
&lt;div style="background-color:#ffffff;color:#000000;font-family:Consolas, &amp;#39;Courier New&amp;#39;, monospace;font-size:14px;font-weight:normal;line-height:19px;white-space:pre;"&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MPSL timslot sample: sender and receiver</title><link>https://devzone.nordicsemi.com/thread/521954?ContentTypeID=1</link><pubDate>Fri, 07 Feb 2025 13:42:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9f95e9c5-111a-4fb2-bfc3-97a9558fd53b</guid><dc:creator>SwRa</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;The sample you&amp;#39;re referring to is the MPSL (Multiprotocol Service Layer) Timeslot sample, which demonstrates how to use basic MPSL Timeslot functionality. This sample is not designed for sending and receiving data between two boards. Instead, it focuses on illustrating how to request and use timeslots within a single device.&lt;/p&gt;
&lt;p&gt;It demonstrates how to open a timeslot session and request timeslots using the MPSL Timeslot API [MPSL timeslot](&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/mpsl/timeslot/README.html)."&gt;docs.nordicsemi.com/.../README.html).&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;As explained in the documentation overview, the application does the following:&lt;br /&gt; - It opens a timeslot session when a key is pressed in the terminal.&lt;br /&gt; - Pressing &amp;#39;a&amp;#39; requests a new timeslot.&lt;br /&gt; - Pressing &amp;#39;b&amp;#39; ends the current timeslot.&lt;br /&gt; - Upon receiving timeslot start signal, the sample configures a timer to trigger before the timeslot ends.&lt;br /&gt; - prints the timeslot signal type.&lt;/p&gt;
&lt;p&gt;To exchange data between two boards, you would need&amp;nbsp;to use different samples that implements a communication protocol. You can read more about MPSL here:&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrfxlib/mpsl/README.html#mpsl"&gt;https://docs.nordicsemi.com/bundle/ncs-latest/page/nrfxlib/mpsl/README.html#mpsl&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Swathy&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>