Secure Telemetry

  1. Home
  2. Secure Telemetry

Secure Telemetry & Internet Relay

The secure data-transfer part of a team telemetry project, designed, developed and tested independently during an engineering internship at the Cyprus Space Exploration Organisation. Other team members handled data collection and its use; this component moves the data safely between computers over the public Internet.

It consists of a sender, a relay, a receiver and a user interface. Delivery is authenticated and integrity-checked, every message is acknowledged, data waits in an offline queue when the link is down, and duplicates are rejected when it comes back. Everything is written to structured logs.

  • Category :Networking / Secure Systems
  • Stack :C++, Rust, Linux
  • Components :Sender, relay, receiver, user interface
  • Delivery :Authenticated, integrity-verified, acknowledged
  • Resilience :Offline buffering, duplicate rejection
  • Validation :Recovery tests across separate systems and networks
  • Status :Working prototype / source code not published

Core Features

The design goal was a data path that keeps working when the network does not: nothing is lost on a dropped link and nothing is processed twice after it recovers.

  • Authenticated delivery between sender, relay and receiver.
  • Integrity verification of every message.
  • Acknowledgement handling, so the sender knows what arrived.
  • Offline queues that hold data while the connection is down.
  • Duplicate detection and rejection after retransmission.
  • Structured logging for diagnosis.

“A telemetry link is only useful if it survives interruptions without losing or repeating data.”

Design Note - Reliability First

Architecture

The system is layered: a transport over the public Internet, a delivery protocol that adds authentication, integrity checks and acknowledgements, a queue-and-recovery layer that buffers and de-duplicates, and the user interface on top. The diagrams are conceptual and show the structure described in the project, not the source code, which is not published.

Delivery Flow

  • The sender prepares an authenticated message.
  • The message travels through the relay to the receiver.
  • The receiver verifies integrity and sends an acknowledgement.
  • If the link is down, the sender keeps the message in the offline queue.
  • After recovery the queue is resent and duplicates are rejected.
  • Every step is written to the structured log.

What It Shows

  • Network programming in C++ and Rust on Linux.
  • Designing for failure: recovery, buffering and de-duplication.
  • Testing across separate computers and networks.
  • Documenting issues and reporting progress with versioned releases.

Related Projects

Sound-to-Action Voice Commands

Sound-to-Action Voice Commands

Python / Audio ML / Local
Neuron: Offline Cognitive AI

Neuron: Offline Cognitive AI

Offline AI / Memory / Modular Architecture
Autonomous Drone Swarm “Like Bees”

Autonomous Drone Swarm “Like Bees”

Arduino / Swarm Intelligence / Vector

Project Summary

Send a direct message about this project and it will be delivered to my email.