• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 1133 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: 15.4 Stack SDK 2.10 (FH mode) - understanding Permit Join ON/OFF feature

Abrar Magdon
Intellectual 585 points
Part Number: CC1310
Other Parts Discussed in Thread: UNIFLASH

Hi,

I am testing out the 15.4 Stack SDK 2.10 in Frequency Hopping mode using CC1310 Launch Pads.

I have made the following changes

  • I have changed the Net Name and Pan ID to a custom one
  • I have Disablen security and enabled FH mode
  • The reporting interval is set to 1 second in the collector

As I power up the collector the RED LED does not blink. My sensors join the collector even without pressing the RIGHT button of the Launch Pad (which turns ON Permit Join). 

When I press the RIGHT button the RED LED starts to Blink, and pressing it again stops the Blink.

1. I would like to know if Permit Join is ON by default for FH mode? 

2. What is the use of Permit Join in FH mode?

3. What happens when I turn Permit Join OFF, Does it disallow NEW sensors joining the network or does it also disallow REPEATING sensors joining the network?

Thank you in advance.

Abrar

  • 0
    Guru 735685 points
    1. Permit Join isn't ON by default for FH mode.
    2. Permit join is for allowing device to send association request to join the permit join enable collector.
    3. If you turn Permit Join OFF, it disallows NEW sensors joining the network.
  • 0 in reply to YiKai Chen
    Intellectual 585 points
    Hi YK Chen,

    When Programmed my sensor and collector, I did a Erase Entire Flash using UniFlash. I also held the RIGHT button when powering on to erase the NV Flash for both the sensor and collector. Even after doing these without turning ON Permit Join the sensors connect to the collector.

    Could you please explain why it behaves like this.

    Thank you.
  • 0 in reply to Abrar Magdon
    Intellectual 585 points
    HI YK Chen,

    I also found this line of code in the,

    Collector_init() --->

    Cllc_init(&Collector_macCallbacks, &cllcCallbacks) --->

    if(!CONFIG_FH_ENABLE)
    {
    ...
    }
    else
    {
    ...
    /* Always set association permit to 1 for FH */
    ApiMac_mlmeSetReqBool(ApiMac_attribute_associatePermit, true);
    ...
    }

    Doesn't this turn ON Permit Join for the collector when its starts up?

    Thank you.

    Abrar
  • 0 in reply to Abrar Magdon
    TI__Genius 12415 points

    the permit join feature is not applicable for frequency hopping mode because the permit join information is reflected on beacons and in frequency hopping beacons are not used for the pairing procedure. Alternatively if you are using frequency hopping you will have to implement your own way of authenticating new devices as specified in the TI 15.4 Stack documentation section below

    "The device can choose one of the source nodes of the PA frame as relay to perform an Authentication and Secure Key Exchange protocol that must be implemented by the application running over the TI 15.4-Stack. Example applications (collector and sensor) included in TI 15.4- Stack do not demonstrate this feature."