Digital simulation interface system of surface satellite attitude and orbit control subsystem

Abstract

The invention provides a digital simulation interface system of a face satellite attitude and orbit control subsystem, and relates to the technical field of computer simulation. Interfaces are divided into two classes according to attributes, the first class is simulation class interfaces, and the second class is simulation class interfaces; the interface is used for initialization parameter setting, simulation process control, simulation target data acquisition and data interaction of a simulation state, a running log, a model event, energy simulation data, thermal simulation data and environment simulation data of an attitude and orbit control subsystem model; and the second type is a business type interface, and the interface is used for data interaction with other subsystems or the outside in the function operation of the attitude and orbit control subsystem. Definitions of the two types of interfaces can cover all simulation activities of a satellite attitude and orbit control subsystem, meanwhile, the related internal simulation activities and external simulation activities can be distinguished, and interface testing of a satellite digital subsystem model can be systematically carried out with the fewest units.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer simulation, in particular, to a digital simulation interface system for a satellite attitude and orbit control subsystem. BACKGROUND

[0002] The satellite attitude and orbit control subsystem mainly completes functions such as satellite orbit insertion, attitude change and maneuvering, so that the satellite can fly according to the predetermined attitude and orbit. In the digital simulation of the satellite attitude and orbit control subsystem, due to the complex function structure of the satellite attitude and orbit control system, the multiple data interaction links with each subsystem, and the multiple variable operation modes, the digital simulation interface structure of the satellite attitude and orbit control subsystem is huge and complex. In view of the above problems in the design of the digital simulation interface of the satellite attitude and orbit control subsystem, the present application provides a design method for the digital simulation interface of the satellite attitude and orbit control subsystem.

[0003] Patent document CN1890639A (application number: 200480036906.3) discloses a satellite simulation modeling system based on an interface standard model. The system comprises: a satellite subsystem standard model for simulating the operation of a physical satellite subsystem; a flight software module for generating a control signal for changing the operation state of the satellite subsystem standard model; an interface standard model for converting data transmitted from the satellite subsystem standard model and the flight software module into data to a receiving component and transmitting the converted data to the receiving component; and a model management unit for generating the satellite subsystem standard model and the interface standard model as independent component objects and controlling each component object to perform satellite simulation. SUMMARY

[0004] In view of the defects in the prior art, the present application aims to provide a digital simulation interface system for a satellite attitude and orbit control subsystem.

[0005] According to the present application, a digital simulation interface system for a satellite attitude and orbit control subsystem is provided, which comprises: a simulation class interface and a business class interface.

[0006] The simulation class interface is used to establish the connection between the model and the simulation platform, the target and the environment, and to support the model to carry out simulation activities.

[0007] The business class interface is used to simulate the business data flow of the installation.

[0008] The simulation class interface and the business class interface are hierarchically refined by using the functional component method, and the interfaces of each functional module are obtained, which are used to hierarchically refine the interface data of each functional module.

[0009] Preferably, the interface data of each functional module comprises basic information data, state data and performance data; wherein the basic information data adopts a unified data format; and the state data and the performance data are both represented by quantized data.

[0010] Preferably, the simulation-type interface comprises a simulation support-type interface and a data acquisition-type interface.

[0011] The simulation support-type interface is configured to support simulation running of the system.

[0012] The data acquisition-type interface is configured to interact with log and state-type data.

[0013] The simulation support-type interface comprises an initialization interface, a simulation control interface, an environment simulation data interface, an energy simulation data interface and a thermal simulation data interface.

[0014] The data acquisition-type interface comprises a running log interface, a model event interface and a simulation state interface.

[0015] Preferably, the initialization interface is configured to determine basic information parameters, total power consumption, total heat consumption, performance parameters, an initial attitude of the satellite, an initial working state, sensor performance parameter information, actuator performance parameter information and a power-on / off state.

[0016] The simulation control interface is configured to implement simulation control and simulation driving.

[0017] The environment simulation data interface is configured to realize centralized acquisition and utilization of objective physical quantities in the digital satellite simulation process through a unified environment interface setting.

