ZigBee SED: Unexpected event in E_NETWORK_JOIN -15 while joining a network

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ZigBee SED: Unexpected event in E_NETWORK_JOIN -15 while joining a network

Jump to solution
3,001 Views
dmsherazi
Contributor IV

I am trying to realize a SED by following the AN1184_ZBP_SleepingEndDevice ...

I am stuck here at this point. SED will start joining and then fail with below debug messages. This is the behavior of the prebuilt .bin file as well. I am using JN5169 as the coordinator and another JN5169 as the SED

APP: Network discovery complete
APP: Found 3 networks
APP: Exhausted channels to scan
APP: No event to process!
APP: Starting ZPS
APP: Network discovery complete
APP: Found 3 networks
APP: Unscanned channels 00000000
     APP: Ext PAN ID = 00158d00019548eb
     APP: Channel = 20
     APP: Stack Profile = 2
     APP: Zigbee Version = 2
     APP: Permit Joining = 1
     APP: Router Capacity = 1
     APP: End Device Capacity = 1
APP: Trying Joining network
APP: Joining network
APP: Unexpected event in E_NETWORK_JOIN - 15
APP: Unexpected event in E_NETWORK_JOIN - 15
APP: Unexpected event in E_NETWORK_JOIN - 15
APP: Unexpected event in E_NETWORK_JOIN - 15
APP: Unexpected event in E_NETWORK_JOIN - 15
APP: Unexpected event in E_NETWORK_JOIN - 15
APP: Unexpected event in E_NETWORK_JOIN - 15
APP: Unexpected event in E_NETWORK_JOIN - 15
APP: Unexpected event in E_NETWORK_JOIN - 15
APP: Unexpected event in E_NETWORK_JOIN - 15
APP: Unexpected event in E_NETWORK_JOIN - 15
APP: Unexpected event in E_NETWORK_JOIN - 15
APP: Unexpected event in E_NETWORK_JOIN - 15
APP: Unexpected event in E_NETWORK_JOIN - 15
APP: Node failed to join network. Retrying ...
APP: No event to process!
APP: Starting ZPS‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

NOTE: I have tried using the AN1223 and AN1216 binaries for the coordinator but the issue persists. I can make clear that the Same coordinator works well some zigbee pro light switches. and other demo examples from AN1189

Labels (2)
1 Solution
2,021 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Dost,

As you know the JN-AN-1184 is a Zigbee PRO Application Template. So, the app note doesn't have the default key, and that is the message you are seeing E_NETWORK_JOIN.

The application is missing the keys, but you have to define if you will work with HA or LL.
If you are using it on HA network, then application note JN-AN-1189 should be referred to add the keys and if the light link is used, the application notes JN-AN-1171 should be referred.

Example: PUBLIC uint8 au8DefaultTCLinkKey[16] = {HA or LL key};

And the end device initialize
ZPS_vAplSecSetInitialSecurityState(ZPS_ZDO_PRECONFIGURED_LINK_KEY,
                                                            au8DefaultTCLinkKey,
                                                            0x00,
                                                            ZPS_APS_GLOBAL_LINK_KEY);

Regards,
Mario

View solution in original post

0 Kudos
10 Replies
2,021 Views
dmsherazi
Contributor IV

Any One from NXP to answer here?

2,022 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Dost,

As you know the JN-AN-1184 is a Zigbee PRO Application Template. So, the app note doesn't have the default key, and that is the message you are seeing E_NETWORK_JOIN.

The application is missing the keys, but you have to define if you will work with HA or LL.
If you are using it on HA network, then application note JN-AN-1189 should be referred to add the keys and if the light link is used, the application notes JN-AN-1171 should be referred.

Example: PUBLIC uint8 au8DefaultTCLinkKey[16] = {HA or LL key};

And the end device initialize
ZPS_vAplSecSetInitialSecurityState(ZPS_ZDO_PRECONFIGURED_LINK_KEY,
                                                            au8DefaultTCLinkKey,
                                                            0x00,
                                                            ZPS_APS_GLOBAL_LINK_KEY);

Regards,
Mario

0 Kudos
2,021 Views
dmsherazi
Contributor IV

Thanks Mario, 

Indeed missing HA Keys was the issue and now the SED node does join the network properly. But I am facing another issue. The SED after reset loses previous network info and will again be looking for new network on every reboot.

After pressing the reset Key although the SED had joined a network before.

APP: Starting ZPS
APP: Network discovery complete
APP: Found 3 networks
APP: Exhausted channels to scan
APP: No event to process!
0 Kudos
2,021 Views
dmsherazi
Contributor IV

mario_castaneda‌ Please help in this regard

0 Kudos
2,021 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Dost,

Did you send the leave request?

I follow the next steps:

1- Create the first network and the end device works as the demo.

2.-I sent the leave request.

3.The device looks for ZigBee networks. I sent the management request join.

pastedImage_1.png

Do you have the sniffer log?

Mario

0 Kudos
2,021 Views
dmsherazi
Contributor IV

The SED will look for new networks when in default state. Then When I enable permit join on Coordinator it joins and works fine. but if the SED Node is switched off it will again be in default state looking for new networks . (The same happens when the module rest pin is pulled low)  If I allow permit join again on coordinator it will join it again. 

0 Kudos
2,021 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Dost,

Could you please confirm the SDK and AN version? Also, Are you working with the Coordinator for this application node?

Do you have a sniffer?

Mario

0 Kudos
2,021 Views
dmsherazi
Contributor IV

How can I get the version of AN from the source ?

0 Kudos
2,021 Views
mario_castaneda
NXP TechSupport
NXP TechSupport

Hi Dost,

I am working with the JN-AN-1184 version 1.6, the at the end of the page of the AN doc, it is mentioned.

SDK JN-AN-4168 version 1620

C:\NXP\bstudio_nxp\sdk\JN-SW-4168 build file

Are you working with the Coordinator for this application node?

Do you have a sniffer?

Best Regards,

Mario

0 Kudos
2,021 Views
dmsherazi
Contributor IV

Hi Mario, 

sdk version is -- Build Number 1620

AN version is 1.6

I am not using a sniffer. Furthermore coordinator is from JN-AN-1216. 

0 Kudos