Zigbit loosing "persistant" EEPROM settings

Go To Last Post
3 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi guys,

I have a bunch of ATZB-900 Zigbit + Serialnet mesh modules running on a mesh for several weeks now. The application can restart the module should it behave erroneous but usually they are on 24/7.
I had the first one not connecting any more some days ago and the second module dropping out a few days after.
Checking those Zigbits revealed that they have lost their pre-programmed ID, when at+gsn? is issued it returns just 0s.
Which explains why it doesn't connect to the mesh any more.
All other settings are fine but get re-written every time the module starts because we assumed that it would neither trigger an EEPROM write cycle as it's always the same values (except for the first time, of course) nor would it happen very often (only in the case when no coordinator is in rage it might happen after ~15min)

- Anyone else experiencing such a behavior?
- Does overwriting a parameter with the same value trigger an EEPROM write cycle and could that eventually wear out the cells?
- Is Bitcloud V1.14.0 and Serialnet V2.7.0 the version to go with, I sometimes see funny numbers for +WROLE and remember to have read that this could be down to a not-fully-bug-free version of the code

Thanks

Last Edited: Fri. Oct 16, 2015 - 02:16 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

SerialNet in BitCloud V1.14.0 is broken, use earlier version.

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

Is Bitcloud V1.14.0 and Serialnet V2.7.0

Atleast that version worked for you for some-days.. It didnt even work for me..