[0018] The energy simulation interface is configured to realize energy interaction simulation between the attitude and orbit control subsystem and the power supply and distribution subsystem.

[0019] The thermal simulation data interface is configured to realize thermal interaction simulation between the attitude and orbit control subsystem and the thermal control subsystem.

[0020] Preferably, the simulation control interface comprises an instruction ID, an instruction type, a running mode, a current simulation time, a simulation running rate and a fault simulation.

[0021] The environment simulation data interface comprises attitude and orbit information of the satellite, satellite-borne load list information, sun position vector information, space environment, ground station environment parameters, remote control data, inter-satellite communication data and an angle between a sun array and a sun vector.

[0022] The energy simulation interface comprises basic information of the attitude and orbit control subsystem, single-machine current and single-machine voltage information.

[0023] The thermal simulation data interface comprises basic information of the attitude and orbit control subsystem and single machine thermal consumption information.

[0024] Preferably, the simulation state interface is used for describing basic information, working state, real-time simulation orbit epoch, orbit root number, real-time simulation attitude, real-time working state information of a sensor and real-time working state information of an actuator of the attitude and orbit control subsystem.

[0025] The running log interface is used for outputting log information of the attitude and orbit control model in the simulation running process.

[0026] The model event interface is used for outputting business event information of the attitude and orbit control model.

[0027] Preferably, the running log interface comprises running log data, and the running log data comprises basic information of the attitude and orbit control subsystem, current simulation time, log number, log level, function name, return value, return value description, data length and reserved word.

[0028] The model event interface comprises basic information of the attitude and orbit control subsystem, current simulation time, event number, event category, event description, data length and reserved word.

[0029] Preferably, the business class interface comprises business class data flow which is consistent with the actual installation and simulates the flow of the star information from the generation end to the processing end; and inside the satellite simulation model, the scheduling transmission and distribution of the data flow between the subsystems and the interaction of various simulation data and business data are realized by providing various virtual bus models.

[0030] Preferably, the business class interface comprises an event trigger class interface and a time trigger class interface.

[0031] The event trigger class interface comprises a bus data reading-in interface, a bus data writing-out interface, a serial port data reading-in interface, a serial port data outputting interface, an analog quantity outputting interface, an analog quantity inputting interface, an OC instruction inputting interface and an OC instruction outputting interface.

[0032] The time trigger class interface comprises a bus request interface.

[0033] Preferably, the bus data reading-in interface, the bus data writing-out interface, the serial port data reading-in interface, the serial port data outputting interface, the analog quantity outputting interface, the analog quantity inputting interface, the OC instruction inputting interface, the OC instruction outputting interface and the bus request interface all adopt the fixed address memory interaction mode to transfer data, which is consistent with the actual installation information flow on one hand and realizes the decoupling of the receiving and the sending on the other hand, so as to achieve the purpose of the loose coupling of the subsystems.

[0034] Compared with the prior art, the application has the following beneficial effects:

[0035] 1、The present application divides it into two interfaces of simulation class and business class from interface attribute, makes the overall structure of subsystem interface decoupling, improves the readability of interface protocol; the structure of describing basic information is unified, realizes the simplification of interface protocol, improves the reusability of interface; the interface of describing state and performance class all adopts quantitative characterization, improves the precision of simulation model;

[0036] 2、The present application provides a satellite attitude and orbit control subsystem digital simulation interface with comprehensive function coverage and simple and readable data structure, to assist relevant designers to complete the simulation digitization of satellite attitude and orbit control subsystem;

[0037] 3、The present application can help to promote the related digitization of satellite attitude and orbit control subsystem, and assist relevant designers to carry out the simulation digitization of subsystem. BRIEF DESCRIPTION OF DRAWINGS

[0038] Other features, objects and advantages of the present application will become more apparent from the following detailed description of non-limiting embodiments with reference to the attached drawings:

[0039] Fig. 1 It is a satellite attitude and orbit control subsystem interface diagram.

[0040] Fig. 2 It is a satellite attitude and orbit control subsystem interface structure diagram.

