# xBee API Response to ND command contains extra undefined characters

**URL:** <https://forums.digi.com/t/xbee-api-response-to-nd-command-contains-extra-undefined-characters/11744>\
**Category:** XBee Programamble (S2C & 900 HP)\
**Tags:** response, nd, api, xbee\
**Created:** [July 18, 2013, 1:45am UTC](https://forums.digi.com/t/xbee-api-response-to-nd-command-contains-extra-undefined-characters/11744 "2013-07-18T01:45:54Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![dvorreiter](https://avatars.discourse-cdn.com/v4/letter/d/a88e57/32.png) [@dvorreiter](https://forums.digi.com/u/dvorreiter)\
**Post date:** [July 18, 2013, 1:45am UTC](https://forums.digi.com/t/xbee-api-response-to-nd-command-contains-extra-undefined-characters/11744/1 "2013-07-18T01:45:54Z")

</div>

Hello

I am using the xBee series 2 devices in API mode.

When I send out the ND command to the local device , I correctly receive information from all devices on the network.

However in the response I also receive two extra bytes before the external device high and low serial numbers. There is nothing in the ND AT command response documentation which indicates what these bytes are.

---

<div class="post-metadata">

**Author:** ![16ksa23](https://avatars.discourse-cdn.com/v4/letter/1/aeb1de/32.png) [@16ksa23](https://forums.digi.com/u/16ksa23)\
**Post date:** [July 18, 2013, 1:47am UTC](https://forums.digi.com/t/xbee-api-response-to-nd-command-contains-extra-undefined-characters/11744/2 "2013-07-18T01:47:35Z")

</div>

Hi,

Provide the full response of the ATND command.

---

<div class="post-metadata">

**Author:** ![dvorreiter](https://avatars.discourse-cdn.com/v4/letter/d/a88e57/32.png) [@dvorreiter](https://forums.digi.com/u/dvorreiter)\
**Post date:** [July 18, 2013, 3:08am UTC](https://forums.digi.com/t/xbee-api-response-to-nd-command-contains-extra-undefined-characters/11744/3 "2013-07-18T03:08:13Z")

</div>

OK here is an example response

7E 00 24 88 01 \<- This is Api header including length etc

4E 44 0 \<- This is original request “ND”

53 \<- Unknown byte 1 \*\*\*\* What Are these ???  
5B \<- Unknown byte 2 \*\*\*\* What Are these ???

00 7D 33 A2 00 High Serial number (escaped)  
40 3E 0E 8A Low Serial Number

45 4E 44 5F 44 45 56 49 43 45 5F 34 0 (NI = END\_DEVICE\_4

FF \<- AT response and APi remainder  
FE  
1  
0  
C1  
5  
10  
1E  
0

---

<div class="post-metadata">

**Author:** ![16ksa23](https://avatars.discourse-cdn.com/v4/letter/1/aeb1de/32.png) [@16ksa23](https://forums.digi.com/u/16ksa23)\
**Post date:** [September 28, 2013, 9:34am UTC](https://forums.digi.com/t/xbee-api-response-to-nd-command-contains-extra-undefined-characters/11744/4 "2013-09-28T09:34:28Z")

</div>

Did you check in the product manual for information these extra bytes?  
If you use the latest firmware does the problem still persists?

---

<div class="post-metadata">

**Author:** ![dvorreiter](https://avatars.discourse-cdn.com/v4/letter/d/a88e57/32.png) [@dvorreiter](https://forums.digi.com/u/dvorreiter)\
**Post date:** [September 30, 2013, 9:19am UTC](https://forums.digi.com/t/xbee-api-response-to-nd-command-contains-extra-undefined-characters/11744/5 "2013-09-30T09:19:06Z")

</div>

I did check in the product information and it does not describe these two bytes.

---

<div class="post-metadata">

**Author:** ![wz2b](https://avatars.discourse-cdn.com/v4/letter/w/e274bd/32.png) [@wz2b](https://forums.digi.com/u/wz2b)\
**Post date:** [November 3, 2014, 10:06am UTC](https://forums.digi.com/t/xbee-api-response-to-nd-command-contains-extra-undefined-characters/11744/6 "2014-11-03T10:06:16Z")

</div>

I don’t know if it’s too late or not, but …

the first two bytes you are getting back - right before the MAC address of the discovered device - is the network-assigned 16 bit address for the device. If you look at the xbee command reference table, this corresponds to what you’d get with an “MY” command.
