How can we modify the Zigbee Network Layer which contains Frame Type and other details, currently there seems to be no method in digi-xbee module to do so

XBee & XBee Gateway XBee - Zigbee
,
1

Frame 542: 63 bytes on wire (504 bits), 63 bytes captured (504 bits) on interface ZigBee/0/22, id 0
IEEE 802.15.4 Data, Dst: 0xa271, Src: 0x0000
ZigBee Network Layer Data, Dst: 0xa271, Src: 0x0000
Frame Control Field: 0x1a48, Frame Type: Data, Discover Route: Enable, Security, Destination, Extended Source Data
Destination: 0xa271
Source: 0x0000
Radius: 30
Sequence Number: 105
Destination: TexasInstrum_XXXXXXX
Extended Source: MaxStream_XXXXX
ZigBee Security Header
ZigBee Application Support Layer Data, Dst Endpt: 0, Src Endpt: 0
ZigBee Device Profile, Node Descriptor Request, Nwk Addr: 0x71a2
Sequence Number: 2
Nwk Addr of Interest: 0x71a2
Data (1 byte)

I want to modify the Frame Type to Frame Type: Data, Discover Route: Supress, Security Data

2

From the looks of it, you are using a Zigbee sniffer. A Zigbee sniffer is a tool that is designed to view the RAW data packets. The functions you are referring to are not something you can disable.

3

When I try to send a Node descriptor request to an end device for pairing the response received from the end device is not correct. It says Invalid request type. Though I compared the data sent was the same with the working one.
I am not able to figure out what’s wrong.

The end device is SNZB01, I am trying to do this with a Zigbee s2c module. And am comparing sniff with it’s own Sonoff USB module.

Please tell me how can I debug or solve this. ?

4

The XBee S2C module is a Zigbee 2006/Zigbee PRO product. Your 3rd party SNZB01 is a Zigbee 3.0 product. They are not running the same standards. I can’t find it in the manuals but suspect this is a Home automation device and the S2C XBee modules are not.

5

Can you recommend one of the zigbee 3.0 modules by digi similar to digi xbee s2c which I can use to communicate?

6

Also the end device does support zigbee pro as in the sniff I can see the communication happening with the zigbee pro protocol.
Let me share you some snapshots for the same for reference. I beleive that’s not a problem.

7

Any one of Zigbee 3 RF Module | Digi XBee 3 Zigbee 3.0 | Digi International would offer a Zigbee 3.0 option via the API interface and the ZS command.

8

I have got the Zigbee 3 RF Module as you mentioned, but I cannot see the end device now while i perform the scan for pairing. Can you help me with the parameters that need to be set on xctu so that I can see the end device while I scan for devices in pairing mode.
The device CE is set to 1, NJ is set to FF.

9

AP 1, AO F

This would allow you to see all of the ZDO commands being sent to the Coordinator and allow you to use the API function of the XBee 3 to respond.

10

Hello,
I am trying to replica a set of commands or pairing a sensor, while in co-ordinator mode, the source address does not change to 0x0000 while I send a Node Descriptor request using the python digi-xbee module but it sends something else. Please help on how I can change the same.

11

In Zigbee 3.0, the source address of 0x00 does not exist. It is a function of the Zigbee 2006 and PRO standards that Digi added support for in their firmware for the Zigbee 3.0 standard. So no, if you are trying to reproduce the Zigbee 3.0 standard, you will not see this change.

12

I think the source address 0×00 is always there is the device is a coordinator, the source 16 bit address would always be 0×00.
And yes I got the address to work, it was a firmware issue which made the address other than 0×00. So I had to reinstall the firmware and it worked.

13

I am eager to know why we don’t have an esit option to change the operating channel in the zigbee 3.0 device. Strange as it’s a valid thing which is needed for device to connect. Everytime I have to reset the device and wait for it to randomly pick the channel that I want to.

14

It is the Coordinator that select the channel based off of the SC value and the noise on the listed supported channels. You can reduce this by reducing the number of channels the module can scan in the SC value of the Coordinator.