Home/Support/Support Forum/Can't set NW

Can't set NW

0 votes
Whenever I send either an AT query api packet, or AT command api packet for NW with 0x0001, I always get back 0x00CF. WTF? How is that parameter getting 'locked'? I can set the PAN ID appropriately, so it's not like I'm not getting api AT command packets across the wire sucessfully...
asked May 2, 2016 in ZigBee PRO Featureset (and legacy ZNet 2.5) by stevefranks New to the Community (1 point)

Please log in or register to answer this question.

2 Answers

0 votes
Which module and firmware version are you working with? What is the CE and SM commands set to on this module?
answered May 3, 2016 by mvut Veteran of the Digi Community (11,969 points)
XBeeCallbacks: Firmware version: 0x23A7
XBeeCallbacks: Hardware Version: 0x1E46
XBeeCallbacks: CE: 0xEC00
XBeeCallbacks: Sleep Mode: 0x00D6

(I'm just assuming CE and SM are 2 bytes, they are probably 1 byte, the manual is ambiguous unless you look at the defaults & range on a lot of these)
0 votes
XBeeCallbacks: Firmware version: 0x23A7
XBeeCallbacks: Hardware Version: 0x1E46
XBeeCallbacks: CE: 0xEC00
XBeeCallbacks: Sleep Mode: 0x00D6

(I'm just assuming CE and SM are 2 bytes, they are probably 1 byte, the manual is ambiguous unless you look at the defaults & range on a lot of these)
answered May 3, 2016 by stevefranks New to the Community (1 point)
edited May 3, 2016 by stevefranks
XBeeCallbacks: Error sending packet: delivery status: 0x22 (0x22 = no network available, 0x24 = bad destination addr [set with ZigDestAddr cmd]), retries: 0, discovery status: 0x22
XBeeApi::ApiTxStatus: FrameType (0x8B): 0x8B; FrameID (215): 0xD7; Addr16: 0x0000; RetryCount: 0; DeliveryStatus (0=sucess): 0x22; DiscoveryStatus: 0x00 .
XBeeCallbacks: Error sending packet: delivery status: 0x22 (0x22 = no network available, 0x24 = bad destination addr [set with ZigDestAddr cmd]), retries: 0, discovery status: 0x22
XBeeApi::ApiTxStatus: FrameType (0x8B): 0x8B; FrameID (216): 0xD8; Addr16: 0x0000; RetryCount: 0; DeliveryStatus (0=sucess): 0x22; DiscoveryStatus: 0x00 .

XBeeCallbacks: Now in network! Will start sending beacons...
XBeeCallbacks: Error sending packet: delivery status: 0x21 (0x22 = no network available, 0x24 = bad destination addr [set with ZigDestAddr cmd]), retries: 0, discovery status: 0x21
XBeeApi::ApiTxStatus: FrameType (0x8B): 0x8B; FrameID (217): 0xD9; Addr16: 0x0000; RetryCount: 0; DeliveryStatus (0=sucess): 0x21; DiscoveryStatus: 0x02 .
XBeeCallbacks: Error sending packet: delivery status: 0x21 (0x22 = no network available, 0x24 = bad destination addr [set with ZigDestAddr cmd]), retries: 0, discovery status: 0x21
XBeeApi::ApiTxStatus: FrameType (0x8B): 0x8B; FrameID (218): 0xDA; Addr16: 0x0000; RetryCount: 0; DeliveryStatus (0=sucess): 0x21; DiscoveryStatus: 0x00 .
XBeeCallbacks: Error sending packet: delivery status: 0x21 (0x22 = no network available, 0x24 = bad destination addr [set with ZigDestAddr cmd]), retries: 0, discovery status: 0x21
XBeeApi::ApiTxStatus: FrameType (0x8B): 0x8B; FrameID (219): 0xDB; Addr16: 0x0000; RetryCount: 0; DeliveryStatus (0=sucess): 0x21; DiscoveryStatus: 0x02 .
Are you using Source Routing? That is, are you issuing the AR command at all?
Our coordinator has AR set to 6.
XBeeApi::ApiTxStatus: FrameType (0x8B): 0x8B; FrameID (61): 0x3D; Addr16: 0xFFFD; RetryCount: 0; DeliveryStatus (0=sucess): 0x24; DiscoveryStatus: 0x01 .

It's stuck in address discovery forever, I get screens full of these messages, even after a successful JV / AI message.
Not sure what you mean. The API Status frame indicates that it was received.
...