Flight Results of the InflateSail Spacecraft and Future Applications of DragSails

The InflateSail CubeSat, designed and built at the Surrey Space Centre (SSC) at the University of Surrey, UK, for the Von Karman Institute (VKI), Belgium, is one of the technology demonstrators for the QB50 programme. The 3.2 kilogram InflateSail is “3U” in size and is equipped with a 1 metre long inflatable boom and a 10 square metre deployable drag sail. InflateSail\u27s primary goal is to demonstrate the effectiveness of using a drag sail in Low Earth Orbit (LEO) to dramatically increase the rate at which satellites lose altitude and re-enter the Earth\u27s atmosphere. InflateSail was launched on Friday 23rd June 2017 into a 505km Sun-synchronous orbit. Shortly after the satellite was inserted into its orbit, the satellite booted up and automatically started its successful deployment sequence and quickly started its decent. The spacecraft exhibited varying dynamic modes, capturing in-situ attitude data throughout the mission lifetime. The InflateSail spacecraft re-entered 72 days after launch. This paper describes the spacecraft and payload, and analyses the effect of payload deployment on its orbital trajectory. The boom/drag-sail technology developed by SSC will next be used on the RemoveDebris mission, which will demonstrate the applicability of the system to microsat deorbiting

The InflateSail CubeSat Mission:The First European Demonstration of Drag-Sail De-Orbiting

The InflateSail (QB50-UK06) CubeSat, designed and built at the Surrey Space Centre (SSC) at the University of Surrey, UK, for the Von Karman Institute (VKI), Belgium – was one of the technology demonstrators for the QB50 pro-gramme. The 3.2 kilogram 3U CubeSat was equipped with a 1 metre long inflat-able boom and a 10m2 deployable drag sail. InflateSail's primary mission was to demonstrate the effectiveness of using a drag sail in Low Earth Orbit (LEO) to dramatically increase the rate at which satellites lose altitude and re-enter the Earth's atmosphere and it was one of 31 satellites that were launched simultane-ously on the PSLV (polar satellite launch vehicle) C-38 from Sriharikota, India on 23rd June 2017 into a 505km, 97.44o Sun-synchronous orbit (SSO). Shortly after orbital insertion, InflateSail booted-up, and, once safely clear of the other satellites on the launch, it automatically activated its payload – firstly, deploying a 1 metre long inflatable boom comprising a metal-polymer laminate tube, using a cool gas generator (CGG) to provide the inflation gas, and secondly, using a brushless DC motor at the end of the boom to extend four lightweight bistable rigid composite (BRC) booms to draw out the 3.1m x 3.1m square, 12 micron thick polymer drag-sail. As intended, the satellite immediately began to lose alti-tude, and re-entered the atmosphere just 72 days later – thus demonstrating for the first time the de-orbiting of a spacecraft using European inflatable and drag-sail technologies. The boom/drag-sail technology developed by SSC will next be used on the RemoveDebris mission, due for launch in 2018, which will demon-strate the capturing and de-orbiting of artificial space debris targets using a net and harpoon system

InflateSail de-orbit flight demonstration results and follow-on drag-sail applications

The InflateSail (QB50-UK06) CubeSat, designed and built at the Surrey Space Centre (SSC) for the Von Karman Institute (VKI), Belgium, was one of the technology demonstrators for the European Commission’s QB50 programme. The 3.2 kg 3U CubeSat was equipped with a 1 metre long inflatable mast and a 10m2 deployable drag sail. InflateSail's primary mission was to demonstrate the effectiveness of using a drag sail in Low Earth Orbit (LEO) to dramatically increase the rate at which satellites lose altitude and re-enter the Earth's atmosphere and it was one of 31 satellites that were launched simultaneously on the PSLV (polar satellite launch vehicle) C-38 from Sriharikota, India on 23rd June 2017 into a 505km, 97.44o Sun-synchronous orbit. Shortly after safe deployment in orbit, InflateSail automatically activated its payload. Firstly, it inflated its metrelong metal-polymer laminate tubular mast, and then activated a stepper motor to extend four lightweight bi-stable rigid composite (BRC) booms from the end of the mast, so as to draw out the 3.1m x 3.1m square, 12m thick polyethylene naphthalate (PEN) drag-sail. As intended, the satellite immediately began to lose altitude, causing it to re-enter the atmosphere just 72 days later – thus successfully demonstrating for the first time the de-orbiting of a spacecraft using European inflatable and drag-sail technologies. The InflateSail project was funded by two European Commission Framework Program Seven (FP7) projects: DEPLOYTECH and QB50. DEPLOYTECH had eight European partners including DLR, Airbus France, RolaTube, Cambridge University, and was assisted by NASA Marshall Space Flight Center. DEPLOYTECH’s objectives were to advance the technological capabilities of three different space deployable technologies by qualifying their concepts for space use. QB50 was a programme, led by VKI, for launching a network of 50 CubeSats built mainly by university teams all over the world to perform first-class science in the largely unexplored lower thermosphere. The boom/drag-sail technology developed by SSC will next be used on a third FP7 Project: RemoveDebris, launched in 2018, which will demonstrate the capturing and de-orbiting of artificial space debris targets using a net and harpoon system. This paper describes the results of the InflateSail mission, including the observed effects of atmospheric density and solar activity on its trajectory and body dynamics. It also describes the application of the technology to RemoveDebris and its potential as a commercial de-orbiting add-on package for future space missions

