Netrom link quality

Hier onder een stukje wat ik tegen kwam in het bbs, het gaat over de quality van een netrom link. Geschreven door John G8BPQ.

——————–
Quality isn’t measured. It is assigned by the sysop to a Netrom link,
and calculated by the node for a Netrom route. In this context a link is
the path between two adjacent stations, and a route is a path between
two stations over one or more links.

Quality doesn’t necessarily define how “good” a link is. It is used by
the software to select the route to use when more than one route exists
between two nodes. Desirability would be a better term. While this may
be related to how good the link is it might include other factors (eg
give preference to RF links and only use Internet links as a backup if
the radio link fails). It is expressed as a number between 0 and 255.
When a route is over two links, the route quality is calculated by
multiplying the link qualities together and dividing by 256. So for two
links of quality 192 the route quality is 144.

The “standard” default quality is 192. You might change this if you
had two links between two stations (maybe a UHF trunk link and a VHF
user link). By assigning a higher quality to the UHF link traffic would
be routed over it and would only use the other if the first failed.

The Netrom routing mechanism was designed to be self learning, building
routing tables from broadcasts heard from other nodes. This can work
quite well, but only if you don’t have any one way paths. If you can
hear a node but not connect to it the system simply doesn’t work. It
sounds from what you have said that is is what you are seeing. Unless
you deliberately disable the mechanism, BPQ will try to keep a link open
to each node it hears a routing broadcast from, and remove it from the
tables if the link can’t be established (or fails) but in the meantime
the routing entries will be used and may be passed on to other stations.

With your current configuration you will add to your table any stations
you hear a routing broadcast from with a quality of 192. This is a
reasonable starting point if you can connect to all the stations you can
hear. If not, there are two approaches you can use. You can ignore
routing messages from specific nodes that you know you can’t connect to
by adding a locked route with a link quality of zero, or you can set the
PORT QUALITY parameter below MINQUAL, so that nothing is automatically
added, and lock routes to the stations you know you can connect to with
a link quality of 192. The second option requires more active
management, but is likely to give a more stable network.

I’m not sure if this has directly answered your question, but hopefully
will help you understand the issues more.
73,

John G8BPQ
———————

Direwolf Soundmodem

Direwolf source

Direwolf example config

Arecord -l

#############################################################
#                                                           #
#               Configuration file for Dire Wolf            #
#                                                           #
#                   Linux version                           #
#                                                           #
#############################################################
# card number reported by "arecord -l" command.

ADEVICE  plughw:0,1
ACHANNELS 1

#############################################################
#                                                           #
#               CHANNEL 0 PROPERTIES                        #
#                                                           #
#############################################################

CHANNEL 0

MYCALL PI1LAP-8
MODEM 1200 1200:2200 E+
PTT /dev/ttyUSB0 DTR
TXDELAY 20
TXTAIL 10
KISSPORT 8001
FIX_BITS 1

PBEACON delay=1  every=30 overlay=S symbol="digi" lat=51^33.52N long=003^48.15E power=4 height=15 gain=6 comment="PI1LAP-10 RX\TX iGate Kortgene,ZLD JO11VN" via=WIDE1-1,WIDE2-1 
DIGIPEAT 0 0 ^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE 
#FILTER 0 1 t/wn 
IGSERVER aprs.pa4tw.nl:14580
IGLOGIN PI1LAP 20391
PBEACON sendto=IG delay=0:30 every=30:00 symbol="igate" overlay=T lat=51^33.52N long=003^48.15E 
#PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=T lat=42^37.14N long=071^20.83W 
IGTXVIA 0 WIDE1-1 WIDE2-1
IGFILTER m/250 
FILTER IG 0 t/m

# Finally, we don't want to flood the radio channel.  
# The IGate function will limit the number of packets transmitted 
# during 1 minute and 5 minute intervals.   If a limit would 
# be exceeded, the packet is dropped and message is displayed in red.

IGTXLIMIT 6 10

Compile Instructions Jnos2.0k

Download Jnos 2.0k Source Jnos

July 26, 2016 - Compile instructions for JNOS 2.0k

1) There is NO incremental update from previous versions, too much
   has changed, and a mass compile is required anyways.

   Put the compressed tar file into an empty directory, then :

    gunzip jnos2.0k.tar.gz
    tar xvf jnos2.0k.tar
    cd jnos/src/rsync

2) Before you compile and IF you have your own config.h from a previous
   version of JNOS 2.0, then you can copy it over if you like. However, if
   you choose to do this, do a 'diff' between your 'config.h' and the new
   'config.h.default' shipped with JNOS 2.0k - to see what new features
   you might be missing out on. It is probably not a big deal, but you
   should know about it anyways.

   IF you are starting from scratch, the compile process automatically
   copies the 'config.h.default' to 'config.h' (only if the latter is not
   present) and then compiles the whole thing.

   IF you want to edit a new config.h BEFORE the compile starts, then use
   the 'make defconfig' command first. That will create the 'config.h' for
   you, then you can edit it to suit your own preferences.

3) To compile and link JNOS, just enter the 'make' command.

   Please note that warnings may happen, although with this release I have
   made extra effort to try and clean them ALL up, your mileage will vary.

4) That's it, if all goes well, you should have a new 'jnos' binary.

5) Why is 'jnos' binary so large AND what to do about JNOS crashing !

   Note that my makefile has debugging turned on, so any 'jnos' binary
   you compile will be large (because it contains debuggin info). If you
   are not at all interested in debugging, then you can reduce the size
   of the 'jnos' binary using the following command :

    strip jnos

   which will strip out the debugging information and symbol table.

   If you ARE interested in helping me fix bugs, then I encourage you to
   run the GDB debugger that comes with most linux distros, AND make sure
   you do NOT strip the 'jnos' binary, since it contains important info for
   the debugger to use when a crash occurs.

   Using GDB is easy. With JNOS running already, find out it's pid, using
   the linux command, 'ps -ef | grep jnos'. Once you know what the pid is,
   then run the gdb debugger something like this :

    gdb -p pid

   GDB will load, JNOS will hang temporarily, and GDB will suddenly give
   you a prompt. Enter the command, 'continue', at the prompt, and JNOS
   will continue to run again.

   When a crash occurs, GDB will break out to the prompt again, and JNOS
   will hang. Take a screen shot of what GDB printed out, then type in
   the command, 'back full', at the GDB prompt, and note the info that
   appears. Please send all of that information to me, with a brief
   explanation of what might have been going on at the time.

   If you have JNOS logging in effect, please send me the log file at
   the time of the crash if you don't mind. Logs are under /jnos/logs/
   directory (by default).

JNOS 2.0k released - 26Jul2016

* Maiko Langelaar / VE4KLM

Bpq32 ardop Config

Configuration example of ardop with BPQ32.

;
;	Sample Config for a ARDOP Port
;
PORT
 PORTNUM=7
 PORTCALL=PI1LAP                    ; This is the call sent to the ARDOP modem
 ID=ARDOP
 TYPE=EXTERNAL
 DLLNAME=ARDOP
 INTERLOCK=1
 CONFIG

 ADDR 127.0.0.1 8515 PTT RTS PATH C:\ARDOP_Chat\ARDOPC.exe
 RIGCONTROL 
 COM2 19200 ICOM IC700 70
 25,7.04730,USB,F3
 5,7.045,USB,F3,D
 ****
 
 CWID FALSE															 
 BUSYHOLD 1                              
 BUSYWAIT 20                             
 GRIDSQUARE JO11VN
 DRIVELEVEL 100
 DEBUGLOG FALSE
 CMDTRACE FALSE
 FECMODE 4PSK.500.100
 FECREPEATS 1
 ARQBW 1000MAX							 
 										 
 ARQTIMEOUT 90

   
ENDPORT
;

MS-Dos 6.22 Files

MS-DOS 6.22

Hier kan je het complete MS-Dos 6.22 besturingssysteem downloaden.
Verder nog de Bootdisks.
Dos6.22 Bootdisk iso > DOS6.22_bootdisk.iso
Dos6.22 automatic bootdisk > Dos6.22.exe
Dos6.22 IMG > Dos6.22.img

ATTRIB.EXE   11,208   Application   05/31/1994 06:22:00 AM
AUTOEXEC.BAT   45   MS-DOS Batch File   05/26/1999 04:45:20 PM
C.BAT   34   MS-DOS Batch File   07/20/1998 10:11:42 AM
CD1.SYS   34,262   System file   09/26/1996 05:13:04 PM
CD2.SYS   16,504   System file   11/21/1996 01:54:00 AM
CD3.SYS   19,984   System file   08/13/1996 01:03:02 AM
CD4.SYS   41,302   System file   05/11/1998 08:01:00 PM
CHKDSK.EXE   12,241   Application   05/31/1994 06:22:00 AM
COMMAND.COM   54,645   MS-DOS Application   05/31/1994 06:22:00 AM
CONFIG.SYS   377   System file   05/29/1999 12:20:38 PM
DELTREE.EXE   11,111   Application   05/31/1994 06:22:00 AM
DOSKEY.COM   5,861   MS-DOS Application   05/31/1994 06:22:00 AM
DRVSPACE.BIN   66,294   BIN File   05/31/1994 06:22:00 AM
EDIT.EXE   69,662   Application   10/17/1994 00:00:00 AM
EDIT.HLP   17,898   Help File   05/31/1994 06:22:00 AM
EDIT.INI   192   Configuration Settings   03/12/1995 05:57:26 PM
EMM386.EXE   120,926   Application   05/31/1994 06:22:00 AM
FDISK.EXE   29,336   Application   05/31/1994 06:22:00 AM
FIND.EXE   6,770   Application   05/31/1994 06:22:00 AM
FORMAT.COM   22,974   MS-DOS Application   05/31/1994 06:22:00 AM
HIMEM.SYS   29,136   System file   05/31/1994 06:22:00 AM
IO.SYS   40,774   System file   05/31/1994 06:22:00 AM
LABEL.EXE   9,390   Application   05/31/1994 06:22:00 AM
MEM.EXE   32,502   Application   05/31/1994 06:22:00 AM
MOUSE.@@@   7   @@@ File   07/06/1997 06:51:06 PM
MOUSE.COM   56,408   MS-DOS Application   03/10/1993 06:00:00 AM
MOUSE.INI   28   Configuration Settings   04/11/1997 01:50:40 AM
MOUSE.SYS   31,701   System file   05/01/1990 03:00:00 AM
MSCDEX.EXE   25,361   Application   05/31/1994 06:22:00 AM
MSDOS.SYS   38,138   System file   05/31/1994 06:22:00 AM
QBASIC.EXE   194,309   Application   05/31/1994 06:22:00 AM
QBASIC.HLP   130,881   Help File   05/31/1994 06:22:00 AM
RESTORE.EXE   38,342   Application   05/31/1994 06:22:00 AM
SCANDISK.EXE   124,262   Application   05/31/1994 06:22:00 AM
SCANDISK.INI   6,920   Configuration Settings   05/31/1994 06:22:00 AM
SETVER.EXE   12,015   Application   05/31/1994 06:22:00 AM
SHARE.EXE   10,912   Application   05/31/1994 06:22:00 AM
SYS.COM   9,432   MS-DOS Application   05/31/1994 06:22:00 AM
TREE.COM   6,945   MS-DOS Application   05/31/1994 06:22:00 AM
UNDELETE.EXE   26,416   Application   05/31/1994 06:22:00 AM
UNDELETE.INI   235   Configuration Settings   02/23/1995 07:36:44 AM
UNFORMAT.COM   12,738   MS-DOS Application   05/31/1994 06:22:00 AM
XCOPY.EXE   16,930   Application   05/31/1994 06:22:00 AM

Pk232 DCD setup (howto)

Msg # 12990 Type:B Stat:$ To: ALL @ALLOH From: KA8TEF Date: 05-Sep/1912
Subject: Setting the DCD THRESHOLD of the 232
Bulletin ID: 5373_N8FIS
Path: AD8I!N8FIS

The following is a reprint of a article in the TAPER newsletter August
1988 Issue 32.

AEA PK-232 Notes:
by Eric Gustafson

Recently, several new packeteers using PK-232s have appeared on our local
duplex repeater which is dedicated to packet radio. This is one environment
where the collision frequency should be verylow since there are no hidden
terminals. Almost immediatly we noticed that the collision frequency had risen
dramatically. After some investigation we discovered certain stations were
almost guarenteed to be involved in stepping on in progress packets. These
stations were contacted and in all but one case they were new users of PK-232s
units.

We were very puzzled as there have always been some stations on the
repeater using PK232s with no apparent
problems. The new stations were asked how their station was configured and
what method was used to get the DCD operation adjusted. We were very
surprised at the answers we got. Every single one of the offending stations
had set their stations up according to the instructions in the PK-232 manual.
However, contrary to the advice given in the manual, none of these stations
had configured their setup so that they could hear what was going on on the
channel when the PK-232 was connected to the radio. None of these new
operators knew what DCD meant, what it did, or why it was important that it
should be working on a multiple access packet channel.

We obtained a PK-232 and the manual to try to discover the exact
nature of the problem. What we found was that although the manual is very
complete and generally very well written, there are some areas where it
leaves something to be desired. Specifically, in this case, the
instructions given on page 2-16 (we had manual PK232UG Rev.B 9/86) for setting
up the PK-232 and an FM radio for DCD operation are simply incorrect. If set
up exactly as described, DCD will NEVER be asserted during a packet trans-
mission by another station on the channel! We had found the cause of our
problem.

