Xbee 节点发现响应 [英] Xbee Node Discovery Response

查看:34
本文介绍了Xbee 节点发现响应的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试从协调器中发现我网络中的设备.所以我向协调器发送了一个 ND 命令,我正确地收到了其他 Xbee 的响应.

I'm trying to discover devices, from a coordinator, in my network. So I sent an ND command to the coordinator and I'm correctly receiving response from other Xbee.

下一步是将我收到的信息存储在网络应用程序中,以便发送命令和数据.

The next step will be to store the information I've received in a web application, in oder to send commands and data.

然而,我仍然缺少的是框架中的某些部分.到目前为止,我已经像这样映射了框架:

However, what I'm still missing is some parts in the frame respose. So far I've mapped the frame like this:

1     7E                  start frame    
===== =================== MESSAGE LENGHT
2-3   0x00 0x19           -> 25
===== =================== PACKET TYPE
4     88                  -> response to a remote AT command
5     02                  frame ID
===== =================== AT COMMAND
6-7   0x4E 0x44           "ND"
8     00                  status byte (00 -> OK)

===== =================== MY - Remote Address
9-10  0x17 0x85
===== =================== SH - SERIAL NUMBER HIGH
11-14 0x00 0x13 0xA2 0x00
===== =================== SL - SERIAL NUMBER LOW    
15-18 0x40 0xB4 0x50 0x23
===== =================== SIGNAL     
19    20
= ======== NI - Node Identifier
20 00 
21 FF     
22 FE     
23 01   
24 00          
25 C1     
26 05
27 10     
28 1E     
===== ===== CHECKSUM (25th bytes from MESSAGE LENGHT)
29 19  

那么,我在哪里可以在此响应中找到设备的地址?我的猜测是在消息的 NI 部分,但是,我没有找到任何关于如何组织数据的示例/信息.

So, where I can find in this response the address of the device ? My guess is in the NI part of the message but, I haven't find any example/information of how the data are organised.

有人能指出我正确的方向吗?

Could someone point me in the right direction?

推荐答案

正如有人在 dig.com 论坛中告诉我的

As someone told me in the dig.com forum

NI<CR>                 (Variable length)
PARENT_NETWORK ADDRESS (2 Bytes)<CR>
DEVICE_TYPE            (1 Byte: 0=Coord, 1=Router, 2=End Device)
STATUS                 (1 Byte: Reserved)
PROFILE_ID             (2 Bytes)
MANUFACTURER_ID        (2 Bytes

所以,期待我的框架响应:

So, loking to my frame response:

00   --- Node Identifier variable, (here 1 byte = 00 because no value is set up).
FFFE --- parent network address (2 bytes)
01   --- device type  
00   --- status
C105 --- profile id
101E --- manufacturing id

afaik,这意味着在帧的最后一部分中,没有提供有关设备地址的信息.唯一的信息是 SL 和 SH.

This, afaik, means that in this last part of the frame, no information about address of the device are given. Only information are the SL and SH.

这篇关于Xbee 节点发现响应的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