• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 699 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: How to set up a transmit receive pair?

Kian
Expert 1595 points
Part Number: CC1350
Other Parts Discussed in Thread: CC1310

Tool/software: TI-RTOS

Hi all,

I have a question on how to set up the pairing for a tx and rx device. Eventually I like to build a product  where one cc1310/cc1350 device sends data to another cc1310/cc1350 device. There should be a means of commissioning or setting up the device as a pair so that it will not inter with my neighbour's device.

Can someone advise on a strategy to do this? I very vaguely read about address filtering. Can someone tell me how that works? Do I need to pre-program a source and destination address in the firmware? Where and how can it be done? It will be great  if I can be referred to some documentation to read up more on this.

From a mass production point of view, it would not make sense to program a different address in every device right? And the user should have the flexibility to unpair and pair to a new device.

Are the examples inside CCS resource explore under the EasyLink folders a good starting point? I presume I would need to use the EasyLink API. I would also need WOR functionality because the receive is to be powered my batteries. But the rfWakeOnRadioRx example doesn't seem to be using the EasyLink API.

Sorry for asking so many questions. I am still new to this platform so I am hoping to get some reference starting point.

Thanks in advance!

  • 0
    TI__Expert 8765 points

    Hello Kian,
    Yes, you can use address filtering to communicate between devices selectively. Please refer to this thread for more information e2e.ti.com/.../2119228
    Yes, typically it is expected that the device address table is pre-programmed, but nothing is stopping it from dynamically changing the address table vectors may be based on contents of previously received payload.
    The address length can be increased to allow for more set of devices for mass production. There is enough flexibility in the system to allow support many devices within a network.
    You can use EasyLink_EnableRxAddrFilter() API to achieve this.
    Regards,
    Prashanth

  • 0 in reply to PrashanthS
    Expert 1595 points

    Thank you PrashanthS for the reply.

    Does the EasyLink API support wake on radio (WOR) functionality? I need the WOR because I really need low power consumption on the transmitter receiver. Any resources on how to implement WOR with the EasyLink API?

    I need to send data from 1 transmitter to multiple receivers. In this case, does this mean that I have to configure it as 1 sensor node and multiple concentrators?

    I was reading the thread that you suggested and know that the destination address in included in the payload, and the receiver checks if the destination address matches its own address. In this case, could I just use the WOR TX and RX examples (with doesn't use the EasyLink API) and just include a destination address in the TX payload?

  • 0 in reply to Kian
    TI__Guru* 86731 points
    The EayLink API does not support WOR. You can use the WOR examples and include address filtering to that example.
    BR
    Siri