[0041] Fig. 3 It is a satellite attitude and orbit control subsystem interface structure diagram. DETAILED DESCRIPTION

[0042] The present application will be described in detail below with reference to specific embodiments. The following embodiments will help those skilled in the art to further understand the present application, but do not limit the present application in any form. It should be pointed out that, for those skilled in the art, without departing from the concept of the present application, a number of changes and improvements can be made. These all belong to the protection scope of the present application.

[0043] Example 1

[0044] According to the satellite attitude and orbit control subsystem digital simulation interface system provided by the present application, as shown in Figs. 1 to 3 It comprises: simulation class interface and business class interface;

[0045] The simulation class interface is used to establish the connection between the model and the simulation platform, the target and the environment, and to support the model to carry out simulation activities;

[0046] The business class interface is used for simulation installation business data flow;

[0047] The simulation type interface and the business type interface are classified and refined by using a functional component method, and the interface data of each functional module is classified and refined.

[0048] The interface data of each functional module includes basic information data, state data and performance data, wherein the basic information data adopts a unified data format, and the state data and the performance data are both represented by quantitative data.

[0049] More specifically, the simulation type interface includes a simulation support type interface and a data acquisition type interface.

[0050] The simulation support type interface is used for supporting the simulation running of the system.

[0051] The data acquisition type interface is used for log and state type data interaction.

[0052] The simulation support type interface includes an initialization interface, a simulation control interface, an environment simulation data interface, an energy simulation data interface and a thermal simulation data interface.

[0053] The data acquisition type interface includes a running log interface, a model event interface and a simulation state interface.

[0054] The initialization interface includes orbit dynamics initialization data for determining initial orbit root, orbit epoch, perturbation parameter and central celestial body gravity parameter, attitude dynamics initialization data for determining satellite initial attitude, sensor initialization data for determining initial working state and sensor performance parameter information, actuator initialization data for determining initial working state and actuator performance parameter information, management and extension unit initialization data for determining on-off state, and orbit maneuver control initialization data for determining basic information parameter, total power consumption, total heat consumption and performance parameter of the entire attitude and orbit control subsystem.

[0055] The simulation control interface includes instruction ID, instruction type, running mode, current simulation time, simulation running rate and fault simulation, and is used for realizing simulation control and simulation driving.

[0056] The environment simulation data interface includes attitude and orbit information of the satellite, satellite on-board load list information, sun position vector information, space environment, ground station environment parameter, remote control data, inter-satellite communication data and angle between solar array and sun vector, and solves the centralized acquisition and utilization of objective physical quantities in the digital satellite simulation process through unified environment interface setting.

[0057] The energy simulation data interface includes basic information of the attitude and orbit control subsystem, single machine current and single machine voltage information, and is used for solving energy interaction simulation between the attitude and orbit control subsystem and the power supply and distribution subsystem.

[0058] The thermal simulation data interface includes basic information of the attitude and orbit control subsystem and single machine heat consumption information, and is used for solving thermal interaction simulation between the attitude and orbit control subsystem and the thermal control subsystem.

[0059] The simulation state interface includes attitude and orbit control subsystem state data used for describing basic information and working state of the attitude and orbit control subsystem, orbit simulation state data used for determining real-time simulation orbit epoch and orbit root number, attitude simulation state data used for determining real-time simulation attitude, sensor state data used for determining real-time working state information of the sensor, and actuator simulation state data used for determining real-time working state information of the actuator.

[0060] The running log interface includes basic information of the attitude and orbit control subsystem, current simulation time, log number, log level, function name, return value, return value description, data length and reserved word, and is mainly used for outputting log information of the attitude and orbit control model in the simulation running process.

[0061] The model event data interface includes basic information of the attitude and orbit control subsystem, current simulation time, event number, event category, event description, data length and reserved word, and is mainly used for outputting business event information of the attitude and orbit control model, such as load working mode switching, antenna pointing adjustment, fault occurrence and the like.

[0062] The business class interface includes an event trigger class interface and a time trigger class interface.

