Text preview for : pk232_node_gateway.pdf part of aea pk232 Command additions for NODE software in the pk232.
Back to : pk232_node_gateway.pdf | Home
PK-232MBX Node/Gateway Option Supplement
1
PK-232MBX
Node/Gateway Option Supplement
Thank you for your purchase of Timewave's node firmware option for the PK232MBX! Please read the enclosed sheet, PK-232MBX EPROM Installation Instruction, for instructions on how to install your new firmware.
New feature outline:
· Timewave packet "node" helps eliminate the need for digipeating. · Enhanced AMTOR- and PACTOR-listen modes show link and connect attempts. · Automatic selection of AMTOR or PACTOR modes when a received signal is tuned with the ARXTOR command. · Enhanced packet MHEARD function identifies TCP/IP, NET/ROM and stations. · MYALIAS has been expanded to enable the "two-ham family" to use more than one packet callsign with their PK-232MBX. · PACTOR "roundtable" operation has been enhanced with the PTROUND command. · EXPERT command now included so you're no longer burdened with a large number of commands to view. · MOPTT command simplifies full break-in CW operation. · The CODE command has been expanded to include the upper/lower case extensions used by AMTOR MSO and APLINK stations. · The SIAM (Signal) mode now identifies PACTOR stations.
Copyright 2001, Timewave Technology Inc., all rights reserved
2
PK-232MBX Node/Gateway Option Supplement
This page intentionally left blank
PK-232MBX Node/Gateway Option Supplement
3
Overview
Your node firmware now supports local acknowledgment (acks) of packets like a full-service BBS/node does, so instead of having to digipeat through your MYALIAS or MYCALL callsign to connect to a destination station, users can now connect to your MYGATE callsign; from there, they can then issue a connect request to the station they want to reach, and your station will be responsible for accepting and sending packet data and acks. (Users can't digipeat through your MYGATE callsign.) Users can also enter the MHEARD command to see the last 18 stations your TNC has heard. For your node to work, simply enter a call into MYGATE--but not the same one as your MYCALL, MYALIAS, or MYMAIL--and set GUSERS to a value greater than zero. To disable the node function, enter MYGATE NONE or set GUSERS to zero. Note: With each station connected to your node, you'll lose a "logical" channel. So, if you have GUSERS set to 3 and three source stations have connected to three destination stations through your node, they'll take up six of your ten channels, leaving you with only four channels to accept and initiate contacts. (If a station connects to your Maildrop that would leave you only three channels.) See the following pages for information about the new commands available to you and improvements over current ones.
Node Operation
Here's what a user would see when using your Node as a packet node. In this example, your MYGATE call is set to N7ML-7:
cmd:C N7ML-7 *** CONNECTED to N7ML-7 +++ N7ML Node. Type ? for help. de N7ML-7 (B,C,D,J,L,N,S,?) >
The first line is the user's connect request to your TNC. The second line is the connect message from the user's TNC. The third line is the greeting, and the fourth is the command prompt from the Node. The user sends a question mark, ?, to obtain the following help menu:
B(ye) Log off node C(onnect) n Connect to station 'n' C n STAY Stay connected to node when 'n' disconnects D(isconnect) Cancel a connect attempt J(heard) Display stations heard L(isten) Toggle monitoring N(odes) Display nodes heard S(end) Broadcast unproto de N7ML-7 (B,C,D,J,L,N,S,?) >
4
PK-232MBX Node/Gateway Option Supplement
The commands' functions are: B(ye) C(onnect) n This is similar to the Bye command used in the Timewave Maildrop and BBS stations. When a user enters a B, the Node will "disconnect." Similar in operation to the CONNECT command in the packet mode. For a packet connection, the user may connect to your Node, then specify a string of digipeaters: C W1AW VIA W2XY, W1XXZ Your Node will try to establish a connection with W1AW as the destination; the user's callsign will be shown as the source but with a difference: the user's SSID is decremented by one to avoid protocol conflicts on the same frequency. Here is an example of the frames sent in establishing a typical connection (with the MONITOR command set to 5):
USER>GATE [C] GATE>USER (UA) GATE>USER [I]: +++ N7ML Node. Type ? for help. de GATE (B,C,D,J,L,N,S,?) > USER>GATE (RR) USER>GATE [I]: c remote GATE>USER (RR) USER-15>REMOTE REMOTE>USER-15 GATE>USER [I]: +++ CONNECTED to REMOTE at GATE USER>GATE (RR) USER>GATE [I]: hello. GATE>USER (RR) USER-15>REMOTE hello. REMOTE>USER-15 REMOTE>USER-15 Yes? GATE>USER [I]: USER-15>REMOTE Yes? USER>GATE (RR)
[C] (UA)
[I]: (RR) [I]: (RR)
Once the connection is established with the destination station, the Node notifies the user that the connection has been made then goes from the "Command" mode into the "Converse" mode. Now, whatever the user sends goes to the destination station as data, instead of to the Node as a command.
PK-232MBX Node/Gateway Option Supplement
5
Normally, when someone disconnects from your Node, no link will remain. However, if a user adds the word STAY as the last argument in a Connect request, (e.g., C callsign STAY), the user will remain connected to your Node even after disconnecting from the destination station. If the connect attempt to the destination station retries out or is busy, your Node sends the user a Retry count exceeded or (Remote) busy message, but remains connected to the user even if STAY wasn't entered. D(isconnect) (To cancel a connect attempt.) Since the source station remains in the Command mode until the connection to the destination station is established, there's no need for the user to wait for your Node to cycle through a full number of retries to attempt a connection--the user can send your Node a Disconnect request which in turn cancels the Connect request the same way it would in a TNC's Command mode. (The user stays connected to your Node even if STAY wasn't used in the original Connect command.) The Disconnect command may be used at any time before the connection is established, regardless of any preceding commands. Once a connection is established and your Node is in the Converse mode, the user can end the connection either by sending a B(ye) command to the destination station if that station supports it, or by issuing a Disconnect request to the user's own TNC. If the user disconnects from your Node this way, it'll force your Node to disconnect the destination station. J(heard) L(isten) N(odes) Your node sends its MHEARD list to the user: A maximum of eighteen stations are kept in the JHEARD list. The node toggles packet monitoring on or off. Your Node sends the user a list of nodes heard. The format is the same as that of the JHEARD command, the difference being that a callsign is put in the Nodes list only if the monitored packet was a UI frame with a PID of CF (NET/ROM) or CD (IP). A maximum of ten stations are kept in the Nodes list. You clear the nodes list and the MHEARD list simultaneously with the same command, MHEARD %. Your Node responds with. . .
+++ Sending. To end, type '='.
S(end)
. . . and sends all subsequent data in the broadcast mode (unproto). The data characters are held until the user sends a (RETURN), whereupon the held data is broadcast.
6
PK-232MBX Node/Gateway Option Supplement
In all operating modes, the user can stop sending "unproto" by sending the "=" character. The Node will then issue a command prompt. The "=" character shouldn't be used within the user's broadcast text.
PACTOR & AMTOR operation with ARXTOR
The ARXTOR command has been added to enhance PACTOR operation. When ARXTOR is turned ON, your PK-232MBX will recognize either PACTOR or AMTOR link attempts. In addition, when monitoring PACTOR stations with PTLIST, AMTOR stations will also be heard if ARXTOR is ON. ARXTOR is also useful for those running the PACTOR or AMTOR Maildrop. When ARXTOR is ON, remote stations can connect to your maildrop in either PACTOR or AMTOR. See the ARXTOR command description later in this supplement for the full details.
PK-232MBX Node/Gateway Option Supplement
7
AList Mode: AMTOR
Immediate Command Host: AL
In AMTOR Listen (and PACTOR Listen) modes, monitored link attempts are now displayed like this: >W1AW The callsigns are shown one per line and are meant to resemble the way the TNC monitors packet connect frames. Since neither mode supports identification within the calling blocks, no source callsign can be shown.
ARXTor ON|OFF Mode: AMTOR and PACTOR Parameters: ON
Default: OFF Host: Ar
Enables automatic detection and switching between AMTOR and PACTOR modes. Disables the automatic detection of non-selected operating modes.
OFF
The ARXTOR command allows the automatic switching from PACTOR Listen mode to AMTOR FEC receive, and from PACTOR Standby to AMTOR ARQ. It also allows the automatic switching from AMTOR Listen to AMTOR FEC receive. With ARXTOR ON, an AMTOR FEC signal is detected by ALIST and PTLIST modes as well as AMTOR Standby mode. There are two methods of FEC mode recognition. AMTOR Standby, ALIST and PTLIST all use FEC idles to recognize FEC transmissions. However, in the AMTOR Standby mode, FEC text patterns are recognized as an additional quick recognition method which may speed locking onto a FEC signal. ARXTOR ON enables PTLIST mode to monitor AMTOR ARQ transmissions. ARXTOR ON also means an incoming AMTOR ARQ call is recognized in PACTOR Standby mode. Only a call for the selcall in MYSELCAL is recognized; PACTOR cannot detect ARQ calls to MYALTCAL or MYIDENT. When a PACTOR mode detects an AMTOR transmission, there is an added delay before the text is shown. Your TNC must switch from PACTOR to AMTOR, where the signal is again detected. For fastest detection of AMTOR FEC, your TNC should be in the AMTOR Standby mode. For fastest syncing on AMTOR ARQ signals, the TNC should be in ALIST mode. At the end of the new mode (AMTOR ARQ or FEC), your TNC returns to the original monitoring mode (AMTOR, ALIST, PACTOR or PTLIST).
8
PK-232MBX Node/Gateway Option Supplement
ARXTOR is defaulted OFF to accommodate old application programs that have no provision for handling a spontaneous change of modes from PACTOR to AMTOR. Here is a summary of the AMTOR/PACTOR mode switching:
Original operating mode Target mode detection AMTOR FEC AMTOR ARQ (MYSELCAL) AMTOR ARQ (MYALTCAL) AMTOR ARQ (MYIDENT) monitor AMTOR ARQ SELFECalways monitor SELFEC PTCONN monitor PACTOR AMTOR if RFEC always always always if ARXT if SRXALL ALIST if ARXT if ARXT PACTOR PTLIST if ARXT
always if ARXT if ARXT & SRX always
if ARXT if ARXT & SRX always always
ATxrtty "n" Mode: Morse, Baudot and ASCII Parameters:
Default: 0 Host: At
"n" 0 to 250, signifying the length of time (in units of 100 msec.) to delay before sending text.
ATXRTTY allows Morse, Baudot or ASCII characters to be transmitted automatically whenever they're typed and the TNC is in the Converse mode. When all the characters in the buffer have been sent, the unit reverts to receive. The number n represents the length of time from the last character typed to the dropping of PTT. This feature makes the repeated use of the commands RCVE and XMIT unnecessary.
CODe "n" Mode: Baudot RTTY, Morse, AMTOR, PACTOR and packet Parameters: "n" CODE 7 8 0 to 8 specifies a code from the list below. Meaning TOR Lower Case Extended Lower Case Morse -- -- Baudot -- --
Default: 0 (International) Host: C1
AMTOR RX/TX RX/TX
Packet -- --
PK-232MBX Node/Gateway Option Supplement
9
Two new settings of the CODE command have been added to support the European and APLINK implementations of upper/lower case AMTOR. CODE 7: TOR lowercase CODE 7 applies to AMTOR operation only. It codes upper and lowercase letters using the NULL character as a shift while in LTRS case. This protocol is used by APLINK stations, European mailboxes, the AMT-3 and G4BMK software. The difference between CODE 7 and CODE 2 (Cyrillic) upper/lower case is that CODE 2 uses LTRS for upper case and NULL for lowercase, while CODE 7 uses the NULL to toggle between upper and lowercase. CODE 7 is invisible to stations using classic AMTOR (CODE 0). However, a CODE 7 station talking to a station using CODE 2 (AEA's already existing upper/lower case protocol) will result in upper/lowercase reversals or constant lower case text. CODE 8: Extended TOR lowercase CODE 8 also applies to AMTOR only. It includes the features of CODE 7 above, and additionally codes new punctuation characters using NULL as an escape while in FIGS case. Thus CODE 8 supports all 95 printable ASCII characters ($20-7E) plus CR, LF, space and ENQ while in AMTOR operating mode, but not BELL, backspace and TAB. At the moment, this protocol is used only on links between mailboxes forwarding messages. It could be used with the Timewave AMTOR-to-Packet Node if all users had CODE 8. CODE 8 isn't invisible to other users.
DAytime date and time Mode: All Parameters: date and time - Current date and time to set.
Default: none Host: DA
DAYTIME sets the data controllers real time date and time clock. Optionally, the following types of Dallas Semiconductor "Smart Watch" chips may be used to hold the date and time when power is turned off. RAM--Use the DS1216C in U5 (RAM). EPROM--Use the DS1216E in U3. Setting the DAYTIME command will set the time of day into any SmartWatch present in the system. The SmartWatch is read is only power-up, RESTART or RESET.
10
PK-232MBX Node/Gateway Option Supplement
EXPert ON|OFF Mode: All Parameters: OFF ON
Default: OFF Host: EX
Disables some of the less frequently used data controller commands in verbose mode. Enables all data controller commands in verbose mode.
The EXPERT command controls your access to the TNC's command set. Because some new TNC owners understandably find the large number of available commands confusing or daunting, this command limits the newcomer's access of the commands to the simplest or most often used. Generally, about half of the total number of commands are available to you after a RESET (EXPERT OFF). If EXPERT is OFF, expert-level commands may not be accessed and don't appear in any output of the DISPLAY command. An attempt to use one of these commands will result in the error message "?EXPERT command." All immediate commands (e.g. CONNECT, PACKET) are "Novice" commands. The error message for an Expert command is now separate from the unknown command message: cmd:FRICK ?EXPERT command
In Host mode, all commands are available regardless of the setting of EXPERT. This command will not affect operation of Timewave PAKRATT programs. The following DISPLAY lists denote when a command is available while EXPERT is OFF ("Novice"); "Retain" means the command keeps its setting during a REINIT operation. cmd: DISPLAY A 8Bitconv Novice ACRDisp AFilter ALFDisp AUTOBaud AWlen Novice BBSmsgs CASedisp DCdconn Echo EScape Flow ILfpack NUCr NULf NULLs PARity TBaud TRFlow TXFlow XFlow
Retain
Retain
Novice Novice
Retain Retain
cmd: DISPLAY B
PK-232MBX Node/Gateway Option Supplement
11
3Rdparty FREe KILONFWD LAstmsg MAildrop MDMon MDPrompt MMsg MTExt MYMail TMail TMPrompt
Novice
Novice Novice Novice Novice Novice Novice Novice Novice
Retain Retain Retain Retain Retain Retain Retain Retain Retain Retain Retain Retain
cmd: DISPLAY C BKondel CANline CANPac CHCall CHDouble CHSwitch Novice COMmand CWid DELete ERrchar HEReis PASs PTOver Novice RECeive REDispla SEndpac STArt STOp TIme XOff XON cmd: DISPLAY F ASPect Novice FAXNeg FSpeed Novice GRaphics Novice LEftrite PRCon Novice PRFax PROut PRType Novice
cmd: DISPLAY I Unproto Novice AAb Novice Beacon BText CBell CMSg Novice CText Novice HId Novice HOMebbs MId Novice MYAlias MYALTcal MYcall Novice MYGate Novice MYIdent Novice MYPTcall Novice MYSelcal Novice WRu cmd: DISPLAY L ACRPack ALFPack Ax25l2v2 CFrom CONMode CONPerm DFrom FUlldup GUsers Novice HBaud Novice LIte MAXframe Novice NEwmode NOmode PACLen Novice PASSAll RAdio Novice RELink REtry Novice SQuelch TRIes Novice USers Novice Vhf Novice XMITOk Novice
Retain Retain Retain Retain Retain Retain Retain Retain Retain Retain Retain Retain Retain
Retain Retain Retain
Retain
Retain
12
PK-232MBX Node/Gateway Option Supplement
cmd: DISPLAY M CONStamp Novice DAYStamp Novice HEAderln MBEll MBx MCon Novice MDigi Novice MFIlter Novice MFrom Monitor Novice MProto MRpt MStamp Novice MTo MXmit TRACe WHYnot Novice cmd: DISPLAY R ABaud Novice ACRRtty ADelay Novice ALFRtty ANSample Novice ARQTmo ARQTOL ARXTor Novice ATxrtty BItinv CODe CRAdd DIDdle Novice EAS Novice MARsdisp MOPtt Novice MSPeed Novice MWeight NAVMsg NAVStn PT200 Novice PTHuff Novice PTRound Novice RBaud Novice RFec RFRame RXRev Novice
Retain
SRXall TDBaud TDChan TXRev USOs WIdeshft WOrdout XBaud
Novice Novice Novice Novice
Retain
Retain
cmd: DISPLAY T ACKprior AUdelay AXDelay AXHang CHeck CMdtime CPactime DWait FRack Novice FRIck PACTime PErsist Novice PPersist RESptime SLottime Novice TXdelay Novice Commands not displayed: ADDress ALTModem CCitt EXPert Novice Retain HOST Novice Retain HPoll Novice JUstify Novice KIss Novice Retain KISSAddr RAWhdlc UBit UCmd ZFree ZStatus
Retain Retain
PK-232MBX Node/Gateway Option Supplement
13
GUsers "n" Mode: Packet, AMTOR, PACTOR Parameters: "n"
Default: 0 Host: GU
0 to 3 specifies the maximum number of users allowed to use your node.
GUSERS allows up to "n" number of stations to connect to the callsign in your MYGATE call. The variable "n" may be 0-3, with zero meaning no station can use your node. Alternatively, n can be thought of as the maximum number of pairs of stations which may be connected through your Node. Your must have your MYGATE call entered and GUSERS set to a number greater than 0 to enable the node.
MHeard Mode: Packet and AMTOR/PACTOR Maildrop
Immediate Command Host: MH
The MHEARD display has been enhanced to support the "Nodes" command in the node. Previously, stations heard directly were displayed with an asterisk ("W1AW*") and digipeated stations were shown without ("W2SZ"). Digipeating isn't used as much as it used to be. Most stations now use nodes so this release discards the asterisk. However, for those few cases in which a station is heard indirectly through a digipeater, the station's callsign is displayed with the message, "via digi". In addition, I- and U-frame packets with PIDs of CF and CD are shown with the indicators "N/R" (for Net/ROM) and "IP" respectively. AMTOR and PACTOR stations accessing the Maildrop or the node are shown in the MHEARD list with an "AMTOR" or "PACTOR" indicator.
MId "n" Mode: Packet, AMTOR, PACTOR Parameters: "n"
Default: 0 (0 sec.) Host: Mi
0 to 250 specifies the Morse ID timing in units of 10-second intervals.
Morse ID now works in AMTOR and PACTOR modes on both ARQ and broadcast transmissions. At intervals you set, your TNC identifies itself in Morse Code while maintaining the internal timing for AMTOR or PACTOR. Because of the nature of these operating modes, the destination station will go into an error state when your TNC sends a Morse ID, but it should recover data synchronization immediately afterwards.
14
PK-232MBX Node/Gateway Option Supplement
MOPtt ON|OFF Mode: Morse Parameters: ON OFF Enables PTT in Morse transmit mode. Disables PTT in Morse transmit mode.
Default: ON Host: Mo
MOPTT controls the PTT output in Morse mode only. To enable PTT for Morse transmissions, both XMITOK and MOPTT must be ON. XMITOK OFF still disables PTT for all operating modes. The most probable use of MOPTT is to disable PTT in Morse to allow full breakin operation but enable PTT in all the other modes. Setting XMITOK ON and MOPTT OFF accomplishes this. MOPTT doesn't affect the Morse IDs generated by the MID command (in Packet mode) and by the CWID character (in other digital operating modes). The ATXRTTY command may also be helpful.
MYAlias call[-n] Mode: Packet Parameters: call "n"
Default: none Host: MA
Alternate packet callsign may be used by other stations to connect to your station. 0 to 15, an optional substation ID (SSID)
For those households with two operators taking turns using the PK-232MBX, the TNC will now accept connections to both MYCALL and MYALIAS. Previously, MYALIAS had been reserved for stations digipeating through your station. If MYMAIL isn't set, the Maildrop also accepts connections to either MYCALL or MYALIAS. Outgoing connect attempts and Unproto frames use only MYCALL as the source callsign.
MYGate call[-n] Mode: Packet Parameters: call "n" Node callsign used by other stations. 0 to 15, an optional substation ID (SSID)
Default: none Host: MY
PK-232MBX Node/Gateway Option Supplement
15
"Call" is the callsign of the Node function of your TNC. Stations can connect to your MYGATE call, then issue a connect request from there. This way, your station takes responsibility for acknowledgements of the user's packets.
OVer Mode: AMTOR/PACTOR
Immediate Command Host: OV
An immediate command that reverses the link direction from ISS to IRS; this can be considered the opposite of the function of the ACHG command. The changeover happens as soon as possible--the TNC doesn't wait for all the characters in the buffer to be sent. OVER should be thought of as analogous to the RCVE command (neither command waits for the buffer to empty) the same way the PTOVER character is analogous to the RECEIVE character (both wait for empty). Host applications can use the ZSTATUS command to detect when all characters have been sent. In PTCONN, this command accomplishes the same thing as sending the PTOVER character. The OVER command is useful in Host mode when sending transparent data (CONMODE TRANS). To change from ISS to IRS, you'd normally send the PTOVER character, but in Transparent mode, the character would be sent as data and would not change the link direction. The OVER command changes the direction without the need to change CONMODE to CONV first. In AMTOR ARQ, this command inserts "+?" into the data stream being sent. If EAS is ON, the "+?" is echoed to the terminal.
PTList Mode: PACTOR Parameters:
Immediate Command Host: PN
In PACTOR Listen (and AMTOR Listen) modes, monitored connect attempts are now displayed like this: >W1AW The callsigns are shown one per line and are meant to resemble the way the TNC monitors connect frames in the packet mode. Since neither mode supports identification within the calling blocks, no source callsign can be shown.
16
PK-232MBX Node/Gateway Option Supplement
PTRound ON|OFF Mode: PACTOR Parameters: OFF ON
Default: OFF Host: Pr
Returns the TNC to the PACTOR-Standby mode after a PTSEND transmission. Returns the TNC to the PACTOR-Listen mode after a PTSEND transmission.
PTROUND facilitates PACTOR "roundtable" conversations with multiple stations using the PTSEND (FEC) mode as opposed to the Connected mode. As the unit finishes sending a PTSEND transmission it normally returns to PACTOR Standby mode. If PTROUND is ON, the unit returns to PTLIST instead in order to copy another station's PACTOR transmission. PTROUND has no effect when a PACTOR connection ends--the unit will always return to PACTOR Standby.
REINIT Mode: All Parameters:
Immediate Command Host: RI
This is an immediate command that you can invoke to get out of trouble caused by setting a lot of commands--especially timing parameters--to strange values. REINIT can be thought of as being halfway between RESTART and RESET. REINIT re-initializes most of the commands to their default settings, then does a RESTART, but the contents of the Maildrop and the NAVTEX message history buffers are preserved. The commands that are preserved are: MYCALL MYALTCAL TBAUD CFROM MTEXT FREE CBELL KISS MYALIAS MYIDENT BTEXT DFROM NAVSTN KILONFWD CONPERM MYMAIL MYPTCALL CTEXT MFROM NAVMSG MAILDROP HBAUD HOMEBBS UNPROTO AAB MTO HOST NDMON TRIES MYGATE AWLEN MDPROMPT MBX 8BIT CONV MMSG MVIA MYSELCAL PARITY TMPROMPT LASTMSG 3RDPARTY TMAIL EXPERT
In Host mode, the REINIT command is acknowledged by a RESTART response (RT).
SIgnal Mode: All
Immediate Command Host: SI
SIGNAL is an immediate command that causes the PK-232 to enter the Signal Identification and Acquisition Mode (SIAM). The Signal Identification mode now identifies PACTOR stations.
PK-232MBX Node/Gateway Option Supplement
17
WOrdout ON|OFF Mode: Baudot, ASCII, AMTOR PACTOR and Morse Parameters: OFF ON
Default: OFF Host: WO
Typed characters are sent directly to the transmitter. Type characters are held in the PK-232MBX's transmit buffer until a space, CR, LF, TAB, RECEIVE CWID, ENQ or `+?' character(s) is typed.
With WORDOUT OFF, the backspace character is transmitted in Baudot, ASCII, AMTOR and PACTOR modes. With WORDOUT ON, pressing the backspace key cancels out the preceding character and neither are transmitted. In Baudot and AMTOR, the backspace character is transmitted as a "?" since there's no backspace in those modes. In ASCII the backspace character is transmitted, but the destination station must be able to pass it. Timewave products should have MFILTER set to zero to allow backspaces to print when monitoring.
18
PK-232MBX Node/Gateway Option Supplement
This page intentionally left blank.