Glossary
Action
Function that a component can be commanded to perform. For example: reboot a system, take a picture, start transmitting data, erase a parameter or set it tfo its original value. In the Ground software mission explorer, it is represented by a grey cog symbol and can be accessed by double-click.
Active Tasks View
Window in the Ground software that shows all tasks in progress, as well as status of previously performed tasks. Access via the button on the left hand side of the bottom bar or via Monitor → Activities.
ADCS
Attitude Determination and Control System. Satellite subsystem responsible for attitude control and determination of the spacecraft.
Aggregation
A defined list of parameters, to be efficiently bit-packed together. Can be associated with or used as inputs to different capabilities like logging, beacons, etc. In the Ground software, can be imported from a file or created in Housekeeping → New aggregation from builder.
Aggregator
Component that packs your data for logging or transfer. Needs an aggregation definition which can be imported from a file or created in Housekeeping → New aggregation from builder.
Archive
Historic store of activity with timestamps, including sent and received frames, packets, aggregations, parameters, events and actions. Manage via Housekeeping → Manage archive stores.
Argument
Variable needed by a method or action as an input in order to perform its intended function.
Asset
The object in orbit that you are trying to reach. Usually the spacecraft. Represented by a blue box symbol in the Ground software mission explorer. Make changes via drop-down menu in the toolbar or File → Mission Management.
Beacon
Component that broadcasts aggregated parameters to the ground. Transmits periodically. Needs an aggregator associated with it, so that it knows what to send. Make the association in Housekeeping → New beacon mapping.
Cascade Windows
Retrieve all the different windows you’ve opened and display them neatly alongside the main MCS window. Accessed via Help → Cascade Windows.
CCSDS
Consultative Committee for Space Data Systems. Forum for the development of spaceflight standards.
CCSDS COP1
Consultative Committee for Space Data Systems Communications Operation Procedure 1. The recommended standard automatic TC retransmission procedure for transferring space application data over a communications link (requires flight side support). In the Ground software, can be managed via Tools → CCSDS COP1.
CFDP
CCSDS File Delivery Protocol. Standard packet-level file transfer protocol for use in space, defined by the Consultative Committee for Space Data Systems.
Check
Defined function in the Ground software which verifies if a parameter value is appropriate for use. Definitions must be uniquely named and can flag a parameter in the logging pane as either a warning or error. Stored in a YAML file, provided when specifying an SCDB in File → Mission Management.
Check Housekeeping
Enables and disables housekeeping checks in the Ground software, from Housekeeping → Check Housekeeping. Employs checks specified in check file associated with SCDB. Any check violations appear in log view.
see SCDB
CLI
Command Line Interface. In the Ground software, the CLI provides an interactive console to test and execute Groovy scripts and is accessed via Monitor → Command Line Interface. In the FSDK, our Command-line tooling (codegen) is used for generating code and documentation relating to spacecraft operations.
Component
Re-usable software module that performs a related set of operations. Sometimes associated with a hardware component. Encapsulates functions and data, which are accessed via actions and parameters. In the Ground software mission explorer, they are represented by a grey brick symbol.
Connection
Communication link to a ground station or satellite (via ground station). In the Ground software, current links can be viewed in the “Connections” tab of the mission explorer. In this tab, can manage a connection point by right clicking on it and selecting “Configure”.
CSL
Clyde Space Limited (CSL) now trading as AAC Clyde Space (ACS).
see ACS
CSV
Data file of Comma-Separated Values. Can be used in the Ground software to save aggregations, logs and other useful things.
Data channel/ Storage channel
Fixed-capacity on-board data storage facility. Can be linear (when full, more data fails) or circular (when full, oldest data is replaced). Length of each row can be set to match data going into it.
Data pool
Temporary store of cached parameter values. Prevents data bus overloading when parameter is frequently accessed. Generally, the data pool version of a parameter should be used instead of the actual one. Must have a sampler configured to update values.
Decode
Translate received log from satellite, from transferable format into a human-readable format. Can create a definition for the decoder or use one defined for an aggregator. In the Ground software, access data log and event log decoders via Tools menu bar option.
Deployment
Collection of components, along with the connections between them, and any initialisation data they require to run.
Documentation
Description of what a selected entry in the Ground software mission explorer does. Displayed in bottom of mission explorer. Toggle display on/off via rightmost button next to search bar on mission explorer.
Event
Generated by on-board component to tell us that something important happened. Can trigger on-board behaviour. Will normally be logged by a logger.
Event Log
Shows all the events that occurred in the specified time range, and their source. Can be accessed in the Ground software via Monitor → Event Log, then click “Retrieve”.
Exception
Error, usually encountered when trying to do something on-board that failed, like access a parameter or invoke an action. Will normally be logged by a logger and the user will be notified.
FARM1
The flight side state machine handling the monitoring and requesting retransmission of missing TC frames for CCSDS COP1.
FDIR
Fault Detection Isolation and Recovery. Technique to detect faults and accurately isolate them.
FSDK
Flight Software Development Kit: Bright Ascension’s software for developing component-based on-board software which interoperates with the MCS.
see MCS
Gantt chart
Bar chart with time on the X axis, used to display schedules. In the Ground software, a Gantt chart displaying recent activities with respect to time can be found in Monitor → Activity Gantt chart.
Gen1
Generation One. The collective name for all Bright Ascension software products, including (but not limited to) the FSDK, MCS, and OBSW.
Get
Query the value of a parameter. Always available, usually used as getParameter (for example, getMessage will return the body of the message). May also have a getParameterLength accessor (for example, getMessageLength) which will return its length.
Graph
Displays historical parameter data as a graph of parameter value on the Y axis and time on the X axis. Accessed via the toolbar or monitor menu. Drag and drop parameters to the window to place them on the graph.
Groovy
A scripting language based on Java, and used by the Ground software for scripts which can be executed by the Ground Schedule.
GSN
Ground Station Network: A network of ground stations accessed via a third-party network service. Require additional credentials supplied by the provider to be set in the connection configuration.
HK
Housekeeping. Refers to data about the satellite and its health and safety. The Housekeeping tab in the mission explorer allows you to view and update the aggregations which are used by the on-board software to transmit housekeeping (system status) and other data.
ID
A numerical identifier assigned to each accessible on-board element at flight software build time. Each accessible entity has its own unique ID (component, action, parameter, event, exception, etc). Each build will generate a newset of fixed IDs. Can be shown in the mission explorer via a button next to the search bar.
JRE
Java Runtime Environment. The MCS requires JRE 11. Check which version you have in either Windows or Linux by typing java -version in a terminal.
Layout
Configuration of the dockable area of the Ground software GUI. Can switch between layouts that focus on different tasks. Accessed via Layouts tab of the mission explorer. Double-click to select a layout.
see GUI, Docking Area
LDT
Large Data Transfer protocol. Used for parameter transfers if supported by OBSW. Initiated by clicking uplink/downlink button of parameter in the Ground software.
Licence
A file containing a licence code that permits software usage. In the MCS, the file also contains the option to specify other information, such as IP address if running over HTTP proxy. Access details of your licence as well as licences for internal components of the MCS via Help → About then click “Licences”.
Logger
On-board component which periodically logs parameter or event data to a data channel. Performs get requests into a buffer, and when the buffer is full, writes to the data channel. Use an aggregator as an input for better efficiency.
Map
Map of the Earth in the Ground software on which useful features such as satellite tracks and ground stations can be visualised. Can be accessed from Monitor → Map.
MCS
Mission Control Software. The Bright Ascension desktop application used to operate a spacecraft running software generated from the Bright Ascension FSDK.
see FSDK
Mission explorer
Left-hand pane of the Ground software GUI. Allows you to view the mission tree. Tabs at the top allow you to switch between useful views: Asset, Connections, Layouts, Housekeeping and Ground.
see GUI
Monitor
Component that periodically checks that parameters are in a specified range, and raises events if the values go out of bounds. Functionally, keeps an eye on spacecraft health.
NACK
Also NAK. Negative acknowledgement response – the platform could not/did not do what you told it to do. The most common type of exception normally encountered.
Packet Monitor
View the current and historical packets of telemetry and telecommand going between the ground and the spacecraft. Accessed from Monitor → Packet Monitor. Can filter for a specific parameter(s) By clicking “Filter” and selecting the ones required. Pause button prevents further input from the current link.
Parameter
A value stored in an On-Board software component, which can be read (and sometimes written) via scripts, and via the Asset tab of the Ground software Mission Explorer.
Parameter (multi-row)
A 2D vector parameter which holds one data entry in each row. Can have a variable number of rows, stores data more efficiently than scalar parameters. Data is accessed by specifying the index/indices of the required row/row range.
Parameter Association File
YAML file in which you can link a calibration or check definition with its intended parameter in the Ground software. Provided when specifying an SCDB in File → Mission Management.
see YAML
Parameter Log
Historical view in the Ground software of the values of the parameters and when they changed. Can be accessed from Monitor → Parameter Log or Monitor → Parameter Table → Show as Log. Drag parameters from mission tree into window, then click “Retrieve”.
Parameter Table
View raw and calibrated values of parameters along with the timestamp of the most recent change. Accessed from Monitor → Parameter Table in the Ground software. Drag parameters from mission tree into window, then click “Retrieve”. Change in parameter values over time can be seen as a graph or log by clicking the appropriate button.
Polling (Ground Schedule)
A method to update the ground schedule without entering the Ground software, by configuring it to check regularly for new or updated schedule files.
Protocol properties
Properties to do with uplink and downlink communications. Can be adjusted from File → Protocol properties or by right-clicking an asset or target and clicking “Configure Asset/Target”. Switch between asset and targets using the drop-down menu at the top of the resulting pop-up window.
PUS
Packet Utilisation Standard. Relates to the utilisation of TMTC source packets for monitoring and remote control of components.
SCDB
Spacecraft database. Generated by tooling from flight software development kit. A file which contains a definition of the deployment. When loaded into the Ground software, provides it with a list of components, actions and parameters that it can access.
Schedule
A list of actions to be performed at specified times. Different types of schedules can be built from the builders found in Tools.
Script
Collection of Groovy commands to be executed. Can be executed via Monitor → Script Execution.
Set
Change the value of a parameter. Not available for read-only parameters such as current, temperature or uptime. Commonly set parameters include enable, which switches a component on or off.
Subsystem
A collection of related on-board subsystems and components. Represented by a yellow box symbol in the Ground software mission explorer. View details by double-clicking, or clicking on the arrow to expand the tree.
Synthetic Parameter
A parameter which does not have its own in-built value, but derives it from a combination of existing parameters. Read-only. Useful for monitoring metrics.
Synthetic Parameter Definition
The definition of a parameter which contains no new information, but is a combination of other existing parameters. Allows more flexibility than calibrations. Can be asset-level (restricted to accessing only the asset on which it is instanced) or mission-level (has access to entire mission). Can be described in a YAML file or made in the Ground software through Tools → Synthetic definition manager.
see YAML
Synthetic Parameter Instance
A created, named parameter, which applies a synthetic parameter definition. Accessible through the Ground software GUI like all other non-synthetic, read-only parameters, usually found in the Mission Explorer, under Ground → logical. Manage instances through Tools → Synthetic parameter manager.
see GUI
Target
The software entity on the asset that you will connect to. Usually a computer on the asset. Represented by green box symbol in the Asset tab in the mission explorer.
Time correlation
The conversion between ground UTC time and the satellite’s on-board clock. Can be configured via Tools → Show time correlation.