[0063] The event trigger class interface includes a data reading-in interface from a bus, a data writing-in interface to a bus, a data reading-in interface from a serial port, a data output interface to a serial port, an analog quantity output interface, an analog quantity input interface, an OC instruction input interface and an OC instruction output interface; and the time trigger class interface includes a bus request interface.

[0064] The business class data interface makes the business class data flow consistent with the actual implementation, and simulates the flow of information on the satellite from a generation end to a processing end. Inside the satellite simulation model, by providing models of various virtual buses, scheduling and transmission and distribution of data flow between subsystems are realized, and interaction of various simulation data and business data is completed.

[0065] The bus read-in data interface, the bus write-in data interface, the serial port read-in data interface, the serial port output data interface, the analog output interface, the analog input interface, the OC instruction input interface, the OC instruction output interface and the bus request interface all adopt the fixed address memory interaction mode to transfer data, which is consistent with the actual information flow and realizes the decoupling of the receiving and the transmitting, so as to achieve the purpose of the loose coupling of the subsystems.

[0066] The application further provides a surface satellite attitude and orbit control subsystem digital simulation interface system, which can be realized by executing the process steps of the surface satellite attitude and orbit control subsystem digital simulation interface system implementation method, that is, the surface satellite attitude and orbit control subsystem digital simulation interface system implementation method can be understood as the preferred embodiment of the surface satellite attitude and orbit control subsystem digital simulation interface system by those skilled in the art.

[0067] Embodiment 2

[0068] Embodiment 2 is a preferred example of embodiment 1

[0069] According to the satellite attitude and orbit control subsystem digital simulation interface system implementation method provided by the application, the following steps are included:

[0070] Step one, define the initialization interface, which specifically includes the following fields: basic information parameters are represented by a general structure; total power consumption is represented by a floating point type; total heat consumption is represented by a floating point type; attitude measurement accuracy is represented by a floating point array (length 3); attitude pointing accuracy is represented by a floating point array (length 3); attitude stability is represented by a floating point array (length 3); maximum attitude offset angle is represented by a floating point type; east-west position keeping accuracy is represented by a floating point type; north-south position keeping accuracy is represented by a floating point type; sun orientation accuracy is represented by a floating point type; initial working mode is represented by an integer type, in this embodiment, 0: wheel control steady state against the ground, 1: magnetic control against the sun mode, 2: wheel control against the sun mode, 3: magnetic damping mode, 4: load task control mode, 5: orbit control mode, 6: jet against the sun mode, 7: magnetic wheel combined control mode, 8: flywheel damping mode, 9: open loop mode; orbit dynamics simulation parameters are represented by a structure; initial attitude parameters are represented by a structure; star sensor parameters are represented by a structure; fiber optic gyroscope parameters are represented by a structure; digital sun sensor is represented by a structure; analog sun sensor is represented by a structure; three-axis magnetometer is represented by a structure; flywheel is represented by a structure; magnetic torque meter is represented by a structure; GNC management unit is represented by a structure; GNC extension unit is represented by a structure.

[0071] Step two, define the basic information parameter structure, which specifically includes the following fields: number ID is represented by a character array; Chinese name is represented by a character array; English name is represented by a character array; type number is represented by an integer type.

[0072] Step three, define the single machine general attribute parameters, including the following fields: installation matrix represented by a floating-point array (4x4 matrix, stored by row), power consumption represented by a floating-point type, heat consumption represented by a floating-point type, working temperature range represented by a floating-point array (the first bit is the lower limit), mass represented by a floating-point type (unit: Kg).