If you have a PK-232 and haven’t already discovered this problem for
yourself, please disregard the instructions in the manual for setting
up a PK-232 and NBFM radio for 1200 baud operations and use the method
presented here. All your packet neighbors will appreciate it very much.

The manual is quite correct EXCEPT where they discuss setting the DCD
THRESHOLD control and receiver audio output level for proper demodulation
and DCD circuit operation. The corect way to set these adjustments is :

1. At least temporarily, arrange to
be able to hear the receiver audio
signal which is being sent to the PK-232.

2. Set the squelch circuit on the
radio for normal squelched operation.
The DCD circuit in the PK-232 is in
capable of proper operation with unsqueched
audio from the receiver.

3. While monitoring incoming packets,
adjust the receiver audio level so
indicator “spreads” fully when
receiving a packet on the channel
which produces the LEAST amount of
audio output level. There are several
limiters in the PK-232 demodulator
so louder stations will not be affected
adversely by this.

4. Once the audio level is properly
set, adjust the DCD THRESHOLD control
on the PK-232 so that the DCD led
lights when there is a packet being
transmitted by the station on the
channelwhich produces the LEAST amount
of audio output from the receiver.
Make sure that the DCD LED is extinguished
when there is no signal and the radio’s
squelch circuit has cut off all audio
from the receiver.

If the above procedure is followed, the PK-232 will properly hold
off transmitting during a packet transmission from another station and
will not send acknowlagements to individual frames of a maxframe greater
than 1 packet while it is still being transmitted.

We hope PK-232 owners will find this information useful and take the
steps to assure that their DCD is operating properly. Multiple access
packet channel throughput is severly degraded when DCD is not working.

Hope this helps out
73 Phil KA8TEF

Xrouter onder Win98 met Baycom modem.

Xrouter onder Windows met een Baycom Modem
v0.40 = 8 Mei, 2003
Deze DOC is geschreven door Richard de CB1RAM

Index :

1. Website’s waar je de software kan downloaden
2. Instellingen voor Xrouter
3. Bestanden die in C:\WINDOWS\SYSTEM moeten staan
4. Regels die toegepast moeten worden aan AUTOEXEC.BAT
5. Thanks to

Allereerst ga ik er vanuit dat je Windows 98 gebruikt. Hoe het met
andere versies is, zoals 2000, NT en XP, weet ik helaas niet.

Ik ga er vanuit dat Xrouter in de map C:\XROUTER staat.

Mocht dat bij nou anders zijn, dan moet je zo her en der wat dingen
aanpassen.

1. Website’s waar je de software kan downloaden

Xrouter:
https://packet-radio.net/wp-content/uploads/2017/04/Xr-Bm.zip

2. Instellingen voor Xrouter

Ik ga er vanuit dat je Xrouter al op je computer hebt staan.

Voorbeeld voor Compoort 1 (3F8) ( XROUTER1.BAT ) :

lh node2bay -I4 -B3f8 -i60 -dbaydrv.vxd
lh pzthost.exe

Voorbeeld voor Compoort 2 (2F8) ( XROUTER2.BAT ) :

lh node2bay -I3 -B2f8 -i60 -dbaydrv.vxd
lh pzthost.exe

Deze 2 opstart bestanden staan ook wel in dit pakketje.

XROUTER1.BAT => Voor Baycom Modem op compoort 1 (3F8)

XROUTER2.BAT => Voor Baycom Modem op compoort 2 (2F8)

Zet alle 6 bestandjes die in dit pakketje zitten (XROUTER)
in de directory waar XROUTER.EXE ook in staat.

BAYDRV.VXD
NODE2BAY.EXE
PZTHOST.EXE
XROUTER.CFG <<< Verander de call , nodecall en alias wel even.
XROUTER1.BAT
XROUTER2.BAT

Deze bestanden staan in dit pakketje (XROUTER)

3. Bestanden die in C:\WINDOWS\SYSTEM moeten staan

Deze 2 bestandjes moeten in de system directory gezet worden.

BPQCODE.386
BPQDLL.DLL

(staan ook in dit pakketje (WINDOWS)

4. Regels die toegepast moeten worden aan AUTOEXEC.BAT

SET PATH=C:\XROUTER;
CD XROUTER
XROUTER1.BAT ( Voor Baycom Modem op compoort 1)
CD\

CD XROUTER
XROUTER2.BAT ( Voor Baycom Modem op compoort 2)
CD\

5. Thanks to

NL2STK: Deze beste man heeft mij geholpen om Xrouter met
een Baycom Modem aan de praat te krijgen.

(c) 2003 by Richard