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.

CC1310: Is it possible to change data rate of TI-15.4 stack at run-time?

Part Number: CC1310

Hi, Team,

One of my customer wants to use 5kbps and 50kbps data rate alternately at run-time, to take a compromise between long range and low power. That is, a sensor uses 50kbps to try to communicate with collector, if it fails for a number of times, it switches to 5kbps and tries to communicate with collector again. Also, collector should work at these two data rate alternately.

In my understanding, as data rate is configured by "#define" at compile time in TI-15.4, it is no possible to switch data rate dynamically at run-time. Please help to confirm whether it is possible to fulfill my customer's requirement with TI-15.4. If yes, hot to? If no, is there any workaround?

Thanks!

  • Hi Felix,

    No this is not supported in the 15.4 Stack. Doing something like this may be possible but it will require a major rework of the applications. We cannot provide a solution for this since this would be a complete new feature and it is not an easy task to achieve. This being said, if they still want to try to implement something like this it will have to be on their own but I can provide a little bit of guidance on how this could be implemented.

    In order to implement something like this they will have to take a look at the coprocessor example which is already doing something similar and merge this into a collector and sensor applications. The files that they should be looking into in the coprocessor example are the mac_user_config files which basically what they are doing is adding all the supported phys to the code.

    Once they have adapted the coprocessor mac_user_configs to the examples they will have to search their example projects and take care of all the places in the code where CONFIG_PHY_ID is being used. And finally once all the PHYs have been compiled in they should my able to use the following API to change the phy
    ApiMac_mlmeSetReqUint8(ApiMac_attribute_phyCurrentDescriptorId, MyRunTimePhy);

    Please note that this has never been tested and we cannot guarantee that the stack or the example applications will work as intended if they make these modifications
  • Hi, Hector,

    Thanks for your quick reply!