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: TI 15.4-Stack 169 MHz support and Wisun related questions

Part Number: CC1312R
Other Parts Discussed in Thread: SYSCONFIG, , CC1352P7,

0Hello, i am currently working with two CC1312R1 LAUNCHPADS for the prototype developing of a low power animal-sensor network intended to work in the 169 MHz band in a forest/rural region.

We are planning to use the 15-4 STACK due to the fact that we need an star network topology for this step of the proyect and we are planning to use a web server in a future to monitor and change some sensors parameters

When using the SDK 15-4 STACK  examples I was not able to select 169 Mhz band (I could not even select in the sysconfig the 433 MHz band). I later found in the documentation that this band is not supported

1 Is it possible to manually change the config files to make the 15-4 STACK in the 

2.  Are there any plans for supporting this band in the near future?

3. In case both answers are NO, we are also considering the use of a mesh network in the future .Should we set up the network as mesh with WISUN with only one router or use another protocol. Which are your suggestions

4 IS there any example for the  CC1312R1 WISUN as sensor node (i only found the configuration for the router and border router for this )

The main goal at this moment is to have an star network in which the controller or border router will be connected to a Bluetooth app (if we are able to set up an internet connection on the field we are working, later we will implement a web server using a raspberry instead of the Bluetooth app)

Thank you in advance

Andres

  • Hi Andres,

    1. As you say we don't currently support the 169 MHz band. We do support 422 MHz band. If you select the C152P-4 LaunchPad this option will be available to you.

    It's not possible for you to change the frequency band.

    2. I cannot answer questions about our roadmap in this public forum.

    3. Wi-SUN sounds like a good fit, depending on the number of nodes you need in the network and how much data is being sent.

    4. Yes, you can use the ns_node example. This implements the router node role. Please note this is a nwp example, you will need a host device to run along. (For a fully embedded Wi-SUN solution you will need a larger flash device, CC1312R7.)

    Cheers,

    Marie H

  • Hi Marie, thank you for your quick response. 

    I would like to ask you the following (and any additional advice's will be more than welcome)

    2. Could you send me a PM regarding this ?  (i would like to know if there is worth it to wait until the release or build up our own solution instead, this is )

    3. We have at this moment 10 nodes so i think is not going to be an issue. If we plan to cover all the animals we will be needing around 50 nodes but we are very restricted by the budget so i do not think that in the following year will be reaching that amount.

    4. Because CC1312R7 is not a viable in providers like mouser and digikey (which sends packages to Argentina where i am located). Is any other way to run the border router or the WISUN protocol without CC1312R7 devices?

    5. What we need in a short term (in a year of work) is to be able to have a set ten nodes in any topology (start or mesh) and to connect the collector/router to a bluetooh app to do the monitoring (in the next year we will be planning to add a web server functionality to do the monitor), and is very desired to have a bidirectional communication to be able to not only monitor the nodes but to change behavior. Regarding the data flow, we will be sending 60 bytes messages every 10 minutes, so is very low (if we want to locate the sensor node we will be making it send a burst message every 1 second, but only one sensor at the time). Based on this and the amount of nodes, and the current needs, do you suggest any protocol or to just build our own based on the EASYLINK examples?

    Thank you a lot

    Best regards

    Andres

  • Hi Andres,

    2. You would need to contact a TI sales representative.

    3. For Wi-SUN we recommend up to 100 devices per border router. However, Wi-SUN FAN does not currently support sleepy nodes. It sounds like this might be required in your product?

    4. CC1312R7 should become available shortly. (We just released it for production last week.) The alternative would be to use CC1352P7.

    5. The usecase you are describing sounds relatively simple and feasible to implement on your own. If you require any of the following features I would recommend TI 15.4-Stack:

    - Auto retransmission of missed packets

    - Over the air firmware upgrade (OAD)

    - Secure commissioning

    I would recommend you to start developing with the RF driver directly and avoid EasyLink. The main reason is that EasyLink is quite limited, so unless the WSN example is very similar to what you're looking for, you might not be able to use it.

    Cheers,

    Marie H

  • Hi Marie!, 

    2. Thank you!, do you have any contact info for a sales representative regarding this specific query

    3. Yes, we need the nodes to sleep most of the time in order to increase their life time. As far as I know, only router or borders routers can't sleep, but nodes yes. Is that correct?

    4. Thank you!. Just to be sure, having a border router with R7 and nodes and router nodes with R1 will work o? (or router nodes needs also to be R7? )

    5. I would to use the 15.4 stack but we need to work in the 169 MHz band because of loss propagation, so unless this change, seems that the best path if to either build our own protocol or use the simplelink examples.

    Thank you!

  • Hi Andres,

    2. You can find world-wide contact information here: https://www.ti.com/info/contact-us.html 

    3. In the Wi-SUN protocol there are no sleepy node implementation.

    4. Router nodes would also need to be CC1312R7 devices. (CC1312R devices only support Wi-SUN in a two-chip architecture, i.e. as a network processor. You would need an additional chip to act as the application processor.)

    5. Agree.

    Cheers,

    Marie H

  • Thank you a lot for all your help Marie!, have a nice day :)