Developed for the European Space Agency, PICosatellite for Atmospheric and Space Science Observations (PICASSO) CubeSat is designed to investigate the upper layers of Earth’s atmosphere and is another satellite that brought Bright Ascension’s innovative software in space.
PICASSO’s payload, composed of two scientific instruments, contributes to the determination of the ozone distribution in the stratosphere, the temperature profile up to the mesosphere and the electronic plasma characterisation in the ionosphere.
Challeges
Mixed-Vendor Hardware and Complexity
PICASSO satellite has a mixed-vendor hardware platform as the CubeSat uses a miniaturised multispectral imager using the Sun as the light source, and a multi-needle ‘Langmuir probe’ in order to sample the electron density of the space.
The platform also contains distributed onboard architecture as there are two onboard computers (OBC) used on the platform, which includes a separate payload computer. This was a unique challenge for the integration of flight software.
Time Constraints
Along with technological constraints and current limitations of CubeSat technology, PICASSO also had time constraints with development effort spreading over approximately one year.
Solutions
Mixed-vendor hardware
The FSDK is an open system, meaning that it can be easily extended to work with new systems, new hardware, new and existing software components. This means any new hardware can be used without building a whole new system.
FSDK effectively defined components interactions in terms of services thus rendering them location independent. The FSDK abstraction allows easy distribution of flight software across multiple computing platforms without adding operational complexity.
Time constraints
FSDK offers a rapid development process and the flexibility to swap components in and out without redesigning the entire package, which provides an ideal solution for the dynamic nature of projects like PICASSO.
Based on the same GenerationOne technology, the flight software also seamlessly integrated with our MCS software to allow operators to easily communicate with the spacecraft from the control centre.
It also included automation components to permit the automation of on-board activities such as responding to events and scheduling on-board activities based on relative time, absolute time or spacecraft orbit.
Outcome
PICASSO was successfully launched on the inaugural flight of the ESA-developed ‘Small Spacecraft Mission System’ dispenser – devoted to CubeSats and other small satellites – on a Vega launcher in 2020.
It is currently in orbit, demonstrating that small satellite technology can be successfully used as a scientific tool for Earth observation and research.
Overview
Developed for the European Space Agency, PICosatellite for Atmospheric and Space Science Observations (PICASSO) CubeSat is designed to investigate the upper layers of Earth’s atmosphere and is another satellite that brought Bright Ascension’s innovative software in space.
PICASSO’s payload, composed of two scientific instruments, contributes to the determination of the ozone distribution in the stratosphere, the temperature profile up to the mesosphere and the electronic plasma characterisation in the ionosphere.
Challeges
Mixed-Vendor Hardware and Complexity
PICASSO satellite has a mixed-vendor hardware platform as the CubeSat uses a miniaturised multispectral imager using the Sun as the light source, and a multi-needle ‘Langmuir probe’ in order to sample the electron density of the space.
The platform also contains distributed onboard architecture as there are two onboard computers (OBC) used on the platform, which includes a separate payload computer. This was a unique challenge for the integration of flight software.
Time Constraints
Along with technological constraints and current limitations of CubeSat technology, PICASSO also had time constraints with development effort spreading over approximately one year.
Solutions
Mixed-vendor hardware
The FSDK is an open system, meaning that it can be easily extended to work with new systems, new hardware, new and existing software components. This means any new hardware can be used without building a whole new system.
FSDK effectively defined components interactions in terms of services thus rendering them location independent. The FSDK abstraction allows easy distribution of flight software across multiple computing platforms without adding operational complexity.
Time constraints
FSDK offers a rapid development process and the flexibility to swap components in and out without redesigning the entire package, which provides an ideal solution for the dynamic nature of projects like PICASSO.
Based on the same GenerationOne technology, the flight software also seamlessly integrated with our MCS software to allow operators to easily communicate with the spacecraft from the control centre.
It also included automation components to permit the automation of on-board activities such as responding to events and scheduling on-board activities based on relative time, absolute time or spacecraft orbit.
Outcome
PICASSO was successfully launched on the inaugural flight of the ESA-developed ‘Small Spacecraft Mission System’ dispenser – devoted to CubeSats and other small satellites – on a Vega launcher in 2020.
It is currently in orbit, demonstrating that small satellite technology can be successfully used as a scientific tool for Earth observation and research.
In looking for solutions to help you develop spacecraft software, there are a variety of options open to you. Some, like our HELIX Flightkit, are commercially licensed, while others are released under open source licences. All seek to solve real problems in space systems.
We have designed Flightkit to not only provide solid engineering solutions, but to also provide dramatic mission-level benefits. Consider how these benefits could contribute to the success of your mission:
Short startup time
Getting software engineers up to speed with new tools takes time, but Flightkit architecture allows teams to focus only on the areas they need to. Flightkit is component-based with hundreds of software components available out of the box, giving engineers the space to concentrate on the new functionality your mission needs.
This means that you can quickly cover all the basic and standard functionality for your mission (e.g. data acquisition, monitoring, logging, FDIR, TM/TC, etc. ) and focus on what makes it unique such as payload interfacing and managing, telemetry handling, communication protocols and your concept of operations.
Simple reuse
Flightkit allows software components written for one mission to be easily reused on another, even if the spacecraft hardware is different – even if the onboard computer the software needs to run on has changed!
Components can often be combined in new ways to achieve new functionality, avoiding the need to start again from the ground up.
Built-in scalability
Flightkit inherently builds in the ability for different elements of the space system to talk to each other. To access functionality on one spacecraft from another, all that is required is a communications link between the two and the relevant easily configured software components. This allows complex networks of assets to be built with little development overhead.
As you space system grows and develops, you may find beneficial to keep your architecture open to new hardware in order to avoid vendor lock-in. Flightkit allows individual modules to be quickly and easily substituted according to your requirements – whether you are adding new capability to a new satellite in your space system or simply trying to save cost by opting for a more cost-effective vendor.
Operations integration
While not required, Flightkit excels when used with our ground software products. When Flightkit-based software is built, a “spacecraft database” is generated – this allows the ground software to understand how to interact with the flight software with almost zero manual configuration.
Operations procedures can be written, tested and iterated upon while the flight software is still in development, reducing development risk.
Save cost
It is easy to choose an open-source solution based on purchase cost only. But it is crucial to think beyond the purchase point and take into account all the expenses and risks through to the final qualified ready-for-flight version.
Flightkit can save considerable cost through faster and more efficient development process, lower risk, simpler and quicker onboarding process to get you started and straightforward scalability options as you forward.
With many hidden elements and overheads, only choosing a well-structured, well tried and tested development environment will give you the lowest development cost and shortest development time of all.
Support and advice
Flightkit is developed by a passionate team who are keen to share the fruits of our labour with our customers. We always seek to help you get the most out of your product. We provide training sessions tailored to your needs and online support via our ticketing system.
We are also happy to discuss the architecture and design of your mission, drawing on our experience across the space industry. Understanding your mission needs ensures we can keep Flightkit developing in the right direction for our customers.
We believe a HELIX Flightkit licence represents real value for money in comparison to a variety of competitors, be they open source solutions or other commercial offerings.
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.
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.
The New Space industry is booming, experiencing a rapid and sustained growth like never before. Small satellites and CubeSats in particular have made space a lot more accessible for a large number of companies, that perhaps wouldn’t have launched otherwise – particularly SMEs and start-ups. But these smaller and more capable satellites that are being launched in higher volumes and at lower cost also make the sector a highly competitive environment. Rapid development is in constant demand and the current expectation can only be a few months!
In the article we will look at how flight software – the “glue” that holds the entire system together – can help speed up and simplify mission development and reduce time to market, getting the spacecraft operational faster than the competition.
What’s the rush?
One key challenge of most small satellite missions is the project schedule, which is often tight, meaning that flight software needs to be available early in the development process and must be made available quickly. To make matters worse, the hardware for the mission may also be in development at the same time and unavailable for software testing until later in the project. The challenge that mission engineers face is to quickly create a simple enough flight software package which covers very unique and complex space mission requirements.
What is flight software so important?
Flight software is “the heart” of any satellite, it is responsible for implementing or coordinating the key operational functions of the spacecraft. With the rapid commercialisation of space and within CubeSat missions in particular, flight software is becoming increasingly complex with more functionality moved out of hardware into software, which gives developers more flexibility by allowing the use of more off-the-shelf components.
The spacecraft flight software becomes the “glue” that is holding everything together. And getting it right from the start is the key to a quick satellite launch.
Can flight software be off-the-shelf?
Wide use of off-the-shelf components for electronics and subsystems is one of the key principles of CubeSat mission development. This is how CubeSat missions are able to achieve rapid development of complex yet reliable spacecraft at relatively low cost and within strict timescales. But since every satellite is unique, with its distinct goals and mission objectives, it is hard to develop a flight software package that can fit all mission – no matter how big or small, or what they are trying to achieve.
On the other hand, developing custom flight and ground software from scratch often comes with prohibitively high costs and lengthy development times.
The answer to this challenge can be modular software, that is based on readily-available and standardised units of reuse (components) and can be quickly and easily adapted to any mission. This off-the-shelf approach to flight software makes CubeSat mission development significantly faster and simpler.
Can off-the-shelf software work for unique missions?
The diversity of space applications developed in recent years makes every mission unique, with its unique payload and unique flight software package. It’s not unreasonable to expect that unique missions call for bespoke solutions.
Not necessarily. Whilst every CubeSat mission is indeed different, most spacecraft perform a number of similar tasks, such as data acquisition, monitoring, logging, etc. Our products come with a pre-verified component library that allows to quickly cover this basic flight software functionality, so that the main engineering effort is concentrated on the unique parts of the mission, significantly reducing development time.
What’s more, we know that requirements can change as missions grow and develop. And that’s where the off-the-shelf and modular approach really excel – the platform allows to quickly and easily integrate any additional components or replace existing ones in response to the change of capability requirements. This means that the change can be very quick and very simple, so there is no need to re-design the entire system from scratch.
Does it make flight software reliable?
Despite the current boom in the global CubeSat market, one fact is often true: lower costs and fast mission development may increase the risk of failures. And once the spacecraft is in orbit – your options to fix or repair the mission are limited. And that’s where our off-the-shelf flight software has another significant advantage over bespoke solutions. Not only are all the library components rigorously tested and pre-verified, our technology comes with impressive flight heritage and over 50 spacecraft in orbit to minimise customer risks.
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.
This ongoing development forms the foundation for our ground-breaking HELIX suite of products, designed to join up various software systems within a mission’s infrastructure. HELIX connects the entire mission lifecycle, from upstream mission development to downstream insights and applications, delivered through space-based services.
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.
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.
What is a CubeSat?
The past decade has seen a substantial shift in the space industry with the arrival of what is often referred to as “New Space”. This takes a different approach to satellite deployment: harnessing the miniaturisation of electronics, it enables smaller, more capable spacecraft to be launched in higher volumes and at lower cost.
At the same time, there has been a boom in potential applications for both data obtained from space and services delivered from space, such as satellite communications or Earth observations. New Space technology has been perfectly placed to address these needs, with significantly shorter time-to-market than more traditional spacecraft.
A CubeSat is a particular type of small satellite that has gained its popularity due to well-defined standards, intended to reduce costs and development effort. The CubeSat standard was developed by California Polytechnic State University (Cal Poly) and Stanford University, originally aimed at scientific research and exploration of new space technologies. Over the years, CubeSats made their way into commercial projects and are now seen as one of the quickest and cost-effective ways to demonstrate space technologies or deliver a service from space.
What is the CubeSat specification?
CubeSats must comply with the standards described in the CubeSat specification, published by Cal Poly. They are made up of 10x10x10cm units (known as 1U size) and weigh no more than 1.33kg per unit. They often use off-the-shelf components to reduce costs and this can include electronics, subsystems and even software. CubeSats can also come in various sizes, such as 1U, 2U, 3U, 6U+, to support more capabilities and more complex technology.
How to build a CubeSat fast
One of the main advantages of a CubeSat is the short time required to develop and launch the satellite. A CubeSat can be designed, built, tested, and delivered in as little as 6 months, but typically takes 18 to 24 months to complete, which is significantly faster than a traditional satellite approach.
This is mainly achieved through the wide use of off-the-shelf components for electronics and subsystems, which is one of the key principles of CubeSat mission development. It allows CubeSat missions to quickly develop complex yet reliable spacecraft at low cost and within time constraints.
Onboard software can also be one the off-the-shelf components of CubeSat development. Just like the hardware, flight software can come readily available to simplify and speed up development, ensure it is accessible early in the development process for rigorous testing and successful integration.
There are a variety of solutions available for spacecraft software development, but they all attempt to solve similar problems – i.e. help users create a reliable and functional flight software package as quickly and as cost-efficiently as possible. It’s important to make informed decisions and consider why commercially licensed off-the-shelf software might be a better option and how it can help the mission succeed.
How to build a CubeSat that works
Despite the current boom in the global CubeSat market, one fact is often true: lower costs and fast space mission development may increase the risk of failures. Once in orbit, CubeSats have to perform without failure as there is no physical access to them to resolve any potential issues. Rigorous testing and robust components can help improve reliability.
Onboard software is the “glue” that is holding all the CubeSat subsystems together and getting it right is the key to reliability. To allow for meticulous testing and sound integration, the flight software package needs to be simple and functional, so it is available early on in the space mission development process and adaptable to accommodate any requirements changes.
One solution to this is off-the-shelf flight software like our Flight Software Development Kit, which is designed to quickly and easily adapt standard software to any unique needs of the mission – no matter whether it’s a single CubeSat or a large constellation.
How to build a CubeSat that doesn’t blow your budget
Standardisation and wide use of off-the-shelf components also allows developers to keep costs under control at fixed prices and limit the requirement for various resources.
From the software perspective, developers want to ensure that the spacecraft flight software package can be built quickly and without the need for specialist skills so the bulk of effort is concentrated on the unique parts of the mission.
Our FSDK is designed to support rapid development with ease and simplicity in mind. Additionally, being an open system, it can be easily extended to work with new subsystems, new hardware, new and existing software components. This means it gives access to the best available and most cost-effective off-the-shelf components in the market.
Know your competition: how many CubeSats have been launched
As of 4th April 2021, 1553 CubeSats have been launched and it is forecasted that over 2500 CubeSats will be launched in in the next 6 years! Such a highly competitive market can make it challenging for new entrants to succeed.
Innovation and continuous improvements in efficiency and productivity is what can bring better results and a positive difference to any space mission.
At Bright Ascension, innovation is at the heart of everything that we do. We offer a unique and innovative approach to spacecraft flight software engineering for quick, efficient and cost-effective CubeSat mission development and operation.
Find out more about what makes our products unique and how they can help your CubeSat mission succeed.
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.
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.
The FSDK currently supports the AAC Clyde Space Kryten and Sirius LEON3, the GomSpace A3200, and a range of Linux-based OBCs such as the Xiphos Q8 and GomSpace Z7000.
The FSDK currently supports FreeRTOS, Linux (and by extension other POSIX-compliant OSes) and RTEMS.
We can usually add support for a new OS or platform, depending on the specific OS/platform characteristics. Please get in touch to discuss your needs in detail.
The resource requirements of an FSDK image depend strongly on the functionality you choose to build into it. As a rough baseline, however, a basic FSDK image will make use of around 1MiB of RAM, occupy <256KiB of non-volatile storage, and use less than 10% of a 50MHz CPU’s available processing time (including basic telemetry gathering, command handling and FDIR). You should expect a fully functional image to use >2MiB of RAM, and occupy >0.5MiB of non-volatile storage. Some system functions (such as data downlinks) will use substantial CPU time.
We release a minimum of 2 updates per year and plan to increase the frequency in the near future.
The FSDK supports a wide range of nanosatellite subsystems. These include ADCSs, batteries, EPSs, radios, reaction wheels sets, and other subsystems from AAC Clyde Space, Cubecom/CPUT, GomSpace, Pumpkin, Satlab and Skylabs. We are continually adding to our component library, so if you have specific needs, please get in touch!
The FSDK tools are quick and easy to run from the Linux command line. It also ships with a plugin for use with the Eclipse IDE.
The FSDK supports a range of ground systems through the use of standard communications protocols, including CCSDS and ECSS PUS.
While we are not satellite system specialists, we have done a lot of software for a number of different hardware configurations. We can tell you what works and, in particular, what will make software development harder and more complex. Simply contact us and we will be happy to share our expertise with you.
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.
What is vendor lock-in and why it should be avoided?
Broadly speaking, a vendor lock-in is a situation when you are forced to use a particular provider. This can happen for various reasons. The cost of switching vendors may be too high, so you may prefer to stay with the same hardware provider. Switching can be time-consuming or you may not have the required specialist skills to re-configure the system. Whatever the reason, you may want to consider avoiding vendor lock-in, where possible, as it comes with a few potential threats:
You have no choice and control over costs, as hardware providers dictate pricing.
As you company grows and develops, the hardware offering may no longer suit you needs.
The quality of your hardware may decrease overtime. Likewise, the level of service may decline.
Your hardware provider may go out of business altogether.
Hardware limitations in the space industry
Within the space industry, there are additional reasons to keep your software architecture open and allow for hardware to be added without building or buying a software package from scratch each and every time:
Hardware vendors may have limited manufacturing capacity. This means you may not get your equipment in time or face extended lead times, which can have a detrimental effect on your project work and timescales.
Overtime, your space system may require the use of new subsystems with new requirements. Or you may simply need different payloads for different purposes. For example, the service you are providing may include both spectral and radar capabilities, meaning that you will need completely different equipment and approaches to payload integration.
This becomes especially true as your system starts to grow, develop and require more scalability.
What is the solution?
Whilst it may be difficult to make your system completely hardware independent, a modular and model-based approach certainly has its benefits. Bright Ascensions’ modular approach is designed with portability in mind and allows individual modules to be substituted and changed according to your requirements, as and when these requirements arise.
An abstraction layer and flexibility of the system make it easy and straightforward to add new onboard computers, operating systems and architectures.
For example, you can quickly and easily develop the software package for a new spacecraft in your system, even when it requires a completely different OBC. All you need to do is change a module in your existing software platform, without the need to re-build the entire system architecture. This modularity will help you get the most out of the flight software each mission, regardless of mission requirements, with only minor tweaks and without having to re-create the flight software from the ground up each and every time.
Improve your bottom line
Your hardware provider preferences do not only have to be determined by technical requirements. You may also want to simply save cost by making use of different price options available in the market. As the system can easily be extended to work with new subsystems, new hardware, new software components, this allows you to freely access the best available or most suitable equipment.
Competition within the manufacturing part of the New Space market has seen prices come down in recent years, and as a number of manufacturing companies scale up, this tendency will continue. As a service provider, you may want to take advantage of price competition between hardware manufacturers and make your constellations heterogeneous, comprising satellites from different manufacturers with different capabilities.
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.
This ongoing development forms the foundation for our ground-breaking HELIX suite of products, designed to join up various software systems within a mission’s infrastructure. HELIX connects the entire mission lifecycle, from upstream mission development to downstream insights and applications, delivered through space-based services.
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.
Overview
Developed for the European Space Agency, PICosatellite for Atmospheric and Space Science Observations (PICASSO) CubeSat is designed to investigate the upper layers of Earth’s atmosphere and is another satellite that brought Bright Ascension’s innovative software in space.
PICASSO’s payload, composed of two scientific instruments, contributes to the determination of the ozone distribution in the stratosphere, the temperature profile up to the mesosphere and the electronic plasma characterisation in the ionosphere.
Challeges
Mixed-Vendor Hardware and Complexity
PICASSO satellite has a mixed-vendor hardware platform as the CubeSat uses a miniaturised multispectral imager using the Sun as the light source, and a multi-needle ‘Langmuir probe’ in order to sample the electron density of the space.
The platform also contains distributed onboard architecture as there are two onboard computers (OBC) used on the platform, which includes a separate payload computer. This was a unique challenge for the integration of flight software.
Time Constraints
Along with technological constraints and current limitations of CubeSat technology, PICASSO also had time constraints with development effort spreading over approximately one year.
Solutions
Mixed-vendor hardware
The FSDK is an open system, meaning that it can be easily extended to work with new systems, new hardware, new and existing software components. This means any new hardware can be used without building a whole new system.
FSDK effectively defined components interactions in terms of services thus rendering them location independent. The FSDK abstraction allows easy distribution of flight software across multiple computing platforms without adding operational complexity.
Time constraints
FSDK offers a rapid development process and the flexibility to swap components in and out without redesigning the entire package, which provides an ideal solution for the dynamic nature of projects like PICASSO.
Based on the same GenerationOne technology, the flight software also seamlessly integrated with our MCS software to allow operators to easily communicate with the spacecraft from the control centre.
It also included automation components to permit the automation of on-board activities such as responding to events and scheduling on-board activities based on relative time, absolute time or spacecraft orbit.
Outcome
PICASSO was successfully launched on the inaugural flight of the ESA-developed ‘Small Spacecraft Mission System’ dispenser – devoted to CubeSats and other small satellites – on a Vega launcher in 2020.
It is currently in orbit, demonstrating that small satellite technology can be successfully used as a scientific tool for Earth observation and research.
BOOK DEMO
Space Software Built Around Your Mission
Select the software product and complete the form.