SCK-2400 · Documentation · User Guide

SCK-2400 User Guide

SpaceCommsKit SCK-2400 — Ground Station User Guide

Version 1.12 — November 2026 SpaceCommsKit — https://spacecommskit.com


Overview

The SCK-2400 is a 2.4GHz RF communications board built on OpenLST roots, using the Texas Instruments CC2652P SimpleLink wireless microcontroller. It replaces the SCK-915's OpenLST packet protocol with CCSDS framing — the same packet standard used by real spacecraft — while keeping the proven payload architecture from SCK-915: a Raspberry Pi Pico payload board running GPS, barometric altimeter, camera, and SD card flight logging.

With the SCK-2400 Ground Station you can:

  • Send and receive CCSDS commands between a ground station and a remote board over 2.4GHz RF

  • View real-time telemetry — uptime, RX/TX counters, link status

  • Update remote firmware over RF using OAD (Over-Air Download) — a full firmware image transfers in about 85 seconds, runs on trial, and falls back to a known-good golden image automatically if it fails

  • Query the payload board for GPS position, barometric altitude, and temperature

  • Trigger camera snapshots and manage files on the payload SD card

  • Build and flash custom firmware to either board from the Ground Station app

Note: The SCK-2400 operates in the 2.4GHz ISM band. Check local regulations for power limits in your jurisdiction before field or high-power operation.


What You Need

Item Description
SCK-2400 Board ×2 CC2652P-based 2.4GHz transceiver (+20 dBm high-power TX) (one Ground Station board, one Remote board)
5 V / 2 A power supply ×2 One per board. The SCK-2400 has no USB port; it runs from its own 5 V supply
3.3 V USB-serial adapter Connects the Ground Station board's J4 (UART1) header to your PC at 921600 baud. FTDI- or CP2102-based adapters work; many CH340/PL2303 clones are unreliable at this speed
Antennas ×2 2.4 GHz antennas with SMA connectors
XDS110 debug probe (optional) Only needed to reflash boards over the J2 header, for example a TI LaunchPad with its debug jumpers removed
Raspberry Pi Pico payload board Runs GPS, altimeter, camera, and SD logging (optional but recommended)
SCK Ground Station software Windows application for commanding and monitoring

Both boards are identical SCK-2400 V3 boards. The firmware sets which one is the Ground Station (APID 0x010) and which is the Remote (0x011). A TI LAUNCHXL-CC1352P-2 LaunchPad can also act as the Ground Station board over its own USB port; see the Developer Guide.


Installation

  1. Run the installer or build from source — see the SCK-2400 Developer Guide for build instructions.

  2. Connect the Ground Station board to your PC through the USB-serial adapter on its J4 header (see Hardware Connections). The adapter appears as one COM port; select it in the Ground Station app. If you use a LaunchPad as the Ground Station, it exposes two COM ports instead: the lower-numbered one (e.g. COM8) is the one the app uses.

  3. Launch SCK Ground Station.

  4. Select "SCK-2400 (CCSDS)" from the Board dropdown in the top right of the application.

Quick Start

Quick Start Checklist:

  1. Power both boards from their 5 V supplies
  2. Connect the Ground Station board's J4 (UART1) header to your PC through the USB-serial adapter (see Hardware Connections)
  3. Select the adapter's COM port and click Connect
  4. Go to the Commands tab and click Get Telem
  5. You should see a tlm_beacon response with a green checkmark

Your boards may be running placeholder keys. Unless you sent us your own AES keys with your order, both boards ship with the public placeholder keys from the open-source firmware. They give no security: anyone with the source code can read and command your radios. Generate your own keys before any real use; see Encryption Keys.

If you see the green checkmark, your Ground Station board is alive and the link is working. To talk to a Remote board over RF, set the APID field to the remote board's address (e.g. 011) before sending commands — the Ground Station board relays the command over RF automatically.


Hardware Connections

Ground Station Board (APID 0x010)

The Ground Station board connects to your PC through a 3.3 V USB-serial adapter on its J4 (UART1) header, at 921600 baud. It must stay connected for the whole session: it relays all RF traffic between the Ground Station app and the Remote board.

