Really continuous rx operation on nRF91x1

[Herr Schubert]

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. After that time it stops automatically and needs to be re-scheduled.

Now I want to have a really continuous operation for an infinite time (which can only stopped by nrf_modem_dect_phy_rx_stop). Is it planned to implement something like this (with the next firmware release)?

[Hakon]

Modem team;

In dect_shell, we have workarounded this lack so that we start the RX for the duration of UINT32_MAX 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.

[Herr Schubert]

Thank you for your reply. I currently implemented it with re-scheduling immediately from operation_complete() as you suggested. That works so far.

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?
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?
In other words does each RX operation just see one half of that message (which are of course invalid for its own)?

[Hakon]

I will ask modem team.

[Hakon]

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.

[Herr Schubert]

Thank you for that clarification.