Quantcast
Channel: Forums - Recent Threads
Viewing all articles
Browse latest Browse all 262198

CC1310: How to effectively solve the data conflict problem between multiple devices

$
0
0

Part Number: CC1310

Hi Team,

Customer sees that most of the solutions are using LBT, but there are some questions about how the Listen Before Talk mechanism works.

1. How many times does the channel assessment evaluate? (assuming the channel is always busy)


2. How long is the interval between each evaluation of the channel?

1
2
backOffTime = (getRN() & ((1 << be++)-1)) *
                        EasyLink_us_To_RadioTime(EASYLINK_CCA_BACKOFF_TIMEUNITS);

In other words, does the actual impact assessment interval is the random number generated? (Question 4)

3. What is the specific function of this part of the code below?

1
2
3
4
5
6
/* Set Tx absolute time to current time + 100ms */
if(EasyLink_getAbsTime(&absTime) != EasyLink_Status_Success)
{
    // Problem getting absolute time
}
lbtPacket.absTime = absTime + EasyLink_ms_To_RadioTime(100);

Send waiting? What is the time of EasyLink_getAbsTime()?

4. When EasyLink is initialized

1
easyLink_params.pGrnFxn = (EasyLink_GetRandomNumber)HalTRNG_GetTRNG;

What is the specific role of the random number above?

Whether this random number affects the interval between channel evaluations?

What is the range of this random number?

5. Is there any other solution for data conflict between multiple devices (>100 units)?

Now the product is in mass production, it is found that the data conflict is more serious. The interval between device uploads is relatively small, then the number of packets uploaded between nodes is a bit large.

Thanks.


Viewing all articles
Browse latest Browse all 262198

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>