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.

CCS/CC1310: Sensor collector example: Changing message retry delay

Part Number: CC1310

Tool/software: Code Composer Studio

Hey guys,

we use the latest SDK for CC1310 sensor/collector example in 15.4 stack. We have set our "max data retry" to 5, which works fine so far. According to the sniffer, the delay between the first send message (not acknowledged) and the retry send process is approximately 300ms (depending on the message length).

How is it possible to set the delay between retry send actions if a message was not acknowledged?

Is it correct, that the backoff exponents are only related to the LBT and CSMA channel scans prior to message transmission?

Is it possible to configure the application, that only data messages or data requests from the sensor are retried, but not disassociation notifications?

best wishes

Slev1n

  • Hi,

    We'll look into this and get back to you.

    Regards,
    Toby

  • After looking into this, it seems that retries are handled within the MAC itself, and the number of retries for any ack-based messages are determined by what value is set for the attribute ApiMac_attribute_maxFrameRetries (by default this is CONFIG_MAX_RETRIES).

    Yes, the backoff exponents are used for CSMA-CA algorithm.

    You could potentially implement a softer requirement for "only data messages or data requests from the sensor are retried, but not disassociation notifications" by setting CONFIG_MAX_RETRIES to 1, then applying your own data retries in the application if the datacnf status indicates no ACK.

  • Thank you for your answer. I think, if it is possible to call ApiMac_attribute_maxFrameRetries() during runtime and not just at the beginning, it is possible to change the value whenever needed. E.g. I could call this in handleMaxDataFail() and set it to 1. After rejoin back to whatever it was before, right?

  • Yes, you should be able to change it at run time.