Emberznet pro software

A single packet buffer can hold up to 32 bytes of data, so a large packet may require as many as 4 packet buffers to store. Packet buffers are also needed for messages buffered on a parent for sleepy end device children and for other transient network data used by the stack. This is the default behavior of the Application Framework already. Default is Default is 6; maximum is Hopefully, this guide has been helpful to you.

If you have any concerns about your large network design, please contact Silicon Labs technical support for advice. No, you can't have end devices attached to the ZC directly. Knowledge Article. Details Details. Answer Following are some useful tips on designing for large, dense networks, such as building automation networks for offices, hotels, or large residential areas. Information Title.

URL Name. Thread Zigbee. Sort by:. Search this feed Aggregator devcies typically need more packet buffers if the the network anticipates heavy traffic flow. Routers need less packet buffers. End devices need fewer still. The default value of the neighbor table is 16, which means that each device is capable of remembering up to 16 of its neighbors. The stack will also handle high density networks where each node has more neighbors than will fit in the table, making intelligent judgments about which neighbors to keep in the table and which to discard.

Note that the neighbor table entries are used as a list of potential next hops for routes being established, so routes to nodes not in the neighbor table require relaying through some other device; consequently, if the neighbor table size is reduced, it could lead to longer routes and potentially higher latency as a result.

It is often easy for an application developer to specify or estimate the maximum number of neighbors that each device is likely to see in a deployed network, and the neighbor table size can be reduced accordingly. Each neighbor table entry eliminated will recover 18 bytes of RAM. We recommend that this value be at least 8.

Note that end device children are tracked in the child table, not the neighbor table, so they do not impact this value. This does not include routed messages, so this can often be safely reduced in applications that have low outgoing traffic requirements.

In many applications this can be well understood and its value can be reduced safely. In the case of a sensor device that only sends messages to the gateway, for example, this could be reduced all the way to 1. For applications relying primarily on the Binding Table rather than the Address Table to remember persistent destinations, reducing the address table size may be worthwhile. However, if your application requires more memory you can apply the information in this article to get a better understanding of what memory is being used by the stack and what tradeoffs you might make by modifying these values.

Gecko Platform Version 4. Knowledge Base Articles Browse our knowledge base articles for information about specific products. Search Knowledge Base. User Forums Browse technical questions, share your ideas, and learn more about our latest solutions. Search the Forums. Still need help? Contact technical support or review a case. Request Support. Simplicity Studio Development Platform. Explore Studio. Close Loading Results. Unifies the Zigbee application standards and improves interoperability among IoT devices.