# Discover node problem

**URL:** <https://forums.digi.com/t/discover-node-problem/18547>\
**Category:** XBee Programamble (S2C & 900 HP)\
**Tags:** node-discovery, digimesh\
**Created:** [July 18, 2017, 9:29am UTC](https://forums.digi.com/t/discover-node-problem/18547 "2017-07-18T09:29:47Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![galazari](https://avatars.discourse-cdn.com/v4/letter/g/3be4f8/32.png) [@galazari](https://forums.digi.com/u/galazari)\
**Post date:** [July 18, 2017, 9:29am UTC](https://forums.digi.com/t/discover-node-problem/18547/1 "2017-07-18T09:29:47Z")

</div>

I am facing a problem with the discover node functionality of digimesh.  
I have a synchronous sleeping network. What I observed is when a ATDN command is issued in the end of a wake cycle to a synchronous sleep node, the node won’t sleep until the next wake cycle.  
For example, if my wake time is 10 seconds, and I issue an ATDN command in the 9th second, the node won’t sleep. The NT parameter is set to it’s minimum value

---

<div class="post-metadata">

**Author:** ![mvut](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/mvut/32/31_2.png) [@mvut](https://forums.digi.com/u/mvut)\
**Post date:** [July 18, 2017, 9:57am UTC](https://forums.digi.com/t/discover-node-problem/18547/2 "2017-07-18T09:57:46Z")

</div>

Which XBee product and firmware version are you working with?

---

<div class="post-metadata">

**Author:** ![galazari](https://avatars.discourse-cdn.com/v4/letter/g/3be4f8/32.png) [@galazari](https://forums.digi.com/u/galazari)\
**Post date:** [July 19, 2017, 10:15am UTC](https://forums.digi.com/t/discover-node-problem/18547/3 "2017-07-19T10:15:23Z")

</div>

I am working with xbee 868lp and I have installed the latest firmware version (8074).

---

<div class="post-metadata">

**Author:** ![mvut](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/mvut/32/31_2.png) [@mvut](https://forums.digi.com/u/mvut)\
**Post date:** [July 19, 2017, 11:27am UTC](https://forums.digi.com/t/discover-node-problem/18547/4 "2017-07-19T11:27:21Z")

</div>

Sounds like you are not using Synchronous sleep.

---

<div class="post-metadata">

**Author:** ![galazari](https://avatars.discourse-cdn.com/v4/letter/g/3be4f8/32.png) [@galazari](https://forums.digi.com/u/galazari)\
**Post date:** [July 19, 2017, 2:26pm UTC](https://forums.digi.com/t/discover-node-problem/18547/5 "2017-07-19T14:26:13Z")

</div>

Yes I do. One device is configured as sleep support and sleep coordinator (SM = 0x7, SO = 0x1) and a node configured as synchronous cyclic sleep and non sleep coordinator (SM = 0x8, SO = 0x2). I didn’t mention it, but what I observed is that when a issue an ATDN command on the end of the wake cycle, the node won’t sleep until the network wakes and sleeps again

---

<div class="post-metadata">

**Author:** ![mvut](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/mvut/32/31_2.png) [@mvut](https://forums.digi.com/u/mvut)\
**Post date:** [July 19, 2017, 2:28pm UTC](https://forums.digi.com/t/discover-node-problem/18547/6 "2017-07-19T14:28:20Z")

</div>

I think that is because the module is in AT command mode until the command completes. So no it is not going to cycle to a sleep state.