Skip to Navigation
Home
  • Company
    • Quick Facts
    • Board of Directors
    • Management Team
    • Press Releases
    • News Coverage
    • Newsletter
    • Careers
    • Articles
    • Ember Chronology
    • Contact Us
  • Products
    • ZigBee Chips
    • ZigBee Software
    • ZigBee Development Tools
    • Documentation
  • Buy
    • Digi-Key (Online)
    • Distributors
  • Applications
    • AMI & AMR
    • Integrated Home Automation
    • Building Automation
    • Others
  • ZigBee
    • About ZigBee
    • Ember & ZigBee
    • ZigBee FAQ
    • Download Specifications
    • ZigBee Events
  • Partners
  • Support
    • Training
  • Events
Home

EmberZNet

What registers control the Sleep Timer on the EM250?

Categories:
  • Software : Embedded
  • EmberZNet PRO
  • EmberZNet
  • EM250

In terms of the register-based configuration of the Sleep Timer on the EM250 platform, this is very much like using the two general-purpose user timers (Timer1 and Timer2), just with a much smaller set of registers and configuration options…

See Also: 
How can I determine the wake source when the EM250 wakes from sleep?
Can I remove halTimerIsr() if I'm not using the buzzer or any timer routines in my application?
  • Read more

Walkthroughs

Categories:
  • ZigBee
  • Training
  • EmberZNet

In this section we feature use case “walkthroughs” that will help you to get started building a particular configuration. A walkthrough should provide all the necessary steps, so if you run into trouble or are unclear about what to do at a certain point, please post a comment to indicate what’s not clear — we’ll update it based on your input.

How does the stack manage my end device's connection with the network? Will it rejoin automatically on boot-up?

Categories:
  • Software : Networking
  • EmberZNet

The stack does not take control of your device to make it decide to join a network; it does not know how often you wish to retry joining (as this will consume battery power and bandwidth) or if you wish to abort the joining process completely and leave the network to try a new scan, or try a new node type.

Basically, the process should happen like this in a typical application:

  • Device calls emberNetworkInit() after reboot.
  • If device was previously part of a network, NetworkInit returns EMBER_SUCCESS; otherwise, it returns EMBER_NOT_JOINED.
See Also: 
Why does my device successfully join the network but can't talk to the other devices?
Zigbee Network Joining
How long can my end device go without polling its parent? What happens after that timeout?
  • Read more

What does the RSSI values mean in emberEnergyScanResultHandler() & emberGetLastHopRssi()?

Categories:
  • Software : Embedded
  • EmberZNet PRO
  • EmberZNet

In emberGetLastHopRssi() the RSSI value is of data type int8s, which is the RSSI energy level in dBm.

In emberEnergyScanResultHandler() the RSSI value is of data type int8u. This is the raw RSSI value straight from the radio, which is offset by -154 from the actual dBm value measured.  So take your unsigned 8-bit result, subtract 154 from that, and that is the RSSI energy level in dBm for that channel.

Using custom tokens

Categories:
  • Software : Embedded
  • Training
  • EmberZNet PRO
  • EmberZNet
  • EM250

Learn how to define and use custom tokens in EmberZNet.

Sending messages to sleepy end devices

Categories:
  • Software : Networking
  • Training
  • EmberZNet PRO
  • EmberZNet

There are certain factors to take into account when sending messages to sleepy devices: Buffered messages take up packet buffers on the parent. The poll period directly influences latency in the delivery of a message to a sleepy device. The maximum time that a parent will buffer a message for a sleepy device is 30 seconds. This How-To will explain in more detail how to consider these limiting factors when designing your application for a network with sleepy end devices.

  • Read more

Reducing RAM usage in EmberZNet PRO

Categories:
  • Software : Embedded
  • Training
  • EmberZNet PRO
  • EmberZNet
How to reduce the RAM used by EmberZNet by reducing the memory available to the stack for certain functions. In some applications not all functions are necessary, or necessary to the same degree -- this how-to discusses which reductions are possible and what network behavior they affect.

Overview

  • Read more

How many different concentrators can I have in a single network?

Categories:
  • Software : Networking
  • EmberZNet PRO
  • EmberZNet

The number of concentrators is limited by the number of routing entries all devices have available to use for many-to-one entries and how often these concentrators send many-to-one route requests.

The many-to-one route requests are broadcasts and the aggregate rate of these must not be larger than the discovery table can handle, and you really want the rate to be much less that this, as broadcasts will affect the throughput of the network. These route entries do time out and (just like normal table routes) become replaceable if not used.

  • Read more

Using security in EmberZNet

Categories:
  • Software : Networking
  • Training
  • EmberZNet PRO
  • EmberZNet

Here are the 4 main types of security configurations in EmberZNet 3.0.1. I have enumerated below all the ways the Security bitmask should be set.

  • Read more

Why does my device successfully join the network but can't talk to the other devices?

Categories:
  • Software : Networking
  • EmberZNet PRO
  • EmberZNet

I am using security in my network (my key is all 0's) and when my device attempts to join the network, it is successful but then cannot talk to the other devices.

The stack does not support security keys of all 0's. This will cause the behavior indicated above. The only fix is to change to a non-zero security key.

12next ›last »
Syndicate content

Search

Primary links
  • Developer Blog
  • Documentation
    • Release Notes
  • Contributed Software
  • FAQs
  • Change Notifications
  • Training
Portal
  • My Account
  • Search
User login
  • Request new password

Company | Products | Buy | Applications | ZigBee | Partners | Support | Events | Contact Us

©2007-2008 Ember Corporation | All rights reserved | Privacy