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.

CCS/CC2650: RemoTI RF4CE Topologies

Part Number: CC2650
Other Parts Discussed in Thread: REMOTI

Tool/software: Code Composer Studio

Hello All,

RemoTI Developer's Guide SWRU198D (fig. 4, page 12) shows point-to-point, point-to-multipoint, and multipoint-to-multipoint topologies, of which RC is only instantiated for point-to-point whereas Universal RC is for the multipoint scenarios. As far as CCS examples, what's the nuance differentiating the RC from the Universal RC?

My interest is in setting up and testing the Universal RC multipoint-to-multipoint topology to test DVD<--->STB communication, and so begs the further questions: are there any issues using Target Emulator to setup and test this topology: two Targets(DVD and STB) and one Originator (Universal RC)? If so, what other alternatives are there? 

Please provide guidance, so I can test communication between DVD and STB.

Will I:

1) need to run two instances of Target Emulator (one each for DVD and STB) and Bind STB to DVD?

2) do I even need to first Bind STB and/or DVD to the Universal RC in order for DVD and STB to transfer data back and forth?

Thanks,

Manuel

  • Hi Manuel,

    Those three bindings would be independent of each other. Either the DVD and/or the STB would have to support both Originator and Recipient (Super). The Target Emulator does not support Originator. I think the easiest/fastest would be to use the source for Linux: github.com/.../zrc20. Note that updates needs to be made to the configuration to set it up to both Originator and Recipient. In fact, it may be possible to configure it as Recipient, but act as Originator in the STB-->DVD binding. I have not tested this, and don't have bandwidth right now to do so.
  • Thanks for the reply Torbjorn. I will have to delve into Linux development to move this along then. Please point me to any Linux setup material/guides I might need, besides github.

    Also, the question on the difference between RC and Universal RC per
    RemoTI Developer's Guide SWRU198D (fig. 4, page 12) remains unanswered.

    Regards,
    Manuel
  • Hi Manuel,

    I personally run a Ubuntu distribution on VMWare. Any Linux based device should work though, as everything is standard C and just requires GCC compiler.

    There's nothing special with the Universal RC compare to the regular RC. It only indicates that one is paired/bound with more than one Target/Recipient node. Our sample remote controller can bind to up to 10 nodes. However! Each key will just create a frame that is sent to the last paired/bound node. In order to map certain keys, or to toggle between nodes, some application updates must be made. Toggling is really as simple as changing the currently active pairing index. You'll find there's an index being used in all RTI_SendDataReq() API calls. This index will select from the pairing table. As long as this index points to a valid pairing entry an RF command will be transmitted. It is even possible, through application updates, to chain two or more commands. For example, pressing the Power button could send an RF command to all paired/bound nodes.

    Sorry for mixing pairing -- binding, and Target -- Recipient. It's just that this concept was updated between ZRC-1.1 and ZRC-2.0. Binding just means that a pairing has been validated by some means (e.g. by user entering a validation code). Recipient is most typically a Target node. However, it also indicates that it supports the new features introduced with the ZRC-2.0 profile.