RTKBase GNSS RTK Base Station

In this hands-on lab, students build, configure, and evaluate an autonomous, outdoor-ready GNSS Real-Time Kinematic (RTK) base station and NTRIP caster orchestrator. Working with an embedded Linux single-board computer, a multi-frequency GNSS receiver module, an active multi-band antenna, and Power over Ethernet (PoE) hardware housed in an environmentally sealed enclosure, students establish precise hardware time synchronization using Pulse-Per-Second (PPS) GPIO interrupts and chrony. They compile and deploy core RTKLIB utility binaries, configure local NTRIP services to broadcast high-accuracy differential RTCM correction streams, and interface diagnostic tooling over serial and TCP networks. Through system deployment and verification, students develop practical competencies in multi-constellation satellite positioning, embedded network architecture, real-time geodetic data distribution, and system-level IoT integration.

GNSS global navigation satellite system RTK real-time kinematic RTKLIB NTRIP RTCM single-board computer SBC Raspberry Pi embedded Linux Pulse-Per-Second PPS chrony Power over Ethernet PoE serial communication surveying and geodesy

Uploaded by demo on 2026-09-03 · ready · Electronics · Original source ↗

Files: RTKBase_README.md · settings.conf.default · web_app_requirements.txt

Readiness checks

  • complete 2026-09-03 15:58 🛡 Cybersecurity: Do not place on an open network · 15 findings 26 searches · 6 pages
    view · PDF

Latest report — 2026-09-03 15:58

Readiness: RTKBase GNSS RTK Base Station

Verdict: Ready with caveats · 2026-09-03 · est. parts cost $577–$732 (one base station; the Septentrio mosaic-X5 option adds roughly $450) Cybersecurity — software & network: Do not place on an open network

