# Loose messages

**URL:** <https://forums.digi.com/t/loose-messages/1082>\
**Category:** XBee - DigiMesh\
**Created:** [January 26, 2010, 7:45pm UTC](https://forums.digi.com/t/loose-messages/1082 "2010-01-26T19:45:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![llans](https://avatars.discourse-cdn.com/v4/letter/l/97f17d/32.png) [@llans](https://forums.digi.com/u/llans)\
**Post date:** [January 26, 2010, 7:45pm UTC](https://forums.digi.com/t/loose-messages/1082/1 "2010-01-26T19:45:49Z")

</div>

Hi!  
Trying to introduce Digi mesh in the data collection system.  
±-----+ ±-----+  
| XBee master| \<---------\> | XBee slave|  
±-----+ | ±-----+  
|  
|  
±-----+  
| XBee |  
±-----+  
X-CTU(monitor)

DigiMesh is set in default broadcast mode.  
Discovers oddity: In the system with one master. It sends requests and receives responses. The answer comes immediately after receiving the request. If I send a short query (10-12 bytes), then have the response. If I just send a second request, then have no response, while though the monitor see the request and response. If I wait a second query about 0,2 s, then the response comes. If I send a long query (80 -100 bytes), then have no response (monitor see the request and response). If answer come with timeout, it’s OK.  
Seems Xbee after transmit can loose incoming message!

---

<div class="post-metadata">

**Author:** ![llans](https://avatars.discourse-cdn.com/v4/letter/l/97f17d/32.png) [@llans](https://forums.digi.com/u/llans)\
**Post date:** [January 29, 2010, 5:54pm UTC](https://forums.digi.com/t/loose-messages/1082/2 "2010-01-29T17:54:01Z")

</div>

Found that I wait too small.  
After long request, XBee something waits and response will come after 0,2…0,3 s. It’s strange and means that we can’t predict response time.
