LPSTK-CC1352R: Conditions for Sensor to join Collector?

Markel Robregado

Part Number: LPSTK-CC1352R
Other Parts Discussed in Thread: CC1352R, SIMPLELINK-CC13X2-26X2-SDK

Hi,

I have 2 LPSTK-CC1352R as sensor and 1 CC1352R Launchpad as collector. Here below are 2 conditions I observed for sensors to join collector.

Both sensor LPSTK-CC1352R already powered on. Then I power on collector. The Tera Term says "Orphaned Sensor Re-Joined . . ." . After that I press the collector left button, I see number of devices 2. Why is it that the sensor joined when I have not press the right button to enable PermitJoin?

Both sensor LPSTK-CC1352R are powered off. Then I power on both LPSTK-CC1352R. I see both LPSTK-CC1352R led red blink and then off. I power on the collector, press left button then right button to enable PermitJoin. Both sensor LPSTK-CC1352R did not join. I power off and power on both sensor LPSTK-CC1352R and now both are able to join collector. Why did both sensor LPSTK-CC1352R did not join before, did it go to low power mode?

It seems the collector does not go to low power mode, meaning it should have constant power supply and not battery powered?

-kel

over 4 years ago

0 Ryan Brown1 over 4 years ago

TI__Guru**** 202086 points

Hi kel,

I assume you are using CCS v9.2 and the SIMPLELINK-CC13X2-26X2-SDK v3.30. Which specific examples are you using (normal, SM, 2.4 GHz, OAD, etc.) and which feature mode are you using (non-beacon, beacon, or frequency hopping)? Join/rejoin behavior changes based on these settings. Are you making sure to completely erase all device memory (including NV items) before programming? http://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_3_30_00_03/docs/ti154stack/html/ti154stack/example-applications.html

Regards,
Ryan

0 Markel Robregado over 4 years ago in reply to Ryan Brown1

Guru 85645 points

Hi Ryan,

I do not know yet all that specifics. I am just evaluating the examples from the Simplelink Academy TI 15.4 for LPSTK-CC1352R.

http://dev.ti.com/tirex/explore/node?node=AIKcHFRMmg0MRAyz1RySsg__pTTHBmu__LATEST

-kel

0 Ryan Brown1 over 4 years ago in reply to Markel Robregado

TI__Guru**** 202086 points

Hello kel,

I gather you are following the LPSTK TI 15.4-Stack SLA: http://dev.ti.com/tirex/explore/node?node=AIKcHFRMmg0MRAyz1RySsg__pTTHBmu__LATEST

I suggest that you erase all memory on the collector device as it appears to have previous NV items which are interfering with your evaluation. I have submitted feedback so that this is made more clear in future SLA documentation. The default feature mode is non-beacon which requires permit joining to be enabled for fresh joins but not rejoins. After failing to find a collector to join or rejoin, the sensor will delay before re-attempting according to the CONFIG_SCAN_BACKOFF_INTERVAL or CONFIG_ORPHAN_BACKOFF_INTERVAL values, accordingly. You can evaluate these macros but you are correct that the collector does not go into low power mode and should have a constant power supply as opposed to being battery-powered.

Regards,
Ryan

Sub-1 GHz

Sub-1 GHz forum

LPSTK-CC1352R: Conditions for Sensor to join Collector?