LAUNCHXL-CC26X2R1: Association permit is false in the Beacon and not able to add devices

RajaG

Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: Z-STACK

I'm using the LAUNCHXL-CC26X2R1 as coordinator and Linux Gateway's command line UI application to add and control the devices.

I am able to add 3 to 4 devices but after that no device is getting added. I have cross verified on the device side, they are able to add to other coordinator.

When I captured the sniffer logs, I have observed that the "Permit Association" set to false in the "Beacon" packet broadcasted by coordinator.

The default setting for the max association table entries is 20. I am sure I haven't added 20 devices to the network. what other factors will effect the association table?
As per the memory size of the LAUNCHXL-CC26X2R1, what would be the optimal association table size?
is there any limitation for the max number of devices in the whole network (not only the direct associations of the coordinator) related to memory?

Details about the test and the sniffer capture:

In the test, I have initiate adding device. It failed three times. At this time the PAN ID was 0x2E9A.

After that I did reset and the new PAN ID is 0x52EA. After reset I am able to add devices.

The sniffer capture and the network keys to decrypt are provided below.

Network Keys:

A8 DE BF BA FD 00 35 D2 E5 C8 55 34 D2 A8 2B 07

A7 52 D5 38 92 33 83 F1 35 25 DA C9 80 C4 6A 1F

permit_assocciation_false_beacon.zip

Thanks

over 4 years ago

0 YiKai Chen over 4 years ago

Guru 735455 points

Do you enable permit join on your coordinator? isd format is sniffer format from Silicon Labs. Please convert it to dcf so we can easily decode it with Uniqua.

0 Ryan Brown1 over 4 years ago

TI__Guru**** 202066 points

Set BDB_COMMISSIONING_MODE_NWK_STEERING to re-enable permit joining, it should last for 180 seconds by default and restart whenever a new device joins. Note that NWK_MAX_BINDING_ENTRIES is 4 by default, however you should be able to join more than 4 devices so long as the network is open. Add any relevant gateway logs which may be useful for debugging if you still encounter issues.

Regards,
Ryan

0 RajaG over 4 years ago in reply to Ryan Brown1

Intellectual 410 points

Hi Ryan

where do I need to enable BDB_COMMISSIONING_MODE_NWK_STEERING? By default, it should be enabled since the unit is acting as the coordinator.

Just to clarify, I am able to open the network by pressing the key "P" from the UI interface and I'm seeing the Permit Join packet being broadcasted to 0xFFFC in the sniffer. But still, the devices are not joining.

Hi YK Chen

Please find the converted sniffer log file below.

permit_association_false_Ubiqua.zip

Thanks

0 RajaG over 4 years ago in reply to RajaG

Intellectual 410 points

Hi Ryan

can you reply to the rest of the questions in my original post related to the association table settings?

Thanks

0 YiKai Chen over 4 years ago in reply to RajaG

Guru 735455 points

The beacon frame of coordinator with PAN ID 0x2E9A shows permit join disable in your sniffer log.

0 RajaG over 4 years ago in reply to YiKai Chen

Intellectual 410 points

Yah, That is what happened.

How it got disabled?

I haven't done anything special other than adding the devices and controlling the on-off switch.

is there any possible option in the UI application to disable permit join? so that I can verify whether I hit that key accidentally?

Thanks

0 YiKai Chen over 4 years ago in reply to RajaG

Guru 735455 points

The permit join flag will be turn off automatically after you enable permit join 180 seconds (if I remember correctly). You should do enable permit join right before you want to join a new device to make sure it enables permit join.

0 RajaG over 4 years ago in reply to YiKai Chen

Intellectual 410 points

If that is the case, how to enable permit join from the UI application? is there any shortcut already present in the UI application?

Thanks

0 YiKai Chen over 4 years ago in reply to RajaG

Guru 735455 points

I think you can press 'P' again to enable it.

0 RajaG over 4 years ago in reply to YiKai Chen

Intellectual 410 points

I am using the same key to enable. By default, it will open for 60 seconds.

Immediately, I am initiating the adding process on the end device also. But still, permit association set to false in the Beacon packet.

You can see the time difference between the permit join request and the beacon packet is 5 seconds.

0 YiKai Chen over 4 years ago in reply to RajaG

Guru 735455 points

Can you attach your sniffer log?

0 Ryan Brown1 over 4 years ago in reply to YiKai Chen

TI__Guru**** 202066 points

Hi Raja,

I have not been able to replicate your issue using my own Z-Stack Linux Gateway on a BeagleBone Black connected to a LAUNCHXL-CC26X2R1 LaunchPad running the Zigbee_3_0_Linux_Gateway_1_0_1\Firmware\znp\CC2652R1LP_GW_ZNP_UART image (sniffer log attached). Please make sure you are following all instructions in the Quick Start Guide and User's Guides. Perhaps evaluate the Web Application and comment on any differences that exist. ZNP_NWK_open.cubx

You can increase NWK_MAX_DEVICE_LIST depending on the number of ZR/ZED devices which must directly be connected to your ZNP acting as the ZC.

Regards,
Ryan

Zigbee & Thread

Zigbee & Thread forum

LAUNCHXL-CC26X2R1: Association permit is false in the Beacon and not able to add devices