• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 54 subscribers
  • Views 310 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.

CC1312R: Collector stops receiving all messages after some time

vadim sof
Prodigy 160 points
Part Number: CC1312R
Other Parts Discussed in Thread: CC1310,

I am using SDK 4.40.04.04 and frequency hopping.

I have a CC1312R as a collector and ~40 CC1310 devices as non-sleepy sensors. Packets are sent from collector to sensors and back every couple minutes and sometimes a couple times a day ~200ms apart to some of them. After about 2-3 weeks the collector stops receiving messages and all devices go into orphan state. I am still able to communicate with collector via UART and a collector reboot will fix the issue and devices will reconnect.

I have another network with 6 sensors and no messages to sensors other then tracking messages and it has been working for over 2 months no issues.

I have setup a test with 30 sensors. Collector sends packets very often (~200ms) to each sensor sequentially. I am able to hit the same issue after about 20min. I tried setting a breakpoint in wsAsyncIndCb(), and it never gets triggered even though I see sensors transmitting PCS frames using packetSniffer.

I see ROV BIOS reports no errors and don't see any stack overflow issues. Its like the stack no longer want to receive messages.

What would you recommend I try to do to debug this?

Thanks in advance.

  • 0
    TI__Guru* 86241 points

    I will assign someone to look into this.

    BR

    Siri

  • 0
    TI__Guru* 82271 points

    Hi Vadim,

    Sorry for the late reply,

    I think your issue is the short timing interval. Our recommendation would be to set this interval to 10 000 ms or preferably 30 000 ms.

  • 0 in reply to Marie H
    Prodigy 160 points

    Hello,

    Are you saying there is a large (>10s)  stack timing requirement between messages, from collector to sensors?

    Currently we send a message to a sensor, wait for it to respond (~80-200ms) then move on to the next sensor. We could potentially have ~50 of these. Are you suggesting we wait 10s in between messages? Could broadcasting help here?

    Thanks,

    Vadim

  • 0 in reply to vadim sof
    TI__Guru* 82271 points

    Hi Vadim,

    This is my recommendation, yes.

    You can use lower intervals but I would advise you to test thoroughly if you do so.

    For your downstream heavy application it would make a lot of sense to use beacon mode. However we don't have an example implementation of beacon mode with frequency hopping.