• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 55 subscribers
  • Views 254 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.

CC1310: CC1310

jaron yoo
Prodigy 20 points

Part Number: CC1310
Other Parts Discussed in Thread: CC113L

Dose CC1310 have frequency hopping feature to avoid any noisy channel with multi channel? If it has frequency hopping feature, does the system have to have two way communication or one way directional is enough ? 

We want to use CC1310 on remote controller side and for opposite, controlled side to use CC113L side. Does it correct way?  

  • 0
    TI__Mastermind 20412 points

    Hi Jaron,

    The CC1310, supports frequency hopping in the TI 15.4 stack examples. Maybe you can look at the TI 15.4 sensor and collector examples. 

    dev.ti.com/.../node

    But if you are using the proprietary PHY and the the RF driver like in the packet TX, packet RX example, then you would have to implement your own custom protocol with frequency hopping. The TX and RX command by themselves don't have frequency hopping. This also means that the receiver should be running the same custom protocol that you write.

    CC113L will not be able to receive with this custom implemented frequency hopping.

    Regards,
    Sid

  • 0 in reply to Sid
    Prodigy 20 points

    Hi Sid thanks to your answer. 

    My understanding is;

    For the frequency hopping feature, we don't need to have bidirectional communication between controller and receiver, means no need radio transmitter on receiver side.  please confirm. 

    So we will use CC1310 on both of controller and receiver but there is no transmitter on receiver side as no need bidirectional communication. please confirm. 

  • 0 in reply to jaron yoo
    TI__Mastermind 20412 points

    Hi Jaron,

    It should be possible to have a receiver only device which may not be the best idea. You would have no acknowledgement or any ability to transmit from the node. So the transmitter will never know if the messages it is transmitting is ever received by the receiver. 

    The 15.4 stack network uses the association process for nodes to join the network. This needs bidirectional communication.

    dev.ti.com/.../node

    But in your custom protocol, if you are using only a receiver on one side, along with the above mentioned disadvantage of never having an acknowledge, there would be no data exchange during association, so any device can listen to this message from the transmitter. 

    When you are writing your own protocol, you would need to keep these in mind. 

    Regards,

    Sid