Kantronics KPC–3 Plus User Manual page 185

Hide thumbs Also See for KPC–3 Plus:
Table of Contents

Advertisement

NETBUFFS n
Default 32
The NETBUFFS command sets the number of node buffers available in the node. If the
NETBUFFS reach zero, node operation may become unstable. Changing NETBUFFS
will cause a soft reset as memory is reallocated. Each NETBUFF allocated uses 320
bytes of RAM.
NETCALL xxxxxx[-n]
default {blank}
The NETCALL is the callsign of the K-Net node and can have an optional Secondary
Station Identifier (SSID) extension of 1 to 15. The NETCALL must be entered before the
K-Net can be operational and must be different from any other callsign used in the
KPC-3 Plus.
Entering a % as the NETCALL will clear both the nodes and routes tables, but not
change any node-related parameters. Entering or changing the NETCALL will cause a
soft reset as memory is reallocated.
NETCIRCS n
default 5
This command limits the number of Network Circuits available in the node. A circuit is a
connection between two nodes. The circuit will contain an uplink (originated by a user or
server), a crosslink (the other network node), and usually a downlink (to another user or
server). The downlink will not exist until requested by the originating uplink user. The
circuit will exist until either the destination user or server or the originating user or server
disconnects. The circuit will also be discontinued if one of the nodes determines that
data can no longer be sent due to a retry time-out (L4N2), or if the inactivity timer (L4TI)
expires. Changing the NETCIRCS will cause a soft reset as memory is reallocated.
Each NETCIRC allocated uses 50 bytes of RAM.
NETDESTS n
default 25
Setting the NETDESTS determines the maximum number of destination nodes that can
be stored in the K-Net node list. This list is sent to users when the NODES command is
given to the K-Net node and also when the node does a nodes broadcast. Setting
NETDESTS to a very large number (i.e. greater than 50 or so) is generally not a good
idea since this can create long node broadcasts and long transmission times to users in
response to a NODES command. Setting NETDESTS to a very low value can result
with a desired node getting "bumped" out of the nodes table. After your K-Net has been
in operation for a while, you should be able to determine how many of the destination
(up to 6 alpha-numeric characters plus optional SSID)
185
(n = 1 - 255)
(n = 1 - 64)
(n = 1 - 255)

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents