• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 459 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Transmission timeout from coordinator to device in non-beacon TIMAC network

Piergiuseppe Tundo
Genius 3155 points
Other Parts Discussed in Thread: TIMAC

Hello.

I'd like to know what is the transmission timeout a coordinator will apply when sending to a polling device (non-beacon scenario).

From API docs, I know TIMAC has a MAC_TRANSACTION_PERSISTENCE_TIME PIB attribute in beacon interval units.

But what does beacon interval in a non-beacon scenario means?

The beacon interval formula, aBaseSuperframeDuration * 2^beaconOrder, gives 15.36ms*2^15=~503s that is way too large in my case even if I set said PIB attribute to 1 (in calculation, 15 is the beacon order requested for non-beacon networks and 15.36ms is the aBaseSuperframeDuration value for 2.4GHz band).

Is there any way to shorten that timeout?

Best regards,

Peppe

  • 0
    Genius 3155 points
    Still hoping for an answer...
    In TIMAC, after how much time a frame in coordinator TX queue will be discarded in a non-beacon scenario (indirect messaging, assuming the frame recipient has stopped polling that coordinator)? Is that time configurable?
    Thank you in advance.
    Kind regards,
    Peppe