• Journal of Astronomy and Space Sciences
• /
• v.19 no.2
• /
• pp.97-106
• /
• 2002

The design feature of KOMPSAT-2 simulator based on object oriented design methodology in terms of unified modeling language (UML) has been discussed in this paper. Also, we present how to embed flight software into the simulator. Flight software em-bedding for KOMPSAT-2 simulator is compared to that of the KOMPSAT-1 simulator.

• 제어로봇시스템학회:학술대회논문집
• /
• 2003.10a
• /
• pp.706-710
• /
• 2003

In this paper, we will present brief design feature, implementations, and tests for verification of KOMPSAT-2 simulator, which is a subsystem of KOMPSAT-2 MCE. SIM is implemented on PC server to minimize costs and troubles on embedding onboard flight software into SIM, OOA/OOD methodology is employed to maximized S/W reusability, and XML is used for S/C characteristics, TC, TM and Simulation data instead of commercial DB. Consequently, we can reduce costs for the system, efforts embedding flight software, and maximize software reusability. SIM subsystem test was performed successfully.

• ETRI Journal
• /
• v.27 no.2
• /
• pp.140-152
• /
• 2005

In this paper, we present design features, implementation, and validation of a satellite simulator subsystem for the Korea Multi-Purpose Satellite-2 (KOMPSAT-2). The satellite simulator subsystem is implemented on a personal computer to minimize costs and trouble on embedding onboard flight software into the simulator. An object-oriented design methodology is employed to maximize software reusability. Also, instead of a high-cost commercial database, XML is used for the manipulation of spacecraft characteristics data, telecommand, telemetry, and simulation data. The KOMPSAT-2 satellite simulator subsystem is validated by various simulations for autonomous onboard launch and early orbit phase operations, anomaly operation, and science fine mode operation. It is also officially verified by successfully passing various tests such as the satellite simulator subsystem test, mission control element system integration test, interface test, site installation test, and acceptance test.