Prolonged pre-firing pancreatic compression with linear staplers in distal pancreatectomy: a valuable technique for post-operative pancreatic fistula prevention

Purpose: Post-operative pancreatic fistula (POPF) remains the main complication after distal pancreatectomy (DP). The aim of this study is to evaluate the potential benefit of different durations of progressive stapler closure on POPF rate and severity after DP. Methods: Patients who underwent DP between 2016 and 2023 were retrospectively enrolled and divided into two groups according to the duration of the stapler closure: those who underwent a progressive compression for < 10 min and those for ≥ 10 min. Results: Among 155 DPs, 83 (53.5%) patients underwent pre-firing compression for < 10 min and 72 (46.5%) for ≥ 10 min. As a whole, 101 (65.1%) developed POPF. A lower incidence rate was found in case of ≥ 10 min compression (34-47.2%) compared to < 10 min compression (67- 80.7%) (p = 0.001). When only clinically relevant (CR) POPFs were considered, a prolonged pre-firing compression led to a lower rate (15-20.8%) than the < 10 min cohort (32-38.6%; p = 0.02). At the multivariate analysis, a compression time of at least 10 min was confirmed as a protective factor for both POPF (OR: 5.47, 95% CI: 2.16-13.87; p = 0.04) and CR-POPF (OR: 2.5, 95% CI: 1.19-5.45; p = 0.04) development. In case of a thick pancreatic gland, a prolonged pancreatic compression for at least 10 min was significantly associated to a lower rate of CR-POPF compared to < 10 min (p = 0.04). Conclusion: A prolonged pre-firing pancreatic compression for at least 10 min seems to significantly reduce the risk of CR-POPF development. Moreover, significant advantages are documented in case of a thick pancreatic gland

Association of kidney disease measures with risk of renal function worsening in patients with type 1 diabetes

Background: Albuminuria has been classically considered a marker of kidney damage progression in diabetic patients and it is routinely assessed to monitor kidney function. However, the role of a mild GFR reduction on the development of stage 653 CKD has been less explored in type 1 diabetes mellitus (T1DM) patients. Aim of the present study was to evaluate the prognostic role of kidney disease measures, namely albuminuria and reduced GFR, on the development of stage 653 CKD in a large cohort of patients affected by T1DM. Methods: A total of 4284 patients affected by T1DM followed-up at 76 diabetes centers participating to the Italian Association of Clinical Diabetologists (Associazione Medici Diabetologi, AMD) initiative constitutes the study population. Urinary albumin excretion (ACR) and estimated GFR (eGFR) were retrieved and analyzed. The incidence of stage 653 CKD (eGFR < 60 mL/min/1.73 m2) or eGFR reduction > 30% from baseline was evaluated. Results: The mean estimated GFR was 98 \ub1 17 mL/min/1.73m2 and the proportion of patients with albuminuria was 15.3% (n = 654) at baseline. About 8% (n = 337) of patients developed one of the two renal endpoints during the 4-year follow-up period. Age, albuminuria (micro or macro) and baseline eGFR < 90 ml/min/m2 were independent risk factors for stage 653 CKD and renal function worsening. When compared to patients with eGFR > 90 ml/min/1.73m2 and normoalbuminuria, those with albuminuria at baseline had a 1.69 greater risk of reaching stage 3 CKD, while patients with mild eGFR reduction (i.e. eGFR between 90 and 60 mL/min/1.73 m2) show a 3.81 greater risk that rose to 8.24 for those patients with albuminuria and mild eGFR reduction at baseline. Conclusions: Albuminuria and eGFR reduction represent independent risk factors for incident stage 653 CKD in T1DM patients. The simultaneous occurrence of reduced eGFR and albuminuria have a synergistic effect on renal function worsening