[0073] Step four, define the orbit dynamics simulation parameter structure, including the following fields: orbit prediction model represented by an integer type (1: two-body model, 2: J2 model, 3: J4 model, 4: SGP4 model, 5: HPOP model); orbit epoch represented by a floating-point type (reduced Julian day); orbit elements represented by a floating-point array (length 6, Kepler six elements a, e, i, raan, w, ma); central celestial body gravity parameters represented by a structure, including gravity description file type represented by an integer type, in this embodiment, 1=EGM96.grv, 2=EGM2008.grv, 3=GEMT1.grv, 4=GGM01C.grv, 5=GGM02C.grv, 6=GGM03C.grv, 7=JGM2.grv, 8=JGM3.grv, 9=WGS72_ZonalsToJ4.grv, 10=WGS84.grv, 11=WGS84_EGM96.grv, 12=WGS84_old.grv, degree of zonal harmonic represented by an integer type, degree of zonal harmonic represented by an integer type, solid tide model, in this embodiment, 1=Fulltide, 2=Permanent tide only, 3=None, ocean tide perturbation represented by an integer type, in this embodiment, 0: not considered, 1: considered, solar radiation pressure perturbation parameters represented by a structure, including flag bit parameters represented by an integer type, model represented by an integer type (0: Spherical), light pressure parameter represented by a floating-point type, surface mass ratio represented by a floating-point type, shadow model represented by an integer type (0: None, 1: Cylindrical, 2: Dual Cone), considering boundary loss flag represented by an integer type (0: not considered, 1: considered), atmospheric / solar radiation flow resistance perturbation parameters represented by a structure, including flag bit parameters represented by an integer type (0: not considered, 1: considered), model represented by an integer type (0: Sphercial), resistance coefficient represented by a floating-point type, surface mass ratio represented by a floating-point type, atmospheric model represented by an integer type (1-10 represent different atmospheric models), daily 10.7 cm solar radiation flux represented by a floating-point type, average value of solar radiation flux F10.7 represented by a floating-point type, geomagnetic index Kp represented by a floating-point type, three-body gravity perturbation parameters represented by an integer array (length 9, the first bit is the solar gravity perturbation flag, the second bit is the moon, the third bit is Mercury, the fourth bit is Venus, and so on, 0 in the flag bit represents not considering, and 1 represents considering).

[0074] Step five, define the attitude parameter structure, including the following fields: roll angle represented by float type, pitch angle represented by float type, azimuth angle represented by float type, azimuth angle rate represented by float type, pitch angle rate represented by float type, roll angle rate represented by float type. (Default sequence 312, angle unit °, angular velocity unit ° / s)

[0075] Step six, define the star sensor parameter structure, including the following fields: basic parameter information represented by the general structure defined in step two, general attribute parameter of single machine represented by the general structure defined in step three, field of view of optical system represented by float type, angle measurement accuracy (random error) represented by float type, angle measurement accuracy (constant deviation) represented by float type, initial working state represented by integer type (0: off, 1: on).

[0076] Step seven, define the fiber-optic gyroscope parameter structure, including the following fields: basic parameter information represented by the general structure defined in step two, general attribute parameter of single machine represented by the general structure defined in step three, speed measurement range represented by float type, absolute error (constant drift stability) represented by float type, relative error (random walk) represented by float type, constant drift represented by float type, initial working state represented by integer type (0: off, 1: on).

[0077] Step eight, define the digital sun sensor parameter structure, including the following fields: basic parameter information represented by the general structure defined in step two, general attribute parameter of single machine represented by the general structure defined in step three, angle measurement accuracy (random error) represented by float type, constant drift represented by float type, initial working state represented by integer type (0: off, 1: on).

[0078] Step nine, define the analog sun sensor parameter structure, including the following fields: basic parameter information represented by the general structure defined in step two, general attribute parameter of single machine represented by the general structure defined in step three, fine measurement field represented by a float array (length 4), fine measurement accuracy represented by a float array (length 2), initial working state represented by integer type (0: off, 1: on).

[0079] Step ten, define the magnetometer parameter structure, including the following fields: basic parameter information represented by the general structure defined in step two, general attribute parameter of single machine represented by the general structure defined in step three, zero error (measurement accuracy) represented by float type, sensitivity error (noise) represented by float type, orthogonal error (stability) represented by float type, initial working state represented by integer type (0: off, 1: on).

[0080] Step eleven, define the flywheel parameter structure, including the following fields: basic parameter information represented by the general structure defined in step two, single machine general attribute parameters represented by the general structure defined in step three, maximum angular momentum represented by float type, angular momentum control error represented by float type, rotation speed range represented by float array (the first bit is the left boundary), initial working state represented by integer type (0: off, 1: on).

