CC2538: znp-host-framework MT_ZDO_NODE_DESC_REQ request not working.

Hi,

What are you using as host to the ZNP?

Try debugging the ZNP and see if it actually receives the command (see function MT_ZdoCommandProcessing).

Regards,
Toby

I also suggest you to use sniffer to check what happens over the air.

Hello YiKai Chen,

In my case the command will not able to send over the network. there is no activity noticed on sniffer logs.

I am reffering following document. 

http://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/158/6758.Z_2D00_Stack-Monitor-and-Test-API.pdf

Refer the ZDO_NODE_DESC_REQ in section 3.12.1.3

Am I doing any thng wrong while sending the following command over uart.

SOC OUT --> 9 Bytes: SOF:FE, Len:04, CMD0:25, CMD1:02, Payload:00:00:99:B5, FCS:0F

Regards,

Shiv patil.

hello Toby Pan,

In your question, What are you using as host to the ZNP?

I am not able to understand what do you means to reffer the host?...

Will you ask more specific so I am able to answer you questions.

Regards,

Shiv Patil.

Make sure you use correct DstAddr and NWKAddrOfInterest.

Yes, I have verified the both addr values. I have also mentioned them in my question.

In general, NWKAddrOfInterest should be the same as DstAddr.

Hello ,

If you look at the permit joining request on the Zigbee Gateway Application for the same device. you will be able to see the 

the NWKAddrOfInterest should be the addr of device which we wants to add in to the network.

Even in Z-Stack Monitor and Test API document its mentioned clearly

Attribute                        Length (byte)                           Description
DstAddr                                2                                           Specifies NWK address of the device generating the inquiry.
NWKAddrOfInterest        2                                           Specifies NWK address of the destination device being queried.

refer following image you will be aple to understand this.

Regards

Shiv patil.

Since I can see node description request is sent in your sniffer log, why do you said “ the command will not able to send over the network. there is no activity noticed on sniffer logs.”?

hello YiKai Chen,

The above sniffer logs are reffering to the Permit Join Request using the Zigbee Gateway Application.

Not for the ZNP Host Framwork application.

I have post this becouse you said.. 

In general, NWKAddrOfInterest should be the same as DstAddr.

Using ZNP Host Framework I am not able to get successfull response for the MT_ZDO_NODE_DESC_REQ.

If you look over the sniffer logs you will be able to understand that,

NWKAddrOfInterest is the addr of the device which node information is requested.
DstAddr is the addr who is requesting the information.

If that request is successfully run over the Zigbee Gateway Application then why it is not working on the ZNP Host Framework Application?...

*** Also I need to know that, Is ZNP Host framework application is tested thoroughly or not & it is deployable for production??????......

Regards,

Shiv Patil.

Do you mean to send node description request from coordinator to device 0xB599 or from device 0xB599 to coordinator?

Coordinator Device is requesting the node information from the 0xB599 device.

so the destination addr should be the Coordinator addr 
& the addr of interest should be the 0xB599  

I have verfied this using the MT_ZDO_NODE_DESC_REQ implementation in zigbee gateway application.

I just want to get the node information of the 0xB599 using the MT_ZDO_NODE_DESC_REQ implementation on ZNP Host Framework application using cmdline example.

Yes its working now,

Thanks for your suggestion. 

But I am not understanding this why both addr should be the same?...

Will you explain this?..

The document is wrong for a long time. I don't know why TI doesn't fix it. If you follow my suggestion in the beginning, you won't waste lots of your precious time.

By "host", I meant what device are you using to control the ZNP? In the case of Gateway Application, the BBB controlled the ZNP, so the BBB would be host.

The destAddr is the address of the device to which this command will be sent.
The nwkAddrOfInterest is the address of the device which should send the Node Descriptor response.

As YK mentioned, most often these are the same.

I can see how the descriptions of destAddr and nwkAddrOfInterest may be misleading.
I'll reach out to the team and see how we can address this.

Hello Toby Pan,

I am using the BB Green with WIFI & the Raspberry Pi as a host to control the znp device.

Thanks to YiKai Chen,

I have solved the problem now.

But I need a modified document that has been tested for each request reponse functionality.

*** I have found another problem in the document, for the ZDO_EXT_SEC_APS_REMOVE_REQ

As per TI's document the byte frame should be like.

Length = 0x05       Cmd0 = 0x25       Cmd1 = 0x51       NWK Address(2B)          Extended Address(8B)          Parent address(2B)

But actual reuqest I have tested & getting successful response is as below,

Length = 0x05       Cmd0 = 0x25       Cmd1 = 0x51       NWK Address(2B)           Parent address(2B)               Extended Address(8B)         

*** here also the  NWK Address &  Parent address are the same as a device addr to which we are requesting.

If document are not accurate, how we start developing the things???

Will you please let me know when ever you update the document for the request response API.

Regards,

Shiv Patil.

Updates to this document will be here: http://dev.ti.com/tirex/explore/node?node=AEEJ0Z3BgvagEoglvx9r1g__pTTHBmu__LATEST

The docs in general will be updated quarterly (in sync with the CC13x2/CC26x2 SDK).

Look forward to seeing your document fix soon.