Migrate apr2020 to oct2021

page modified October 20, 2021
Specifications may change without notice.

apr2020 and oct2021 are the names of the repositories for the two most modern TARPN releases. It is from one of these two repositories that your node fetches it's installers, applications, and and any updates. In addition to the release repositories, there are a plethora of test repositories including nov2020test and jun2021test. The jun2021test has been renamed oct2021 and the next tarpn update you perform will change your selected repository. For those of you who are using apr2020 and nov2020test, there is a trivial path to update to the oct2021 release.

The Oct 2021 version has been in development since late summer 2020 and in beta test since June 2021. It was started in order to support the NinoTNC A4.

There was a complexity imposed by the NinoTNC with regards to configuring the node/switch software as to which TNC was associated with which radio and neighbor callsign. The solution Nino and I tried first was to provide a serial number to be stored in the FLASH memory of the NinoTNC CPU which would identify the NinoTNC to the Raspberry PI, the operator and G8BPQ code. The storage and serial number were called KAUP8R which stands for "KISS Accessible User Programmable 8-character Register". The beta version nov2020test has been dead ended due to unsolvable limitations in the use of the KAUP8R for our ID purpose. The oct2021 version completely does away with the NinoTNC USB Identification problem.

The system of TNC identification used in the jun2021test beta version, which begat the oct2021 release, requires that each NinoTNC can hear the beacons from the neighbors, before the TNC is identified. We already create a node.ini file giving the callsigns of the neighbor nodes. Once the G8BPQ node hears the neighbor's broadcast, TARPN software can match up the port number with the neighbor callsign. The disadvantage of this method is that it takes up to 20 minutes for this to happen if the neighbor node is active. It will take forever or until the neighbor node becomes active if the neighbor node is not ever heard. Another disadvantage is the handy labelling of the ports in the QT-term application is broken. Instead they'll be labelled port 1, port 2, and etc. The R or R R command have to be used to reveal the association of port with neighbor callsign.

Every TARPN node op should move over to this and get help via the reflector if this webpage is not sufficient.

What does it do?

This gives us several new features and limitations.

Since the apr2020 version, we've updated the bootloader to support programming the NinoTNC A4 FAT CPUs. This version programs NinoTNCs running the version-b/version-B bootloader, as well as the old version-a bootloader.
This version sorts the NinoTNCs after the G8BPQ node is up and running, instead of using the KAUP8R 8-character serial ID and instead of using the USB discovery order. The USB discovery-order method resulted in NinoTNCs being selected incorrectly so the node would be looking for the wrong neighbor on a given port
This version adds statistics gathering and other features from the GET-ALL data, reported by the NinoTNCs. This permits the TINFO node command to show you the switch positions, baud rate, FEC mode, and TxDelay of each NinoTNC.
This version adds the LINKTEST node command. It will prompt for a port #. It will then send 100 medium length packets to that port #.
This version breaks the TRR command. We're working on that. In the mean time, we have a local link analysis display on TARPN-HOME that is pretty, but it only shows your links. TRR let us connect to distant nodes and do analysis. It'll be back, just gotta catch up on some of this software. W4EIP, who wrote the original TRR is back on the case.
This version does not support TNC-PIs. If you still have a TNC-PI and are a pistol shooter, you are in luck. The TNC-PI makes a dandy target at about 25 feet.
This version wants to use NinoTNC A3 and A4 boards with the USB-B Printer socket. The earlier micro-USB FTDI NinoTNCs are treated as special citizens, along with any other TNC connected via FTDI USB adapter. The FTDI devices show up as ttyUSB# in the Linux device list, where-as the A3 and A4 NinoTNCs show up as ttyACM# in that list. This version can support up to ten of the ttyACM# NinoTNC A3 and A4 and up to two of the ttyUSB FTDI devices.
This version delivers a new TARPN-HOME which includes several bandwidth-saving features and a bunch of improvements aimed at the user, including a very long scroll back, a chat history log searching feature, a link analysis capability, BBS reply that includes the previous message, scrolling chatters list which identifies stations that recently dropped off the list, and better support for smart-phone browser access.
When you start your node, the routes table is completely blank. This is very different from previous versions. In prior TARPN installations you had to carefully identify the NinoTNC or TNC-PI that is associated with each radio and assign a callsign to that TNC. In this version, you just tell the software what neighbors you have, and what the FRACK time to that neighbor should be. The software watches the Mheard list for each discovered NinoTNC A3 or A4 and assigns your neighbor to the port where that neighbor is heard. The routes table builds as the node is running.
This completely eliminates the hassle of assigning addresses and KAUP8R serial numbers, and eliminates the hassle of making sure the USB ports are not changed for each NinoTNC.

