AVR-Chat

I don't think that you read the manual correctly.  Unless you want some
other kind of sleep mode.  To quote from the "Sleep" section of the XBee
manual:

"Sleep Modes enable the RF module to enter states of low-power consumption
when not in use. In
order to enter Sleep Mode, one of the following conditions must be met (in
addition to the module
having a non-zero SM parameter value):
• Sleep_RQ (pin 9) is asserted.
• The module is idle (no data transmission or reception) for the amount of
time defined by the
ST (Time before Sleep) parameter. [NOTE: ST is only active when SM = 4-5.]
The SM command is central to setting Sleep Mode configurations. By
default, Sleep Modes are disabled
(SM = 0) and the module remains in Idle/Receive Mode. When in this state,
the module is
constantly ready to respond to serial or RF activity.
Higher Voltages. Sleep Mode current consumption is highly sensitive to
voltage. Voltages above
3.0V will cause much higher current consumption.
Pin/Host-controlled Sleep Modes
The transient current when waking from pin sleep (SM = 1 or 2) does not
exceed the idle current
of the module. The current ramps up exponentially to its idle current.
Pin Hibernate (SM = 1)
• Pin/Host-controlled
• Typical power-down current: < 10 &#956;A (@3.0 VCC)
• Wake-up time: 13.2 msec
Pin Hibernate Mode minimizes quiescent power (power consumed when in a
state of rest or inactivity).
This mode is voltage level-activated; when Sleep_RQ is asserted, the
module will finish any
transmit, receive or association activities, enter Idle Mode and then
enter a state of sleep. The
module will not respond to either serial or RF activity while in pin sleep.
To wake a sleeping module operating in Pin Hibernate Mode, de-assert
Sleep_RQ (pin 9). The
module will wake when Sleep_RQ is de-asserted and is ready to transmit or
receive when the CTS
line is low. When waking the module, the pin must be de-asserted at least
two 'byte times' after
CTS goes low. This assures that there is time for the data to enter the DI
buffer."

  Blah, that didn't format out too well...  Anyway, the XBee networks are
designed to run in low power sleep mode for sensor arrays, so sleep and
indirect transmission queueing are indeed supported at the coordinator.

DLC

> Thanks for various responses to my original Zigbee question ...
>
> Had a quick scan of the XBee Zigbee manual (as opposed to 15.4) and it
> would appear these modules don't support sleep mode for "end devices" -
> is this correct, and does it therefore mean that XBee isn't suitable for
> mesh networking with battery powered end devices?
>
> Does one have to buy membership of the Zigbee Alliance to use these (or
> any other) modules in a commercial product? The ZA membership FAQ
> suggests strongly that this is the case:
>
> *"Q: If my company uses a ZigBee module in my product, do I need to be a
> member?*
> A: Yes."
>
> Are all commercial XBee users coughing up $3500 to ZA?!
>
> Mark
>
>
> larry barello wrote:
>> I did my complete development with the Xbee using TTY serial on my
>> doodads
>> (connected to mega128's).   They were pretty easy to use once I figured
>> out
>> how to configure them to do what I wanted.  You only need the level
>> shifter
>> if you want to connect to a PC for firmware upgrades (or
>> communications).
>>
>> I don't know about the 1 mile.  You can talk with the Xbee support folks
>> (they are *very* phone friendly) and they will give you a white paper
>> detailing how they came across that number.  It involved the whip
>> antennas
>> and line-of-site.  YMWV
>>
>>
>>
>>
>
>
>
> Yahoo! Groups Links
>
>
>
>