Connections

Goal: pick the data sources, connect and verify APRS-IS, then get the RF link working.

Five links: many RX, one TX#

Path: Settings → Connection → Data sources. Every ticked link receives, but there is only one transmit source — the one marked with the dot. Transmitting the same callsign over two links produces duplicate packets.

SourceLinkRXTX
APRS-ISinternet TCP, default rotate.aprs2.net:14580✓✓
TNCBluetooth SPP / USB serial (OTG), KISS, into a radio✓✓
Audioheadphone jack into a radio, AFSK 1200 (Bell 202)✓✓
PKWDWPLBluetooth/serial reader of a Kenwood radio’s $PKWDWPL waypoints✓✗ receive-only
WLAN radio directWi-Fi / Ethernet direct link (supporting IC-705 / IC-9700 / IC-7610 / IC-905 etc.), CI-V + LAN audio✓✓
📡

The receive range defaults to 300 km (10 km minimum), filtered with r/lat/lng/radius — press “Save & apply” after changing it. For worldwide reception, raise the radius or stop following your position.

Connect APRS-IS#

  1. Settings → Connection: leave the server at rotate.aprs2.net, port 14580.
  2. Enter your Passcode (generated for the full callsign, see Quick Start).
  3. Press “Save & apply” — connection edits do nothing until you save.
  4. Back on the home page the link card reads “connected” and the counter climbs.
  • It reconnects by itself: progressive backoff of 8 → 16 → 32 → 60 s.
  • Server replies unverified = the Passcode failed — go back to step 2.
  • Custom relay / WebSocket: fill WebSocket URL (optional) in the same place; empty = plain TCP.

Into a radio: TNC / audio / PKWDWPL / Icom#

All four RF paths live under Settings → Device (the overview lists the current link and four sub-pages):

PathSub-pageKey parameters
Bluetooth/USB TNCDevice → TNCinit string, serial baud, KISS params (txDelay 300 ms, txTail 50 ms, P=63, slot 100 ms, 330 B frames), path WIDE1-1,WIDE2-1
Audio (soundcard)Device → Audio22050 sample rate, 1200 baud, mark 1200 Hz / space 2200 Hz, TX level, 3000 ms CSMA wait
Kenwood waypointsDevice → PKWDWPLread-only link; strict checksum off by default (mismatches are flagged, not dropped)
Icom Radio LinkDevice → Icom Radio SettingsWLAN/LAN remote control, Network User credentials, radio IP, CI-V address (default 0xA4), band mode set to FM-D
  1. Bind the device: tap “Scan devices” (paired Bluetooth + USB serial) in the sub-page and pick yours.
  2. TNC receives but will not transmit: send the init string first — many modules boot into command mode and need KISS ON; then match the serial baud on both ends (9600/19200/38400/57600/115200 are common; Bluetooth SPP has no baud rate).
  3. Audio nobody can decode: check the TX level — too low or clipped both fail; wire it (headphone jack → radio data/mic), never speaker-to-microphone.
  4. Receive-only: switch off “allow TX / allow RF beacon” — listening only is the calmest setup and never keys the PTT by mistake.
  5. Icom Direct Link: enable WLAN / LAN remote control on the radio and create a Network User; ensure device and radio are on the same local network, enter IP, port, credentials and CI-V address in the sub-page; set the radio band mode to FM-D.
⚠️

RF transmission requires a licence — follow local regulations. RF beaconing is off by default; confirm your licence allows it before enabling.

iGate#

The iGate relays packets heard on RF into APRS-IS (adding qAr/qAR and your callsign). Entry: Settings → Device → Gateway (iGate).

  1. Meet the conditions: tick APRS-IS and one RF source (TNC or audio) — the UI names whichever is missing.
  2. Turn on Enable gateway — RF → IS only by default.
  3. Optionally enable two-way: it really transmits on RF, but only relays point-to-point messages addressed to stations heard on RF recently; broadcasts like position/weather are never relayed.
🔁

Loop protection (automatic): packets carrying TCPIP* or an existing q-construct (they came from the internet) are never sent back, and the same frame is injected once per 30 s. The counters in that section (RF seen / gated / duplicates dropped / loops blocked) are the live readings of those four gates.

Self-test & order of diagnosis#

When something breaks, work down this order — one layer at a time:

  1. Link status card (top of the home page): is the link up, are the counters moving, what did the server reply?
  2. Link self-test (device page): TNC protocol loopback plus the AFSK modulate/demodulate loop; the TNC side also offers an init string and a TX self-test that writes one status frame with no coordinates (it never moves you on aprs.fi).
  3. Packets tab: did the frames arrive at all? Received but never plotted = filter or coordinate issue (see Stations).
  4. Gateway counters stay flat: follow the hints — “RF seen = 0” means nothing arrived: check radio volume, squelch and antenna first.
✅

Best evidence when reporting: the raw packet from the Packets tab plus the link log.