Integrated Flight & Ground Software Framework for Fast Mission Timelines

Flight and ground segment software in university missions is often developed only after hardware has matured sufficiently towards flight configuration and also as bespoke codebases to address key subsystems in power, communications, attitude, and payload control with little commonality. This bespoke software process is often hardware specific, highly sequential, and costly in staff/monitory resources and, ultimately, development time. Within Surrey Space Centre (SSC), there are a number of satellite missions under development with similar delivery timelines that have overlapping requirements for the common tasks and additional payload handling. To address the needs of multiple missions with limited staff resources in a given delivery schedule, computing commonality for both flight and ground segment software is exploited by implementing a common set of flight tasks (or modules) which can be automatically generated into ground segment databases to deliver advanced debugging support during system end-to-end test (SEET) and operations. This paper focuses on the development, implementation, and testing of SSC’s common software framework on the Stellenbosch ADCS stack and OBC emulators for numerous missions including Alsat-1N, RemoveDebris, SME-SAT, and InflateSail. The framework uses a combination of open-source embedded and enterprise tools such as the FreeRTOS operating system coupled with rapid development templates used to auto-generate C and Python scripts offline from ‘message databases’. In the flight software, a ‘core’ packet router thread forwards messages between threads for inter process communication (IPC). On the ground, this is complemented with an auto-generated PostgreSQL database and web interface to test, log, and display results in the SSC satellite operations centre. Profiling is performed using FreeRTOS primitives to manage module behaviour, context, time and memory – especially important during integration. This new framework has allowed for flight and ground software to be developed in parallel across SSC’s current and future missions more efficiently, with fewer propagated errors, and increased consistency between the flight software, ground station and project documentation

Integrated Flight & Ground Software Framework for Fast Mission Timelines

Flight and ground segment software in university missions is often developed only after hardware has matured sufficiently towards flight configuration and also as bespoke codebases to address key subsystems in power, communications, attitude, and payload control with little commonality. This bespoke software process is often hardware specific, highly sequential, and costly in staff/monitory resources and, ultimately, development time. Within Surrey Space Centre (SSC), there are a number of satellite missions under development with similar delivery timelines that have overlapping requirements for the common tasks and additional payload handling. To address the needs of multiple missions with limited staff resources in a given delivery schedule, computing commonality for both flight and ground segment software is exploited by implementing a common set of flight tasks (or modules) which can be automatically generated into ground segment databases to deliver advanced debugging support during system end-to-end test (SEET) and operations. This paper focuses on the development, implementation, and testing of SSC’s common software framework on the Stellenbosch ADCS stack and OBC emulators for numerous missions including Alsat-1N, RemoveDebris, SME-SAT, and InflateSail. The framework uses a combination of open-source embedded and enterprise tools such as the FreeRTOS operating system coupled with rapid development templates used to auto-generate C and Python scripts offline from ‘message databases’. In the flight software, a ‘core’ packet router thread forwards messages between threads for inter process communication (IPC). On the ground, this is complemented with an auto-generated PostgreSQL database and web interface to test, log, and display results in the SSC satellite operations centre. Profiling is performed using FreeRTOS primitives to manage module behaviour, context, time and memory – especially important during integration. This new framework has allowed for flight and ground software to be developed in parallel across SSC’s current and future missions more efficiently, with fewer propagated errors, and increased consistency between the flight software, ground station and project documentation

The InflateSail CubeSat Mission – The First European Demonstration of Drag-Sail De-Orbiting

