.sNwkStatusIndicationEvent.u8Status = 0x11

cancel
Showing results for 
Search instead for 
Did you mean: 

.sNwkStatusIndicationEvent.u8Status = 0x11

273 Views
Contributor II

Hi Mario,

JN5169 / AN1216 / SW4170

I cannot find the enum or the #define of the field u8Status in the structure ZPS_tsAfNwkStatusIndEvent.

The stack is sending me this event often with status = 0x11.

>        case ZPS_EVENT_NWK_STATUS_INDICATION:
>           vLog_Printf(TRACE_APP,LOG_DEBUG, "\nNwkStat: Addr:%x Status:%x",
>                  psStackEvent->uEvent.sNwkStatusIndicationEvent.u16NwkAddr,
>                    psStackEvent->uEvent.sNwkStatusIndicationEvent.u8Status);
>                   
>            OUTPUT ==>        NwkStat: Addr:2ef2 Status:11

I need to know the meaning of this status.

Best regards

Benoit

Labels (2)
Tags (1)
0 Kudos
8 Replies

108 Views
NXP TechSupport
NXP TechSupport

Hi Benoit,

Please look at the Zigbee Pro Stack User Guide https://www.nxp.com/docs/en/user-guide/JN-UG-3048.pdf 

pastedImage_1.png

Are you sure that you are getting 0x11? What is the process that you are following?

Regards,

Mario

0 Kudos

108 Views
Contributor II

Hi Mario,

I don’t follow any particular process. The stack is running as a coordinator. This event happens without any visible link to the context. It happens during a communication with some other devices. But it is random.

And the code is well 0x11 and is not in the List of code of the Stack user guide. Hence my question to you.

Attached is the packets of the sniffer showing a OTA next image request from an end device. And it yields a NwkIStatusndicationEvent status 0x11. Attached is the log of our gateway of the same event.

However, for this particular end device, 5 minutes later, it sent another OTA image request, and the stack didn’t sent such an NwkStatusIndicationEvent.

Best regards

Benoit

De : mario_castaneda <admin@community.nxp.com>

Envoyé : mercredi 17 juin 2020 02:00

À : benoit roue <benoit.roue@otodo.com>

Objet : Re: - Re: .sNwkStatusIndicationEvent.u8Status = 0x11

NXP Community <https://community.freescale.com/resources/statics/1000/35400-NXP-Community-Email-banner-600x75.jpg>

Re: .sNwkStatusIndicationEvent.u8Status = 0x11

reply from Mario Ignacio Castaneda Lopez<https://community.nxp.com/people/mario_castaneda?et=watches.email.thread> in Wireless Connectivity - View the full discussion<https://community.nxp.com/message/1327614?commentID=1327614&et=watches.email.thread#comment-1327614>

0 Kudos

108 Views
NXP TechSupport
NXP TechSupport

Hi Benoit,

Sorry for my late response.

Just to confirm, you are working with the JN-AN-1216 as a coordinator. 

What is the application note that you are using in the end device?

The status is (E_ZCL_ERR_ATTRIBUTE_TYPE_UNSUPPORTED), it could be for the request of the OTA cluster. I will try to reproduce this issue.

Regards,

Mario

0 Kudos

106 Views
Contributor II

Hi Mario,

Yes, it is AN1216.

The end devices are not mine. They are any other ZigBee devices that are on the market. And this problem happened with many of them. But the most important is to focus on the messages they send.

I found the NXP stack has no problem to get and reply to OTA requests. Usually, there is no error message (Devices are continuously requesting for next image.)

The NwkStatusIndicationEvent with error code 11 happens at any time, and I don’t see any related message on the sniffer that can explain this event.

I have captured the packets in the air with a sniffer, and the gateway logs at the same time (use Epoch time as a reference).

You can check the two files. On this particular sequence, there is no OTA request involved.

Best regards

<https://www.otodo.com/>

104 boulevard du Montparnasse

75014 Paris

www.otodo.com<http://www.otodo.com/>;

Benoit Roué

Lead Developer Embedded Software

benoit.roue@otodo.com<mailto:benoit.roue@otodo.com>

06.64.52.10.20

<https://www.facebook.com/OtodoOfficiel/>[Twitter icon]<https://twitter.com/OtodoOfficiel>[Linkedin icon]<https://www.linkedin.com/company/otodo/?lipi=urn%3Ali%3Apage%3Ad_flagship3_company_admin%3BJ1FpXoKeRwWGYatbYhzdaQ%3D%3D>[Youtube icon]<https://www.youtube.com/channel/UCHC7TXW-IldDkKhoZ8MAfMA?view_as=subscriber>

De : mario_castaneda <admin@community.nxp.com>

Envoyé : vendredi 26 juin 2020 00:53

À : benoit roue <benoit.roue@otodo.com>

Objet : Re: - Re: .sNwkStatusIndicationEvent.u8Status = 0x11

NXP Community <https://community.freescale.com/resources/statics/1000/35400-NXP-Community-Email-banner-600x75.jpg>

Re: .sNwkStatusIndicationEvent.u8Status = 0x11

reply from Mario Ignacio Castaneda Lopez<https://community.nxp.com/people/mario_castaneda?et=watches.email.thread> in Wireless Connectivity - View the full discussion<https://community.nxp.com/message/1332081?commentID=1332081&et=watches.email.thread#comment-1332081>

0 Kudos

106 Views
NXP TechSupport
NXP TechSupport

Hi Benoit,

We need some extra information from the terminal log side. We are checking the root cause of this issue.

Is it possible that you could add a print DBG_vPrintf information where E_ZCL_ERR_ATTRIBUTE_TYPE_UNSUPPORTED is triggered inside Zcl.c , Zcl_attribute.c and zcl_configureReportingCommandHandle.c, then narrow down which one invoked :

              [1593173220] I (9142331) Java: ZigBeeData : Status: 0x11 (E_ZCL_ERR_ATTRIBUTE_TYPE_UNSUPPORTED)

in Gateway Logs

Regards,

Mario

0 Kudos

106 Views
Contributor II

Hi Mario,

E_ZCL_ERR_ATTRIBUTE_TYPE_UNSUPPORTED is not triggered inside Zcl.c

The Event is triggered by the stack and handled by 

PUBLIC void APP_vHandleStackEvents ( ZPS_tsAfEvent*    psStackEvent ) in app_general_events_handler.c

The event is sNwkStatusIndicationEvent, with status=0x11.

Of course, the meaning of 0x11 is not E_ZCL_ERR_ATTRIBUTE_TYPE_UNSUPPORTED because it is not related to ZCL.

My question was what is the meaning of this status. I cannot find any enum of define in the NXP documentation. However, I found a meaning in the ZigBee spec. It means "Bad frame counter". See 3.4.3.3.1 Status code in ZigBee Document 05-3474-21.

But how to know whether it is good or bad? Is it ok for the stack to work like this?

Best regards

Benoit

22 Views
NXP TechSupport
NXP TechSupport

Hi Benoit,

I am currently checking this specific issue.

Regards,

Mario

0 Kudos

105 Views
NXP TechSupport
NXP TechSupport

Hi Benoit,

I'm sorry for my late respone. we are checking the new sniffer file that you provided. I was able to open the file correctly.

Regards,

Mario

0 Kudos