This is what the new TINFO command shows me on TADD node:


Connected to TINFO
TARPN vb103
lat/lon coordinates: 35.8897, -78.6798
TARPN Updates URL:   http://tarpn.net/jun2021test
Linux UPTIME:        09:56:17 up 3 days, 13:39,  3 users,  load average: 0.09, 0.20, 0.23
Node started:        Sat 21 Aug 2021 03 27 54 PM EDT  Node background Service is (AUTO)
Raspberry PI Reset:  2021-10-20 20:17:09
TARPN HOME:          is running              TARPN HOME is set to START
TARPN-HOME build-utc:Oct 19 13:09
TARPN-HOME install:  Sat 19 Oct 2021 02:54:49 PM EDT
Rasberry PI Hardware:type 4 B 2GB made in UK
OS version:          Raspbian GNU/Linux 10 (buster)
Ethernet MAC:        dc:a6:32:52:b7:d0   CPU temp=51.0'C   SDcard=1599350888
TARPN Installed:     Oct 19  2020
UpdateApps Last run: Oct 19 14:54

Date  Time Port AsnNghbr FWver  Board Switch  Baud Modu  FEC   TXD
10-19 09:53 p1  KA2DEW-3   3.01  A3    0001  >9600 GFSK  IL2P<  21
10-19 09:46 p2  N3LTV-2    3.01  A3    0001  >9600 GFSK  IL2P<  16
10-19 09:53 p3  KM4EP-2    3.01  A3    0101  >2400 DAPSK IL2P<  120
10-19 09:53 p4  KN4ORB-2   3.01  A3    0111  >1200 AFSK  IL2P<  120
10-19 09:52 p5  K4RGN-2    3.01  A4r1  0001  >9600 GFSK  IL2P<  20

Undervoltage Events found in Log file = 0
My IP address is 10.0.0.200
Router info:default via 10.0.0.1 dev eth0 proto dhcp src 10.0.0.200 metric 202

How do I get it?

At a Linux prompt type tarpn service stop
At a Linux prompt type cp node.ini old-node.ini
This backs up your node.ini file for future reference.
At a Linux prompt type tarpn url
tarpn url changes the repository from which the tarpn applications and scripts are loaded.
When prompted, type http://tarpn.net/oct2021
The script should tell you
```
I saw source URL=http://tarpn.net/oct2021

source URL confirmed

source URL saved -- next update or BPQ node restart will be from the new source URL
      
```
And then you should be back to the Linux prompt.
At a Linux prompt type tarpn update
That will run for about a minute
At a Linux prompt type tarpn updateapps
That will run for between 2 minutes and 20 minutes
At a Linux prompt type tarpn config and follow the instructions.
Externally, you know which NinoTNC faces which neighbor, what the bit rate/baud of the port is, and what kind of radio you have. The TARPN app software does not know these things so it can't generate a Frame-Acknowledge time (FRACK)for you. You have to specify that for each port. FRACK is in milliseconds and is the amount of time it takes for your end to key up your radio, send the packet, have the other end key up, and send a packet. We usually use 2000 for a Tait at 9600 baud, and 9000 for a TK760 at 1200 baud. if you have doubt, set the FRACK at 9000 to start and we'll fine tune it later.
If you have NinoTNC A2, use port 11 and 12 for those TNCs. In that case you'll have to use the proper /device name /dev/ttyUSB0 for instance, to specify the TNC.
Do not specify NinoTNC A3 and A4 devices in ports 11 and 12. 11 and 12 are only for ttyUSB ports.
At a Linux prompt type tarpn test and make sure it gets down to TNC Emulation Complete and then stops printing.
Give it a minute, watching for stability, and then use control-C to quit out of the test. If any errors or flakey looking messages are printed, please reply to the TARPN groups.io.
At a Linux prompt type tarpn service start which will start your node and run it in the background.
You'll be able to use qtTerm to monitor the startup. Neighbors will only show up in R R after the -2 callsign for the neighbor has been heard over-the-air.
TARPN-HOME may be updated after you start the node. At a Linux prompt type tarpn home update
After TARPN-HOME updates, load it in the web browser. It should say v2.10 at the bottom. If not, do a force refresh of your browser. That may be Alt F5 or hold down some control key and click the refresh icon.


