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

RTOS/CC1350: TI-15.4 stack taking around 5 secs to send config req/rsp from collector to nodes?

Pratik Bhagat
Intellectual 700 points
Part Number: CC1350

Tool/software: TI-RTOS

Hi all,

In 15.4 stack, reporting interval is 10 sec.

In between that config, tracking req/rsp will come.

I have noticed that it is taking around 3-7 secs, for config req to come from collector to node.

Why it is taking that much delay. i have just connected a single node to collector.

How can i reduce this time.I want it to be within 1 sec.

Thanks,

Pratik

  • 0
    Prodigy 30 points

    Part Number: CC1350

    Hi, 

    We are using TI CC1350 devices which are running TI 15.4 Stack. We have one node(custom CC1350 board) and one concentrator(TI CC1350LP) in the network. 
    We have slightly modified the example applications provided by TI to send a custom message from Concetrator to Node.
    We would like to know what is the maximum air time required to send a packet from the concentrator to the node? 
    We are sending a message which is 40 bytes in size and the data rate we are using is 50Kbps.
    At present it is taking around 3 seconds to 6 seconds for us to receive the message on the node. Is this due to any network overhead? Maybe on the MAC co-processor? 
    Can we reduce the airtime to less than 1 second?
    Please advice. Thanks
  • 0 in reply to Bhanu Prakash C U
    TI__Guru**** 217237 points
    Hi Pratik, Bhanu,

    Please refer to Task 4 of the Sensor and Collector Project Zero SLA lab: dev.ti.com/.../154-stack_01_sensor_collector.html

    You will need to configure CONFIG_POLLING_INTERVAL and MIN_POLLING_INTERVAL accordingly.

    Regards,
    Ryan
  • 0 in reply to Ryan Brown1
    Intellectual 700 points
    Hi Ryan,
    Thanks for your quick reply.
    I gone through these link: dev.ti.com/.../154-stack_01_sensor_collector.html
    I have set polling interval to 100 ms.
    For me it reduced my air time in range of 1-1.5 secs.
    I want to know that what role is played by polling interval in doing these.
    What is the min value we can set to Polling Interval.


    Thanks,
    Pratik
  • 0 in reply to Pratik Bhagat
    TI__Guru**** 217237 points
    Hi Pratik,

    Step 5 of Task 4 specifies that MIN_POLLING_INTERVAL in sensor.c must be reduced below the default value of 1000 if you would like CONFIG_POLLING_INTERVAL of config.h to be effective below 1 second. You can read through the TI 15.4-Stack User's Guide for more information on how polling operates for devices in the network. The stack has been tested for a polling interval at 10 ms before, below this value it is more reasonable to leave the sensor as an always-on device instead of entering standby mode. dev.ti.com/.../ti154stack-index-cc13x2_26x2.html

    Regards,
    Ryan