J4 PinSignalConnect to
1GNDAdapter GND
2RX (DIO12)Adapter TX
3TX (DIO13)Adapter RX
4+3V3Not connected
5BACKDOOR (DIO6)Not connected
  • Power the board from its own 5 V / 2 A supply. Never power it from the adapter's 3.3 V pin: the adapter cannot supply the +20 dBm transmit peaks, and the board browns out.
  • TX goes to RX. Adapter TX goes to the board's RX and adapter RX to the board's TX. Some adapters label their pins for what they connect to, so if the board never answers, swap the TX and RX wires once before anything else.
  • Leave J4.5 open. Grounding it at reset starts the chip's ROM bootloader instead of the firmware (see Wired Recovery).

Remote Board (APID 0x011)

This is the board that flies on your mission, or sits across the room during bench testing. It connects via RF to the Ground Station board and, optionally, via UART to a Raspberry Pi Pico payload board.

Remote board → Pico wiring:

Remote Board Pin Pico Pin Function
J3.5 — TX (DIO5) GPIO1 (pin 2) UART TX → Pico RX
J3.4 — RX (DIO16) GPIO0 (pin 1) UART RX ← Pico TX
J3.1 — GND GND Common ground

Both boards run on 3.3V logic — no level shifter is required.

Power Requirements

Component Supply Typical Current
SCK-2400 V3 (each board) 5 V, from a supply rated 2 A Highest during +20 dBm TX
LAUNCHXL-CC1352P-2 (if used as Ground Station) 5 V USB ~100 mA idle, higher during RF TX
Raspberry Pi Pico 5V USB or 3.3V ~25mA typical
BMP581/MS5611 altimeter 3.3V <1mA
GPS NEO-6M 3.3V/5V ~50mA

Home Tab

The Home tab shows live telemetry from the connected and addressed board.

Field Description
Uptime Seconds since last boot
RX Count Packets received over RF
TX Count Packets transmitted over RF
VCC Supply voltage

Telemetry updates each time you click Get Telem on the Commands tab, or automatically if the board's autonomous beacon is enabled.


Commands Tab

Provides quick access to standard CCSDS commands.

Button Opcode Description
Get Telem 0x01 Request telemetry from the addressed board
Reboot 0x02 Reboot the addressed board
Beacon ON / OFF 0x04 Enable or disable the autonomous RF beacon

OAD (Over-Air Download) Controls

Control Description
Start OAD Streams the built firmware image to the addressed remote board over RF
Inter-chunk delay 10 ms to 100 ms, default 30 ms — controls streaming speed. Values below 30 ms are for link testing only
Flash Status Transfer progress, plus the trial state of the running image and whether a golden image is stored
Set Golden Image Store the running, confirmed firmware as the board's fallback image
Abort OAD Cancel an in-progress transfer and clear the flash slot

OAD performance: A full 312 KB firmware image transfers in about 85 seconds at the 30 ms default (measured on SCK-2400 V3 hardware, encrypted RF link). That is about 18% of a typical 8-minute LEO ground station pass, leaving time for acquisition, confirmation and telemetry.

The remote board reboots into the new firmware once the transfer completes and the image CRC is verified. The new firmware then runs on trial until it hears from the ground. See Firmware Updates, Failover & Recovery for how a failed update is rolled back automatically.


Custom Commands Tab

Lets you send any CCSDS command opcode with any payload. Commands persist between sessions in customcommands.json.

Pre-loaded payload board commands:

Name Opcode Payload Expected Response
PICO Ping 0x20 — PICO:ACK
PICO Read Temp 0x21 — TEMP:13.47C
PICO Snap 0x22 — SNAP:OK:snap_001.jpg:4617
PICO List Files 0x23 — LIST:snap_001.jpg,...
PICO Get GPS 0x27 — GPS:lat,lon,alt,sats,fix,hpa,baro_alt,temp_c
PICO Get Baro 0x28 — BARO:hpa,baro_alt,temp_c
PICO Beacon ON 0x29 01 BEACON:ON
PICO Beacon OFF 0x29 00 BEACON:OFF

Tip: The Pico transmits its own GPS+baro beacon autonomously every 10 seconds. If your responses occasionally look mixed up or garbled, send PICO Beacon OFF first, run your commands, then send PICO Beacon ON when finished.


GPS / Map Tab

Displays live position from the payload board's GPS and barometric altimeter on an interactive map.