[0081] Step twelve, define the magnetic torque parameter structure, including the following fields: basic parameter information represented by the general structure defined in step two, single machine general attribute parameters represented by the general structure defined in step three, initial working state represented by integer type (0: off, 1: on).

[0082] Step thirteen, define the management unit parameter structure, including the following fields: basic parameter information represented by the general structure defined in step two, single machine general attribute parameters represented by the general structure defined in step three, initial working state represented by integer type (0: off, 1: on).

[0083] Step fourteen, define the extension unit parameter structure, including the following fields: basic parameter information represented by the general structure defined in step two, single machine general attribute parameters represented by the general structure defined in step three, initial working state represented by integer type (0: off, 1: on).

[0084] Step fifteen, define the simulation control interface, including the following fields: instruction ID represented by integer type, instruction type represented by integer type (1: start, 2: start and synchronization, 3: speed change, 4: time jump, 5: end, 6: pause), running mode represented by integer type, time jump time represented by float type (reduced Julian day), current simulation time represented by float type (reduced Julian day), running rate represented by float type, fault simulation represented by integer type, reserved word represented by character array (length is 1024).

[0085] Step sixteen, define the environment simulation data interface, including the following fields: real-time orbit information of the star in a structure, real-time attitude information of the star in a structure, a list of antennas on the star in a general list structure array, a list of radars on the star in a general list structure array, a list of cameras on the star in a general list structure array, a list of optical heads on the star in a general list structure array, a solar position vector in J2000 coordinate system represented by a float array (x, y, z in turn), a solar position vector in VVLH coordinate system represented by a float array (x, y, z in turn), ground station environment parameters represented by a structure array, space environment represented by a structure array, remote control data represented by a character array (length 1024), inter-satellite communication data represented by a character array (length 1024), the angle between the solar array normal and the solar vector represented by a float type, and a reserved field represented by a character array (length 1024).

[0086] Step seventeen, define the orbit state data, including the following fields: orbit type represented by an integer (0: PosVel, 1: Kepler, 2: TLE, 3: LLA), orbit epoch represented by a structure (year, mon, day, hour, minu, sec), orbit epoch (reduced Julian day) represented by a float type, position and velocity in J2000 coordinate system represented by a structure (x, y, z, Vx, Vy, Vz), Kepler elements represented by a structure (a, e, i, raan, w, ma).

[0087] Step eighteen, define the attitude state data, including the following fields: attitude type represented by an integer (0: Euler angles, 1: quaternion), Euler angles represented by a structure (including rotation sequence and three rotation angle information), quaternion represented by a float array.

[0088] Step nineteen, define the general list information, including the following fields: device basic information represented by the general structure defined in step two, pointing information (satellite body system) represented by a float array (length 2, the first bit is azimuth).

[0089] Step twenty, define the ground station environment parameters, including the following fields: basic information represented by the general structure defined in step two, position information represented by a float array (longitude, latitude, height in turn), relative position VVLH represented by a float array (longitude, latitude, height in turn), relative position in the body system represented by a float array (longitude, latitude, height in turn), relative position in the station horizontal coordinate system represented by a float array (longitude, latitude, height in turn), ground EIRP value represented by a float type, ground G / T value represented by a float type, ground environment represented by a structure.

[0090] Step twenty-one, define the ground environment structure body described in step twenty, specifically including the following fields: fog level is represented by integer (0 = NULL, 1 = small fog, 2 = medium fog, 3 = heavy fog, 4 = thick fog), rain level is represented by integer (0 = NULL, 1 = drizzle, 2 = light rain, 3 = moderate rain, 4 = heavy rain, 5 = storm, 6 = heavy storm, 7 = super heavy storm), snow level is represented by integer (0 = NULL, 1 = light snow, 2 = moderate snow, 3 = heavy snow, 4 = heavy snow), temperature is represented by float, water vapor density is represented by float, atmospheric pressure is represented by float, wind speed is represented by float array (in turn, the north component, the east component).

