<?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>Really continuous rx operation on nRF91x1</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/114808/really-continuous-rx-operation-on-nrf91x1</link><description>Currently with the DECT NR+ modem API on nRF91x1 I can schedule rx operations in mode NRF_MODEM_DECT_PHY_RX_MODE_CONTINUOUS given to nrf_modem_dect_phy_rx via nrf_modem_dect_phy_rx_params . But that means it gets scheduled for at most uint32_t duration</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 16 Oct 2025 09:30:02 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/114808/really-continuous-rx-operation-on-nrf91x1" /><item><title>RE: Really continuous rx operation on nRF91x1</title><link>https://devzone.nordicsemi.com/thread/551686?ContentTypeID=1</link><pubDate>Thu, 16 Oct 2025 09:30:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a2d7656c-6719-48bf-bc12-34376316d46b</guid><dc:creator>Herr Schubert</dc:creator><description>&lt;p&gt;Definitly! &lt;br /&gt;With our scanner/scan-feature we currently have the problem of that small &amp;quot;rx-gap&amp;quot; when doing un-synchronized scan. If the chip would provide that continous rx-mode we of course would use that.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Really continuous rx operation on nRF91x1</title><link>https://devzone.nordicsemi.com/thread/551676?ContentTypeID=1</link><pubDate>Thu, 16 Oct 2025 08:30:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:07e072e0-061a-492d-b9fb-ae8206b99279</guid><dc:creator>Mich@l</dc:creator><description>&lt;p&gt;Are there any new updates? Are there any plans to add really continous reception?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Really continuous rx operation on nRF91x1</title><link>https://devzone.nordicsemi.com/thread/508755?ContentTypeID=1</link><pubDate>Fri, 01 Nov 2024 07:47:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bf3c0db3-f39e-4154-9427-a7e3568c36b8</guid><dc:creator>Herr Schubert</dc:creator><description>&lt;p&gt;Thank you for that clarification.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Really continuous rx operation on nRF91x1</title><link>https://devzone.nordicsemi.com/thread/508670?ContentTypeID=1</link><pubDate>Thu, 31 Oct 2024 13:20:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f486d443-fb14-4311-9f94-6b24bd81287d</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;&lt;span&gt;Modem team; There will be a small gap between the end of previous RX operation and start of the next scheduled one, i.e those are two separate operations with RX stop → RX start. So there is a chance that the device misses the start of the packet (resulting to missing packet as STF + Pcc is not detected) in case the msg is incoming when there is the gap in reception.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Really continuous rx operation on nRF91x1</title><link>https://devzone.nordicsemi.com/thread/508567?ContentTypeID=1</link><pubDate>Wed, 30 Oct 2024 16:21:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1b516e69-204e-4adb-928d-1be3d6fa7020</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;I will ask modem team.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Really continuous rx operation on nRF91x1</title><link>https://devzone.nordicsemi.com/thread/506105?ContentTypeID=1</link><pubDate>Mon, 14 Oct 2024 12:09:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:999e26f4-9fdf-417d-8f8f-5c3863c101e4</guid><dc:creator>Herr Schubert</dc:creator><description>&lt;p&gt;Thank you for your reply. I currently implemented it with re-scheduling immediately from operation_complete() as you suggested. That works so far.&lt;br /&gt;&lt;br /&gt;But with that re-scheduling new RX in advance does the modem just proceed with RX or does it stop and restart the rx process?&lt;br /&gt;Is it then possible to receive a message which gets received while the old rx process terminates and the new rx process gets started directly after it? Or is that message still lost?&lt;br /&gt;In other words does each RX operation just see one half of that message (which are of course invalid for its own)?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Really continuous rx operation on nRF91x1</title><link>https://devzone.nordicsemi.com/thread/505706?ContentTypeID=1</link><pubDate>Thu, 10 Oct 2024 10:51:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:600ea26e-620b-4b60-a04a-151b63528fdb</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;Modem team;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;In dect_shell, we have workarounded this lack so that we start the RX for the duration of &lt;code&gt;UINT32_MAX&lt;/code&gt; and when that gets completed: we simply restart it. Yeah, there is a gap when RX is not on when restarting but in our case that is not crucial. To get rid of that gap, application could reschedule new RX just before previous is completing.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Really continuous rx operation on nRF91x1</title><link>https://devzone.nordicsemi.com/thread/504180?ContentTypeID=1</link><pubDate>Fri, 27 Sep 2024 12:50:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7e4ecb8a-c65c-438d-a991-caeedde29ad7</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;Modem team;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Duration is initially specified to cover the maximum DECT NR+ beacon interval, so 32 bits has been enough. But this is good input for us to improve the API in future releases! Unfortunately next release content is already fixed but we evaluate this for the following one.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Really continuous rx operation on nRF91x1</title><link>https://devzone.nordicsemi.com/thread/503685?ContentTypeID=1</link><pubDate>Wed, 25 Sep 2024 08:56:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b77000bb-78de-4a44-80b3-b3982c08715f</guid><dc:creator>Hakon</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I will ask the modem team if there is any plan for this.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>