pi@taddpacket:~ $ tarpn test
#### =TARPN vb103 =
#####
##### TEST --  Starts BPQ node immediately and runs it in the foreground until
#####          a control C is issued in this window, or until a   tarpn stop
#####          command is issued in another window.

source url exists
node.ini exists.
tarpn usb
#####
##### Show ttyUSB and ttyACM devices (NinoTNC) found in /dev
#####
#####   ------------- start
ttyACM0
ttyACM1
ttyACM2
ttyACM3
ttyACM4
ttyUSB0
#####   ------------- end

#####  List of tty ports called out in node.ini
#####
#####  ------------- start
neighborA:KA2DEW-3
neighborB:KM4EP-2
neighborC:K4RGN-2
neighborD:N3LTV-2
neighborE:KN4ORB-2
#####   ------------- end
#####
#####
#####
##### Starting BPQ Node by calling RUNBPQ.SH
runbpq.sh:  hello user >>pi<<
#### =RUNBPQ vB044 =
#### =MAKE LOCAL BPQ v138
Number of NinoTNC A3 and A4 units using ttyACM# device name = 5


Enable BBS application
local-op-callsign is specified.  Enable HOST mode
chatcall:ka2dew-5
SUCCESS...
### RUNBPQ.SH:
### RUNBPQ.SH: Launching G8BPQ node software.  Note, this script does not end
### RUNBPQ.SH: until the node is STOPPED/control-C etc..
### RUNBPQ.SH:
G8BPQ AX25 Packet Switch System Version 6.0.21.40 March 2021
Copyright ? 2001-2021 John Wiseman G8BPQ
Current Directory is /home/pi/bpq

Configuration file Preprocessor.
Using Configuration file /home/pi/bpq/bpq32.cfg
Conversion (probably) successful

PORTS 0x234af0 LINKS 0x239fd8 DESTS 0x23aa20 ROUTES 0x23d2c0 L4 0x23d7a0 BUFFERS 0x243e30

Route/Node recovery file BPQNODES.dat not found - Continuing without it
Initialising Port 01     ASYNC /dev/ttyACM0 Chan A
Initialising Port 02     ASYNC /dev/ttyACM1 Chan A
Initialising Port 03     ASYNC /dev/ttyACM2 Chan A
Initialising Port 04     ASYNC /dev/ttyACM3 Chan A
Initialising Port 05     ASYNC /dev/ttyACM4 Chan A
Initialising Port 32     Telnet Server
Starting Chat
Config File is /home/pi/bpq/chatconfig.cfg
Chat Started
Starting Mail
Config File is /home/pi/bpq/linmail.cfg
Config Processed
Mail Started
slave device: /dev/pts/1. symlink to /home/pi/minicom/com1 created
slave device: /dev/pts/2. symlink to /home/pi/minicom/com4 created
slave device: /dev/pts/3. symlink to /home/pi/minicom/com5 created
slave device: /dev/pts/4. symlink to /home/pi/minicom/com6 created
slave device: /dev/pts/5. symlink to /home/pi/minicom/com7 created
slave device: /dev/pts/6. symlink to /home/pi/minicom/com8 created
TNC Emulator Init Complete