OpenBCM V1.08-5-g2f4a (Linux)

Packet Radio Mailbox

IZ3LSV

[San Dona' di P. JN]

 Login: GUEST





  
EI2GYB > PACKET   09.12.18 10:13l 140 Lines 7542 Bytes #999 (0) @ WW
BID : 2377_EI2GYB
Read: GUEST
Subj: INTRODUCTION TO PACKET - Part 11
Path: IZ3LSV<IK8VKW<IR2UBX<F1OYP<ON0AR<GB7CIP<EI2GYB
Sent: 181201/1113Z 2377@EI2GYB.DGL.IRL.EURO BPQ6.0.16

INTRODUCTION TO PACKET - Part 11 - by Larry Kenney, WB9LOZ

COMMANDS USED ON THE PACKET NODE NETWORK - continued from Part 10

ROUTES: The ROUTES command (abbreviated as R) will give you a list of the
direct routes to other nodes from the node you're using.  The direct routes
are the ones where the node can connect directly to the other node.  The
quality of each route is shown along with the obsolescence count.  (See the
NODES command in part 10 for an explanation of obsolescence count.)  Any
route marked with an exclamation point (!) means that the route values have
been entered manually by the owner of the node and it usually means that the
route is not reliable for regular use.

USERS: The USERS command (abbreviated as U) will show you the callsigns of
all the stations now using the node that you're connected to.  There are
five descriptions used by the node to describe how users are connected:
   UPLINK: The station indicated is connected directly to the node.
   DOWNLINK: The node has made a connection from the first station to the
      second station.  Example:  DOWNLINK (K9AT-15 N6UWK)  would mean that
      the node connected to N6UWK at the request of K9AT.
   CIRCUIT: Indicates that the station indicated has connected FROM another
      node when the node and user callsign are on the left of the <--> and
      indicates that the station has connected TO another node if node is on
      the right of the <-->.  If you see dashes between the arrows, the
      circuit is in use.  If you see <~~>, the connection is in progress.
      The alias and call of any other nodes being used are shown prior to
      the user's callsign.
      Examples:
           Circuit (SFW:W6PW-1 WA6DDM) <--> AA6ZV
      would mean that WA6DDM is using this node, that he connected to it
      from the SFW node and is now connected to AA6ZV.
           N6PGH <--> Circuit (DIA:WB6SDS-2 N6PGH)
      would mean that N6PGH connected direct to this node and has connected
      to the DIA node.
           Circuit (SSF2:KA6EYH-2 KK6SD) <~~> (AMCYN:WZ6X-2)
      indicates that KK6SD has connected to the node you're using from the
      SSF2 node and is now attempting to connect to the AMCYN node.
   CQ: See "CQ command" below.
   HOST: The user is connected directly from the node terminal.  This is
      seen when the owner of the node is a user, or the BBS associated with
      the node is using it to forward messages.

CQ: The CQ command is used both for calling CQ and for replying to the CQ
of another station.  The command is available only in the latest versions
of NET/ROM and TheNet.  Enter a ? when connected to a node to see if it's
available there.  The CQ command is used to transmit a short text message
from a node, and is also used to enable stations that receive the trans-
mission to connect to the station that originated it.  The command is
entered as: CQ textmessage  The "textmessage" can be any information up to
77 characters long including spaces and punctuation, and it's optional.
In response to a CQ command, the node transmits the specified textmessage
in "unproto" mode, using the callsign of the originating user as the source
and "CQ" as the destination.  As with all node transmissions, the SSID will
be translated; that is, the SSID will be 15-N, where N is the SSID of the
original callsign.  WB9LOZ-0 would become WB9LOZ-15, WB9LOZ-1 would become
WB9LOZ-14, etc.

Here is an example of how the node CQ command is used: If station W6XYZ-3
connects to a node and issues the command: "CQ Anybody around tonight?",
the node would then transmit:  "W6XYZ-12>CQ:Anybody around tonight?"  After
making the transmission in response to the CQ command, the node arms a
mechanism to permit other stations to reply to the CQ. A station wishing to
reply may do so simply by connecting to the originating callsign shown in
the CQ transmission (W6XYZ-12 in the example above).  Note here that you
connect to the station using the translated SSID.  A CQ command remains
armed to accept replies for 15 minutes, or until the originating user
issues another command or disconnects from the node.

Any station connected to a node may determine if there are any stations
awaiting a reply to a CQ by issuing a USERS command.  An armed CQ channel
appears in the USERS display as:
    (Circuit, Host, or Uplink) <~~> CQ(usercall).
The station may reply to such a pending CQ by issuing a CONNECT to the user
callsign specified in the CQ(...) portion of the USERS display--it is not
necessary for the station to disconnect from the node and reconnect.

Here's what a typical transmission would look like: (* = entered by user)
*  cmd: C W6PW-1
   cmd: *** Connected to W6PW-1
*  USERS
   {SFW:W6PW-1} NET/ROM 1.3 (669)
   Uplink(K9AT)
   Circuit(LAS:K7WS-1 W1XYZ)  <~~>  CQ(W1XYZ-15)
   Uplink(WB6QVU)             <-->  Circuit(SFBBS:W6PW-3 WB6QVU)
*  CONNECT W1XYZ-15
   {SFW:W6PW-1} Connected to W1XYZ
*  Hello!  This is George in San Francisco
   Hi George!  Thanks for answering my CQ.   etc.

Users of the CQ command are cautioned to be patient in waiting for a
response.  Remember, your CQ will remain armed for 15 minutes, and will be
visible to any user who issues a USERS command at the node during that time.
Wait a few minutes before issuing another CQ to give other stations a chance
to reply to your first one!  Don't be surprised, however, if you don't
receive a response.  For some unknown reason, I've found that very few users
take advantage of the feature.  When you connect to a distant node, the CQ
command is a great way to start a QSO with a station in that area, but more
users need to be made aware of the CQ feature before it will become very
useful.

BBS: The BBS command (which cannot be abbreviated) is available on nodes
using the G8BPQ software and having an associated packet bulletin board
system.  Entering BBS will connect you to the associated BBS.

IDENT: The IDENT command (abbreviated as I) found on NET/ROM nodes will give
you the identification of the node you're using.

INFO: The INFO command (abbreviated as I) found on TheNet nodes will give
you information about the node, usually the alias, callsign and location.

INFO: The INFO command (abbreviated as I) found on G8BPQ nodes will give
you the identification of the node and a list of the commands available.

MHEARD: The MHEARD command (abbreviated as M) found on TheNet and G8BPQ
nodes will give you a list of stations heard by the node.  If the node has
more than one port, you must specify which port you want the listing for by
entering a space after the M and then the port number.  Examples: M 1 will
give you a list for port 1 and M 2 will give you a list for port 2.  Use the
PORTS (P) command to get a list of the ports and the associated frequencies.

PARMS: The PARMS (Parameters) command (abbreviated as P) found on NET/ROM
and TheNet nodes is for the owner's use in determining how his station is
working.  It will give you a list of the node's parameters.

PORTS: The PORTS command (abbreviated as P) found on G8GPQ nodes will list
the frequencies of all ports available.

BYE: The BYE command (abbreviated as B) is available on TheNet and G8BPQ
nodes.  It's used for disconnecting from the node.  If the node has other
software, you must disconnect using the D command in your TNC.

?: Entering a ? will give you a list of the commands available on the node.

Remember, when you are connected to a network of nodes, any commands you
send will be directed to the last node you connected to.

- - - -




Read previous mail | Read next mail


 23.12.2024 11:50:26lGo back Go up