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.
Part Number: LPSTK-CC1352R
I have 2 LPSTK-CC1352R sensor connected to 1 CC1352R Launchpad collector. After disassociation of 2 sensor the sensor address changes. Example before the sensor address is 0x0001 and 0x0003, after disassociation the sensor address now becomes 0x0003 and 0x0004. It will be hard to keep track of sensor nodes if the address keeps changing especially if my application is IOT. Is this normal? Can I make it to not change sensor address after disassociation?
Do, click "This Resolved my issue", if any of my replies helps solve your problem. For Tiva ARM Forum, see links below.
TM4C123 NMI unlock - To those who want to use PF0 and PD7, be reminded that these pins default as NMI ! ! !
JTAG Communication Failures
Featured Blog Projects: Create Bluetooth Projects using TI CC2640R2F Launchpad Online Course, Adding Bluetooth Connectivity to DPS3005 Programmable Power Supply using TI CC2640R2F BLE MCU, Bluetooth Low energy Point Of Sale using TI CC2652RB Simplelink™ Crystal-less BAW Wireless MCU, TI CC2640R2F Eddystone Beacon, Bluetooth Low Energy Game Controller, Bluetooth Low Energy Power Bank, Secure Internet Of Things Humidifier
Company Projects: FOBO Tag - World’s 1st Patented Bluetooth 5 Tracker
Rejoining devices should maintain the same address but disassociation will cause the collector to delete all previous device information and not re-use the previous address. So on a new join the previously-disassociated device will be assigned a new short address. You can maintain a record of the extended addresses in your application to resolve the issue.
https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/778273 https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/845450 https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/839149 https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/819301
To better aid the community, please click on the "This Resolved my issue" button whenever a post answers your question!
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Ryan Brown1:
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.