Specifications

platform’s section at the end of this manual to determine whether this parameter applies to your
platform.
ID 34 through 38 – Reserved for Future Use
Reserved for future Synapse use.
ID 39 – Radio LQ Threshold
This allows for ignoring packets with poor Link Quality.
Link quality values range from a theoretical 0 (perfect signal, 0 attenuation) to a theoretical 127 (127
dBm “down”). This parameter defaults to a value of 127, which makes it have no effect (you cannot
receive a packet with a link quality “worse” than 127).
If you lower this parameter from its default value of 127, you are in effect defining an “acceptance
criteria” on all received packets. If a packet comes in with a link quality worse (higher) than the
specified threshold, then the packet will be completely ignored.
This gives you the option to ignore other nodes that are “on the edge” of radio range. The idea is that
you want other (closer) nodes to take care of communicating to that node.
Caution – if you set this parameter too low, your node may not accept any packets.
ID 40 – SNAPpy CRC
The 16-bit Cyclic Redundancy check (CRC) of the currently loaded SNAPpy script.
Most users will not need to write to this NV parameter. If you do change it from its automatically
calculated value, you will make the SNAP node think its copy of the SNAPpy script is invalid, and it
will not use it.
ID 41 – Platform
This System NV parameter makes it easier to write scripts that work on more than one type of SNAP
Node. Set this string parameter to some label that identifies your hardware platform.
New RF100 SNAP Engines from Synapse will come with “RF100” in this parameter. Older RF100
engines may have had “RFEngine” here. If you are working with SNAP-compatible radios or engines
from another source, the parameter might not be loaded with any meaningful value. Furthermore, like
other NV parameters the value can be changed. To make use of this field, it is the responsibility of the
user to ensure that the value in the parameter is meaningful and consistent across your collection of
nodes.
In your script, you must include the following line:
8
from synapse.snapsys import *
8
The synapse.snapsys file must be imported, but may be imported indirectly. For example, if you import synapse.platforms
to get a meaningful enumeration of GPIO pins for SNAP Engines, that script already imports synapse.snapsys, so you do
not need to explicitly import it separately.
Page 102 of 202 SNAP Reference Manual Document Number 600-0007K