CC2652P: Is it possible to modify/set/adjust routing strategy

Hi Robert,

Many of the available configurations are summarized here: https://dev.ti.com/tirex/content/simplelink_cc13xx_cc26xx_sdk_7_41_00_17/docs/zigbee/html/zigbee/network_configuration.html?highlight=zglobal#changing-stack-parameters

You can check the various "radius" parameters, for example "zcl_radius" in zcl.h limits the amount of hops a message is allowed to travel.
More fine-tuned routing would require source code.

Note that optimizing for lower hop count also saves RAM and reduces potential network congestion.

Given two points A and B, it may also be that not all possible paths are determined at a given time, thus the lowest cost path which has been discovered and is "good enough" will more often than not become the route which is used between A and B (i.e. breadth first search).

Thanks,
Toby

Hi Toby,

Thank you for your answer. I understand why reducing hop count is important. However we have noticed that some routes are with very poor LQI and in reality star architecture is build rather than mesh - which is obvious due to the routing algorithm. Eventually this leads to system with performance that is not accepted by our client, we need to have response (router-coordinator-router) time below 0.5s.

Hi Robert,

Thanks for clarifying the concerns.

To give a rough idea, what are some of the response time you are observing?
Do you see a lot of re-tries over the air? 

Regarding devices:

How many devices do you expect to operate in the network?

Are all those devices based on TI Z-Stack (or perhaps some third party products as well)?

One way to enforce routing is reducing the number of neighbors allowed per router (MAX_NEIGHBOR_ENTRIES).

Thanks,
Toby

Additionally, perhaps this might help: dev.ti.com/.../z-stack-overview.html

Hi Toby,

Thanks for reply. The link and MAX_NEIGHBOR_ENTRIES (for coordinator) might help. I will check the impact!

Thanks!