ever, if UIDWAIT is set ON, the packets awaiting to be digipeated will be sub
-
ject to the same wait times as not-to-be-digipeated packets awaiting transmission.
+
By subjecting “special” to-be-digipeated packets to a delay determined by
slottime and persist, it is more likely that to-be-digipeated packets of two or more
stations in the same vicinity would not collide. This may be good if one wants to
guarantee that a digipeated packet will “make it out” of its neighborhood but bad
if one wishes to limit the number of times a packet is redigipeated, such as in
APRS applications.
See also: dwait, persist, uidwait
UIFLOOD name, n,[ID|NOID] (name = 5 char max)(n=0-255)
default disabled,30,NOID
When a UI frame is received with a call in the to-be-digipeated field of the form
‘name’x-y where x is a number (1-7) appended to ‘name’ and y is a ssid (1-7),
the ssid is decrement and the UI frame is digipeated without setting the H bit.
When the packet is digipeated, a checksum is formed over the source, destina-
tion, and data fields of the packet. This checksum is kept for n seconds (0-255). If
an incoming UI packet is eligible for digipeating as above, but its checksum
matches one of those being saved, the packet is discarded (not digipeated). The
buffer holds a maximum of 64 checksums. If the optional parameter ID is se
-
lected, the MYCALL call sign is inserted in an additional digipeater address field
with its H bit set.
See also: uidwait
UITRACE name, n
default disabled, 30
When a UI frame is received with a call in the to-be-digipeated field of the form
‘name’x-y where x is a number (1-7) appended to ‘name’ and y is a ssid (1-7),
and MYCALL does not appear in the source field or any of the
has-been-digipeated fields, MYCALL with the H bit set is inserted before the
KAM’98 Commands Command Reference
KAM’98 v 8.3 317 User’s Guide
To Next Page