SeaHawk-1 is an innovative ocean colour monitoring CubeSat, designed by the University of North Carolina. It was built with our Flight Software Development Kit to accelerate mission development and is taking full advantage of the benefits offered by our Mission Control Software.
SeaHawk’s colour sensor observes changes in ocean surface colour, which relates directly to the substances and the organisms within it. Captured daily, high-resolution observations of ocean colour changes can be used for multiple environmental and maritime applications.
Challeges
The SeaHawk project utilises a 3U CubeSat platform to observe the changing biology of the ocean surface and its implication for various maritime applications.
Limitations on computing platform
The payload of the spacecraft generates a large amount of data at 1.1GB for a full observation sweep, and requires a high performance x-band downlink. This large volume of generated data put significant limitations on the computing platform, meaning that there was a demand for the software to use as minimal computing resources as possible.
From the software perspective, the restriction on computing power was the main challenge in this mission.
NASA Near Earth Network (NEN)
The NEN is a global network of satellite ground stations which is normally used by much larger spacecraft. We believe this is the first time it was used by a CubeSat.
Reducing operational complexity
SeaHawk is unusual for a CubeSat because its payload and its platform are operated by two distinct groups using different operations centres. The satellite itself is commanded by AAC Clyde Space in Glasgow, Scotland, using our Mission Control Software product. Payload data is downlinked to the NEN and processed by NASA Goddard Space Flight Centre. Tasking requests are passed from the payload to the platform team but there was a desire to keep this interface as simple as possible. In addition, since this is a pilot mission, some aspects of the performance of the system were uncertain, so there was a need to remain flexible.
Solutions
Limitations on computing platform
The FSDK allows the operator full control over how often the software performs certain actions such as checking the status of a component, or sending health checks to the operations centre. So the operator can decide which elements of the mission need to be prioritised.
Flexibility is a crucial part of the software development process as requirements may change mid-development. The FSDK allowed software to be developed from previous iterations, so that the flight package design could be easily changed without rewriting from the ground up.
NASA Near Earth Network (NEN)
In order to enable NEN interactions, we needed to ensure that our transmissions followed the internationally-recognised CCSDS standards, which was easy to achieve as the FSDK has an existing library of CCSDS protocol implementations to draw on.
Reducing operational complexity
In order to help reduce operational complexity, we ensured that all of the necessary platform data was included in the payload set so it can be correctly processed. We also automated the on-board processing and management of payload data, while providing flexibility to respond to the changing needs of the mission. Coupled with the on-board scheduling and scripting capabilities provided by our flight and ground software, it is possible for the majority of spacecraft operations to be automated.
We’ve been involved in the mission from the early stages, helping to define the payload interface and concept of operations for the mission, and are providing ongoing technical assistance during the on-orbit operations.
Overview
SeaHawk-1 is an innovative ocean colour monitoring CubeSat, designed by the University of North Carolina. It was built with our Flight Software Development Kit to accelerate mission development and is taking full advantage of the benefits offered by our Mission Control Software.
SeaHawk’s colour sensor observes changes in ocean surface colour, which relates directly to the substances and the organisms within it. Captured daily, high-resolution observations of ocean colour changes can be used for multiple environmental and maritime applications.
Challeges
The SeaHawk project utilises a 3U CubeSat platform to observe the changing biology of the ocean surface and its implication for various maritime applications.
Limitations on computing platform
The payload of the spacecraft generates a large amount of data at 1.1GB for a full observation sweep, and requires a high performance x-band downlink. This large volume of generated data put significant limitations on the computing platform, meaning that there was a demand for the software to use as minimal computing resources as possible.
From the software perspective, the restriction on computing power was the main challenge in this mission.
NASA Near Earth Network (NEN)
The NEN is a global network of satellite ground stations which is normally used by much larger spacecraft. We believe this is the first time it was used by a CubeSat.
Reducing operational complexity
SeaHawk is unusual for a CubeSat because its payload and its platform are operated by two distinct groups using different operations centres. The satellite itself is commanded by AAC Clyde Space in Glasgow, Scotland, using our Mission Control Software product. Payload data is downlinked to the NEN and processed by NASA Goddard Space Flight Centre. Tasking requests are passed from the payload to the platform team but there was a desire to keep this interface as simple as possible. In addition, since this is a pilot mission, some aspects of the performance of the system were uncertain, so there was a need to remain flexible.
Solutions
Limitations on computing platform
The FSDK allows the operator full control over how often the software performs certain actions such as checking the status of a component, or sending health checks to the operations centre. So the operator can decide which elements of the mission need to be prioritised.
Flexibility is a crucial part of the software development process as requirements may change mid-development. The FSDK allowed software to be developed from previous iterations, so that the flight package design could be easily changed without rewriting from the ground up.
NASA Near Earth Network (NEN)
In order to enable NEN interactions, we needed to ensure that our transmissions followed the internationally-recognised CCSDS standards, which was easy to achieve as the FSDK has an existing library of CCSDS protocol implementations to draw on.
Reducing operational complexity
In order to help reduce operational complexity, we ensured that all of the necessary platform data was included in the payload set so it can be correctly processed. We also automated the on-board processing and management of payload data, while providing flexibility to respond to the changing needs of the mission. Coupled with the on-board scheduling and scripting capabilities provided by our flight and ground software, it is possible for the majority of spacecraft operations to be automated.
We’ve been involved in the mission from the early stages, helping to define the payload interface and concept of operations for the mission, and are providing ongoing technical assistance during the on-orbit operations.
What are satellites used for?
We’ve come a long way since the first artificial satellite, Sputnik 1, was successfully placed in orbit around the Earth in 1957. Today, we can hardly imagine our lives without satellite technology. Often, we do not even realise the numerous ways they have become a part of our daily lives.
Broadly speaking, satellites applications can be broken down into three categories:
Earth observation applications
Communications satellites
Global Navigation Satellite Systems
Each of these categories includes multiple uses for artificial satellites, designed to make a positive impact on our lives and societies.
Earth Observation satellites
According to the Satellite Database, assembled by the Union of Concerned Scientists (UCS), nearly a third of satellites currently in orbit are used for Earth observation purposes. They provide us with images from around the globe and help us monitor areas that are too remote for human access.
The most obvious and recognisable applications of Earth observation satellites are weather forecasts and maps. However, they can be used for many more diverse purposes. For instance, they can help combat the ongoing climate change crisis: by observing and monitoring the changing environment, they provide reliable evidence of coastal erosion, temperature changes, deforestation, melting ice sheets, ocean pollution, coral reef bleaching and many other observations that provide invaluable data on the changing climate.
How Earth observation satellites work
Essentially, there are two main types of Earth Observation satellites: optical and radar.
Optical satellites use reflected sunlight to gather data. They view the world as the human eye does, which means imagery is only available on a clear and mostly cloudless day. Radar satellites, on the other hand, work by emitting microwave pulses which reflect off ground features. This provides uninterrupted views day and night under any weather conditions. In the recent years, it has become more common for Earth observation scientists to use both optical and radar data sets in their analysis and research.
Earth observation space missions built on Bright Ascension’s software
At Bright Ascension, we have been privileged to support a number of Earth observation space missions over the years.
SeaHawk-1 is an earth observation CubeSat. The innovative ocean colour monitoring CubeSat, was designed by the University of North Carolina. Its sensor observes changes in ocean surface colour, which relates directly to the substances and the organisms within it. Captured daily, high-resolution observations of ocean changes can be used for multiple purposes: from alerting researchers to the onset and expansion of harmful algal blooms, to potential fishing zones. This CubeSat is a proof of concept of a system which has the potential to greatly increase the availability and resolution of scientifically important ocean colour data through a network of satellites that are much smaller and cheaper than those currently used for this purpose.
The IOD-1 space mission was the key first step in the Orbital Micro Systems’ GEMS programme roll-out to test the commercial viability of the proposed service and prove its concept and technology.
The company’s weather observation payload, developed as part of the Global Environmental Monitoring Satellite (GEMS) program, is designed to deliver highly accurate and frequent weather readings for the benefit of the insurance, aerospace, maritime, energy and agricultural industries. For example, airlines and shipping companies will be able to plan routes taking into account optimal weather conditions, reducing delays, fuel consumption and emissions while operating with greater safety.
The GEMS network is expected to gather weather data more frequently and with better clarity than the large institutional satellites currently in use. IOD-1 GEMS was built to demonstrate the viability of the service to potential customers and prove successful operation of the payload technology.
The IOD-1 GEMS CubeSat, successfully deployed in 2020, ran a flight software suite developed by Bright Ascension using our Flight Software Development Kit, and communicated with our Mission Control Software running at the operations centre.
See our Launched Missions to find out more about the different types of earth observation CubeSats and other space missions we’ve supported over the years. Alternatively, contact us today to discuss your satellite software needs.
What is model-based software engineering?
At Bright Ascension we talk a lot about model-based software engineering, but what exactly does it mean?
Our model-based software platform provides a machine-readable description of the architecture of the system, which is understandable by both the space side and the ground side and is used across the life cycle of the system. The central elements of this platform are software components, which are entirely self-contained and have a coherent set of functionality. They are designed to create mission-specific spacecraft flight software through our HELIX Flightkit software by combining bespoke components with library components which have been previously validated.
Model-based software engineering: the ticket to space
This basic approach based on components means we can adapt our platform to any system that is suited to model-based software engineering. This could be small satellites, robotics, automated space systems, and much more. And it doesn’t just mean Low Earth Orbit either – we can take it much further than that.
Component-based engineering
While every spacecraft and mission are different, most space vehicles perform similar tasks, such as data acquisition, monitoring, logging, FDIR, TM/TC, scheduled/automated actions.
Our model-based software platform is built on a wide range of components, such as:
Data handling and monitoring components
Sampling, data pool, aggregation, logging, monitoring, statistics
Support for most common onboard monitoring functions
Communications components
Packet handling, telemetry reporting
Support for a number of different communications protocols
Support for ECSS PUS, CFDP and more
Automation components
Absolute and relative time scheduling, orbit-based scheduling
This component-based approach allows the platform to work with new systems, new hardware, new and existing software components, meaning that the model-based software engineering approach can do so much more than just CubeSats. Furthermore, with its abstraction from hardware, operating system, I/O and devices, our technology can manage many missions and applications that go beyond the CubeSat domain, such as all types of small satellites, complex and automated space systems, satellite constellations, robotics in space and more.
To find out more about how our model-based software engineering can help your mission – whether it’s a single satellite or a complex space system – contact us today.
Traditional approach to mission software development
The ground and space segments of a satellite project are often developed independently of each other, by different teams, or even different contractors, and at different life cycles of the mission. In other words, there has traditionally been a noticeable tendency to de-couple the development of separate flight software and mission operations system.
The most common way to establish this separation early on is to establish communication via packet data. In order to efficiently operate a spacecraft, developers need to thoroughly describe the telecommand and telemetry packets that will perform exchanges between the flight and the ground sides. This means that the spacecraft functionality and its exposure to the control centre have to be described in significant detail and then captured at packet level.
The limitations of traditional approach
As a result, this approach has certain downsides:
It offers an impoverished view of the available functionality
It is labour intensive and prone to errors
it does not readily capture high-level patterns of interaction
it is hard to change and adapt
it complicates operations and automation
it does not scale well in terms of constellations once your space system starts to grow
Alternative approach: Model-Based
Our flight-proven industry-leading technology offers an alternative solution and addresses these key challenges through its unique approach to space software engineering.
Model-based software engineering
The underlying platform used across all our software products is both component-based and model-based. “Component-based” means that it is designed to create limitless combinations of software components which are entirely self-contained and have a coherent set of functionality. While every mission is different, software systems tend to perform a number of similar tasks such as data acquisition, monitoring, logging, FDIR, TM/TC, scheduled and automated actions. These common functions are provided as library components which allows users to quickly cover basic functionality of the system and focus on the development of bespoke components, unique to their particular mission.
Once the component structure is defined, the system provides a machine-readable description (a model) of its entire architecture, which is understandable by both the space side and the ground side, and is used across the life cycle of the system. Each mission defines its own model to represent the facilities available and the chosen configuration options.
Why choose model-based approach
The real advantage of the model-based approach is that the entire flight software package, developed through our software can be quickly and easily understood by our ground-based products.
For example, the spacecraft database generated by each specific deployment can be loaded up into our operations software to automatically populate it with all the spacecraft components. It gives the system a full view of the different components and their services and makes integration and configuration virtually automatic.
This unified approach to flight and ground software development through a shared functional architectural model brings a wide range of benefits to all aspects of missions, end-to-end and across the full life cycle:
It facilitates rapid interaction
It improves efficiency of operations
It allows for light level of automation
It supports scalability
Model-based approach across upstream and downstream activities
This model-based approach stretched beyond flight software development and mission operations and right into space-based service delivery and the downstream sector, solely focussed on applying the data or services to produce actionable insights and applications for a wide range of industries.
Our mode-based technology forms the foundation for the HELIX suite of products, designed to joined up various software systems within a mission infrastructure. HELIX connects the entire mission lifecycle, from upstream mission development to downstream insights and applications, delivered through space-based services:
Rapid flight software development
Automated testing and simulation
Automated operations and ground control software
Mission add-on/app development for spacecraft or ground deployment
Accessing space data for value-added insights and intelligence
Cross-product monitoring and analytics
Perhaps one of the most challenging aspects of the dynamic New Space landscape is the constant growth, evolution, and scaling up of missions. With each new spacecraft or mission comes a host of new requirements, hardware components, vendors, and technologies. Predicting the exact trajectory of these changes can be daunting and the key to successful operations lies in seamless integration mechanisms and efficient management of available assets and resources.
HELIX is designed to integrate together the entire end-to-end space software provision – from flight software to ground operations and data-insights applications. It tightly connects currently disjointed and fragmented space software systems for significantly improved efficiency, simplicity, and noticeably lower costs. .
Learn more: Book a Demo
We’ve been evolving our technology over the past 12 years through extensive development work. During this time, our software has powered more than 50 spacecraft in orbit, helping them to maximise their mission potential.
Contact us today to see our products in action and arrange a one-to-one demo of our software, tailored to your unique mission needs and requirements.
Our software is a model-based solution that is not dedicated to any particular system. Our component-based architecture also means that the software you produce can be fully customised and adopted to your specific mission needs. This means you can potentially do a whole lot more than a NanoSat or a CubeSat: small satellites, robotics, automated space systems, and much more.
Overview
SeaHawk-1 is an innovative ocean colour monitoring CubeSat, designed by the University of North Carolina. It was built with our Flight Software Development Kit to accelerate mission development and is taking full advantage of the benefits offered by our Mission Control Software.
SeaHawk’s colour sensor observes changes in ocean surface colour, which relates directly to the substances and the organisms within it. Captured daily, high-resolution observations of ocean colour changes can be used for multiple environmental and maritime applications.
Challeges
The SeaHawk project utilises a 3U CubeSat platform to observe the changing biology of the ocean surface and its implication for various maritime applications.
Limitations on computing platform
The payload of the spacecraft generates a large amount of data at 1.1GB for a full observation sweep, and requires a high performance x-band downlink. This large volume of generated data put significant limitations on the computing platform, meaning that there was a demand for the software to use as minimal computing resources as possible.
From the software perspective, the restriction on computing power was the main challenge in this mission.
NASA Near Earth Network (NEN)
The NEN is a global network of satellite ground stations which is normally used by much larger spacecraft. We believe this is the first time it was used by a CubeSat.
Reducing operational complexity
SeaHawk is unusual for a CubeSat because its payload and its platform are operated by two distinct groups using different operations centres. The satellite itself is commanded by AAC Clyde Space in Glasgow, Scotland, using our Mission Control Software product. Payload data is downlinked to the NEN and processed by NASA Goddard Space Flight Centre. Tasking requests are passed from the payload to the platform team but there was a desire to keep this interface as simple as possible. In addition, since this is a pilot mission, some aspects of the performance of the system were uncertain, so there was a need to remain flexible.
Solutions
Limitations on computing platform
The FSDK allows the operator full control over how often the software performs certain actions such as checking the status of a component, or sending health checks to the operations centre. So the operator can decide which elements of the mission need to be prioritised.
Flexibility is a crucial part of the software development process as requirements may change mid-development. The FSDK allowed software to be developed from previous iterations, so that the flight package design could be easily changed without rewriting from the ground up.
NASA Near Earth Network (NEN)
In order to enable NEN interactions, we needed to ensure that our transmissions followed the internationally-recognised CCSDS standards, which was easy to achieve as the FSDK has an existing library of CCSDS protocol implementations to draw on.
Reducing operational complexity
In order to help reduce operational complexity, we ensured that all of the necessary platform data was included in the payload set so it can be correctly processed. We also automated the on-board processing and management of payload data, while providing flexibility to respond to the changing needs of the mission. Coupled with the on-board scheduling and scripting capabilities provided by our flight and ground software, it is possible for the majority of spacecraft operations to be automated.
We’ve been involved in the mission from the early stages, helping to define the payload interface and concept of operations for the mission, and are providing ongoing technical assistance during the on-orbit operations.
WHY MCS?
4 REASONS TO CHOOSE THE MCS
The mission control software provides a flexible and integrated graphical environment for all aspect of mission operations, tying together monitoring, control and automation.
Mission monitoring
The MCS provides a rich environment for parameter and event monitoring, including telemetry visualisation and archiving, telemetry monitoring with alarms and condition notification, and many more features under active development.
The graphical environment of the MCS integrates commanding with monitoring and other talks, which provides a clear and more efficient view of operations. And its powerful scripting means that complex tasks can be achieved quickly and effortlessly.
The MCS provides extensive scheduling and automation features, such as automated pass management including downlink/uplink handling. This allows to enable efficient unattended operations to improve reliability of the mission and maximise uptime.
Our underlying core technology creates a model of the system that is shared by the entire mission: both flight and ground. This means the MCS understands how to interact with the flight side with almost zero manual configuration, saving time, effort and cost.
6 Ways to Build a Space System with Operations in Mind
Space system developers see flight software as separate and independent from its ground counterpart. Consider an alternative approach that focusses on what you are trying to achieve for your mission…
Benefits of Integrated Space-Ground Software Systems
The ground and space segments of a satellite project are often developed independently of each other and at different life cycles of the mission. Find out about an alternative model-based…
Avoiding Common Pitfalls in Space Software Development
Over the past 10 years we have gained an impressive amount of experience building diverse satellite missions. See our list of “Dos” and “Don’ts” that we often come across in…
The Faraday Phoenix mission enables multiple third-party payloads to ‘rideshare ’ on a single satellite platform, providing fast and low-cost access to space.
Another Five Spacecraft Launched With Our Flight Software Onboard
The Faraday Phoenix and KSF1 missions add to the list of successfully launched spacecraft with our software onboard, taking the current total to 24 satellites, with many more in development.
Underpinning every software product we provide is our model-based core technology. It creates a machine-readable description of the system that can be used across all life-cycle stages.
This means that the MCS automatically reads the entire flight structure with little to no configuration, enabling intuitive automation and unattended operations, even across large systems and constellations.
In the rapidly changing commercial space market, there is a strong need to produce satellite software quickly and at low cost. Find our how our technology supports software reuse.
Benefits of Integrated Space-Ground Software Systems
The ground and space segments of a satellite project are often developed independently of each other and at different life cycles of the mission. Find out about an alternative model-based…
Discover our range of space software products, built on our flight-proven technology, which brings a wide range of benefits to all aspects of missions, end-to-end and across the full life-cycle.
Learn how we deliver robust and scalable mission-specific control systems, seamlessly integrated with pre-existing flight software.
Integrated Flight & Ground Software Development
Find out how we ensure a seamless, end-to-end approach to flight & ground software development, reducing both risk and development time.
INTEGRATED SOLUTION
Flight Software
For maximum efficiency, increased performance and reduced operating costs, make sure to take advantage of the seamless integration of our space- and ground-based products.
CubeSats can’t simply be launched into space and left to do their jobs.
There are several challenges that can present themselves to objects in orbit, and missions need a constant flow of information back and forth from satellite to ground.
Missions that intend to gather data about space, or the Earth itself, particularly require CubeSat communication to reap the desired rewards as the mission unfolds— especially before the CubeSat falls from orbit and burns up!
Read on to find out how CubeSats communicate.
How do CubeSats communicate with Earth?
CubeSats communicate with Earth using radio waves. These waves are received by ground stations back on Earth, which downlink the signals and convert the information into its ‘true form’, such as images or data logs.
It’s not dissimilar to how your radio or television receives and converts signals, albeit on a much larger scale and travelling over considerably longer distances.
Satellite communication makes use of several different frequency bands. Recently, there has been a shift towards preference for higher frequency bands, particularly for small satellites, due to a need for higher data rates. Higher frequency bands mean wider bandwidth, but they are also more likely to be affected by the atmosphere, weather conditions and what’s called “rain fade”, the absorption of radio signals by rain, snow or ice.
L-Band (1-2 GHz): a very diverse range of satellites, including communications, GPS (Global Positioning System), GNSS (Global Navigation Satellite Systems), etc.
S-Band (2-4 GHz): weather monitoring, space operations (including communication with International Space Station and Space Shuttle), many remote sensing satellites
C-Band (4-8 GHz): mostly used by satellite TV broadcast and similar satellite communications
X-Band (8-12 GHz): space research, civil and military applications, such as air traffic control, martime tracking, defence, weather monitoring, etc. Many satellites carry complimentary S-Band and X-Band transmitters.
Ku-Band (12-18 GHz): mostly used in communications, domestic satellite TV broadcast, etc.
Ka-Band (26-40 GHz): primarily used for satellite communications, high-resolution, close-range targeting radars, military aircraft, etc. Not very useful in tropical regions due to signal absorption by water and rain.
CubeSats suffer from reduced power compared to larger conventional satellites, which affects their ability to transmit data in large volumes. However, research into using laser-based communication technology may yield the answers. This allows downlinking from the satellite to ground station using fewer resources.
Why do CubeSats need to communicate with Earth?
CubeSats need to communicate with Earth for various reasons, and possibly on a continuous basis for the duration of their lifespans.
‘Communication’ can be for logistical purposes, monitoring the onboard systems of the CubeSat and ensuring that everything is running as it should. It could entail telemetry, sending commands from ground to satellite to adjust orientation, avoid collisions, and activate or deactivate components.
Communication can also mean downloading data from the satellite so that it can be saved and utilised by a team waiting back on Earth. Satellites undertaking Earth observation missions will likely be downlinking data such as photographs and atmospheric readings.
Other satellites might be in orbit to test or prove a concept, such as NASA’s BioSentinel mission which aims to test the survivability of biological organisms in the presence of space radiation (don’t worry, they’re only using yeast—we’ve learned from Laika the dog).
CubeSats need to be able to communicate with Earth because once they go up, there’s no coming down. Deorbiting, for a CubeSat, effectively means re-entering the atmosphere and burning up. This renders a CubeSat unable to store data for retrieval later, as it needs to be downlinked before the satellite itself is destroyed at the end of its life cycle.
Communication channels between ground station and satellite allow data to be retrieved in real time and means the most ‘bang for buck’ in terms of the CubeSat’s available time.
CubeSat communication systems
Being built out of COTS (commercial-off-the-shelf) components, CubeSat communications systems can be purchased in a readymade state and incorporated into the satellite.
There is a degree of choice when building a CubeSat as to whether you want to incorporate only a transmitter or opt for a transceiver.
The former only generates and sends radio signals, allowing the transferal of data. The latter allows signals to be both received and sent to and from the satellite, acting as both transmitter and receiver (thus the portmanteau).
A transceiver is necessary if the satellite needs to receive commands and uplink from the ground, rather than only sending its data back down to ground.
Communication systems that can use high-frequency bands are more expensive, owing to the fact that they can transmit data at a higher rate. Additionally, a transceiver that can use full-duplex transmission—both receiving and sending data simultaneously—will again make for a more costly component than one which is only half-duplex, sending and receiving as separate tasks at a time.
A ground station is necessary to receive the satellite’s data, which will also need tracking software and ideally the ability to move itself in order to keep its communication link whilst the satellite is overhead.
Making CubeSats simpler
Handling the communication of a CubeSat is much smoother with pre-validated software that’s guaranteed to work. Bright Ascension’s Mission Control Software makes CubeSat communication easy, with automation features making uplink and downlink handling, as well as other tasks, effortless.
ACADEMIC PROGRAMME
TRY OUR SOFTWARE FOR FREE
To support future skill-building within the academic community we offer to affordable (in some instances free) licences for our flight and ground software products.
We’ve been evolving our technology over the past 12 years through extensive development work. During this time, our software has powered more than 50 spacecraft in orbit, helping them to maximise their mission potential.
Contact us today to see our products in action and arrange a one-to-one demo of our software, tailored to your unique mission needs and requirements.
BOOK DEMO
Space Software Built Around Your Mission
Select the software product and complete the form.