• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 802 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: Associate/Disassociate Sensor CC1310 with Collector CC1312R1

user4841866
Prodigy 230 points

Other Parts Discussed in Thread: CC1310

Tool/software: Code Composer Studio

Hi,

I have a problem with connection between sensor and collector. For sensor example (sleepy device) i use CC1310 launchpad (TI15.4 Stack SDK 3.20.00.23) and for collector example i use CC1312R1 lauchpad (TI15.4 Stack SDK 3.20.0.68 & TI15.4 Stack SDK 3.30.00.03). First connection between sensor and collector is successfull. Then I successfully disassociate sensor from collector with pressing button on sensor board. When I pressing button on sensor board for associate (Starting...), the sensor joined successfully (State changed: 3) but the problem occurs with the Config message. On the sensor side constantly displays error "dataCnf: 64" (getting config message) and on the collector side, it never displays "ConfigRsp" and constantly displays "!Responding". With the sniffer help i figured out that the sensor gets config message and sends response message successfully but the collector ignores that message. How can I solve this problem? I want to reconnect the sensor to the collector without reseting any of them.

Thank you for your ansfer.

Regards, Aleš

  • 0
    Prodigy 230 points

    I forgot to mention that it works in FH mode.

  • 0
    TI__Mastermind 25810 points
    Hey Ales, Can you try reproducing using our latest SDK (www.ti.com/.../SIMPLELINK-CC13X2-26X2-SDK) You may be experiencing a similar issue that was resolved in our latest SDK.
  • 0 in reply to Ammar N
    Prodigy 230 points

    Hi,

    with SDK 3.30.00.3 (i think this is the latest) I'm still having the same problem.

    Regards, Ales

  • 0
    Prodigy 230 points

    And I have another question, if I have connection between sensor and collector and I use Cllc_remove() on collector side, the collector removes all about that sensor. Should't the sensor go into the orphan mode (state:5)? I tested that with the latest SDK 3.30.00.03 on CC1312 and SDK 3.20.00.23 on CC1310.

  • 0 in reply to user4841866
    TI__Mastermind 25810 points

    Hey Ales,

    I will try and reproduce using your setup and report back. I previously used similar devices (i.e. x2 CC1312s) in the setup and I see you are using separate devices. Can you try using the CC1312 as the sensor to see if the issue is reproduced?

    user4841866 said:
    if I have connection between sensor and collector and I use Cllc_remove() on collector side, the collector removes all about that sensor. Should't the sensor go into the orphan mode (state:5)?

    This API is usually called when a disassociation request is sent. If this API is called without a disassociation request, the sensor will not know that it's collector has disassociated. The collector will simply have no memory stored for that sensor. So what you've said makes sense, as per design.

    I will report back when I've tested your setup.

  • 0 in reply to Ammar N
    TI__Mastermind 25810 points

    Hey Ales,

    Unfortunately, I was unable to reproduce the issue. I tested the default example in NBCN mode and flashed the collector and sensor examples.

    On the CC1312 I'm running the collector - CC13x2/CC26x2 sdk 3.30. On the CC1310, I'm running the sensor - CC13x0 sdk 3.20.

    I performed the following steps:

    1. Start the 15.4 network on the collector and turn on permit join.
    2. Start the sensor by pressing the right button.
    3. Once they joined, I press the left button to disassociate.
    4. After the collector prints the Disassociate Sensor message, I press the right button on the sensor to start the joining process.

    I did see the collector print the Config Rsp as expected.

    Am I doing something differently?

  • 0 in reply to Ammar N
    Prodigy 230 points

    Hi,

    And after second joining procces, does it reconnect normally and send messages? In my case, this didn't worked. I used frequency hoping mode (APIMAC_GENERIC_ETSI_LRM_863_PHY_131)

    I will try this case again and changed to different modes and reported the results.

    Regards,

    a

  • 0 in reply to user4841866
    TI__Mastermind 25810 points

    Do you have any updates? I haven’t heard from you in some time, so I’m assuming you were able to resolve your issue. If this isn’t the case, please click the "This did NOT resolve my issue" button and reply to this thread with more information. If this thread locks, please click the "Ask a related question" button and in the new thread describe the current status of your issue and any additional details you may have to assist us in helping to solve your issues.