{"id":350,"date":"2017-08-28T13:16:23","date_gmt":"2017-08-28T11:16:23","guid":{"rendered":"https:\/\/aerospaceresearch.net\/?p=350"},"modified":"2017-08-31T09:20:18","modified_gmt":"2017-08-31T07:20:18","slug":"gsoc2017-introduction-to-the-generic-creation-of-a-ground-station-using-usoc","status":"publish","type":"post","link":"https:\/\/aerospaceresearch.net\/?p=350","title":{"rendered":"[GSOC2017] Introduction to the generic creation of a ground station using USOC"},"content":{"rendered":"

Introduction<\/h1>\n

\"\"<\/p>\n

The Universal Space Operations Center<\/strong>, USOC, is an\u00a0open-source tool that allows a simple and easy creation of a working groundstation to aid (student) space projects.<\/p>\n

Due to the fact that the functionality of every experiment should be checked before lift-off, a communication software for up- und downlink is required.\u00a0USOC follows a generic approach and offers the possibility to write this software automatically using a configuration file. The program structure is divided into three main components:<\/p>\n

    \n
  1. Communication software<\/li>\n
  2. Graphical user interface (GUI)<\/li>\n
  3. Controller for interaction between communication software and graphical user interface<\/li>\n<\/ol>\n

    Based on the input of the user in the configuration file, the GUI and partially also the controllers can be written automatically.\u00a0In this matter, USOC generates appropriate functionalities within\u00a0the controllers for individual GUI contents, which can then be adapted manually.\u00a0Changes in the configuration file are detected, localized and the corresponding GUI structures and controller functionalities are regenerated. If these are manually written functionalities, they are recognized and not overwritten.\u00a0USOC also brings\u00a0pre-coded functions, such as\u00a0communication via serial ports and\/or the Iridium satellite network, as well as a three-dimensional visualization of GNSS data. For further details of these functions, I would like to refer to the GSoC2017 project of Valentin Starlinger, whose blog post can be reached here<\/a>.<\/p>\n

    In this way, essential parts of a ground segment software can be created quickly and easily. Because of the wide diversity concerning the experiments in the space sector,\u00a0people from all over the world can use USOC\u00a0and add functionalities for their individual project to develop\u00a0and extend\u00a0the Universal Space Operations Center.<\/span><\/p>\n

    <\/p>\n

    Development Process<\/h1>\n

    USOC has been\u00a0programmed in Java using the Netbeans IDE. Instead of Java Swing, which is the\u00a0library used for the\u00a0MIRKA2-RX<\/a>\u00a0ground segment software, JavaFX was\u00a0used for the GUI as it provides advantages such as the separation of application logic and application design and the support of Cascading Style Sheets (CSS) for easy-to-handle and individual design adjustments.
    \nJavaFX provides two different ways of creating GUI\u2019s:<\/p>\n

      \n
    1. The GUI can be created in just one single file using JavaFX. Application design and application logic are merged.<\/li>\n
    2. With FXML JavaFX introduces an XML-based language that provides the structure in order to build a user interface separate from the application logic of the code. This structure can be coded\u00a0manually or by using the GUI builder \u2018Scene Builder\u2019.<\/li>\n<\/ol>\n

      Due to the separation of application design and application logic, the code is easier to maintain. Therefore, a JavaFX FXML application has\u00a0been preferred for this project.\u00a0In addition, the hierarchical markup language FXML is very suitable for the generic approach.<\/p>\n

      At the beginning of the project, thoughts about a general, reasonable structure of the ground station were made. This was subsequently implemented. By introducing a Java Properties file as the configuration file with\u00a0an associated syntax for specifying the GUI content, it was then possible to generically create\u00a0first parts of the interface.\u00a0This approach was continued until all desired functionalities were implemented in a generic manner.<\/p>\n

      Then a Java Properties comparison file was created and the Java class ConfigHandler<\/em> was coded.\u00a0The comparison file contains all the keywords and corresponding values \u200b\u200bof the configuration file. In this way, changes can be detected.\u00a0The ConfigHandler<\/em> communicates with the configuration file. It controls the syntax of the entered values, detects and locates changes and forwards them to the GuiBuilder<\/em> class. Afterwards\u00a0the GuiBiulder<\/em> was coded, which writes the FXML structures as well as\u00a0the corresponding controllers automatically based on the user’s input.<\/p>\n

      The last step consisted of merging the progress of Valentin Starlingers\u00a0project<\/a>\u00a0with mine.<\/p>\n

      User Manual<\/h1>\n

      USOC Files<\/h2>\n

      Since an overview of the code is relevant for the use of USOC, the most important files for the arrangement\u00a0of the graphical user interface seen in the figure below are briefly presented in the following.<\/p>\n

      \"\"<\/p>\n

      FXML Files<\/h3>\n

      These\u00a0files\u00a0are all generated automatically based on the configuration file.\u00a0Manual changes <\/strong>are not provided<\/strong>.<\/p>\n

      MainFrame.fxml<\/h4>\n

      The MainFrame is the main window of the ground station. It is divided into the MainPanel, the LogPanel and, if specified in the configuration file, the StatePanel.<\/p>\n

      MainFrame with keyword\u00a0statePanel<\/em> set to\u00a0true<\/em>:
      \n\"\"MainFrame with keyword\u00a0statePanel<\/em> set to\u00a0false:
      \n<\/em>\"\"<\/p>\n

      MainPanel.fxml<\/h4>\n

      The MainPanel is the dynamic central window of the MainFrame. The diagrams are shown here. When configured in the configuration file, the three-dimensional visualization of GNSS data can be accessed via the „GNSS 3D View“ tab in the MainPanel.<\/p>\n

      \"\"<\/p>\n

      LogPanel.fxml<\/h4>\n

      The LogPanel is located on the right side of the MainFrame. Various communication paths are displayed here. Communication via the serial port and via the Iridium satellite network are already pre-coded. Individual tabs can be created via the configuration\u00a0file.
      \n\"\"<\/p>\n

      StatePanel.fxml<\/h4>\n

      The StatePanel is located on the left side of the MainFrame. Various parameters such as current modes can be displayed here.<\/p>\n

      iridiumpanel.fxml<\/h4>\n

      The IridiumPanel.fxml file contains the FXML structure of the Iridium tab in the LogPanel.<\/p>\n

      serialpanel.fxml<\/h4>\n

      The SerialPanel.fxml\u00a0file contains the FXML structure of the Serial\u00a0tab in the LogPanel.<\/p>\n

      Configuration Files<\/h3>\n

      config.properties<\/h4>\n

      The config.properties file contains all necessary information to set up the graphical user interface of the ground station.<\/p>\n

      configMod.properties<\/h4>\n

      The configmod.properties file serves as a comparison file to detect changes within configuration file. It contains all keywords and associated values \u200b\u200bof the config.properties file. During\u00a0each program run, it is matched with the config.properties file and updated afterwards.\u00a0Manual changes <\/strong>are not provided<\/strong>.<\/p>\n

      GUI Controller<\/h3>\n

      These\u00a0files\u00a0are all generated automatically based on the configuration file.\u00a0Manual changes <\/strong>are not provided<\/strong>.\u00a0The generated dummy methods, which are marked by the comment ‚\/\/Automatically generated method dummyMethod()‘<\/em>, can be filled in manually. If the files are regenerated due to changes in the configuration file, the manually entered method contents are recognized and not overwritten.<\/p>\n

      MainPanelController.java<\/h4>\n

      The MainPanelController<\/em> is a class whose methods ensure the functionality of the MainPanel. The charts are declared and records are assigned.<\/p>\n

      LogPanelController.java<\/h4>\n

      The LogPanelController<\/em> provides the functionality of the LogPanel. Apart from pre-coded methods for the SerialLog and IridiumLog, a dummy method is\u00a0written for each button of the individually designed tabs. These methods can be supplemented manually. Those method\u00a0contents are recognized and will not be lost if the button label has been changed. Then the corresponding FXML structure and controller are regenerated.<\/p>\n

      StatePanelcontroller.java<\/h4>\n

      The StatePanelController contains a method for setting and updating the labels in the StatePanel. A label is automatically set for every entered keyword.<\/p>\n

      GuiBuilder.java<\/h3>\n
      \n

      The GuiBuilder.java<\/em> class includes methods for regenerating individual FXML structures. Manually added method contents are recognized at specified points in order to ensure these when changes are made to corresponding GUI elements.\u00a0The GuiBuilder\u00a0includes the following methods:<\/span><\/p>\n