by Charles Brabham N5PVL
This command summary was taken directly from the FlexNet docs and then "Americanized" by substituting U.S. callsigns in the examples. - N5PVL
Statements inside [ ] are optional.
-----------------------------------------------
A - display Announcement text/texts
B - display beacon-file text
C - start converse mode (255 ch)
/w - list node users
/w n - list convers users on channel n
/c - display convers channel number
/c n - switch to channel n
/s call text - send private msg to user
/q - quit converse mode
C call [v] [digi] - connect
D [*] [call] - display destination table, path to destination
F <call> - FIND-command, look for <call>
H - display HELP text
I - display INFO text
IO - In/Out - status
L - display Node Interlink information
LO - display LOCAL logon text
M [?] - connect to BBS
MH [...] - display Heard-list [selectively]
MY - display Mycall and SSID-range
P - display parameters and statistics
Q - quit, disconnect
S - SETSEARCH, display search-paths
T <call> <text> - send text to other connected user
U [*] [port/"="] - display user list [selectively]
User commands are those commands that normal users can access. The sysop has an additional set of commands, and can specify additional parameters to some normal user commands. In this documentation, <CR> represents a Carriage Return, $0D. The "=>" is the system prompt of FlexNet; where commands are entered. All input can be made in either upper or lower case. If a command not listed below is entered, the node answers with:
"invalid command".
L<A>test News
Syntax: A <CR>
The A Command shows the Announcement text made by the sysop.
<B>eacon
Syntax: B <CR>
The B Command shows the current beacon file. In this file you can see which beacon is sent on which port in which interval. After a cold reboot the default beacon is sent on port 0 or 1.
<C>onvers mode
Syntax: C <CR>
If no callsign is given, the CONNECT command puts you in convers mode. By this mode, a great number of stations can have a round table conversation There are 255 different convers channels available. After entering the C-Command, you get a list of all stations connected to the node and, if they are in convers mode too, the channel on which they are located. Now the node prompts for a number, which selects the channel you want to join.
Example:
=>C <CR>
users:
0: KC5LRY 0:KC5LLR ---: N5GGS 73: N5ITT 73: N5PPY
channel ? 73 <CR>
*** starting convers, exit: /q
In this example, KC5LRY and KC5LLR are on channel no. 0 and N5ITT and N5PPY on channel 73. N5GGS is connected to the node without being in convers mode. Having given the desired number 73, the conversation starts. All stations logged in onto the chosen channel get the message:
" <KB5IWU>: *** Logon"
While being in convers mode you have the following commands at your disposal:
"/w" shows all stations connected to the node (with convers
channel number if available)
"/c" shows the actual channel number
"/c n" switches to channel n
"/s <call> <msg>" sends private msg to <call> only
"/m <call> <msg>" sends private msg to <call> only
"/q" quits convers mode
If a station disconnects while being in convers mode or quits convers mode, all other users of the channel get the message:
"<KB5IWU>: *** Logoff".
If a user changes to another channel, the users of the left channel get the message:
"<KB5IWU>: *** switched to channel n"
If there is no channel number entered on convers start-up, convers mode is ended immediately. You are then prompted for a new command.
Syntax: C Call [via] [digi1 digi2 ... digi8] <CR>
The CONNECT command is used to connect further onwards. The node will try to connect you to the station via the path you specified. To confirm your command, you get the message "link setup...".As soon as the connection is made, you will get "*** connected to <call>" from the node. When the called station did not respond, you get "*** failure with <call>". If the called station sends a Busy (DM), the message "*** busy from <call>" is sent to you.
The link setup can be interrupted by sending a single <CR> to the node.
If you see the message "*** can`t connect twice", you have tried to establish a QSO which already exists with the same callsign fields.
With the C-Command it is also possible to change the user port, if the node has more than one. By typing "C -7" you change to the port with the SSID 7. This is acknowledged by the message "*** <call>: SSID OK".
If you connect to another station from the node onwards, and that station disconnects you, you will get reconnected to the node. To show you what happened, you get a "*** reconnected to <call>" then.
A connect request will be denied, if it causes a loop in the network.
If, for example, you are connected to KB5IWT via N5PVL, you cannot connect back to N5PVL nor to other nodes behind N5PVL. You should quit the QSO with KB5IWT then and retry after the reconnect.
Example: (user is connected to WA5ZRP)
=> C N5PVL <CR>
link setup...
*** connected to N5PVL
RMNC/FlexNet V3.3d - N5PVL - EM13OT - H for Help
=> C WA5ZRP <CR>
*** N5PVL: loop detected
=> Q <CR>
73!
*** reconnected to WA5ZRP
=>
<D>estinations
Syntax: D [call] <CR>
The DESTINATIONS command prints out the destination table maintained by the node. In this table all nodes, where the autorouter knows a way to, are shown. For every callsign there are the SSID range of the callsign and the average round trip time in 100 ms steps are shown. As an optional parameter a destination callsign may be given. The node will now try to work out the way to this node and will show it (after some seconds, depending on the (round-trip time).
Uppercase callsigns mean that the node knows the FlexNet protocol, lower case callsigns are inserted by the autorouter to reach the next FlexNet node. The characters "???" mean, that the previous digi does not know the way to the destination. This may happen, when the route to the destination is reorganized at the moment or when the destination is not reachable anymore.
The "D-Table" is usually the same on all nodes. Only when round trip times get too high, a node is not shown anymore. Only nodes that you can reach without link loops are shown by default. This reduces link load and has the advantage that you will see only the nodes that are not in your direction. By using the option "*", you will get the complete list. Another possibility is the selective display of a part of the list. By entering "D KC5" for example, you get all destinations containing "KC5" in the callsign. Both parameters may be used together. If you type "D * KC5" you will get all KC5xxx destinations, including those you cannot reach without loops.
<F>ind
Syntax: F call <CR>
With the FIND command it is possible to look for a station which is standby on this or another node. When the F-Command and the callsign are entered, the digi sends UI-frames with the POLL-bit set to this station via some neighbor nodes. Source callsign is the callsign of the OM who issued the FIND command. If the called station hears the frame, it will answer with a DM- Frame. The node analyses all frames coming back and is able to determine if this was an answer of the FIND command. If this is the case, you will get a message via which node the station was found. If the called station is already connected to the node, no special frame is sent and the user will get the message that the user is QRV on the digi.
Example:
=>F N5PPY <CR>
*** N5PPY found via N5PVL
=>
Only the node via which the called station was found is put out. It will be known to the autorouter. If the station was not found, a system prompt "=>" appears again. Since the used UI and DM frames may get lost, it is advisable to use the FIND command more than only once to be sure the user is not QRV. Due to the protocol, the SSID of the called station must be known.
<H>elp
Syntax: H <CR>
The H-Command prints out the text-file HELP. The text can be entered by the sysop only and should give short help text about using the node. After a cold reboot the text is empty.
<I>nfo
Syntax: I <CR>
The I-Command prints out the text-file INFO. This text can be entered by the sysop only and should provide information about the node (QTH, equipment, antennas and so on). After a cold reboot the text is empty.
<IO> (In/Out)
Syntax: IO <CR>
The IO-Command shows the state of the I/O-ports of the RMNC reset card. There are 16 lines in and 16 lines out. The latter may be set only by the sysop. Using this ability it is possible to remote control the node by hardware. There are no limits to the fantasy of the sysop. The data is shown binary.
Example:
=>IO<CR>
I: 0000 0000 0000 0000 O: 0000 0000 0000 0000
=>
The input lines are shown first and then those of the output. 0 means "low", 1 means "high". The meaning of the single bits needs to be documented by the sysop.
<L>inks
Syntax: L <CR>
The LINKS-Command displays the link table set up by the sysop.
Example:
=>L <CR>
KB5IWT 0-7 60/68 P1
K5OWK 0-15 (---) P2
ND5C 0-1 583 P3 @
WA5JMM 0-8 (355/399) via ND5C
N5PPY 8-11 44/67 P0 -
N5CBA P4
N5AUX 0-15 --- P5
In the first column the callsigns of the neighbor nodes are shown. Second column shows the SSID ranges of these stations (default: 0-15). In the third column you read the round trip time to the neighbor in 100 ms - steps. No number here means that the round trip time is not calculated. Three hyphens mean that the link is not available at the moment. Three hyphens within brackets mean that the link is not available but the autorouter is aware of another way to the station. If there is only one number in the column, the link partner does not know about the FlexNet protocol, or the internode QSO could not be established. When the sysop knows that the neighbor does not know the FlexNet protocol, he may set the attribute "@" to the link. Then only the link is tested, not if the partner knows the protocol. If the round trip time is surrounded by brackets, the link is so bad that it is not made known to the network. If there are two numbers, separated by a diagonal stroke, the neighbor is a FlexNet node. In this case the round trip times of both directions are shown. If these values are within brackets, the autorouter knows a better way to the destination, i.e. the direct link is not used. The 4th column shows either the port number of the link to the neighbor (on direct links) or the stations via which the neighbor is reachable. A hyphen behind the port number means that the link is not made known to the network. This may be used for temporary links or software tests for example.
"L *" shows the last 16 round trip times that have been calculated. This makes the diagnosis of problems more easy.
<LO>cal
Syntax: LO <CR>
The LO-Command shows the text-file LOCAL. This text is appended to the CTEXT for local users, but it can be displayed by the LO command separately. The text may only be entered by the sysop. After a cold reboot this text is empty.
<M>ail
Syntax: M <CR>
The MAIL-Command connects you to the nearest BBS as defined by the sysop.
This command therefore works like a "Connect" command with predefined destination. The BBS callsign can be shown with "M ?" (notice the space!)
<MH>eard
Syntax: MH [options] <CR>
The MHeard-Command by default displays the last 30 direct heard callsigns.
Optionally, a port number, a callsign (with or without SSID) or a number (16 ... 200) of entries to be listed, may be given.
"MH x" shows all entries that contain the "x" in the callsign i.e. "MH WJ"
shows the entries for K4WJS and N5PWJ but also a WJ2O callsign.
<MY>call
Syntax: MY <CR>
The mycall command gives the callsign and the SSID range of the node.
Example:
=> MY <CR>
mycall: N5PVL, SSID's: 0-7
=>
<P>arameters
Syntax: P <CR>
The PARAMETERS command puts out a list of the current parameters and some channel statistics. Additionally, the links as shown with the <L> command are displayed.
Example:
=> P <CR>
po id td qso usr tifr rifr tkby rkby qty mode links
1 -- 10 30 1 365 287 50 33 100 9600d*+ KB5IWT 0-10 6/6
2 -- 1 36 1 271 908 30 163 99 19200d*+ NZ2T 0-0 4
3 -- 1 1 1 0 0 0 0 100 9600d*+ NZ2T 6-6 10
4 -- 40 3 1 27 3 2 0 82 1200*+ WB5CQU 0-15 580/647
5 -- 1 50 1 835 377 102 55 100 19200dtr*+ WB5FRO 0-15 11/39
6 -- 1 39 1 582 546 78 42 100 38400d*+ NZ2T 10-12 1/1
7 -- 40 4 1 31 3 2 0 70 1200*+ NA5C 0-15 229/243
8 7 40 8 8 184 36 34 1 92 1200*+
The single columns mean:
po: Port number
id: Port SSID, on interlink-only ports "--"
td: TxDelay in 10 ms units
qso: number of QSOs on this port, internode QSOs are also counted
usr: number of stations heard on this port (since 3 mins)
tifr: transmitted I-frames within the last 10 mins
rifr: received I-frames within the last 10 mins
tkby: transmitted kilobytes within the last 10 mins
rkby: received kilobytes within the last 10 mins
qty: quality of the channel; this is updated every 10 mins, but not if
there was nothing to send.
mode: Baudrate on this port, additionally:
"c" KISS: CRC-Mode, HDLC: Software-DCD (depends on hardware)
"d" fullduplex
"t" external TX-Clock
"r" external RX-Clock
"z" NRZ mode
"m" DAMA master
"s" port is synchronized
"u" port is user port
"y" autosysop
"+" 8 Mhz CPU-Clock (RMNC)
"!" 12 Mhz CPU-Clock (RMNC)
"#" 16 Mhz CPU-Clock (RMNC)
links: see <L>-Command
When counting the I-frames, re-iterated frames and frames which got lost due to DISC are not counted. The kilobyte statements are only the contents of the acknowledged I-frames, re-iterations are not counted, too. Thus, this is the genuine net data rate.
<Q>uit
Syntax: Q <CR>
The QUIT-Command ends the QSO with the node. After a "73!" you get disconnected.
<S>etsearch
Syntax: S <CR>
The SETSEARCH-Command displays all digipeaters via which the FIND-Command searches for someone.
Example:
=>S<CR>
search digi's:
N5PVL
KB5IWT via N5PVL
WD5IVD via N5PVL
N5GMS via N5PVL
ND5C via N5PVL
=>
The frame generated by the FIND-Command would be sent via N5PVL, KB5IWT, N5GMS, WD5IVD and ND5C.
<T>alk
Syntax: T <call> [<text>] <CR>
With this command you can talk to other users connected to the node. There are two modes: If there is a text given behind the callsign, then this line is sent and you get back to the prompt. Thus, you have to issue a new Talk-Command for each line. By "T <call> <CR>" you get into the permanent talk mode which can be left later by using "/q". This is similar to convers mode, with the difference that it does not happen on a convers channel. All Convers-Commands are active and the current status can be displayed with "/c".
<U>sers
Syntax: U [n] <CR>
The USERS-command displays all users which have a QSO with or via the node. Additional information is provided:
Example:
=> U <CR>
1: S5 P0: N5PVL>N5ITT
6: S7 U1 P0: N5PVL>N5PPY
35: S5 P0: KC5LRY>NZ2T v N5PVL KB5IWT
2014: S5 P8: NZ2T>KC5LRY v KB5IWT N5PVL
i.e.
1. column: QSO number. The node uses this number for internal management of the QSO.
2. column: QSO state. This number shows the state of the QSO. (see appendix for explanation)
3. column: shows the number of unacknowledged frames of the QSO, if there are any.
4. column: port
5. column: calls and digipeater field
The QSOs with the node are shown first, then the ones which run via the node. Additional parameters may be specified on the "U" command line. If you enter an "i", only QSOs with the node are shown. If you enter a port number, you get all QSOs via that port. Using "U *" you get additional information about the QSOs. The parameters may be combined. For example, "U * 4" shows all QSOs on port 4 with detailed information.
Example:
=> U * <CR>
1: S5 F100 M3 P0 : N5PVL > N5ITT
6: S7 U1 F87 M7 P0 : N5PVL > N5PPY
35: S5 ! F50 M4 P0 : KC5LRY > NZ2T v N5PVL KB5IWT
2014: S5 ! F66 M7 P8 : NZ2T > KC5LRY v KB5IWT N5PVL
Additionally, the actual FRACK time "Fxxx" and the MAXFRAME "Mx" are shown for each QSO. On DAMA masters the DAMA priority is shown instead of FRACK. A "!" in front of the F-value says, that the QSO is using header- compression.