Control Description
Get GPS Request a fresh GPS+baro fix on demand
Get Baro Request barometric data only
Beacon ON / OFF Toggle the payload board's autonomous 10-second beacon
Clear Track Clear the plotted flight track from the map
Export KML Save the current track as a KML file for Google Earth
Record Begin recording a flight session to disk
Replay Play back a previously recorded flight session

The map shows current position, altitude, ascent rate, GPS/baro altitude delta, and satellite fix status — updated live as beacon packets or on-demand GPS responses arrive.


Files Tab

A file manager for the payload board's SD card.

Before using the Files tab: send PICO Beacon OFF to prevent the autonomous beacon from interrupting file transfers.

Downloading a File

  1. Click Refresh List to retrieve the current SD card file listing
  2. Click a filename to select it
  3. Click Get File — the file transfers in 200-byte chunks over RF
  4. When complete, the file is saved locally and opens automatically

A typical flight log (.sckflight) or small JPEG transfers in a few seconds depending on RF conditions and file size.


Firmware Tab

Used to build, sign, and flash custom firmware for either board.

Building

  1. Set Project Dir to your sck2400_firmware CCS project folder
  2. Set Board Role — Ground Station (APID 0x010) or Remote (APID 0x011, 0x012, ...)

  3. Choose RF Power Mode — Bench (0 dBm, indoor/safe) or Max Power (field/HAB/LEO mission)

  4. Click Clean + Build

Always use Clean + Build after making source code changes. Stale object files are the most common cause of mysterious firmware behavior.

Flashing

  1. Verify the HEX File path points to the freshly built output
  2. Click Flash (or Build + Flash to do both in one step)
  3. The Ground Station merges the application image with the bootloader (BIM) automatically and programs the board over the XDS110 debug interface

After flashing, send 2–3 Get Telem commands before moving the board to remote RF operation to confirm the radio stack is healthy.

Firmware Updates, Failover & Recovery

An SCK-2400 remote board can be updated over the air during a pass, and a bad update cannot leave it dead. Each update is checked twice. It then runs on trial and is only kept if the board hears from the ground. If it never does, the board puts back a known-good golden image by itself. If even that is gone, a wired recovery path through the J4 header can reflash the chip from scratch.

SCK-2400 firmware update, failover and recovery flow An over-the-air update is verified twice, installed as a trial, and kept only if the board hears from the ground. After three unconfirmed boots the bootloader restores the golden image. If nothing valid remains, the ROM bootloader on J4 allows a full reflash. 1 · Ground station sends the update 128-byte chunks → external-flash candidate slot 2 · Received image CRC-16 matches? checked by the board at OAD END No Update refused Running firmware untouched; retry Yes 3 · Candidate marked ready OAD END ACK (status 0x00) · board resets 4 · BIM: image CRC-32 valid? computed over the copy in external flash No Not installed Board boots its current firmware Yes 5 · BIM installs and starts it copied to internal flash · trial boot 1 of 3 6 · Command from ground within 30 min? any valid command to this board confirms it Yes CONFIRMED Normal operation from here on Set Golden once you trust this build No — timeout, crash or watchdog 7 · Board resets BIM records another unconfirmed boot 8 · Three unconfirmed boots? counted in the candidate's metadata No — next trial boot Yes 9 · Candidate REJECTED BIM verifies the golden image CRC, then restores it to internal flash No golden image set? Nothing to revert to: the rejected image keeps running 10 · Board back on the golden image Flash Status: REJECTED · boots used 3 Last resort — no valid image anywhere The BIM never parks the chip in low-power mode: it waits about 10 s and resets, forever. Hold J4.5 (DIO6) low through a reset → the ROM bootloader starts on J4.2 / J4.3 (UART) → reflash the merged hex (BIM + app). Works even if internal flash is fully erased.

Blue: normal steps · dashed cyan: checks · green: good outcome · amber: automatic fallback · red: hands-on recovery.

