Specifications

This feature was added to better supports nodes that spend most of their time “sleeping.” If a node is
going to be asleep, there may be no point in it becoming part of routes for other nodes while it is
(briefly) awake.
This can also be useful if some nodes are externally powered, while others are battery-powered.
Assuming sufficient radio coverage (all the externally powered nodes can “hear” all of the other
nodes), then the Mesh Override can be set to 1 in the battery powered nodes, extending their battery
life at the expense of reducing the “redundancy” in the overall mesh network.
NOTE – Enabling this feature on your bridge node means Portal will no longer be able to
communicate with the rest of your network, regardless of how everything else is configured. No nodes
in your network (except for your bridge node) will be able to receive commands or information from
Portal or send commands or information to Portal.
ID 31 – Mesh Routing LQ Threshold
This allows for penalizing hops with poor Link Quality.
Hops that have a link quality worse than (i.e. a higher value than) the specified threshold will be
counted as two hops instead of one. This allows the nodes to choose (for example) a two-hop route
with good link quality over a one-hop route with poor link quality.
The default threshold setting of 127 is the highest valid value, so that no “one hop penalty” will ever
be applied.
See also NV Parameters #32, #39, and #27.
ID 32 – Mesh Rejection LQ Threshold
This allows for rejecting hops with poor link quality.
Hops that have a link quality worse than (i.e. a higher value than) the specified threshold will be
rejected as the node performs route requests. The default threshold setting of 127 is the highest valid
value, so that all routes will be considered for mesh routing.
See also NV Parameters #31, #39, and #27.
ID 33 – Noise Floor
The Carrier Sense and Collision Detect features work by checking the current ambient signal level
before broadcasting (for Carrier Sense) and immediately after broadcasting (for Collision Detect) to
determine whether some other node is broadcasting. In an environment with a lot of background noise,
the noise floor can trigger false positives for these features, preventing the node from broadcasting, or
causing it to endlessly rebroadcast packets.
On platforms that do not allow pokes (or radioPokes) to adjust the noise floor level, NV Parameter 33
can be used to define the signal strength that must be encountered to trigger the Carrier Sense and
Collision Detect features. The parameter is in negative dBm, with a range from 0 to 127. Refer to your
SNAP Reference Manual Document Number 600-0007K Page 101 of 202