User Tools

Site Tools


nodes:gb7bsk

GB7BSK Basingstoke, Hampshire

See live packet connectivity map

Sysop: 2E0HKD
Locator: IO91kg

RF Ports

(Port 1 is a non-public telnet interface)

Port Frequency Mode NinoTNC Mode Status
2 144.950 MHz FM 3600 baud QPSK IL2P+CRC 0101 (v39 only) Operational
3 70.3125 MHz FM 4800 baud GFSK IL2P+CRC 0100 Semi-Operational (new port still being tested)

The 3600 baud mode is available with NinoTNC firmware v39, setting 0101 (this firmware replaces the old 0101 mode of DPSK 2400 IL2P)

Good link to GB7RDG.

BBS/Mail, and Chat available. SSID for direct connection to BBS GB7BSK-1, and for chat GB7BSK-4.

Forwarding enabled for bulletins to:

Rejects bulls @WW over 5000 bytes from external BBSes to avoid saturating onward HF links within the network, please keep bulls a sensible length as you never know what links they may need to traverse!

You may have seen the node appear on APRS maps, but you cannot currently contact it via APRS. At the moment, it only beacons via APRS-IS to raise visibility. In the future, proper RF APRS may become available.

QtSoundModem Settings

NOTE: The new NinoTNC 3600 bps mode does not yet work with QtSoundModem, but compatibility is being worked on! Unfortunately the 2400 bps mode mentioned below will no longer work with the node.

If using QtSoundModem as a modem, you should select “QPSK V26A 2400bps” and a centre frequency of 1500 hz.

And in the modem settings (Settings → Setup Modems) enable FX25 and IL2P for RX+TX, and tick the CRC box.

AX.25 2.2 with SREJ

It is also possible to connect using Ax.25 2.2, which may have some advantages described below.

To do this from a BPQ node, use the “nc” (new connect) command, rather than the more common “c” (or “connect”) command, and force L2 (no NET/ROM) by putting an exclamation mark in front of the callsign. E.g.:

nc 2 !gb7bsk
(The 2 in this example specifies the port, use the “ports” command on a node to work out which one is on the appropriate band).

One advantage of this type of connection is the ability for SREJ, or selective reject, to be used. Normally, several packet may be sent out in order, and if one of them is not received correctly the entire batch is rejected with a REJ message. The whole set of packets then has to be retransmitted. SREJ allows only specific packets to be rejected, so only those individual packet need to be retransmitted.

Technical

  • Raspberry Pi 1 model B
  • 2m Tait T2010-321-F00
  • 4m Tait TM8110
  • NinoTNC on all ports
  • 2m Dipole (vertical)
  • 4m “hour glass” loop (vertical)
nodes/gb7bsk.txt · Last modified: 2024/07/15 17:00 by 2e0hkd

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki