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

CCS/LAUNCHXL-CC1310: Sensor with a PAN ID joins to an unintended collector.

Guyan Jayaratne
Intellectual 360 points
Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: CC1310

Tool/software: Code Composer Studio

Support Path: /Tools & software/Help me with an issue/Design Kits / Evaluation Modules / Boards/Software issue/

Hi All,

I'm running the TI 15.4 stack examples that came with the SDK for CC1310. Particularly the Collector and sensor example

I have two  networks. Each containing a collector and a sensor. It can be graphically visualised as bellow

Network1_Collector <---> Network1_Sensor  (Both have CONFIG_PAN_ID 0x2002)

&

Network2_Collector <---> Network2_Sensor  (Both have CONFIG_PAN_ID 0x1234)

In the TI's 15.4 embedded developer's guide, for the description for CONFIG_PAN_ID it states

"Used to restrict the network to a certain PAN ID. If left as 0xFFFF, the collector starts with PAN ID 0x0001. If this parameter is set to a certain value for the collector, the value should be set to either the same value or 0xFFF for the sensor application, so that the sensor joins the intended parent."

According to this description, a particular sensor should only join to the network that has the PAN_ID that it was set for. That is. 0x2002 collector to 0x2002 Sensor.

My problem is the sensor with 0x1234 PAN_ID joins the 0x2002 network. And 0x2002 sensor can join the 0x1234 Collector too. Basically, any of my sensor boards can join to the collector although it does not match the required PAN_ID particular to that network.

Thank you in advance. Any help or guidance is appreciated.

Kind regards,

Guyan

  • 0
    Prodigy 130 points

    I see this issue too. Same senario, CCS and latest CC13x0 SDK (1.40.00.10) just different PAN ID numbers.

  • 0
    TI__Prodigy 20 points
    Hi Guyan,

    I have just tried to replicate your problem on my side. I used 2 sets of CC1310 launchpads and the newest SDK (1.40.00.10). For one set I programmed a sensor and collector both with CONFIG_PAN_ID = 0x1234. For the other set, I programmed a sensor and collector with CONFIG_PAN_ID = 0x2002. Everything else about the sensor and collector applications was left as default.

    After testing the networks, I was unable to replicate the problem you are describing. With my two networks, each sensor will only join the collector that has the same PAN, as it is supposed to.

    What version of the SDK are you using? Also, are there any other changes that you have made to the default example applications?

    Tyler
  • 0 in reply to sisk001
    Intellectual 360 points
    Hi Tyler,

    You're right. I imported fresh copies of the sensor and collector to a fresh workspace and ran again. The problem didn't appear. Version of SDK is 1.40.00.10.

    There are a couple of things with my original version I got the problem in.
    1) I had frequency hopping CONFIG_FH_ENABLE set to 'true' in both sensor and collector.
    2) I had CONFIG_REPORTING_INTERVAL set to 15000 ms

    The moment I turned CONFIG_FH_ENABLE to 'true', it connected to the wrong network again.

    Thank you Tyler, your answer steered us in a useful path.

    The following thread says it's PAN_ID with Frequency Hopping is going to be fixed in the next SDK version. Until that you could differentiate the networks using the CONFIG_FH_NETNAME definition. This can be found in the config.h file too.
    e2e.ti.com/.../2047740

    for eg:
    Collector with CONFIG_FH_NETNAME {"FHabcd"} -connects to- Sensor with CONFIG_FH_NETNAME {"FHabcd"
    }

    It worked.

    Thanks.
    Guyan