# Xbee parameters goes to default values

**URL:** <https://forums.digi.com/t/xbee-parameters-goes-to-default-values/18640>\
**Category:** XBee - 802.15.4\
**Tags:** factory-defaults, s8, xbee\
**Created:** [August 14, 2017, 10:57am UTC](https://forums.digi.com/t/xbee-parameters-goes-to-default-values/18640 "2017-08-14T10:57:53Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![yafisdamda](https://avatars.discourse-cdn.com/v4/letter/y/9dc877/32.png) [@yafisdamda](https://forums.digi.com/u/yafisdamda)\
**Post date:** [August 14, 2017, 10:57am UTC](https://forums.digi.com/t/xbee-parameters-goes-to-default-values/18640/1 "2017-08-14T10:57:53Z")

</div>

Hi.  
I am using Xbee S8 (868) in API1 mode. The Xbee is connected to host controller over UART.  
I use AT mode for setting Network ID of the device by changing the mode.  
The problem is some times the values of Xbee parameters changes to default without me sending any RE command. Sometimes only one value changes. The values i am concerned about are Network ID and EE (encryption enable). It gets changed and my complete network gets affected.  
Any inputs?

---

<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:** [August 14, 2017, 11:16am UTC](https://forums.digi.com/t/xbee-parameters-goes-to-default-values/18640/2 "2017-08-14T11:16:20Z")

</div>

Are you using the Write parameter when setting the values?

Are you seeing any API status frames indicating a watch dog reset or anything?

---

<div class="post-metadata">

**Author:** ![yafisdamda](https://avatars.discourse-cdn.com/v4/letter/y/9dc877/32.png) [@yafisdamda](https://forums.digi.com/u/yafisdamda)\
**Post date:** [August 16, 2017, 2:20pm UTC](https://forums.digi.com/t/xbee-parameters-goes-to-default-values/18640/3 "2017-08-16T14:20:22Z")

</div>

Hi.  
I am setting these values using xctu, atleast the EE parameter. But the network-id is set by the host processor.  
I am not seeing any frames indicating watchdog reset.  
Does a watchdog reset sets these values to default?

---

<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:** [August 16, 2017, 2:22pm UTC](https://forums.digi.com/t/xbee-parameters-goes-to-default-values/18640/4 "2017-08-16T14:22:20Z")

</div>

As long as the settings are written to flash with the WR command, a watch dog reset would not change them.

---

<div class="post-metadata">

**Author:** ![yafisdamda](https://avatars.discourse-cdn.com/v4/letter/y/9dc877/32.png) [@yafisdamda](https://forums.digi.com/u/yafisdamda)\
**Post date:** [August 17, 2017, 11:00am UTC](https://forums.digi.com/t/xbee-parameters-goes-to-default-values/18640/5 "2017-08-17T11:00:56Z")

</div>

Yes. I am using WR command. But my concern is how come the EE parameter is changed? I set this using xctu.

---

<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:** [August 17, 2017, 11:04am UTC](https://forums.digi.com/t/xbee-parameters-goes-to-default-values/18640/6 "2017-08-17T11:04:51Z")

</div>

Do you see this occur when the module is NOT connected to your processor? That is, can you reproduce this outside of your hardware?

---

<div class="post-metadata">

**Author:** ![yafisdamda](https://avatars.discourse-cdn.com/v4/letter/y/9dc877/32.png) [@yafisdamda](https://forums.digi.com/u/yafisdamda)\
**Post date:** [August 18, 2017, 11:01am UTC](https://forums.digi.com/t/xbee-parameters-goes-to-default-values/18640/7 "2017-08-18T11:01:03Z")

</div>

No. I have not observed this behavior outside of my hardware. Strangely this occur sometimes. But i have faced this quiet a few times.

---

<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:** [August 18, 2017, 11:11am UTC](https://forums.digi.com/t/xbee-parameters-goes-to-default-values/18640/8 "2017-08-18T11:11:19Z")

</div>

Than it has to be something in your application that issuing the change of the command or an ATRE or something of that nature.

---

<div class="post-metadata">

**Author:** ![yafisdamda](https://avatars.discourse-cdn.com/v4/letter/y/9dc877/32.png) [@yafisdamda](https://forums.digi.com/u/yafisdamda)\
**Post date:** [August 22, 2017, 2:06pm UTC](https://forums.digi.com/t/xbee-parameters-goes-to-default-values/18640/9 "2017-08-22T14:06:14Z")

</div>

well. The application is not sing ATRE command. I will check it anyway. What else could be the reason?

---

<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:** [August 22, 2017, 2:14pm UTC](https://forums.digi.com/t/xbee-parameters-goes-to-default-values/18640/10 "2017-08-22T14:14:46Z")

</div>

If you have written the values to memory using the WR command, the only way to change them is by entering command mode and changing the value again, issue an ATRE via the local UART or either from an over the air command. That is it.

---

<div class="post-metadata">

**Author:** ![yafisdamda](https://avatars.discourse-cdn.com/v4/letter/y/9dc877/32.png) [@yafisdamda](https://forums.digi.com/u/yafisdamda)\
**Post date:** [August 24, 2017, 9:33am UTC](https://forums.digi.com/t/xbee-parameters-goes-to-default-values/18640/11 "2017-08-24T09:33:24Z")

</div>

Can this happen because of power fluctuations?

---

<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:** [August 24, 2017, 9:40am UTC](https://forums.digi.com/t/xbee-parameters-goes-to-default-values/18640/12 "2017-08-24T09:40:05Z")

</div>

If you mean by providing the radio less than then VCC Min? if so, than anything can occur when you operate out of the VCC Specification.
