• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 127 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.

CC1352P: Network having same details creating issue

Haricharan Sarpatwar1
Expert 1065 points
Part Number: CC1352P
Other Parts Discussed in Thread: CC1352R

Hi All,

We are using CC1352P as Collector ad CC1352r as a sensor with TI 15.4 SDK examples. We use Non-beacon mode, 50 KBPS data rate, and 868MHz frequency band.

1. Can we change the short ID of the collector by using a Random number generator?

2. What are the places in which we need to change the short ID in the collector code?

3. Is there any impact with networks if we paired sensors with the random number generated short ID?

Why we would like to go with a different short ID for each network, because we had collectors which have the same network details like Channel, PAN, and short ID.

The sensors joined to are collector1 and sensors joined to collector 2 are sending telemetry data and vice versa are working fine if both collectors are powered ON, but if Collector1 is powered off still sensors connected to collector 1 are sending data to the network and later if I powered on collector 1 the collector could not able to send data to the sensors.

  • 0
    TI__Genius 14845 points

    Hi Haricharan, 

    To avoid this issue when a sensor is connected to multiple collectors, you can configure an address interval for each collector so the addresses don't overlap.

    1. I would not recommend a random number generator. Instead you can allocate different address intervals for the different collectors to make sure that the short addresses don't overlap. 

    2. In which cases would you need to change the address? 

    3. As mentioned in the first question, using random numbers won't guarantee that there are no overlaps. So you might run into a scenario where the random number generators for the different collectors will generate the same number. This scenario can be avoided if you are using dedicated addresses for the different collectors. 

    Thanks, 
    Elin 

  • 0 in reply to Elin W
    Expert 1065 points

    Hi Elin,

    Haricharan Sarpatwar1 said:
    The sensors joined to are collector1 and sensors joined to collector 2 are sending telemetry data and vice versa are working fine if both collectors are powered ON, but if Collector1 is powered off still sensors connected to collector 1 are sending data to the network and later if I powered on collector 1 the collector could not able to send data to the sensors.

    As I said, there are more number collectors and those all will be from the Production lot, where "allocate different address intervals for the different collectors to make sure that the short addresses don't overlap" will not be possible. 

    Instead, we would like to use the "MAC ID of the collector", the first two bytes that are different and unique.

    Which will support any number of collectors having the same channel but different short addresses.

    We understood the places where we can change the Short address of the collector (usually at network start and after programming)

    Also, we have tested with the 4 digit mac id as short address the association and disassociation and repairing is happening smoothly.