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/LAUNCHXL-CC1352R1: Newbie questions regarding FH

Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: CC1310

Tool/software: Code Composer Studio

Hey guys,

I went through http://dev.ti.com/tirex/content/simplelink_cc13x0_sdk_1_30_00_06/docs/ti154stack/ti154stack-sdg/ti154stack-sdg/TI%2015.4-Stack%20Overview.html#frequency-hopping-mode

and I still have few questions. Note that we will have one collector and several sensor nodes, the latter one being sleepy devices.

  1. How many network devices are supported (e.g. for CC1310 or CC1352R1) because I read something about 50 neighbours max.?
  2. We currently use (beacon mode) extended address format if data messages are send from sensor to collector, is this still possible?
  3. For sleepy devices we need "unicast" and fixed channels to save power, is this correct? Where can I set this in config.h or is this set automatically if "RxOnIdle = 0" is detected?
  4. What exactly is a hopping neighbour? (sensor to sensor or sensor to collector?)

kind regards

Slev1n

  • Hello,

    See below my answers in RED.

    1. How many network devices are supported (e.g. for CC1310 or CC1352R1) because I read something about 50 neighbours max.?
      1. If using a 1310 as the collector device with security enabled, you have a maximum of 50 devices connected to it
      2. If using a cc1312 as the collector device with security enabled you have ~150 devices connected to it
    2. We currently use (beacon mode) extended address format if data messages are send from sensor to collector, is this still possible?
      1. Yes, this is possible.  You will need to change addessing mode to extended when sending the msg.
    3. For sleepy devices we need "unicast" and fixed channels to save power, is this correct? Where can I set this in config.h or is this set automatically if "RxOnIdle = 0" is detected?
      1. If using FH mode, this will automatically make the device stay in one channel and wake up at a set interval, if using Beacon mode every device will be on the same channel.
    4. What exactly is a hopping neighbor? (sensor to sensor or sensor to collector?)
      1. by definition both, but in our stack and the way is developed it will allow sensors to hear and save configuration messages sent by neighbors (sensors or collectors) you could potentially also listen to regular data frames from sensor to sensor but you will need to develop this functionality

  • I have one more question regarding the association process when there are 3 different collectors present.

    If I recall correctly, in non-beacon mode, the sensor decides based on the beacon of the collector which one to associate with (the one with the best RSSI?!)

    Is this the same procedure in FH mode for sleepy sensors?

    kind regards

    Slev1n