Hi
I am quite well familiar with DECT-NR+ and the Nordic Boards, as well as nrf91xx, we use a nrf9151.
Also some kind of involved at this opener initiative, but I cannot say here any more about this.
We using the latest (shared with us) mfw version at PHY and haveing our "own" MAC Implementation.
But my we going down to radio, so ignore the MAC.
My question is related according to TX - TX Latency, basically I have two different TX Operations and want them to schedule.
One Operation starts at Slot 16 and goes two Slots, so it ends at Slot 18.
2nd Operation starts at Slot 18 and my assumption was that when I schedule quite the same Operation and staying in the same mode (TX Operation, only)
than there is no delay in between.
But it looks lilke that at least the Latency for TX Transmission "idle_to_active" with 29030 ticks is needed to schedule another Operation within this time.
It feels odd and strange together, because why? is there any delay for TX - TX necessary? just for IPC communication and transfer data from nrf to Radio ? or?
And why is a whole slot needed ? the 29030 - 28800 = 230 which is a Slot plus 230 ticks.
Is there a magic switch or function pointer I can use to have a schedule_tx_after_tx operation ? similiar question with schedule_rx_after_rx operation ? with delays
From AI answer: "If your two TX operations are logically one burst, consider whether they can be combined into a single longer TX operation rather than two separate scheduled ones."
good point, but the Receiver is different etc.
Kind regards
thanks
