one digipeated address with each hop. Again, see the examples below and the
command descriptions for detail.
The current setting of UIDWAIT determines whether or not a delay is added to
UI digipeat packets (those formed by UIDIGI, UIFLOOD, or UITRACE) before
transmission, once the channel is clear. If UIDWAIT is ON, the delay is deter
-
mined by slottime or persist settings.
The purpose of the UIGATE (which is in multi-port devices only) is to prevent
heavy high speed UI frame activity from congesting (“flooding”) the low speed
(port 1) frequency.
Each of these commands is documented in the “Command Reference”.
Note: Digipeater priority for call signs is as follows: MYCALL, MYNODE,
MYALIAS, UIDIGI, UIFLOOD, UITRACE (e.g. if you assign the same call sign
to MYALIAS and UIDIGI, a to-be-digipeated frame with that call sign will be
digipeated according to the rules that apply to MYALIAS.)
Using “UI” Digipeat Commands: UIDIGI, UIFLOOD, and
UITRACE
The following are actual monitored outputs of a lab system consisting of one po-
sition reporting station and three digipeaters, where each digi is configured using
the UIDIGI, UIFLOOD, or UITRACE command and where UIDWAIT is set
ON. We set UIDWAIT ON to force the system to digipeat all or most of the UI
frames without collision. In all examples, the reporting station, NØGZZ, is used
to launch a UI packet with the path set by the UNPROTO command.
With UIDWAIT OFF, several digipeaters would transmit at the same time, result
-
ing in corrupted packets. In actual on-the-air use, a system of digipeaters may
work well with UIDWAIT OFF, depending upon their mix of location and trans
-
mitter power.
+
In actual use, GPS/APRS reporting stations would set their path with the LTP
command.
Configuring Three Digis Using the UIDIGI Command
GPS NMEA Interfacing Capability Packet Modes of Operation
KAM’98 v 8.3 191 User’s Guide
To Next Page
Loading...