Sending an Update

  1. Build the new firmware on the Firmware tab for the board you are updating. Choose the remote's role (for example Remote 1, 0x011), then click Clean + Build. Don't click Flash. The Ground Station patches the image header and CRC for you.
  2. On the Commands tab, set the APID to the remote board and click Flash Status. The board should reply with trial: confirmed (or none) and golden image: present.
  3. Click Start OAD and read the confirmation. It names the board the firmware was built for. If that doesn't match the APID box, the app offers to send it to the right board instead. A 312 KB image takes about 85 seconds at the default 30 ms inter-chunk delay.
  4. When the log shows image verified OK — board is rebooting..., wait. The Ground Station polls the board until it answers, which usually takes about 10 seconds. That first answer also confirms the new firmware.
  5. Click Flash Status again. You should see trial: confirmed boots used: 1.
  6. Once you have tested the new build and trust it, click Set Golden Image so it becomes the board's fallback. This takes about 7 seconds.

Set a golden image on every board before it flies. The automatic fallback can only restore a golden image that exists. With no golden image, a rejected update simply keeps running. Set Golden is part of provisioning.

What "On Trial" Means

A newly installed image has to prove the board can still talk to the ground. It does that by receiving any valid command addressed to that board, such as Get Telem. Until then it is on trial:

  • If no command arrives within 30 minutes, the board resets itself. A crash or a watchdog reset counts the same way.
  • Each of those resets uses up one of three trial boots.
  • After the third unconfirmed boot, the bootloader rejects the new image. It checks the golden image's CRC, restores it, and the board is back on the golden image at its usual address.

In practice, a build that crashes falls back within a few minutes. A build that runs but can't hear the ground falls back after about 90 minutes, roughly one LEO orbit. Either way the board comes back on its own, with no one at the bench.

Confirmation only proves the link works. A build that talks to the ground but has some other bug (for example a payload command) is confirmed and stays. To roll back a confirmed build, send the previous build with another OAD.

Reading Flash Status

TrialMeaningWhat to do
noneNo over-the-air update on recordNormal
PENDINGNew image installed, not yet confirmed (shows the boots used so far)Send Get Telem to confirm it
confirmedNew image accepted and runningNormal · Set Golden when you trust it
REJECTEDNew image never confirmed; board fell back to the golden imageFind out why the build failed before sending it again

golden image: present means a verified fallback is stored. NONE means no fallback exists. Run Set Golden Image.

Set Golden Image

Copies the firmware currently running on the addressed board into its golden slot, verifies every byte, and records it as the fallback. The board refuses the command and the log explains why if:

  • an OAD transfer is in progress, or
  • the running image is still on trial. Send Get Telem first to confirm it.

Only set golden firmware that you have tested on that board. Golden is the image the board trusts when everything else has failed.

Wired Recovery (J4 Header)

If no valid firmware is left anywhere, the bootloader doesn't give up. It waits about 10 seconds and resets, over and over. The chip's built-in ROM bootloader can then be used to reflash it over a plain 3.3 V USB-serial adapter:

J4 PinSignalConnect to
1GNDAdapter GND
2RX (DIO12)Adapter TX
3TX (DIO13)Adapter RX
4+3V3Leave unconnected if the board is powered
5BACKDOOR (DIO6)Jumper to GND to enter the bootloader
6RST (production V3)Momentary to GND to reset
  1. Connect the adapter (3.3 V logic only) and jumper J4.5 to GND.
  2. Reset the board. Tap J4.6 to GND, or power-cycle boards without the RST pin. The ROM bootloader starts instead of the firmware.
  3. Reflash the merged image (bootloader + application) using the steps in the Developer Guide, Section 2.4.
  4. Remove the J4.5 jumper, reset, and confirm Get Telem works. Then run Set Golden Image again.

With J4.5 held low the board will always start the ROM bootloader, so never leave the jumper fitted in flight. In normal use a pull-up resistor holds the pin high.

If the board is on the bench, a normal Flash over the J2 programming header (Firmware tab) does the same job faster. J4 recovery is for boards where J2 isn't reachable or the debug probe can't connect.


Provision Tab

One-time setup for new boards — flashes the bootloader (BIM) and sets the board's APID (address). BIM is permanent after initial flashing and is never overwritten by subsequent application or OAD updates.

Encryption Keys

