Crux Lexicon
The Crux Lexicon provides plain-language definitions and explains how each term is used within Crux projects and systems.
| Term | Definition |
|---|---|
| Atlas | Crux’s governed operational intelligence system for interpreting system state, coordinating workflows, and presenting actions or decisions. |
| Atlas Bridge | The CRUX wall-mounted interface between MeshCore radio communications, local device indications and the Atlas host system. |
| Bootloader | Firmware supporting startup and, depending on design, a supported method for updating device application software. |
| Bridge Node | A node that transfers approved information between two communications domains, interfaces, or operational systems. |
| CMSIS-DAP | A standard protocol enabling host debugging software to communicate with supported ARM debug probes. |
| Controlled Publishing | A publishing process in which content is reviewed, verified, staged, and approved before it reaches a public system. |
| Crux Karoo Observatory | Crux’s long-term observatory, research, education, and field-systems programme in the Karoo. |
| Crux Sensor Net | Crux’s distributed network for environmental sensing, resilient communications, node health monitoring, and public status reporting. |
| Daymark | A Crux interaction point that turns a recognised event or tap into a clear acknowledgement and next action. |
| Delivery Evidence | The recorded observations used to distinguish a locally accepted message from actual reception or acknowledgement at its intended destination. |
| DFU | DFUDevice Firmware Update: a method for transferring firmware to a device through a compatible update mechanism.Crux usage: After SWD bootloader restoration, the MeshCore USB Companion application was delivered using serial DFU.Open full definition: a method for transferring firmware to a device through a compatible update mechanism. |
| Evidence Vault | The protected repository for original engineering evidence and approved derivatives that support traceability, verification, and audit. |
| Firmware baseline | A documented, reproducible combination of firmware artifacts, compatible versions and acceptance checks for a target board. |
| Gateway Node | A network node that connects a local radio network to another system, service, or data path. |
| GNSS | The collective term for satellite constellations and augmentation systems used to determine position, navigation, and precise time. |
| Guardian | An Atlas supervision layer that compares independent observations of a service, interface and publishing path before reporting their operational state. |
| Host a Node | A Crux participation pathway through which an approved person or site provides a suitable location for a maintained network node. |
| IDCODE | Identification value read from an ARM debug port during low-level target communication. |
| Menhir | A vertical sentinel structure that combines orientation, public interaction, environmental sensing, communications, and local systems. |
| MeshCore | An open-source, off-grid mesh communications system that uses LoRa-capable nodes to relay messages across a network. |
| MeshCore USB Companion | A MeshCore firmware role that exposes a USB host interface for participating in and observing a MeshCore network. |
| NFC | A short-range wireless technology that allows compatible devices or tags to exchange information when brought very close together. |
| nRF52840 | Nordic Semiconductor ARM Cortex-M4F microcontroller and wireless system-on-chip. |
| Observer Node | A node that listens to network activity and records operational evidence without being the primary originator of that traffic. |
| Optical Blinders | Physical ribs or shielding around an indicator that limit stray or sideways visibility of its light. |
| PoE | A method of carrying electrical power and network data over the same Ethernet cabling. |
| pyOCD | Open-source host-side tools for debugging and programming supported ARM microcontrollers. |
| QR code | A two-dimensional machine-readable code that can open a link or carry a small amount of structured information. |
| Quiet Communications | A resilient communications approach favouring local autonomy, controlled network exposure and restrained human interruption. |
| RAK19007 | RAKwireless RAK19007RAKwireless WisBlock baseboard providing mechanical module connection, power/USB and access to core and expansion signals.Crux usage: The RAK4631 was seated on a RAK19007 and the target powered through its USB-C port during SWD programming.Open full definition providing mechanical module connection, power/USB and access to core and expansion signals. |
| RAK4631 | RAK4631WisBlock Core module combining a Nordic nRF52840 microcontroller and an SX1262 LoRa radio.Crux usage: The module used as a MeshCore USB Companion in the Atlas Bridge recovery campaign.Open full definition module combining a nRF52840Nordic Semiconductor ARM Cortex-M4F microcontroller and wireless system-on-chip.Crux usage: Processing device inside the RAK4631, accessed during recovery using SWD.Open full definition microcontroller and an SX1262Semtech LoRa transceiver IC for sub-GHz radio communications.Crux usage: Provides the RAK4631’s LoRa radio path in CRUX MeshCore nodes.Open full definition LoRa radio. |
| RAKDAP1 | USB-connected programmer/debugger providing CMSIS-DAPA standard protocol enabling host debugging software to communicate with supported ARM debug probes.Crux usage: The RAKDAP1 presents a CMSIS-DAP interface for host tools such as pyOCD.Open full definition access to ARM SWDSerial Wire Debug, an ARM debugging and programming interface using SWDIO, SWCLK and a common electrical reference.Crux usage: Provides a lower-level diagnostic path to the RAK4631 processor when ordinary USB access is unavailable.Open full definition targets. |
| Repeater Node | A node positioned primarily to receive and retransmit radio traffic, extending coverage between other nodes. |
| RUI3 | RAKwireless Unified Interface V3, a firmware/API environment for supported RAK modules. |
| Sanitised Status Export | A governed, privacy-conscious subset of operational observations prepared for publication outside the private Atlas system. |
| Single Serial Owner | The designated host process with exclusive access to a USB-connected MeshCore Companion serial interface. |
| SoftDevice | Nordic’s precompiled Bluetooth protocol stack used with compatible nRF52 applications and BootloaderFirmware supporting startup and, depending on design, a supported method for updating device application software.Crux usage: The recovery campaign restored a compatible UF2 bootloader environment before applying the MeshCore USB Companion firmware.Open full definition configurations. |
| Status Aperture | The narrow illuminated opening in the Atlas Bridge enclosure through which selected device conditions are made visible. |
| SWD | Serial Wire Debug, an ARM debugging and programming interface using SWDIO, SWCLK and a common electrical reference. |
| SX1262 | Semtech LoRa transceiver IC for sub-GHz radio communications. |
| UF2 | UF2USB Flashing Format, a firmware package format commonly supported by USB mass-storage bootloaders.Crux usage: UF2 0.4.4 was used in the recorded compatible RAK4631 bootloader baseline.Open full definition, a firmware package format commonly supported by USB mass-storage bootloaders. |
Only approved public Lexicon entries are included in this build.