This is the cold check — the first readiness report for this lab, so it establishes the baseline every future check measures drift against. Every functional block of the base station can be sourced today from evidence gathered this run. Four things keep it off a clean "Ready": the PoE splitter in the BOM (TRENDnet TPE-104GS) is Obsolete with 30 pieces left at one distributor and no ECIA-authorized distributor carrying it; the host Raspberry Pi 3 Model B+ is Not For New Designs (though 14,996 are on the shelf, and the snapshot's equally acceptable Pi 3 Model B is Active); the snapshot's representative RF-cable part number turns out to be a BNC-to-BNC 6-inch jumper rather than the SMA-to-TNC outdoor run the lab needs, and it is out of stock everywhere; and the DA910 antenna could not be found at retail under that model name. Verified, in-stock substitutes were found for all three of the last group, so nothing here blocks a build.

Action required

Part Problem Recommended action
TRENDnet TPE-104GS (PoE splitter) Obsolete at DigiKey, 30 pieces left; no ECIA-authorized distributor lists it at all. Its rated 2 A at 5 V is also below the lab's own ≥ 2.4 A criterion. Switch to Tycon POE-SPLT-BT-UNI-P ($69.25, 381 in stock). Feed it from the BOM's 802.3at PoE+ injector, not a plain 802.3af midspan, and replace the barrel-to-micro-USB adapter with a bare-wire-to-micro-USB lead — its DC output is a wire terminal block.
Amphenol 115101-09-06.00 (antenna RF cable) The representative part number is a BNC-to-BNC 6-inch jumper — wrong connectors, wrong length — and every ECIA distributor shows 0 stock. Order Siretta ASMZG500A058L13 (SMA male to TNC male, 16.4 ft / 5 m, $50.55, 70 in stock).
DA910 GNSS antenna No retail listing found under that model name this run. Order the SparkFun SPK6618H multi-band surveying antenna ($179.69, 255 in stock) — TNC female, L1/L2/L5, 5/8"-11 survey mount. Confirm LNA gain and bias voltage on its datasheet.
SanDisk SDSQQNR-032G-GN6IA (microSD) DigiKey returns no product; the exact part number sells at $127.63 — about five times the going rate. Buy any high-endurance Class 10 / U1 card of 16 GB or more, as the lab's own notes allow: SanDisk High Endurance, $22.99.
Raspberry Pi 3 Model B+ (SC0073) Not For New Designs; RS quotes a 364-day factory lead time and ECIA rates supply-chain risk High. Safe to buy today — 14,996 in stock at $40.00 — but plan the next build around SC0022 (Pi 3 Model B, $35.00) or an Orange Pi Zero, both documented in the lab.

Cybersecurity — software & network

Do not place on an open network — The web control panel ships with a documented default password over plain HTTP, the documentation adds an unauthenticated serial-over-TCP listener, and 10 of the 41 pinned Python packages carry published advisories - four of them high severity in the web-facing stack.

Component Version How known Support status
RTKBase (web app + services) 2.7.0 read from project (settings.conf.default line 5 'version=2.7.0' (fetched/02-settings.conf.default)) —
RTKLIB-EX (rtklibexplorer RTKLIB, str2str) v2.5.0 read from project (tools/install.sh line 204 downloads tags/v2.5.0.tar.gz (fetched/04-install.sh); note README line 96 still documents 2.4.3b34j) —
Debian GNU/Linux 12 inferred (README line 339 requires 'Debian base distro >= 12 (Bookworms)' - a floor, not a pin; 12 taken as the floor) extended/LTS support only until 2028-06-30
Python 3 3.11 inferred (README line 340 requires 'Python >= 3.11' - a floor, not a pin; 3.11 taken as the floor) supported until 2027-10-31
Armbian_RTKBase SBC image not determined unpinned (the documented image URL github.com/Stefal/build/releases/latest always resolves to the newest release) —
pi-gen RTKBase image not determined unpinned (the documented image URL github.com/jancelin/pi-gen/releases/latest always resolves to the newest release) —
gpsd not determined unpinned (README line 202 asks for 'a gpsd release >= 3.2'; installed via apt with no version pin) —
click 8.1.8 read from project (web_app/requirements.txt (fetched/01-requirements.txt)) —
Flask 3.1.2 read from project (web_app/requirements.txt (fetched/01-requirements.txt)) —
idna 3.10 read from project (web_app/requirements.txt (fetched/01-requirements.txt)) —
lxml 6.0.1 read from project (web_app/requirements.txt (fetched/01-requirements.txt)) —
python-engineio 4.12.2 read from project (web_app/requirements.txt (fetched/01-requirements.txt)) —
python-socketio 5.13.0 read from project (web_app/requirements.txt (fetched/01-requirements.txt)) —
requests 2.32.5 read from project (web_app/requirements.txt (fetched/01-requirements.txt)) —
setuptools 80.9.0 read from project (web_app/requirements.txt (fetched/01-requirements.txt)) —
urllib3 2.5.0 read from project (web_app/requirements.txt (fetched/01-requirements.txt)) —
Werkzeug 3.1.3 read from project (web_app/requirements.txt (fetched/01-requirements.txt)) —
Component Finding Severity Fix available?
click Click's edit() helper passes arbitrary OS commands through; this only bites if RTKBase actually calls click.edit(), which the evidence does not establish either way. — PYSEC-2026-2132 high Yes - update to 8.3.3 in web_app/requirements.txt
lxml lxml's default parser settings allow XML external entity attacks, so XML the base station parses could be used to read local files off the SBC. — GHSA-vfmq-68hx-4jfw high Yes - update to 6.1.0 in web_app/requirements.txt
python-engineio The websocket transport under the web GUI allocates threads without bound and does not always enforce its maximum payload size, so anyone who can reach port 80 can knock the interface over. — GHSA-cgwc-pv48-fhj5, GHSA-m9gh-vj53-gvh9 high Yes - update to 4.13.2 in web_app/requirements.txt
python-socketio The same live-update layer accumulates binary attachments until memory runs out, and in multi-server deployments can be made to execute arbitrary Python through a malicious pickle - both reachable from the web GUI's port. — GHSA-5w7q-77mv-v69f, GHSA-g8c6-8fjj-2r4m high Yes - update to 5.16.2 in web_app/requirements.txt
urllib3 The HTTP library behind the base station's outbound requests mishandles compressed responses and cross-origin redirects, so a hostile or compromised server it fetches from (map tiles, update checks) can exhaust the SBC's memory or have sensitive headers forwarded to it. — GHSA-38jv-5279-wg99, GHSA-qccp-gfcp-xxvc, GHSA-2xpw-w6gg-jr37, GHSA-gm62-xv2j-4w53 high Yes - update to 2.7.0 in web_app/requirements.txt
idna Crafted domain names can slip past idna.encode()'s validation, which matters where the base station resolves a hostname supplied to it (for example an NTRIP caster address). — GHSA-65pc-fj4g-8rjx moderate Yes - update to 3.15 in web_app/requirements.txt
requests The requests library reuses a predictable temporary file in extract_zipped_paths(), which a local account on the SBC could abuse. — GHSA-gc5v-m9x4-r6x2 moderate Yes - update to 2.33.0 in web_app/requirements.txt
setuptools A packaging flaw that lets files escape MANIFEST.in exclusions on macOS filesystems; it does not affect a running Debian base station, but the pinned version is behind. — GHSA-h35f-9h28-mq5c moderate Yes - update to 83.0.0 in web_app/requirements.txt
Werkzeug Werkzeug's safe_join() can be tricked by Windows special device names; the base station runs on Debian, so the practical exposure here is low. — GHSA-29vq-49wr-vm6x, GHSA-87hc-h4r5-73f7, GHSA-hgf8-39gv-g3f2 moderate Yes - update to 3.1.6 in web_app/requirements.txt
Flask Flask omits the 'Vary: Cookie' header in some cases, which can cause a cache in front of the GUI to serve one session's page to another viewer. — GHSA-68rp-wp8r-4726 low Yes - update to 3.1.3 in web_app/requirements.txt
Debian GNU/Linux 12 Debian 12's standard security support ended 2026-07-11; the release now gets patches only from the LTS/extended stream (until 2028-06-30), so fixes arrive on a slower, narrower track. posture Mitigation only - target a release still in standard support for new builds; the lab requires only 'Debian >= 12'.
Local NTRIP caster (str2str_local_ntrip_caster, TCP 2101) The shipped configuration leaves local_ntripc_user and local_ntripc_pwd empty, so the local NTRIP caster has no credentials set out of the box. posture Mitigation only - set local_ntripc_user and local_ntripc_pwd before enabling the local caster.
RTKBase installer (tools/install.sh) The installer pulls code that the pinned requirements file does not cover: 'pip install nmcli' and 'pip install git+https://github.com/Stefal/sim-modem.git' (a git URL with no tag or commit), plus 'pip install --upgrade pip setuptools wheel', all served through the third-party piwheels index. posture Mitigation only - pin these installs to versions or commits and review the sources before running install.sh.
RTKBase web interface The web GUI ships with the published default password 'admin' and its default PBKDF2 hash baked into settings.conf.default, and it is served over plain HTTP on port 80, so anyone who can reach the base station can log in and change its settings until that password is changed. posture Mitigation only - change the web password at first boot; there is no TLS option, so keep the device off open networks.
socat receiver bridge (documented optional step) The documentation tells operators to expose the GNSS receiver's serial port with 'sudo socat tcp-listen:128,reuseaddr /dev/ttyS1,b115200,raw,echo=0', an unauthenticated TCP listener on port 128 that lets anyone on the network drive the receiver directly. posture Mitigation only - bind the listener to localhost or reach it through an SSH tunnel, and stop it as soon as the configuration session ends.

What this means for your lab

This base station is meant to sit on a network and hand out correction data, and out of the box it is not safe to expose. Its web control panel answers on the ordinary web port with the password 'admin', which is printed in the project's own documentation, and the connection is plain HTTP, so anyone who can reach the device on your campus network can log in, change the base coordinates, read its data, or redirect where it streams to - and anyone watching the network can read the password as you type it. The optional 'socat' diagnostic step in the instructions opens a second door with no password at all, straight onto the GNSS receiver. On top of that, all 41 of the Python packages the web application pins were checked this run and 10 of them have published security bugs, including several in the very components that serve the web page and its live updates; 31 came back clean. What to do: change the web password before the device ever touches a network, put it on an isolated segment or VLAN of its own (not the campus wireless), leave the socat bridge off except while you are actively configuring the receiver, update the listed Python packages, and talk to campus IT before connecting it - a device that publishes its own location and accepts remote configuration is exactly the sort of thing they want to know about.

Not checked

  • Armbian_RTKBase SBC image: unpinned - the documented URL always resolves to the latest GitHub release, so there is no version to check
  • pi-gen RTKBase image: unpinned - the documented URL always resolves to the latest GitHub release, so there is no version to check
  • RTKLIB-EX v2.5.0 (str2str, rtkrcv, convbin): compiled from a GitHub source tag; no vulnerability database covers it, so this is 'not examined', not 'clean'
  • 18 apt system packages (git, build-essential, pps-tools, python3-pip, python3-dev, python3-setuptools, python3-wheel, libsystemd-dev, bc, dos2unix, socat, zip, unzip, pkg-config, psmisc, avahi-daemon, chrony, gpsd): installed with 'apt install -y' and no version pins; the version is whatever the OS ships, so there is nothing fixed to look up
  • gpsd: the project asks for '>= 3.2', a range rather than a pin, and installs it from apt
  • pip, setuptools, wheel (installer bootstrap): installed with 'pip install --upgrade', so the version is whatever is current at install time
  • sim-modem: installed from 'git+https://github.com/Stefal/sim-modem.git' with no tag or commit pin and no registry release to look up

Parts

Part Spec/Package Status Stock Price Source
GentleBOX JE-200 enclosure Outdoor weatherproof box with cable glands readily available — $19.15 Retail — Jirous GB-JE-200
Raspberry Pi 3 Model B+ — SC0073 SBC 1.4 GHz 4-core 1 GB, 85.09 × 55.88 mm Not For New Designs 14,996 $40.00 DigiKey
Orange Pi Zero (512 MB) — alternative SBC Ultra-compact SBC, 48 × 46 mm, 26-pin header readily available — $24.97 Retail (Orange Pi Zero LTS 512 MB listed at $31.49)
u-blox ZED-F9P receiver, breakout board Carrier board with USB, SMA, PPS/UART header readily available at board level 319 $275.00 DigiKey — SparkFun GPS-15136, the carrier the lab names. Bare module also Active: ZED-F9P-04B $127.42, stock 6,136. Drotek's own board and the Ardusimple simpleRTK2B were not priced this run.
Septentrio mosaic-X5 — alternative receiver Breakout / dev board, USB + IP interface available, high cost 19 $649.95 DigiKey — SparkFun GPS-28766. Bare module 410546, $625.00, stock 3,214.
Unicore UM980 / UM982 — alternative receiver Carrier breakout, USB/UART, SMA readily available — $201.92 Retail (listings from $150.00 to $213.80)
DA910 multi-band GNSS antenna Survey dome, TNC female, active LNA 3–12 V not found this run — — No DA910 listing returned; see Substitutes
Antenna RF cable — Amphenol 115101-09-06.00 Snapshot needs SMA male to TNC male, 1–5 m, 50 Ω wrong spec (BNC to BNC, 6 in) and 0 distributor stock 0 $24.81 DigiKey; all five ECIA distributors out of stock. See Substitutes
TRENDnet TPE-115GI PoE+ injector 802.3at midspan, 100–240 V AC in available, single source 40 $34.00 DigiKey (listed by VEC Supply); no ECIA distributor carries it
TRENDnet TPE-104GS PoE splitter Gigabit splitter, 5 V/9 V/12 V selectable, 2 A Obsolete 30 $25.00 DigiKey; no ECIA distributor carries it. See Substitutes
DC barrel-to-micro-USB adapter cable 5.5 × 2.1 mm female barrel to micro-USB male readily available — $5.99 Retail, from $1.90; the ≥ 2.5 A rating is not stated in any listing
PPS timing / ground jumper wires 2.54 mm female-to-female DuPont, 2 conductors readily available — $1.80 Retail — 40-piece pack, 20 cm
USB interconnect cable — Tensility 10-00648 USB 2.0 A to micro-USB, short assembly readily available 123 $3.51 DigiKey
Ethernet cable — L-com TRD855SCR-10 Cat5e shielded RJ45-RJ45, 10 ft available; not stated outdoor-rated 83 (Heilind) $36.39 DigiKey; ECIA: Heilind 83 @ $42.86, ICC 16, Mouser 546 on order @ $33.36
MicroSD card — SanDisk SDSQQNR-032G-GN6IA Class 10 / UHS-I, ≥ 16 GB exact part number badly overpriced — $127.63 Retail; DigiKey returns no product. See Substitutes

Substitutes

For part Substitute Differences Verified Judgment
Raspberry Pi 3 Model B+ (SC0073, NFND) SC0022 — Pi 3 Model B, $35.00, stock 18,155 Slower CPU (1.2 GHz vs 1.4 GHz 4-core, same 1 GB RAM) and 10/100 rather than the B+'s faster Ethernet — neither matters for one RTCM stream. Board outline 85.60 × 56.50 mm vs 85.09 × 55.88 mm: same mechanical class, both inside the lab's 85 × 56 mm figure. The lab names "Raspberry Pi 3 Model B (or Model B+)" as its reference build. Verified: board dimensions, CPU/RAM class, lifecycle and stock (DigiKey parametrics). Not verified: that DigiKey's order code SC0022 carries the exact "Model B" marketing name; GPIO 18 PPS pin assignment on the substitute. Acceptable — the lab's own alternative primary, Active and plentiful.
TRENDnet TPE-104GS (Obsolete) Tycon POE-SPLT-BT-UNI-P, $69.25, stock 381 Input 802.3af/at/bt, 44–57 V — meets the lab's 36–57 V. Selectable 5 V/9 V/12 V/24 V output — meets the 5 V rail. 14 A / 90 W output vs the original's 2 A — exceeds the ≥ 2.4 A requirement. Power budget: on 802.3af the device gives only 12 W total, below the Pi 3 B+ 12.5 W peak, so it must run off the BOM's 802.3at injector (24 W). DC output is a wire terminal block, not a barrel jack — the barrel-to-micro-USB adapter no longer mates. Larger: 119.4 × 86.4 × 27.9 mm DIN-rail housing vs 83.8 × 63.5 × 22.1 mm. Wider temperature range (−40 to +75 °C vs 0 to +40 °C) — exceeds. Verified: 802.3af/at/bt input, selectable 5 V output and the af/at power budget (manufacturer product page fetched this run); input range, output voltages, output current, temperature and dimensions (DigiKey parametrics). Not verified: that the 5 V rail sustains 2.4 A while the pass-through PoE port is also loaded; mechanical fit inside the JE-200. Acceptable with two caveats — pair with the 802.3at injector, and check enclosure space.
DA910 antenna (not found) SparkFun SPK6618H — DigiKey 21801, $179.69, stock 255 Bands L1/L2/L5/E6 across GPS, GLONASS, Galileo, BeiDou — meets and exceeds the lab's L1/L2 requirement. TNC female connector — matches, so the same SMA-to-TNC cable applies. 5/8"-11 TPI survey thread — matches the lab's threaded bottom mount. NGS-certified (SFESPK6618H). Verified: connector type and gender, band and constellation coverage, mount thread (SparkFun product page fetched this run); frequency ranges 1.15–1.278 GHz and 1.55–1.61 GHz, lifecycle, price, stock (DigiKey). Not verified: the ≥ 28 dB LNA gain and the 3.0–12.0 V bias range — neither figure appears in the parametrics or the fetched page. Acceptable, pending a datasheet check of gain and bias voltage.
Amphenol 115101-09-06.00 (wrong spec, no stock) Siretta ASMZG500A058L13, $50.55, stock 70 SMA male to TNC male, both free-hanging in-line — matches the receiver's SMA female and the antenna's TNC female. 16.4 ft (5 m), the top of the lab's 1–5 m range. Frequency to 6 GHz vs the required ≥ 1.6 GHz — exceeds. Verified: both connector genders, mounting style, maximum frequency and length (DigiKey parametrics and description); lifecycle, price, stock (DigiKey). Not verified: 50 Ω characteristic impedance and the outdoor/UV rating — neither is in this part's parametrics. Acceptable for the RF path; weatherproof the antenna-end connection and confirm impedance on the datasheet. Rejected on the evidence: RF Solutions CBA-TNCF-SMAM / -SMAMR (TNC female bulkhead, 7.8 in — wrong gender and length) and McGill RG223-SF-TM (SMA female — wrong gender at the receiver).
SanDisk SDSQQNR-032G-GN6IA (overpriced) SanDisk High Endurance, $22.99 or SanDisk Max Endurance 32 GB SDSQQVR-032G, $37.11 Same family, same 32 GB capacity class; the lab allows any high-endurance Class 10 / U1 card of 16 GB or more. Verified: nothing beyond listing titles and prices — these are retail search results and no product page was fetched. Not verified: endurance class, capacity and speed grade of the specific listings. Plausible, unverified — buy from a reputable seller and check the card's endurance rating on the packaging.

Verify any substitute against its datasheet before ordering.

Other dependencies

  • Fabrication: none. The build is entirely commercial off-the-shelf — no PCB, Gerber, drill or board CAD files. The only mechanical work is drilling the GentleBOX JE-200 baseplate to mount the SBC and the receiver carrier.
  • github.com/Stefal/rtkbase — the installer script and release tarball the lab downloads from. Reachable: files at tag v2.7.0 were fetched successfully this run.
  • github.com/rtklibexplorer/RTKLIB — the source archive the installer pulls. Referenced by the fetched installer, but the archive itself was not downloaded — not checked.
  • MapTiler Cloud (maptiler.com) — optional aerial map tiles in the GUI, needs a registered API key — not checked.
  • OpenStreetMap tile servers — the GUI's default map tile provider — not checked.
  • caster.centipede.fr:2101 — the default upstream NTRIP caster the base station streams to — not checked.

Watch list

  • TRENDnet TPE-104GS — obsolete with 30 pieces at a single distributor and no authorized channel behind it; expect this to be gone by the next check. The Tycon substitute is the durable answer.
  • TRENDnet TPE-115GI — 40 pieces at one distributor, no ECIA coverage. Not a problem yet (any 802.3at midspan will do), but the exact part is one order away from unavailable.
  • Raspberry Pi 3 Model B+ (SC0073) — Not For New Designs, 364-day factory lead time at RS, supply-chain risk rated High. Today's 14,996 pieces are the tail of the run.
  • u-blox ZED-F9P-02B — already Not For New Designs; the -04B, -05B and -15B variants are the ones to buy.
  • DA910 antenna — no retail presence found at all; treat it as gone unless the instructor knows a vendor.
  • SanDisk SDSQQNR-032G-GN6IA — no distributor stock and a five-times-market asking price; the exact part number is effectively obsolete even though equivalent cards are cheap.
Snapshot What the lab depended on when it was uploaded — the baseline the readiness checks research against.

This document is an environmental and temporal dependency analysis for the RTKBase GNSS RTK Base Station project.

The RTKBase system is an autonomous, headless multi-band GNSS Real-Time Kinematic (RTK) base station and NTRIP caster orchestrator. It couples an embedded Linux single-board computer (SBC) with a multi-frequency GNSS receiver module, an active multi-band external antenna, and a Power over Ethernet (PoE) split power subsystem, all mounted inside an outdoor weatherproof enclosure. The electrical architecture is organized around three primary DC voltage domains: incoming 48 V nominal 802.3af/802.3at PoE power supplied via an external Cat5e/Cat6 Ethernet line; a 5.0 V DC (±5%) main system rail delivered by an active PoE extractor/splitter via micro-USB or DC barrel jack to supply the host SBC and GNSS receiver USB bus; and a 3.3 V DC logic domain on the SBC GPIO header used for Pulse-Per-Second (PPS) / Timepulse hardware interrupt synchronization and UART serial communications.

Bill of Materials

Enclosure

  • Identity: GentleBOX JE-200 (outdoor waterproof plastic enclosure with pre-drilled cable gland entries for antenna and Ethernet cables)
  • Quantity: 1
  • Footprint/package: Weatherproof mast/wall-mount enclosure with integrated cable glands
  • Electrical constraints: Non-conductive UV-resistant enclosure; passive environmental protection (IP65 or higher rated)
  • Substitution latitude: Any waterproof outdoor electronics enclosure providing sufficient internal volume for SBC, GNSS receiver, and PoE splitter, with at least two cable glands (one RF coaxial, one RJ45).
  • Operated control: No
  • Sourcing plan: retail shopping search: GentleBOX JE-200 outdoor enclosure

Host Single-Board Computer (Primary Reference Build)

  • Identity: Raspberry Pi Foundation Raspberry Pi 3 Model B (or Model B+)
  • Quantity: 1
  • Footprint/package: Single-board computer, 85 mm x 56 mm, with 40-pin GPIO header, 4x USB-A, 1x 10/100 Ethernet, Micro-USB power input
  • Electrical constraints: Supply voltage 5.0 V DC (±5%) via Micro-USB or 5 V pin; peak current draw 2.5 A; 3.3 V CMOS logic on GPIO 18 (PPS input pin)
  • Substitution latitude: Orange Pi Zero (512MB RAM), Orange Pi Zero 2, or Orange Pi Zero 3 are documented first-class supported alternatives. Any Debian-compatible Arm Linux SBC with at least 512 MB RAM, an Ethernet port, at least one USB or UART port, and a hardware PPS-capable GPIO pin can substitute.
  • Operated control: No
  • Sourcing plan: distributor lookup: RASPBERRY PI 3 MODEL B+

Alternative Single-Board Computer (Documented Secondary Build)

  • Identity: Xunlong Orange Pi Zero (512MB RAM version)
  • Quantity: 1 (alternative to Raspberry Pi 3)
  • Footprint/package: Ultra-compact SBC, 48 mm x 46 mm, 26-pin header, 10/100 Ethernet, Micro-USB power input
  • Electrical constraints: Supply voltage 5.0 V DC (2 A recommended) via Micro-USB or header; 3.3 V CMOS logic on pin PA19 (PPS timing input)
  • Substitution latitude: Functional drop-in alternative explicitly documented in RTKBase build instructions; requires Orange Pi Armbian OS overlay configuration.
  • Operated control: No
  • Sourcing plan: retail shopping search: Orange Pi Zero 512MB

GNSS Receiver Module (Reference Build)

  • Identity: Drotek U-Blox ZED-F9P RTK GNSS Module (breakout board incorporating U-Blox ZED-F9P multi-band receiver IC)
  • Quantity: 1
  • Footprint/package: Breakout board module with USB connector, SMA RF antenna connector, and pin headers (PPS, TX/RX UART, 5V, GND)
  • Electrical constraints: Operating voltage 5.0 V DC via USB or 3.3 V to 5.0 V via pin header; 3.3 V logic on UART and Timepulse (PPS) output pin; RF input 50 Ω matched, active antenna bias 3.3 V to 5 V
  • Substitution latitude: Software supports auto-detection and direct configuration for U-Blox ZED-F9P (any manufacturer's breakout board such as SparkFun GPS-15136 or Ardusimple simpleRTK2B), Septentrio Mosaic-X5, Unicore UM980, and Unicore UM982. Other receivers outputting standard RTCM 3.x or raw GNSS data streams can be manually configured.
  • Operated control: No
  • Sourcing plan: distributor lookup: ZED-F9P

Alternative GNSS Receiver Module (Documented Septentrio Option)

  • Identity: Septentrio Mosaic-X5 (breakout / dev board version)
  • Quantity: 1 (alternative to ZED-F9P)
  • Footprint/package: Multi-pin evaluation/breakout board with USB, Ethernet/IP interface, and antenna connector
  • Electrical constraints: Supply voltage 3.3 V to 5.0 V DC; integrated IP interface running on internal address 192.168.3.1 via virtual Ethernet over USB
  • Substitution latitude: Explicitly supported in configuration files and auto-detection routines.
  • Operated control: No
  • Sourcing plan: distributor lookup: MOSAIC-X5

Alternative GNSS Receiver Modules (Documented Unicore Options)

  • Identity: Unicore Communications UM980 / UM982 multi-channel high-precision GNSS receiver modules (on carrier breakout board)
  • Quantity: 1 (alternative to ZED-F9P)
  • Footprint/package: Breakout module with USB / UART serial interfaces and RF antenna connection
  • Electrical constraints: Operating voltage 3.3 V to 5.0 V DC; 3.3 V UART logic levels
  • Substitution latitude: Explicitly supported in RTKBase automated configuration script.
  • Operated control: No
  • Sourcing plan: retail shopping search: Unicore UM980 receiver board

Active Multi-Band GNSS Antenna

  • Identity: DA910 High-Precision Multi-Band GNSS Survey Antenna
  • Quantity: 1
  • Footprint/package: Outdoor weatherproof survey dome antenna with threaded bottom mount and female TNC connector
  • Electrical constraints: Reception frequencies for GPS L1/L2, GLONASS G1/G2, BeiDou B1/B2/B3, Galileo E1/E5b/E6; active LNA supply voltage 3.0 V to 12.0 V DC (phantom powered via coaxial cable); 50 Ω impedance
  • Substitution latitude: Any high-precision multi-band active GNSS antenna supporting at least dual frequency (L1/L2 or L1/L5) covering GPS, GLONASS, Galileo, and BeiDou with suitable active gain (≥ 28 dB) and high multipath suppression.
  • Operated control: No
  • Sourcing plan: retail shopping search: DA910 GNSS antenna

Antenna RF Interconnect Cable

  • Identity: Outdoor low-loss 50 Ω coaxial cable assembly, SMA male to TNC male
  • Quantity: 1
  • Footprint/package: Flexible coaxial cable (RG58, RG316, or low-loss LMR195/LMR200 equivalent) terminated with straight SMA male on receiver end and straight or right-angle TNC male on antenna end
  • Electrical constraints: 50 Ω characteristic impedance, frequency response up to at least 1.6 GHz, rated for continuous outdoor UV and moisture exposure
  • Substitution latitude: Connector genders must match specific receiver board connector (usually SMA female) and antenna connector (usually TNC female). Length typically 1 to 5 meters depending on mast configuration.
  • Operated control: No
  • Sourcing plan: distributor lookup (representative example — sources give spec only): Amphenol 115101-09-06.00

Power over Ethernet (PoE) Injector

  • Identity: TRENDnet TPE-115GI (Gigabit Power over Ethernet Plus / PoE+ Injector)
  • Quantity: 1
  • Footprint/package: Standalone AC mains powered desktop unit with AC power input plug, 1x Gigabit Data In RJ45 port, 1x Gigabit PoE/Data Out RJ45 port
  • Electrical constraints: Input 100-240 V AC 50/60 Hz; output compliant with IEEE 802.3af (15.4 W) or IEEE 802.3at PoE+ (30 W), 48 V to 56 V DC on Ethernet pins 4,5(+) and 7,8(-) or 1,2(+) and 3,6(-)
  • Substitution latitude: Any standard IEEE 802.3af or 802.3at compliant PoE/PoE+ midspan injector delivering at least 15.4 W over Cat5e or higher cable.
  • Operated control: No
  • Sourcing plan: distributor lookup: TPE-115GI

Power over Ethernet (PoE) Splitter / Extractor

  • Identity: TRENDnet TPE-104GS (Gigabit PoE Splitter)
  • Quantity: 1
  • Footprint/package: Compact enclosure with 1x Gigabit PoE In RJ45 port, 1x Gigabit Data Out RJ45 port, 1x DC power output barrel jack (with selectable 5V/9V/12V switch)
  • Electrical constraints: Input compliant with IEEE 802.3af/at (36 V to 57 V DC); output switchable to 5.0 V DC at up to 2.0 A (10 W) or 2.5 A depending on revision
  • Substitution latitude: Any active 802.3af/at Gigabit PoE splitter capable of regulated 5.0 V DC output at ≥ 2.4 A (e.g. 5V PoE micro-USB splitters).
  • Operated control: Set-once voltage selection switch (MUST be set to 5V; must not be operated during service).
  • Sourcing plan: distributor lookup: TPE-104GS

DC Power Adapter Cable / Converter

  • Identity: DC Barrel Jack to Micro-USB Plug Adapter Cable
  • Quantity: 1
  • Footprint/package: 5.5 mm x 2.1 mm (or 5.5 mm x 2.5 mm matching TPE-104GS splitter DC jack) female barrel to Micro-USB male plug
  • Electrical constraints: Continuous current rating ≥ 2.5 A at 5.0 V DC
  • Substitution latitude: Any barrel-to-micro-USB or barrel-to-USB-C cable (depending on target SBC power port) capable of carrying 2.5 A without excessive voltage drop.
  • Operated control: No
  • Sourcing plan: retail shopping search: 5.5mm 2.1mm DC barrel female to micro USB male cable

PPS Timing and Ground Interconnect Wiring

  • Identity: 24 AWG to 28 AWG insulated stranded hookup wire jumper with female DuPont sockets (or soldered direct wire)
  • Quantity: 2 conductors (1x Timepulse signal, 1x Signal Ground)
  • Footprint/package: 0.1 inch (2.54 mm) single-pin female DuPont headers or solder tails
  • Electrical constraints: 3.3 V CMOS pulse signal (< 5 mA current); connects GNSS receiver Timepulse pin to SBC GPIO (Raspberry Pi GPIO 18, Orange Pi Zero PA19) and receiver GND to SBC GND
  • Substitution latitude: Any standard 0.1-inch pitch female-female jumper wires.
  • Operated control: No
  • Sourcing plan: retail shopping search: 2.54mm female to female DuPont jumper wire

USB Interconnect Cable

  • Identity: USB 2.0 Type-A to Micro-USB (or Mini-USB, depending on GNSS receiver module connector) cable
  • Quantity: 1
  • Footprint/package: Cable assembly, length 15 cm to 30 cm
  • Electrical constraints: 5.0 V DC VBUS power delivery (up to 500 mA) and USB 2.0 differential signaling (D+/D-)
  • Substitution latitude: Connector must physically match GNSS breakout board (Drotek modules use Micro-USB or Mini-USB; Ardusimple simpleRTK2B uses Micro-USB).
  • Operated control: No
  • Sourcing plan: distributor lookup (representative example — sources give spec only): Tensility 10-00648

Ethernet Cable (Outdoor Run)

  • Identity: Category 5e or Category 6 UTP/STP outdoor UV-resistant patch cable terminated with RJ45 8P8C plugs
  • Quantity: 1 (length as required by installation)
  • Footprint/package: Standard RJ45 modular plug to RJ45 modular plug
  • Electrical constraints: Rated for IEEE 802.3af/at PoE power transport (24 AWG solid or stranded copper preferred) and Gigabit 1000BASE-T data transmission
  • Substitution latitude: Any standard outdoor-grade Cat5e/Cat6 patch cable.
  • Operated control: No
  • Sourcing plan: distributor lookup (representative example — sources give spec only): L-com TRD855SCR-10

MicroSD Flash Memory Card

  • Identity: Class 10 / UHS-I MicroSDHC or MicroSDXC flash card, minimum 16 GB capacity
  • Quantity: 1
  • Footprint/package: MicroSD standard form factor
  • Electrical constraints: Standard 3.3 V SD bus interface
  • Substitution latitude: Any high-endurance, Class 10/U1 MicroSD card compatible with Raspberry Pi or Orange Pi SBCs.
  • Operated control: No
  • Sourcing plan: distributor lookup (representative example — sources give spec only): SanDisk SDSQQNR-032G-GN6IA

Software and network dependencies

Operating System and Base Platform Images

  • Debian GNU/Linux

    • Name: Debian Linux
    • Repository / Image URL: https://www.debian.org / official distribution repositories
    • Version: ≥ 12 (Bookworm)
    • Where the version came from: stated in documentation (RTKBase_README.md line "Requirements: Debian base distro >= 12 (Bookworms)")
    • Version pinning: Not pinned to a point release (floating range ≥ 12)
    • Check plan: support-status lookup: Debian 12

  • Armbian RTKBase Custom Image

    • Name: Armbian_RTKBase (for Raspberry Pi, Orange Pi Zero, Orange Pi Zero 2, Orange Pi Zero 3)
    • Repository / Image URL: https://github.com/Stefal/build/releases/latest
    • Version: latest
    • Where the version came from: stated in documentation (RTKBase_README.md)
    • Version pinning: Unpinned (points to latest GitHub release)
    • Check plan: not checkable: release URL points to dynamic latest release asset

  • Raspberry Pi OS via pi-gen

    • Name: pi-gen RTKBase image
    • Repository / Image URL: https://github.com/jancelin/pi-gen/releases/latest
    • Version: latest
    • Where the version came from: stated in documentation (RTKBase_README.md)
    • Version pinning: Unpinned (points to latest GitHub release)
    • Check plan: not checkable: release URL points to dynamic latest release asset

Runtime Environment

  • Python
    • Name: Python 3
    • Repository / Image URL: https://www.python.org / Debian package repository
    • Version: ≥ 3.11
    • Where the version came from: stated in documentation (RTKBase_README.md line "Python >= 3.11")
    • Version pinning: Unpinned lower bound
    • Check plan: support-status lookup: Python 3.11

Operating System APT System Packages The following 18 packages are installed via Debian/Ubuntu apt-get package manager without pinned versions (sudo apt install -y <packages> in RTKBase_README.md and install.sh):

  • git (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • build-essential (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • pps-tools (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • python3-pip (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • python3-dev (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • python3-setuptools (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • python3-wheel (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • libsystemd-dev (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • bc (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • dos2unix (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • socat (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • zip (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • unzip (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • pkg-config (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • psmisc (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • avahi-daemon (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • chrony (version: not stated; where version came from: not stated; check plan: not checkable: unpinned apt package)
  • gpsd (version: ≥ 3.2; where the version came from: stated in documentation: "Install a gpsd release >= 3.2 or it won't work with a F9P"; check plan: not checkable: unpinned range)

External Core Applications Compiled from Source

Python Packages The application specifies 41 Python packages in its manifest file web_app_requirements.txt, along with installation bootstrap tools pip, setuptools, and wheel. All packages in web_app_requirements.txt are pinned to exact versions:

  • bidict / PyPI / 0.23.1 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: bidict / PyPI / 0.23.1
  • blinker / PyPI / 1.9.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: blinker / PyPI / 1.9.0
  • Bootstrap-Flask / PyPI / 2.5.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: Bootstrap-Flask / PyPI / 2.5.0
  • certifi / PyPI / 2025.8.3 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: certifi / PyPI / 2025.8.3
  • charset-normalizer / PyPI / 3.4.3 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: charset-normalizer / PyPI / 3.4.3
  • click / PyPI / 8.1.8 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: click / PyPI / 8.1.8
  • distro / PyPI / 1.9.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: distro / PyPI / 1.9.0
  • Flask / PyPI / 3.1.2 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: Flask / PyPI / 3.1.2
  • Flask-Login / PyPI / 0.6.3 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: Flask-Login / PyPI / 0.6.3
  • Flask-SocketIO / PyPI / 5.5.1 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: Flask-SocketIO / PyPI / 5.5.1
  • Flask-WTF / PyPI / 1.2.2 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: Flask-WTF / PyPI / 1.2.2
  • future / PyPI / 1.0.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: future / PyPI / 1.0.0
  • gevent / PyPI / 25.4.2 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: gevent / PyPI / 25.4.2
  • greenlet / PyPI / 3.2.4 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: greenlet / PyPI / 3.2.4
  • gunicorn / PyPI / 23.0.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: gunicorn / PyPI / 23.0.0
  • h11 / PyPI / 0.16.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: h11 / PyPI / 0.16.0
  • idna / PyPI / 3.10 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: idna / PyPI / 3.10
  • iso8601 / PyPI / 2.1.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: iso8601 / PyPI / 2.1.0
  • itsdangerous / PyPI / 2.2.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: itsdangerous / PyPI / 2.2.0
  • Jinja2 / PyPI / 3.1.6 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: Jinja2 / PyPI / 3.1.6
  • lxml / PyPI / 6.0.1 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: lxml / PyPI / 6.0.1
  • MarkupSafe / PyPI / 3.0.2 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: MarkupSafe / PyPI / 3.0.2
  • nmcli / PyPI / 1.5.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: nmcli / PyPI / 1.5.0
  • packaging / PyPI / 25.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: packaging / PyPI / 25.0
  • pexpect / PyPI / 4.9.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: pexpect / PyPI / 4.9.0
  • psutil / PyPI / 7.0.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: psutil / PyPI / 7.0.0
  • ptyprocess / PyPI / 0.7.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: ptyprocess / PyPI / 0.7.0
  • pystemd / PyPI / 0.13.4 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: pystemd / PyPI / 0.13.4
  • python-engineio / PyPI / 4.12.2 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: python-engineio / PyPI / 4.12.2
  • python-socketio / PyPI / 5.13.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: python-socketio / PyPI / 5.13.0
  • PyYAML / PyPI / 6.0.2 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: PyYAML / PyPI / 6.0.2
  • requests / PyPI / 2.32.5 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: requests / PyPI / 2.32.5
  • serial / PyPI / 0.0.97 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: serial / PyPI / 0.0.97
  • setuptools / PyPI / 80.9.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: setuptools / PyPI / 80.9.0
  • simple-websocket / PyPI / 1.1.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: simple-websocket / PyPI / 1.1.0
  • urllib3 / PyPI / 2.5.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: urllib3 / PyPI / 2.5.0
  • Werkzeug / PyPI / 3.1.3 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: Werkzeug / PyPI / 3.1.3
  • wsproto / PyPI / 1.2.0 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: wsproto / PyPI / 1.2.0
  • WTForms / PyPI / 3.2.1 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: WTForms / PyPI / 3.2.1
  • zope.event / PyPI / 5.1.1 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: zope.event / PyPI / 5.1.1
  • zope.interface / PyPI / 7.2 / pinned in web_app_requirements.txt / check plan: vulnerability lookup: zope.interface / PyPI / 7.2
  • Additional Python bootstrapping dependencies installed via python3 -m pip install --upgrade pip setuptools wheel: pip, setuptools, wheel are unpinned in RTKBase_README.md installation step 4. Check plan: not checkable: unpinned upgrade command.
  • Extra wheel repository utilized during pip install: https://www.piwheels.org/simple

Manifest Location

  • Requirements file path: web_app_requirements.txt (referenced during install as rtkbase/web_app/requirements.txt)
  • Configuration manifest: settings.conf.default

Network Exposure

  • Interface Attachment: The SBC joins the local network via Ethernet (RJ45 connected to PoE splitter) or integrated Wi-Fi.
  • Web GUI Service (rtkbase_web.service / Gunicorn + Flask): Listens on TCP port 80 (configurable via web_port=80 in settings.conf.default). Documentation states: "Open a web browser to http://ip_of_your_sbc... Default password is admin." Password authentication is enabled by default (web_authentification=true). Default PBKDF2-SHA256 password hash is hardcoded in settings.conf.default: pbkdf2:sha256:150000$kWdEE8eU$d30b1a75e5cf898684bad60b47a45a8058b6c33535560be005b6e0110b947cf6.
  • Septentrio Mosaic-X5 Web Proxy: Listens on TCP port 9090 (gnss_rcv_web_proxy_port=9090 in settings.conf.default), proxying the receiver's internal web interface at 192.168.3.1.
  • Raw GNSS Data Stream (str2str_tcp.service): Listens on TCP port 5015, bound by default to localhost 127.0.0.1 (tcp_host_addr='127.0.0.1', tcp_port='5015' in settings.conf.default). Feeds local RTKLIB consumers and GPSD.
  • NMEA Service (rtkbase_raw2nmea.service): Listens on TCP port 5014 (nmea_port='5014').
  • Local RTCM Server (str2str_rtcm_svr.service): Listens on TCP port 5016 (rtcm_svr_port='5016').
  • Local NTRIP Caster (str2str_local_ntrip_caster.service): Listens on TCP port 2101 (local_ntripc_port='2101'). Accepts user credentials defined by local_ntripc_user and local_ntripc_pwd.
  • Outbound NTRIP Streaming (str2str_ntrip_A.service, str2str_ntrip_B.service): Connects outbound via TCP to default caster caster.centipede.fr on port 2101 (svr_addr_a='caster.centipede.fr', svr_port_a='2101').
  • Receiver Diagnostic Bridging (Documented optional step): Documentation instructs students/operators to expose the GNSS serial port over the network via socat: sudo socat tcp-listen:128,reuseaddr /dev/ttyS1,b115200,raw,echo=0, exposing an unauthenticated TCP listener on port 128 for remote U-center management.
  • Zeroconf / mDNS Discovery: Broadcasts via avahi-daemon over UDP port 5353 using service definition /etc/avahi/services/rtkbase_web.service.
  • NTP / Time Synchronization: chrony disciplines local time via GPS SHM refclock and PPS (/dev/pps0); can be configured as a Stratum 1 NTP server listening on UDP port 123.
  • Remote Administration: Operator setup instructions require SSH/console access on standard TCP port 22.

Downloads and External Web Services

  • RTKBase Installer Script: https://raw.githubusercontent.com/Stefal/rtkbase/master/tools/install.sh (or dev branch https://raw.githubusercontent.com/Stefal/rtkbase/dev/tools/install.sh)
  • RTKBase Official Release Tarball: https://github.com/stefal/rtkbase/releases/latest/download/rtkbase.tar.gz
  • RTKLIB-EX Source Archive: https://github.com/rtklibexplorer/RTKLIB/archive/refs/tags/b34j.tar.gz
  • MapTiler Cloud Tile Service: External web API used optionally for aerial map layers in GUI; requires API key registered at https://www.maptiler.com/ and entered as maptiler_key in settings.conf.
  • OpenStreetMap Tile Servers: Default online tile provider accessed via GUI front-end at https://www.openstreetmap.org.
  • Centipede NTRIP Caster: Default upstream RTCM caster hosted at caster.centipede.fr:2101.

Fabrication Requirements

This system is constructed exclusively from commercial off-the-shelf (COTS) modules, single-board computers, and interconnection cables. There are no custom PCB design files (Gerber, drill, or board CAD files) required to fabricate or assemble this lab. Mast and enclosure mounting require standard mechanical drilling of the GentleBOX JE-200 baseplate to secure the SBC and receiver breakout carrier.