Every packet between the boards is encrypted and authenticated with AES-128-CCM, using three keys built into the firmware. All boards that talk to each other must have the same three keys.

  • Placeholder keys. Boards ordered without your own keys ship with the public placeholder keys (all 0xFF). The build log shows security.h: using placeholder keys while they are in use. Placeholder keys are fine for a first bench test and nothing else.
  • Your own keys. Click Generate in the Provision tab. The app writes the keys into the firmware build for you; they are never committed to git.
  • Reflash every board. Rebuild and flash the Ground Station board and every Remote board with the new keys, then set the golden image on each (below). A board on different keys cannot talk to the others.
  • Back up your keys. Store them somewhere safe and offline. If they are lost, every board has to be reflashed over the cable with new keys.

If you sent us your keys and APIDs with your order, your boards were built and tested with them and are ready to use.

Last provisioning step: once the board's firmware has passed your tests, address the board and click Set Golden Image (Commands tab). Then confirm Flash Status shows golden image: present. A board without a golden image has no automatic fallback.


Troubleshooting

No reply to Get Telem on Ground Station board (0x010)

  • Check the COM port is the USB-serial adapter's (or the XDS110's on a LaunchPad Ground Station)
  • Swap the adapter's TX and RX wires once; a reversed pair is the most common cause

  • Confirm the board is on its own 5 V supply, the adapter's 3.3 V wire is not connected, and J4.5 is open

  • Rapid LED double-blink pattern indicates the bootloader is running without a valid application — reflash the application firmware

No reply to Get Telem on Remote board (0x011)

  • Confirm the Ground Station board (0x010) responds first — it relays RF commands

  • Boards should be at least a few feet apart during bench testing to avoid RF saturation

  • Try Get Telem 2–3 times — the first packet after boot is sometimes missed while the RF synthesizer stabilizes

PICO commands return no reply

  • Confirm the Pico is running main.py and showing beacon output on its serial console

  • Verify UART wiring: Remote board DIO5 → Pico GPIO1, DIO16 → Pico GPIO0

  • Send PICO Beacon OFF before other payload commands to avoid response collisions with the autonomous beacon

PICO responses look garbled or mixed up

  • This is the autonomous beacon racing with your command response. Send PICO Beacon OFF, wait a moment, then retry

OAD transfer fails or times out

  • Confirm the remote board responded to OAD Status before starting
  • If a transfer fails partway through, the Ground Station automatically retries once — re-erasing the flash slot and re-streaming

  • A failed or interrupted transfer never touches the running firmware — the new image is only installed after both CRC checks pass

  • Use the 30 ms default inter-chunk delay. Shorter delays can drop chunks on the RF link

Board silent after an update

  • Wait. If the new image can't hear the ground, it resets itself every 30 minutes. After three tries the board restores its golden image and answers again, about 90 minutes in the worst case. A build that crashes falls back within minutes

  • On the bench you can speed this up: each power-cycle uses up one trial boot

  • When it answers, Flash Status shows REJECTED. The update was rolled back

  • If it never comes back (no golden image was set, or the board is damaged), use wired recovery through J4

Set Golden Image refused

  • running image is still on trial — send Get Telem to confirm it, then retry

  • an OAD session is active — finish or abort the transfer first

  • Any flash error or verify mismatch — retry once. If it repeats, the board's external flash needs checking

Board unresponsive after a firmware flash

  • Confirm you flashed the merged hex (application + BIM), not the application-only hex — the Ground Station does this automatically via Build + Flash

  • A rapid 1-flash-pause-3-flash LED pattern after reset usually indicates BIM is running without a valid application image


Specifications

Parameter Value
RF Frequency 2.4GHz ISM band
Microcontroller (dev) Texas Instruments CC1352P1F3RGZ (LAUNCHXL-CC1352P-2)
Microcontroller (production) Texas Instruments CC2652P1FRGZ
RTOS TI-RTOS7
Protocol CCSDS Space Packet Protocol
OAD transfer (312 KB image) ~85 seconds @ 30 ms inter-chunk delay
Update failover Trial boot (3 boots, 30-minute confirm window) with automatic golden-image restore
Wired recovery ROM serial bootloader on J4 (backdoor DIO6, active low)
Cold boot time <40ms
Interface USB (XDS110), 921600 baud to Ground Station
Payload UART 115200 baud, ESP framing, to Raspberry Pi Pico

SpaceCommsKit SCK-2400 User Guide v1.13 For updates and source code see https://spacecommskit.com