home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
HAM Radio 3
/
hamradioversion3.0examsandprograms1992.iso
/
packet
/
tn116
/
tn1160.doc
< prev
Wrap
Text File
|
1991-02-14
|
14KB
|
347 lines
Here is the file TN116.DOC:
Hello sysops,
Version 1.16 is a forerunner of version 1.2, which will be little changed
from this version. It has been pointed out to me that in versions 1.0 and
1.1, it is possible for a user, by means of "bombardment" of the nodes with
many commands at one time (for example, sending a file that contained the
NODES-command 50 times), to send the node into reset for lack of free
buffer. That is corrected in ver 1.16. With free buffer less than 300 the
access to the command interpreter is simply blocked. That is, of the 50
commands none would be executed until there is again free buffer space.
Due to lack of storage space in EPROM the Host-Interface has been omitted.
The RS-232 connector is for connection to another TNC and not a terminal, as
in earlier versions. Since all the parameters can be accessed remotely, the
Host-Interface is no longer necessary.
Password is now copied into RAM with a block-move (LDIR). Because of that
the order of parameters in the EPROM has been changed.
See PARMS.DOC
!!!The password in EPROM must have 80 characters!!! In return, the 0-
terminator is left off. Whoever wants a shorter password can fill the rest
with spaces. The info-text in the EPROM is omitted from its usual place;
in return, however, the INFO-command becomes somewhat expanded (see below).
The list of remotely switched parameters has been expanded from 26 to 30.
The parameters 'fullduplex', 'pausenflags' and 'TXDelay' are now also
remotely switchable. In addition a bit-transparent 16-bit-systemflag is
added. (Variable name 'Flags') (Parameter 30)
The changes of version 1.16 compared to 1.01 follow:
Each and every parameter with the exception of Call and Password are
remotely switchable. It is possible to define 2 different ID's at one time
for the HDLC (RF)-port and for the RS232-port. Also these ID's are remotely
changeable.
Since some new options are provided over whose meaning and purpose one could
argue, most of them are also made remotely switchable. In order to not get
an additional flood of parameters, these software switches are summarized
bit transparent in the new Parameter 30.
See the file PARM30.DOC!
New Commands:
----------------------------------------------------------------
Command INFO (I):
=================
The default info text is dropped from the EPROM. In its place an
info text with a variable number of characters can be entered
remotely under sysop control. This text is limited to 250
characters including CR LF. The info text is enter line by line.
Example:
I line 1
I line 2
etc.
Additional I lines will be appended. Should one want to enter a completely
new info text, the CLINFO-command is used to clear out the old text. (see
below)
If an empty line is to be inserted the character '@' is used.
Example:
I @ (gives a blank line)
----------------------------------------------------------------
Command CTEXT (CT):
===================
Analogous to info text, connect text of 250 characters can be entered
remotely under sysop control, except the command here is called 'CT' rather
than 'I'.
Example:
CT line 1
CT line 2
etc.
also 'CT @' etc. is usable. Cancel with the CLINFO command.
A file might be prepared with both the CText and InfoText and transmitted to
the node to upload both texts.
Attention sysops (in Europe)!
The connect text can result in problems with users of DIGICOM. This can be
avoided however, by ending EACH text line with a '>'. To be certain, this is
not very attractive but it does make the DIGICOM user happy. With SP up to
4.0, with YAPP and with TurboPacket there are no problems.
----------------------------------------------------------------
Command CLINFO (CL):
====================
Under sysop control:
CL 0 cancel connect text
CL 1 cancel info text
----------------------------------------------------------------
Command FLAG (F):
=================
Here we find the system flags of the newly introduced Parameters 30.
Without sysop authorization the system flags of Parameter 30 are displayed.
Under sysop control, these flags can be set.
Example:
F 5 1 sets Parameter 30 bit 5 to 1.
F 12 0 sets Parameter 30 bit 12 to 0.
For the meaning of the various flags see PARM30.DOC.
-----------------------------------------------------------------
Command TEST (T):
=================
This command is similar to the CALIBRATE command of TAPR-Soft. The node
radiates a signal which at 1200 baud corresponds to a key ratio of 1:1. It
keys high-low tones alternately. Normally this occurs under sysop control.
However, in Parameter 30 if the bit 0 were set on 1 ('F 0 1'), each user
could call up this routine. The thought is that in some cases, for example, a
user could request the sysop to permit it for testing purposes. The
duration of this routine is be entered with the command, for example:
'T 50' the test signal would be radiated for 50 seconds.
By the execution of this TEST-command the SIO of the TNC is completely
reprogrammed. In order to avoid problems the internal timer (interrupts) of
the TNC are switched off during the running of this routine. The TNC
operates during this time in a timing loop and for other activities is dead.
Therefore, the time duration would also be limited to 2 minutes ('T 120').
Please take note also that the watchdog is done with the control time. The
time is for a TNC with a crystal frequency of 4.9152 MHz.
----------------------------------------------------------------
Command Y (Y):
==============
Normally the maximum number of connects to a node is 25. If this number is
exceeded, the user receives a 'Node Busy'. If in certain situations it
seems a restriction of the maximum permissible connects should be offered,
the maximum can be set here with the Y-command. (naturally under sysop
control).
Example:
'Y 10" sets the max. possible connects to 10.
Attention: It can only be set lower, but never above 25.
----------------------------------------------------------------
Command ID (ID):
================
With this both ID's of the node can be changed.
Example:
'ID HUGO #OTTO' sets the ID on the HDLC (RF)-port to HUGO and
the ID on the RS232-port to #OTTO.
Normally both ID's are the same. In that case the ID would appear also in
the prompt before the double period. If the ID's were different, no ID
would appear in the prompt. Meaning and purpose are illustrated by an
example: The node DB0XYZ stands on the border between DL and F (the
countries and callsign are arbitrarily chosen). Now the nodes near the
border in DL have a quantity of F-callsigns in the node list and the nodes
near the border in F each a quantity of DL-callsigns. This can lead to
disarrangement relatively quickly. Therefore sysop Waldheini, the caretaker
of DB0XYZ, decides to introduce 2 ID's. In the direction of F the node is
called DLLINK:DB0XYZ and in the direction of DL it is called FLINK:DB0XYZ.
Furthermore in each direction the passing on of the corresponding nodes in
the nodes list would be spread by means of Parameter 30 bit 4,5,6 and 7 (see
PARM30.DOC).
Also, if more nodes link to the same box, whose ID's thereafter, for example
XXXBOX would be listed by all nodes, 2 ID's are very useful.
----------------------------------------------------------------
Command QUIT (Q):
=================
Generally accessible command. Causes the node to disconnect for its part at
that time. In connection with RECONNECT (see PARM30.DOC) its meaning and
purpose are here illustrated:
OM Waldheini has connected with considerable effort step by step through
from Munich to Kiel to DB0IL. From there he has connected to DB0IL-1 and
the BBS DB0OQ, then abandoned it with the command 'QUIT'. If DB0IL were now
reconnectable (version 1.16) OM Waldheini would again end up on DB0IL and
could connect from there to other OM's in Kiel without having to renew, with
great effort, the connection from Munich to Kiel. In that DB0IL does not
have at this time version 1.16, OM Waldheini would end up on the next
reconnectable node, WHICH HE HAD CONNECTED TO MANUALLY, in this case for
example DB0HHW (Hamburg-west). If he wanted now to go back further, for
example to Verden, he would enter a 'QUIT' to DB0HHW and end up on the
Verden node (always assuming that he had connected to Verden manually).
This idea originated from DB2OS and DL8ZAW and has been installed
into TheNetNode.
----------------------------------------------------------------
Command LED (L):
================
The routine for remote control of the CON LED and the STA LED was
removed from its customary location. (111 Bytes saved...).
The new command is called:
'LED 0': Both LED's off.
'LED 1': STA LED on, CON LED off.
'LED 2': CON LED on, STA LED off.
'LED 3': Both LED's on.
The current supplied to light the LED may be used to actuate external relays
---------------------------------------------------------------
Command NODES expanded:
=======================
The command 'N callsign' would bring up, in the case of a callsign not in
the list, not the entire list but rather the announcement 'no entry for:
callsign'.
------------------------------------------
Here is the file PARM30.DOC
Parameter 30 (16 bit) is bit-transparent, that is each bit is a
particular flag.
Bit 0 (Value 1): TEST-diddle available
The command TEST generally available (without
sysop) For details see TN116.DOC.
Bit 1 (Value 2): Downlink blocked
The node can indeed be connected to, however
a level 2 connect for a user from there on
out is not possible. (significant with a
clean interlink-node).
Bit 2 (Value 4): Uplink blocked
The node can indeed be connected by way of
level 2, any other command with the exception
of the sysop's leads to a disconnect. (should
prevent a user entering on an interlink,
similar to version 1.1-i from DF3AV.
Bit 3 (Value 8): Connect by means of ID not possible.
Anyone who is of the opinion that the ID is
not an official callsign although it appears
in the address field and so the user should
be permitted to enter a node only with the
call and not with the ID, should set this
flag on 1.
Bit 4 (Value 16): Broadcast on the HDLC-port completely shut off.
Significant for the entered node. Then in
general no node list would be sent on the
RF-port (also not the particular node
callsign!). Users of simple terminal programs
will be thankful that no control characters
mess up the screen or completely wipe it out.
Bit 5 (Value 32): Broadcast on the RS232-port completely shut
down. As with bit 4, so again on the
RS232-port. Can be useful, in order to
separate a net immediately and to permit
manual entry of only certain connections.
See also TN116.DOC under 'Command ID'.
Bit 6 (Value 64): Broadcast on the HDLC-port shut down with
the exception of the passing on of certain
node-calls.
Bit 7 (Value 128): Broadcast on the RS232-port shut down with
the exception of certain node-calls.
Bits 6 and 7 set together have the same
effect as parameter 6 > parameter 5. Only
it is now possible to separate each port.
Bit 8 (Value 256): User prompt enable
User prompt on as with TheNetNode. In that
some terminal programs have had trouble with
older versions, it is made switchable.
Bit 9 (Value 512): Start prompt disable
The prompt at the beginning of a node
announcement (for example INFO) can appear
not good visually. Now it can be shut down,
except for a few cases, where certain
terminal programs have an allergic reaction.
(for example PAR on a terminal program with
parameter values)
Bit 10 (Value 1024): Reconnect enable.
Brought over from TheNetNode.
See TN116.DOC, QUIT and RECONNECT
Bit 15 : PTT - disable
Shuts down the node transmitter. Results
directly in the level 1 partition.
CAUTION!!! There is now no possibility to
re-enable the PTT over the HDLC (radio) port.
It can be accessed only through a node that is
connected to its RS-232 port.
The value of the Parameter 30 can be set from the various values
together.
Example:
Par 30 = 0: TEST-diddle only for sysop
Downlink available
Uplink available
Par 30 = 1: TEST-diddle generally available
Par 30 = 6: TEST-diddle only for sysop
Downlink and uplink blocked
I hope this is generally clear.
(Translator's note: Not at all clear to me, but the following is better:)
For everyone who does not understand this, in order to facilitate
it the FLAG-command is newly introduced under sysop control.
'F 5 0' for example means par 30 bit 5 would be set to 0.
'F 15 1': PTT would be closed down
This can be a one-way street!!!!!!!!!!!!!!
'F' displays the individual flags
DL2LAY @ DB0HB Translation to English by W9BVD
Additional editing by K3AKK