Figure 7 - uploaded by Martin Langer
Content may be subject to copyright.
Contexts in source publication
Context 1
... user data rate of the VHF downlink can be derived from the VHF frames recorded by the ground segment. Figure 7 shows the VHF data rate over the duration of the flight. Values are averaged over a window of 60 seconds. ...
Context 2
... the flight, the ground station software had to be restarted seven times. Restarts of the ground station software and the resulting communication dropouts are marked in Figure 7 as red vertical lines. Please note that due to the time needed to restart the ground station soft- ware there is some discrepancy in time between the two graphs in Figures 7 and 8. ...
Context 3
... of the ground station software and the resulting communication dropouts are marked in Figure 7 as red vertical lines. Please note that due to the time needed to restart the ground station soft- ware there is some discrepancy in time between the two graphs in Figures 7 and 8. ...
Context 4
... minute 56, frames with a repetitive pattern with a size of 990 bit were transmitted for 240 seconds. At the same time, we observed a sharp decline in the data rate (see mark 1 in Figure 7). This may have been due to a lack of bit transitions in the transmitted pattern, which caused the receiver's timing recovery to fall out of lock. ...
Context 5
... declines in the SNR in minutes 89 and 96 resulted in frame losses, which in turn caused drops in the data rate (see marks 2 and 3 in Figure 7). It is likely that these were caused by interference from nearby hand-held radio devices. ...
Similar publications
A low-cost, compact, and high gain Fabry–Perot cavity (FPC) antenna which operates at 300 GHz is presented. The antenna is fabricated using laser-cutting brass technology. The proposed antenna consists of seven metallic layers; a ground layer, an integrated stepped horn element (three-layers), a coupling layer, a cavity layer, and an aperture-frequ...
Citations
... During this mission the communication link was tested in the stratosphere over a distance of 270 km. 13 Payload As its scientific goal, the MOVE-II CubeSat will be used for the verification of novel 4-junction solar cells under space conditions. On top of the CubeSat one full size solar cell (8x4 cm 2 ) and four corresponding isotope cells (2x2 cm 2 ) are located . ...
MOVE-II (Munich Orbital Verification Experiment II) is a 1 Unit CubeSat currently under development at the Technical University of Munich (TUM). This paper reports on the technical as well as the organizational advancements of the project. With overall more than 130 students involved so far, the project is currently in Phase D, with the launch of the satellite scheduled for early 2018. For communication purposes, MOVE-II will utilize a novel robust and efficient radio protocol for small satellite radio links, called Nanolink, both on an UHF/VHF transceiver and an S-Band transceiver. The usual power restrictions of the 1U envelope are overcome by four deployable solar panels, which are held down and released by a reusable shape memory mechanism. This allows repeated tests of the mechanism and true test-as-your-fly philosophy. As its scientific goal, the MOVE-II CubeSat will be used for the verification of novel 4-junction solar cells. With a footprint of 10x10 cm, the payload consists of one full size solar cell (8x4 cm) and five positions (each 2x2 cm) for the corresponding isotype solar cells. As opposed to its predecessor mission, MOVE-II will be the first CubeSat of TUM utilizing a magnetorquer based, active attitude determination and control system (ADCS). The system consists of five Printed-Circuit-Boards with directly integrated magnetic coils, forming the outer shell of the spacecraft, and one so-called ADCS Mainboard, located in the board stack of the satellite. Each Sidepanel has its own microcontroller and is connected to the ADCS Mainboard with one of two redundant SPI buses. From an organizational point of view, we tried to increase the reliability of MOVE-II by fast prototyping and releases as well as enhanced hardware-in-the loop tests. We will present the application of agile software development in the project as well as methods that we applied to assure reliability on system level. For that purpose a Reliability Growth Model, based on our CubeSat Failure Database, was adapted for the project.