[0091] Step twenty-two, define the space environment data structure body, specifically including the following fields: geomagnetic index Kp is represented by float, ionospheric attenuation is represented by float, noise temperature is represented by float, solar storm level is represented by integer, geomagnetic field component in the body-fixed system is represented by float array (in turn, the components in XYZ directions), background noise is represented by float, single particle event is represented by integer.

[0092] Step twenty-three, define the running log structure body, specifically including the following fields: basic information is represented by the general structure defined in step two, simulation time is represented by float (reduced Julian day), log level is represented by integer (1 = fatal [FATAL], 2 = error [ERROR], 3 = warning [WARN], 4 = notification [INFO], 5 = debugging [DEBUG]), log number is represented by long integer, function name is represented by character array (length 32), return value is represented by character array (length 8), return value description is represented by character array (length 100), data length is represented by integer, reserved word is represented by character array (length 100).

[0093] Step twenty-four, define the model event data structure body, specifically including the following fields: basic information is represented by the general structure defined in step two, simulation time is represented by float (reduced Julian day), event category is represented by integer (1 = power-on / off class, 2 = working mode switching class, 3 = fault class, 4 = service execution condition class), event number is represented by character array (length 8), event description is represented by character array (length 100), data length is represented by integer, reserved word is represented by character array (length 100).

[0094] Step twenty-five, define the energy simulation data structure body, specifically including the following fields: subsystem basic information is represented by the general structure defined in step two, single machine energy consumption list is represented by structure array.

[0095] Step twenty-six, define single machine energy consumption data structure body, specifically including the following fields: single machine basic information is expressed by the general structure defined in step two, single machine current is expressed by floating point type, single machine voltage is expressed by floating point type.

[0096] Step twenty-seven, define thermal simulation data structure body, specifically including the following fields: sub-system basic information is expressed by the general structure defined in step two, single machine heat consumption list is expressed by structure body array.

[0097] Step twenty-eight, define single machine heat consumption structure body, specifically including the following fields: single machine basic information is expressed by the general structure defined in step two, single machine heat consumption is expressed by floating point type.

[0098] Step twenty-nine, define service class interface, service class interface data format and implementation remain consistent, adopt variable assignment transmission mode, input and output data interface requests according to event triggering mechanism, and is uniformly called by the bus model of the whole star, and the bus request interface requests according to time triggering mechanism.

[0099] Those skilled in the art know that, in addition to implementing the system, device and each module thereof provided by the present application in the form of pure computer readable program code, the same program can be realized by logically programming the method steps to make the system, device and each module thereof provided by the present application in the form of logic gate, switch, application specific integrated circuit, programmable logic controller and embedded microcontroller. Therefore, the system, device and each module thereof provided by the present application can be considered as a hardware component, and the modules included therein for realizing various programs can also be considered as structures in the hardware component; the modules for realizing various functions can also be considered as both software programs for realizing methods and structures in the hardware component.

[0100] The specific embodiments of the present application are described above. It needs to be understood that the present application is not limited to the above specific embodiments, and those skilled in the art can make various changes or modifications within the scope of the claims, which does not affect the essential content of the present application. In the case of no conflict, the embodiments of the present application and the features in the embodiments can be combined with each other at will.

Claims

1. A digital simulation interface system for a satellite attitude and orbit control subsystem, characterized by, The application relates to a simulation interface and a business interface. The simulation interface is used for establishing a model and connecting a simulation platform, a target and an environment, and supporting the model to carry out simulation activities. The business interface is used for simulating business data flow. The simulation interface and the business interface are classified and refined by using a functional component method, and the interface data of each functional module is classified and refined. The interface data of each functional module comprises basic information data, state data and performance data; wherein the basic information data adopts a unified data format; and the state data and the performance data are both represented by quantitative data.

2. The digital simulation interface system for the attitude and orbit control subsystem of a formation flying satellite according to claim 1, wherein, The simulation interface comprises a simulation support interface and a data acquisition interface.

