How to operate F&B function of JN5169

[1979717461]

I followed the instructions in the manual (Application Note: JN-AN-1217 ZigBee 3.0 Base Device) to bind the coordinator node and EndDevice, but it failed. I don't know where there is a problem, maybe it is not operating correctly, the following are the print contents of the coordinator node and the EndDevice:

Coordinator:

APP-EVT: Event 2, NodeState=1
APP-EVT: Find and Bind initiate 00
BDB: APP_vGenCallback [1 1]
BDB: APP_vGenCallback [255 2]
APP-EVT: Event 1, NodeState=1
BDB: APP_vGenCallback [1 1]

EP EVT: Custom Cl 0003
- for identify cluster
APP-BDB: No Identify Query Response
BDB: APP_vGenCallback [1 1]
BDB: APP_vGenCallback [255 2]
BDB: APP_vGenCallback [1 1]

EP EVT: Custom Cl 0003
- for identify cluster
APP-EVT: Event 2, NodeState=1
APP-EVT: Find and Bind initiate 06
APP-EVT: Event 1, NodeState=1

EndDevice:

[minhtan_uet]

Hi. Mario
Can i config once Router as Initiator device?
Many Thanks

[mario_castaneda]

Hi @minhtan_uet,

You have to modify the code, taking as reference the coordinator example.

You must add the bdb_fb_initiator.c file and start the process avoiding the target code.

Regards,

Mario

[minhtan_uet]

Yes. I understand!

[mario_castaneda]

Hi,

As the Zigbee Base Device Behavior Specification provides 2 different to find and bind 2 devices.

Finding & binding procedure for an initiator endpoint.

In this procedure, the initiator endpoint first searches for identifying target endpoints and if one is found, its simple descriptor is requested. The initiator endpoint then searches for any matching clusters between itself and the target endpoint and for each match found, it creates a corresponding entry in its binding table.

In this case, the JN-AN-1217 is implementing a Finding & binding procedure for a target endpoint

This section defines the finding & binding procedure for a target endpoint. In this procedure, the target endpoint identifies itself for a finite duration and then handles subsequent finding & binding requests from an initiator endpoint.

In other words, the coordinator and the end device are defined as an initiator.

4.2.4 Binding Nodes (Coordinator)
‘Finding and Binding’ is the process whereby controlling devices find controlled devices by matching operational clusters and create entries in the Binding table. The Coordinator supports Finding and Binding as an ‘Initiator’ that tries to find targets to bind to

4.4.4 Binding Devices
The End Device supports ‘Finding and Binding’ as an Initiator that tries to find targets to bind to.

and the Router.

4.3.4 Binding Devices
The Router supports the On/Off cluster as a server and implements the Finding and Binding process as a Target.

Trigger the bind, the Router to self-identify for 180 seconds, while the Initiator will try to find the identifying devices, query their capabilities, and create bindings on those with matching operational clusters.

So, you have to bind the router with the ED or the Coordinator.

Regards,

Mario