CCS/CC1352R: Retrieving a List of Network Devices 15.4

Alex L1

Part Number: CC1352R
Other Parts Discussed in Thread: CC1310, SYSCONFIG

Tool/software: Code Composer Studio

Hello!
I am developing an application based on TI 15.4 Stack. As a starting point I took the examples dmm_154collector_remote_display_app (on cc1352r1) and sensor (on cc1310). Nonbeacon mode. I have a question: how can I get a list of devices on the collector before connecting devices to the network and read certain data from them? I understand that this may not be entirely correct, but is it possible to do this?

In general, before connecting a device to the network, I need to check its parameters and if they match the odd ones, then associate it.

Thanks!

over 3 years ago

0 IUsedToBeARealPerson (M-W) over 3 years ago

TI__Guru 58425 points

Hi Alex,

Sounds like you are talking about some kind of "Allow list" implementation, is that correct? Or are you referring to old sensors rejoining the existing network?

In short, you have control of more or less all the information that exists. For example, if you want to deny access to a certain device you could intercept the the join request in the "cllcDeviceJoiningCB()" function and insert additional checks in ID etc.

0 Alex L1 over 3 years ago in reply to IUsedToBeARealPerson (M-W)

Intellectual 390 points

M-W,

The idea is as follows.
1. The collector, at the user's command, scans the network and generates a list of network devices (paired or not, absolutely everyone who is in the network)
2. The user sees this list in the top-level software and chooses which device to add to the network and which to remove

Thanks!

0 IUsedToBeARealPerson (M-W) over 3 years ago in reply to Alex L1

TI__Guru 58425 points

Hi Alex,

To do what you describe you can use the "assocIndCb()" found in the cllc.c file. This is where the decision is made on if to allow the sensor to join or not. You could gather information about the sensor here and choose to not allow anything in unless you specifically want to.

0 Alex L1 over 3 years ago in reply to IUsedToBeARealPerson (M-W)

Intellectual 390 points

Thanks for the recommendation, I'll try.
And I also noticed: when the collector is turned off, after turning it back on, the sensors can no longer connect to it. What could be the problem? I ran both examples on launchpad cc1310 and cc1352r1 debug points.

Thanks!

0 IUsedToBeARealPerson (M-W) over 3 years ago in reply to Alex L1

TI__Guru 58425 points

Hi Alex,

They should be able to re-join as long as the sensors where allowed to join and the collector did not reset the NV (button combination during reset).

It could however take some time before the sensor re-join if it consider itself orphan as it will back-of for a while (you should be able to configure this in the config.h).

0 Alex L1 over 3 years ago in reply to IUsedToBeARealPerson (M-W)

Intellectual 390 points

Hi M-W,

Yes, I waited longer and the sensors were connected. But it took about 5 minutes. Apparently this is this CONFIG_ORPHAN_BACKOFF_INTERVAL constant?

0 IUsedToBeARealPerson (M-W) over 3 years ago in reply to Alex L1

TI__Guru 58425 points

Hi Alex,

Yes, the default back-off interval is set to 300s which is 5 minutes. You could lower this if you want in the config.h (or SysConfig in case you got a CC13x2 Sensor)

Sub-1 GHz

Sub-1 GHz forum

CCS/CC1352R: Retrieving a List of Network Devices 15.4