Home/Support/Support Forum/Xbee zb API coordinator doesn't respond to Beacon request

Xbee zb API coordinator doesn't respond to Beacon request

0 votes
Hello!

I have few other manufacturers zigbee ha devices. Another one, router (adhoco S1), joins properly after sending beacon request message to the coordinator (s2c). See below:
[22:19:30.976651]
Beacon Request 03-08-03-FF-FF-FF-FF-07-FF-FF

Frame Information: (10 bytes)
Packet Number: 20
Protocol: ZigBee
Timestamp: 22:19:30.976651
Time Delta: 7.865496
Channel: 25
Length: 10
Link Quality: -2 dBm
Source: USB0687
Layer: MAC
Status: Normal
MAC Header: 0xFFFFFFFF030803
Frame Control: 0x0803
···· ···· ···· ·011 = Frame Type: [0x3] MAC Command
···· ···· ···· 0··· = Security Enabled: [0x0] No
···· ···· ···0 ···· = Frame Pending: [0x0] No
···· ···· ··0· ···· = Acknowledgement Request: [0x0] No
···· ···· ·0·· ···· = Intra-PAN: [0x0] No
···· ··00 0··· ···· = Reserved: 0x0
···· 10·· ···· ···· = Destination Addr Mode: [0x2] 16-bit Short Address
··00 ···· ···· ···· = Reserved: 0x0
00·· ···· ···· ···· = Source Addr Mode: [0x0] No Address
Sequence Number: 3
Destination PAN ID: 0xFFFF
Destination Address: 0xFFFF
MAC Payload: 0x07
Command Frame ID: [0x07] Beacon Request
MAC Footer: 0xFFFF
Frame Check Sequence: 0xFFFF

And the xbee zb beacon message:
[23:12:39.804003] Beacon 00-80-F7-F4-78-00-00-FF-CF-00-00-00-22-84-6A-33-90-E5-A2-C3-51-D6-FF-FF-FF-00-FF-FF
Frame Information: (28 bytes)
Packet Number: 331
Protocol: ZigBee
Timestamp: 23:12:39.804003
Time Delta: 0.038768
Channel: 25
Length: 28
Link Quality: -29 dBm
Source: USB0687
Layer: NWK
Status: Normal
MAC Header: 0x000078F4F78000
Frame Control: 0x8000
···· ···· ···· ·000 = Frame Type: [0x0] Beacon
···· ···· ···· 0··· = Security Enabled: [0x0] No
···· ···· ···0 ···· = Frame Pending: [0x0] No
···· ···· ··0· ···· = Acknowledgement Request: [0x0] No
···· ···· ·0·· ···· = Intra-PAN: [0x0] No
···· ··00 0··· ···· = Reserved: 0x0
···· 00·· ···· ···· = Destination Addr Mode: [0x0] No Address
··00 ···· ···· ···· = Reserved: 0x0
10·· ···· ···· ···· = Source Addr Mode: [0x2] 16-bit Short Address
Sequence Number: 247
Source PAN ID: 0x78F4
Source Address: 0x0000
MAC Payload: (19 bytes)
Super Frame Specification: 0xCFFF
···· ···· ···· 1111 = Beacon Order: 0xF
···· ···· 1111 ···· = Super Frame Order: 0xF
···· 1111 ···· ···· = Final Capacity Slot: 0xF
···0 ···· ···· ···· = Battery Life Extension: [0x0] No
··0· ···· ···· ···· = Reserved: 0x0
·1·· ···· ···· ···· = PAN Coordinator: [0x1] Yes
1··· ···· ···· ···· = Association Permit: [0x1] Yes
GTS Fields: 0x00
GTS Specifications: 0x00
···· ·000 = GTS Descriptor Count: 0x0
·000 0··· = Reserved: 0x0
0··· ···· = GTS Permit: [0x0] No
Pending Addresses Fields: 0x00
Pending Addresses Specification: 0x00
···· ·000 = Pending Short Addresses Count: 0x0
···· 0··· = Reserved: 0x0
·000 ···· = Pending Extended Addresses Count: 0x0
0··· ···· = Reserved: 0x0
Beacon Payload: (15 bytes)
Protocol ID: [0x00] ZigBee
NWK Layer Information: 0x8422
···· ···· ···· 0010 = Stack Profile: 0x2
···· ···· 0010 ···· = NWK Protocol Version: 0x2
···· ··00 ···· ···· = Reserved: 0x0
···· ·1·· ···· ···· = Router Capacity: [0x1] Yes
·000 0··· ···· ···· = Device Depth: 0x0
1··· ···· ···· ···· = End Device Capacity: [0x1] Yes
NWK Extended PAN ID: D6:51:C3:A2:E5:90:33:6A
Tx Offset: 0xFFFFFF
NWK Update ID: 0x00
MAC Footer: 0xFFFF
Frame Check Sequence: 0xFFFF

When I try to join the other device (endevice, adhoco R1) xbee coordinator doesn't respond to the beacon request. The beacon request are almost identical. The second one is presented below:
[22:58:50.112995] Beacon Request 03-08-F6-FF-FF-FF-FF-07-FF-FF
Frame Information: (10 bytes)
Packet Number: 271
Protocol: ZigBee
Timestamp: 22:58:50.112995
Time Delta: 0.133528
Channel: 25
Length: 10
Link Quality: -18 dBm
Source: USB0687
Layer: MAC
Status: Normal
MAC Header: 0xFFFFFFFFF60803
Frame Control: 0x0803
···· ···· ···· ·011 = Frame Type: [0x3] MAC Command
···· ···· ···· 0··· = Security Enabled: [0x0] No
···· ···· ···0 ···· = Frame Pending: [0x0] No
···· ···· ··0· ···· = Acknowledgement Request: [0x0] No
···· ···· ·0·· ···· = Intra-PAN: [0x0] No
···· ··00 0··· ···· = Reserved: 0x0
···· 10·· ···· ···· = Destination Addr Mode: [0x2] 16-bit Short Address
··00 ···· ···· ···· = Reserved: 0x0
00·· ···· ···· ···· = Source Addr Mode: [0x0] No Address
Sequence Number: 246
Destination PAN ID: 0xFFFF
Destination Address: 0xFFFF
MAC Payload: 0x07
Command Frame ID: [0x07] Beacon Request
MAC Footer: 0xFFFF
Frame Check Sequence: 0xFFFF

Any ideas how to fix this? or what to try next? Is there any way to force a end device to join or make end device to join without beacon message? A way to send the beacon response from xctu, c or python.

Coordinators settings are close to factory values, except
ZS = 2, CE = 1, EE = 0, AP = 1, AO = 3

Br.
J
asked Nov 3, 2015 in RF Solutions and XBee by JulliMullins New to the Community (2 points)

Please log in or register to answer this question.

2 Answers

0 votes
From what I can see, only the sequence number and packet number are different. What happens if you reset this 3rd party device?
answered Nov 4, 2015 by mvut Veteran of the Digi Community (12,001 points)
0 votes
Sorry for late reply. The 3rd party device ask for a beacon only after I fully reset the device.
answered Nov 9, 2015 by JulliMullins New to the Community (2 points)
...