3. The digital simulation interface system for the attitude and orbit control subsystem of a formation flying satellite according to claim 1, wherein, The simulation support interface is used for supporting simulation running of the system. The data acquisition interface is used for log and state data interaction. The simulation support interface comprises an initialization interface, a simulation control interface, an environment simulation data interface, an energy simulation data interface and a thermal simulation data interface. The data acquisition interface comprises a running log interface, a model event interface and a simulation state interface. The initialization interface is used for determining basic information parameters, total power consumption, total heat consumption, performance parameters, a satellite initial attitude, an initial working state, sensitive sensor performance parameter information, actuator performance parameter information and on-off state.

4. The digital simulation interface system for the MEO satellite attitude and orbit control subsystem according to claim 3, characterized in that, The simulation control interface is used for realizing simulation control and simulation driving. The environment simulation data interface is used for realizing centralized acquisition and utilization of objective physical quantities in a digital satellite simulation process through a unified environment interface setting. The energy simulation interface is used for realizing energy interaction simulation between an attitude and orbit control subsystem and a power supply and distribution subsystem. The thermal simulation data interface is used for realizing thermal interaction simulation between the attitude and orbit control subsystem and a thermal control subsystem. The simulation control interface comprises an instruction ID, an instruction type, a running mode, a current simulation time, a simulation running rate and fault simulation.

5. The digital simulation interface system for the MEO satellite attitude and orbit control subsystem according to claim 4, characterized in that, The environment simulation data interface comprises attitude and orbit information of a star, star-borne load list information, sun position vector information, a space environment, ground station environment parameters, remote control data, inter-satellite communication data and an angle between a sun array and a sun vector. The energy simulation interface comprises basic information of the attitude and orbit control subsystem, single-machine current and single-machine voltage information. The thermal simulation data interface comprises basic information of the attitude and orbit control subsystem and single-machine heat consumption information. The simulation state interface is used for describing basic information of the attitude and orbit control subsystem, a working state, a real-time simulation orbit epoch, orbit root numbers, a real-time simulation attitude, sensitive sensor real-time working state information and actuator real-time working state information.

6. The digital simulation interface system for the MEO satellite attitude and orbit control subsystem according to claim 3, wherein, The running log interface is used for outputting log information of the attitude and orbit control model in a simulation running process. The model event interface is used for outputting business event information of the attitude and orbit control model. The running log interface comprises running log data; and the running log data comprises attitude and orbit control subsystem basic information, a current simulation time, a log number, a log level, a function name, a return value, a return value description, data length and a reserved word.

7. The digital simulation interface system for the MEO satellite attitude and orbit control subsystem according to claim 6, characterized in that, ​ The model event interface comprises: basic information of an attitude orbit control subsystem, a current simulation time, an event number, an event category, an event description, a data length, and a reserved word.

8. The digital simulation interface system for the MEO satellite attitude and orbit control subsystem according to claim 1, characterized in that, The service class interface comprises: a service class data stream consistent with the implementation, and a process of simulating transmission of on-orbit information from a generation end to a processing end; inside the satellite simulation model, a model of each type of virtual bus is provided to realize scheduling transmission and distribution of data streams between subsystems, and to complete interaction of each type of simulation data and service data.

9. The digital simulation interface system for the MEO satellite attitude and orbit control subsystem according to claim 1, wherein, The service class interface comprises: an event trigger class interface and a time trigger class interface. The event trigger class interface comprises: a data reading-in interface from a bus, a data writing-in interface to a bus, a data reading-in interface from a serial port, a data output interface to a serial port, an analog output interface, an analog input interface, an OC instruction input interface, and an OC instruction output interface. The time trigger class interface comprises: a bus request interface.

10. The digital simulation interface system for the MEO satellite attitude and orbit control subsystem according to claim 9, wherein, The data reading-in interface from a bus, the data writing-in interface to a bus, the data reading-in interface from a serial port, the data output interface to a serial port, the analog output interface, the analog input interface, the OC instruction input interface, the OC instruction output interface, and the bus request interface all adopt a fixed address memory interaction mode to transmit data, which is consistent with the implementation information flow on one hand, and realizes decoupling of receiving and transmitting on the other hand, so as to achieve the purpose of loose coupling of each subsystem.

Images