The InflateSail (QB50-UK06) CubeSat, designed and built at the Surrey Space Centre (SSC) at the University of Surrey, UK, for the Von Karman Institute (VKI), Belgium – was one of the technology demonstrators for the QB50 pro-gramme. The 3.2 kilogram 3U CubeSat was equipped with a 1 metre long inflat-able boom and a 10m2 deployable drag sail. InflateSail's primary mission was to demonstrate the effectiveness of using a drag sail in Low Earth Orbit (LEO) to dramatically increase the rate at which satellites lose altitude and re-enter the Earth's atmosphere and it was one of 31 satellites that were launched simultane-ously on the PSLV (polar satellite launch vehicle) C-38 from Sriharikota, India on 23rd June 2017 into a 505km, 97.44o Sun-synchronous orbit (SSO). Shortly after orbital insertion, InflateSail booted-up, and, once safely clear of the other satellites on the launch, it automatically activated its payload – firstly, deploying a 1 metre long inflatable boom comprising a metal-polymer laminate tube, using a cool gas generator (CGG) to provide the inflation gas, and secondly, using a brushless DC motor at the end of the boom to extend four lightweight bistable rigid composite (BRC) booms to draw out the 3.1m x 3.1m square, 12 micron thick polymer drag-sail. As intended, the satellite immediately began to lose alti-tude, and re-entered the atmosphere just 72 days later – thus demonstrating for the first time the de-orbiting of a spacecraft using European inflatable and drag-sail technologies. The boom/drag-sail technology developed by SSC will next be used on the RemoveDebris mission, due for launch in 2018, which will demon-strate the capturing and de-orbiting of artificial space debris targets using a net and harpoon system

Flight Results of the InflateSail Spacecraft and Future Applications of Drag Sails

The InflateSail CubeSat, designed and built at the Surrey Space Centre (SSC) at the University of Surrey, UK, for the Von Karman Institute (VKI), Belgium, is one of the technology demonstrators for the QB50 programme. The 3.2 kilogram InflateSail is “3U” in size and is equipped with a 1 metre long inflatable boom and a 10 square metre deployable drag sail. InflateSail's primary goal is to demonstrate the effectiveness of using a drag sail in Low Earth Orbit (LEO) to dramatically increase the rate at which satellites lose altitude and re-enter the Earth's atmosphere. InflateSail was launched on Friday 23rd June 2017 into a 505km Sun-synchronous orbit. Shortly after the satellite was inserted into its orbit, the satellite booted up and automatically started its successful deployment sequence and quickly started its decent. The spacecraft exhibited varying dynamic modes, capturing in-situ attitude data throughout the mission lifetime. The InflateSail spacecraft re-entered 72 days after launch. This paper describes the spacecraft and payload, and analyses the effect of payload deployment on its orbital trajectory. The boom/drag-sail technology developed by SSC will next be used on the RemoveDebris mission, which will demonstrate the applicability of the system to microsat deorbiting

The InflateSail CubeSat Mission – The First European Demonstration of Drag-Sail De-Orbiting

The InflateSail (QB50-UK06) CubeSat, designed and built at the Surrey Space Centre (SSC) at the University of Surrey, UK, for the Von Karman Institute (VKI), Belgium – was one of the technology demonstrators for the QB50 pro-gramme. The 3.2 kilogram 3U CubeSat was equipped with a 1 metre long inflat-able boom and a 10m2 deployable drag sail. InflateSail's primary mission was to demonstrate the effectiveness of using a drag sail in Low Earth Orbit (LEO) to dramatically increase the rate at which satellites lose altitude and re-enter the Earth's atmosphere and it was one of 31 satellites that were launched simultane-ously on the PSLV (polar satellite launch vehicle) C-38 from Sriharikota, India on 23rd June 2017 into a 505km, 97.44o Sun-synchronous orbit (SSO). Shortly after orbital insertion, InflateSail booted-up, and, once safely clear of the other satellites on the launch, it automatically activated its payload – firstly, deploying a 1 metre long inflatable boom comprising a metal-polymer laminate tube, using a cool gas generator (CGG) to provide the inflation gas, and secondly, using a brushless DC motor at the end of the boom to extend four lightweight bistable rigid composite (BRC) booms to draw out the 3.1m x 3.1m square, 12 micron thick polymer drag-sail. As intended, the satellite immediately began to lose alti-tude, and re-entered the atmosphere just 72 days later – thus demonstrating for the first time the de-orbiting of a spacecraft using European inflatable and drag-sail technologies. The boom/drag-sail technology developed by SSC will next be used on the RemoveDebris mission, due for launch in 2018, which will demon-strate the capturing and de-orbiting of artificial space debris targets using a net and harpoon system