Spacecraft component equipment description method oriented to intelligent synthesis

Abstract

The invention relates to an intelligent synthesis-oriented spacecraft component equipment description method, and belongs to the technical field of architecture design. Abstract modeling and unified description are carried out on management operation of common component equipment in a spacecraft control subsystem, an application example is given, and the development efficiency and quality of spaceflight embedded software intelligent composite codes can be improved. According to the method, firstly, component equipment composition of an existing spacecraft control subsystem is combed, then general and difference demand analysis is carried out on component equipment management functions of the spacecraft control subsystem, then a software unified equipment model oriented to control system components is established, and finally a specific example is given. The method can quickly adapt to software codes formed by different parts of the control system, the reuse capability of the control software is improved, and then intelligent synthesis of the software is supported.

Description

Technical Field

[0001] This invention belongs to the field of architecture design technology and relates to a method for describing spacecraft components and equipment for intelligent synthesis. Background Technology

[0002] The operation of spacecraft control software on components and equipment mainly includes: powering on / off components, communicating with components according to communication protocols, and judging the validity of communication data and processing it accordingly. Traditional software design methods generally involve customized development based on specific hardware interfaces, which presents the following problems: 1. Strong coupling exists between component management operations and hardware communication interfaces and timing implementations, making code reuse difficult after hardware replacement; 2. Code cannot be reused when protocols for the same type of component change; 3. Differences exist in component operations such as validity, fault diagnosis, and handling, making code reuse impossible. These problems prevent the intelligent synthesis of spacecraft control software. Therefore, it is necessary to establish a spacecraft component and equipment description method oriented towards intelligent synthesis to adapt to different component and equipment compositions, improve the reusability of control software, and thus support intelligent software synthesis. Summary of the Invention

[0003] The technical problem solved by this invention is to overcome the shortcomings of the prior art and propose a spacecraft component equipment description method for intelligent synthesis, which can quickly adapt to the software code implementation of different components of the control system, improve the reusability of control software, and thus support intelligent software synthesis.

[0004] The solution of the present invention is:

[0005] A method for describing spacecraft component equipment for intelligent synthesis, comprising:

[0006] Step 1: Review the components and equipment of the existing spacecraft control subsystem;

[0007] Step 2: Analyze the common requirements of the components, equipment, and their management operation source code identified in Step 1 to obtain the common requirements of the components and equipment. The common requirements of the components and equipment include 5 categories: component power-on and initialization, sending component control commands, receiving component data, judging the validity of component data, and diagnosing and handling communication faults.

[0008] Step 3: Establish a unified component data structure based on the common requirements of the components and equipment in Step 2;

[0009] Step 4: Design a unified component operation interface based on the common requirements of the components and equipment in Step 2;

[0010] Step 5: Complete the construction of a unified description model for spacecraft components and equipment.

[0011] In the above-mentioned method for describing spacecraft components and equipment for intelligent synthesis, in step one, the components and equipment are divided into two categories: attitude sensors and actuators.

[0012] Attitude sensors are components that measure satellite attitude through data acquisition and processing, and output real-time attitude information of the satellite. They include gyroscopes, accelerometers, earth sensors, sun sensors, star sensors, and triaxial magnetometers.

[0013] The actuator is a component or device that performs attitude control functions based on the satellite's attitude information and the target's attitude, including chemical fuel thrusters, electric thrusters, cold gas thrusters, momentum wheels, control torque gyroscopes, and magnetic torque generators.

[0014] In the above-mentioned method for describing spacecraft components and equipment for intelligent synthesis, in step three, the structure for powering on and initializing the component is defined as a data structure PWR_CMD_MAP_T, including the power-on sequence number inno, code 1wd1, code 2wd2, the wait cycle of the instruction waitcycle, the execution cycle of the instruction execycle, the subsequent instruction number nextno, the component sequence number pid of the shift flag, the shift flag bit number pbit, the shift flag value pval, the number of other shifts set cntsimu, the wait cycle of the shift waittonL, and the shift wait cycle set value waitSet.

[0015] In the above-mentioned method for describing spacecraft components and equipment for intelligent synthesis, in step three, the structure for sending component control commands is defined as a data structure BUS_MSGDATASEND_T, which includes an index number index, a message sending function pfunSend, a frame count frameCnt, and raw data sendBuf.

[0016] In the above-mentioned method for describing spacecraft components and equipment for intelligent synthesis, in step three, the structure of the data collected by the receiving component is defined as a data structure BUS_MSGDATARECV_T, which includes an index number index, a message receiving function pfunRecv, a receiving frame count frameCnt, and receiving raw data recvBuf.

[0017] In the above-mentioned method for describing spacecraft components and equipment for intelligent synthesis, in step three, the structure for determining the validity of component data is defined as the data structure PART_DATAVALID_T, which includes message validity msgvalid, component data source code communication status comstatus, the number of messages for which validity checks are performed comCnt, and the consecutive error count CntComErr.

[0018] In the above-mentioned method for describing spacecraft components and equipment for intelligent synthesis, in step three, the structure for communication fault diagnosis and processing is defined as a data structure IO_COMDIAG_T, which includes a threshold of consecutive communication error count Cnt1, a threshold of consecutive communication error count after restart Cnt2, a communication cycle interval Cnt3 between sending a power-off command and resending a power-on command, the number of allowed power-on retries CntLoopPwr, the number of allowed backup switching CntLoopSwitch, the component's last power-on / off status endPwrStatus, the power-off sequence number pwrOff, the power-on sequence number pwrOn, and the backup power-on sequence number SlaveOn.

[0019] In the above-mentioned method for describing spacecraft components and equipment for intelligent synthesis, in step four, the operation of powering on and initializing the component is abstracted as an interface function void CS_SetPwrCmd, where the physical meaning of each parameter is the instruction number bInno, the number of times the instruction is executed cexecycle, the waiting period for the next instruction cwaitcycle, and the number of the next instruction bnextno.

[0020] In the above-mentioned method for describing spacecraft components and equipment for intelligent synthesis, in step four, the operation of sending component control commands is abstracted as the interface function void CS_SendCtrl, which has no constraints on the formal parameters and calls the data structure defined by the structure for sending component control commands.

[0021] The operation of the receiving component to collect data is abstracted into the interface function void CS_AcqData, which has no constraints on the formal parameters and calls the data structure defined by the receiving component to collect data.

[0022] In the above-mentioned method for describing spacecraft components and equipment for intelligent synthesis, in step four, the operations of component data validity judgment and communication fault diagnosis and processing are uniformly abstracted into the interface function void CS_ComDiagMain, where the physical meaning of each parameter is message validity msgvalid, communication fault diagnosis and processing structure *ioComDiag, component data source code communication status comstatus, and the number of messages for validity checking comCnt.

[0023] The advantages of this invention compared to the prior art are:

[0024] (1) The present invention proposes a spacecraft component and equipment description method for intelligent synthesis. It establishes a component and equipment abstraction layer for spacecraft control software architecture design. The component layer provides access interface to the control software application layer above and accesses the component and equipment driver library below, playing a connecting role in the software architecture.

[0025] (2) This invention analyzes the common and different requirements of the equipment management function of the spacecraft control subsystem components, establishes a unified software equipment model for control system components, and adapts to the different components of the control software.

[0026] (3) The present invention can quickly adapt to the software code implementation of different components of the control system, improve the reusability of control software, and thus support intelligent software synthesis, meeting the requirements of rapid intelligent synthesis of control software. Attached Figure Description

[0027] Figure 1 This is a flowchart describing the spacecraft component equipment for intelligent synthesis according to the present invention. Detailed Implementation

[0028] The present invention will be further described below with reference to the embodiments.

[0029] This invention provides a method for describing spacecraft components and equipment for intelligent synthesis, which solves the problems of high software maintenance costs, low reusability, and difficulty in rapid portability in existing design methods.

[0030] Methods for describing spacecraft components and equipment for intelligent synthesis, such as Figure 1 As shown, the specific steps include the following:

[0031] Step 1: Review the components and equipment of the existing spacecraft control subsystem.

[0032] The components are divided into two categories: attitude sensors and actuators; respectively:

[0033] Attitude sensors are components that measure satellite attitude through data acquisition and processing, and output real-time attitude information of the satellite. They include gyroscopes, accelerometers, earth sensors, sun sensors, star sensors, and triaxial magnetometers.

[0034] The actuator is a component or device that performs attitude control functions based on the satellite's attitude information and the target's attitude, including chemical fuel thrusters, electric thrusters, cold gas thrusters, momentum wheels, control torque gyroscopes, and magnetic torque generators.

[0035] Step 2: Analyze the common requirements of the components, equipment, and their management operation source code identified in Step 1 to obtain the common requirements of the components and equipment. The common requirements of the components and equipment include 5 categories: component power-on and initialization, sending component control commands, receiving component data, judging the validity of component data, and diagnosing and handling communication faults.

[0036] Step 3: Establish a unified component data structure based on the common requirements of the components and equipment in Step 2.

[0037] The structure for setting the power-on and initialization of components is defined as the data structure PWR_CMD_MAP_T, including the power-on sequence number inno, code 1wd1, code 2wd2, the wait cycle of this instruction waitcycle, the execution cycle of this instruction execycle, the subsequent instruction number nextno, the component sequence number pid of the shift flag, the shift flag bit number pbit, the shift flag value pval, the number of other shifts set simultaneously cntsimu, the wait cycle of the shift waittonL, and the load value of the shift wait cycle waitSet. The structure definition is as follows:

[0038]

[0039] Taking a satellite with three star sensors as an example, the configuration code is as follows:

[0040]

[0041]

[0042] The structure for setting the control commands for the sending component is defined as the data structure BUS_MSGDATASEND_T, which includes the index number index, the message sending function pfunSend, the frame count frameCnt, and the raw data sendBuf. The structure definition is as follows:

[0043]

[0044] Taking a satellite with three star sensors as an example, each star sensor has two control commands, configured as follows:

[0045]

[0046] The data structure for the receiving component is defined as BUS_MSGDATARECV_T, which includes the index number (index), the message receiving function (pfunRecv), the received frame count (frameCnt), and the received raw data (recvBuf). The structure definition is as follows:

[0047]

[0048] Taking a satellite with three star sensors as an example, each star sensor receives three messages, and the configuration code is as follows:

[0049]

[0050]

[0051] The structure for determining the validity of component data is defined as the data structure PART_DATAVALID_T, which includes message validity msgvalid, component data source code communication status comstatus, the number of messages for which validity checks are performed comCnt, and the consecutive error count CntComErr.

[0052] The structure for communication fault diagnosis and handling is defined as the data structure IO_COMDIAG_T, which includes the following: threshold number of consecutive communication errors (Cnt1), threshold number of consecutive communication errors after restart (Cnt2), communication cycle interval (Cnt3) between sending a power-off command and resending a power-on command, allowed number of power-on retries (CntLoopPwr), allowed number of backup switching attempts (CntLoopSwitch), the last power-on / off status of the component (endPwrStatus), power-off sequence number (pwrOff), power-on sequence number (pwrOn), and backup power-on sequence number (SlaveOn). The structure definition is as follows:

[0053]

[0054]

[0055] Taking a satellite with three star sensors as an example, the configuration code is as follows:

[0056]

[0057] Step 4: Design a unified component operation interface based on the common requirements of the components and equipment in Step 2.

[0058] The operation of setting the component's power-on and initialization is abstracted into the interface function `void CS_SetPwrCmd`, where the physical meaning of each parameter is: instruction number `bInno`, the number of times the instruction has been executed `cexecycle`, the wait cycle for the next instruction `cwaitcycle`, and the instruction number `bnextno`. Taking a star sensor as an example:

[0059]

[0060] The operation of sending component control commands is abstracted into the interface function void CS_SendCtrl, which has no constraints on the formal parameters and calls the data structure defined in the structure for sending component control commands.

[0061] The operation of the receiving component to collect data is abstracted into the interface function void CS_AcqData, which has no constraints on the formal parameters and calls the data structure defined by the receiving component to collect data.

[0062] The operations for component data validity judgment and communication fault diagnosis and handling are uniformly abstracted into the interface function `void CS_ComDiagMain`, where the physical meanings of each parameter are: message validity `msgvalid`, communication fault diagnosis and handling structure `*ioComDiag`, component data source code communication status `comstatus`, and the number of messages for validity checking `comCnt`. Taking Xingmin as an example, the code for component data validity judgment and communication fault diagnosis and handling is as follows:

[0063]

[0064] Step 5: Complete the construction of a unified description model for spacecraft components and equipment.

[0065] This invention proposes a method for describing spacecraft components and equipment for intelligent synthesis. It establishes a component and equipment abstraction layer for the spacecraft control software architecture. The component layer provides access interfaces to the control software application layer above and accesses the component and equipment driver library below, playing a bridging role in the software architecture.

[0066] This invention analyzes the common and different requirements of the equipment management functions of spacecraft control subsystem components, establishes a unified software equipment model for control system components, and adapts to different component compositions of control software.

[0067] This invention can quickly adapt to the software code implementation of different components of the control system, improve the reusability of control software, and thus support intelligent software synthesis, meeting the requirements of rapid intelligent synthesis of control software.

[0068] Although the present invention has been disclosed above with reference to preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art can make possible changes and modifications to the technical solutions of the present invention by utilizing the methods and techniques disclosed above without departing from the spirit and scope of the present invention. Therefore, any simple modifications, equivalent changes and alterations made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solutions of the present invention shall fall within the protection scope of the technical solutions of the present invention.

Claims

1. A method for describing spacecraft component equipment for intelligent synthesis, characterized in that: include: Step 1: Review the components and equipment of the existing spacecraft control subsystem; Step 2: Analyze the common requirements of the components, equipment, and their management operation source code identified in Step 1 to obtain the common requirements of the components and equipment. The common requirements of the components and equipment include 5 categories: component power-on and initialization, sending component control commands, receiving component data, judging the validity of component data, and diagnosing and handling communication faults. Step 3: Establish a unified component data structure based on the common requirements of the components and equipment in Step 2; Step 4: Design a unified component operation interface based on the common requirements of the components and equipment in Step 2; Step 5: Complete the construction of a unified description model for spacecraft components and equipment.

2. The method for describing spacecraft components and equipment for intelligent synthesis according to claim 1, characterized in that: In step one, the component equipment is divided into two categories: attitude sensor and actuator. Attitude sensors are components that measure satellite attitude through data acquisition and processing, and output real-time attitude information of the satellite. They include gyroscopes, accelerometers, earth sensors, sun sensors, star sensors, and triaxial magnetometers. The actuator is a component or device that performs attitude control functions based on the satellite's attitude information and the target's attitude, including chemical fuel thrusters, electric thrusters, cold gas thrusters, momentum wheels, control torque gyroscopes, and magnetic torque generators.

3. The method for describing spacecraft components and equipment for intelligent synthesis according to claim 1, characterized in that: In step three, the structure for powering on and initializing the component is defined as a data structure PWR_CMD_MAP_T, including the power-on sequence number inno, code 1wd1, code 2wd2, the wait cycle of the instruction waitcycle, the execution cycle of the instruction execycle, the subsequent instruction number nextno, the component sequence number pid of the shift flag, the shift flag bit number pbit, the shift flag value pval, the number of other shifts set cntsimu, the wait cycle of the shift waittonL, and the shift wait cycle set value waitSet.

4. The method for describing spacecraft components and equipment for intelligent synthesis according to claim 3, characterized in that: In step three, the structure of the control command for the sending component is defined as a data structure BUS_MSGDATASEND_T, which includes an index number, a message sending function pfunSend, a frame count frameCnt, and raw data sendBuf.

5. The method for describing spacecraft components and equipment for intelligent synthesis according to claim 4, characterized in that: In step three, the structure of the data collected by the receiving component is defined as the data structure BUS_MSGDATARECV_T, which includes the index number index, the message receiving function pfunRecv, the receiving frame count frameCnt, and the received raw data recvBuf.

6. The method for describing spacecraft components and equipment for intelligent synthesis according to claim 5, characterized in that: In step three, the structure for determining the validity of component data is defined as the data structure PART_DATAVALID_T, which includes message validity msgvalid, component data source code communication status comstatus, the number of messages for which validity checks are performed comCnt, and the consecutive error count CntComErr.

7. The method for describing spacecraft components and equipment for intelligent synthesis according to claim 6, characterized in that: In step three, the structure for communication fault diagnosis and handling is defined as the data structure IO_COMDIAG_T, which includes the following: continuous communication error threshold Cnt1, continuous communication error threshold Cnt2 after restart, communication cycle interval Cnt3 after sending a power-off command and then sending a power-on command, the number of allowed power-on retries CntLoopPwr, the number of allowed backup switching CntLoopSwitch, the last power-on / off status of the component endPwrStatus, power-off sequence number pwrOff, power-on sequence number pwrOn, and backup power-on sequence number SlaveOn.

8. The method for describing spacecraft components and equipment for intelligent synthesis according to claim 1, characterized in that: In step four, the operation of setting the component power-on and initialization is abstracted as the interface function void CS_SetPwrCmd, where the physical meaning of each formal parameter is the instruction number bInno, the number of times the instruction is executed cexecycle, the waiting period for the next instruction cwaitcycle, and the number of the next instruction bnextno.

9. A method for describing spacecraft components and equipment for intelligent synthesis according to claim 5, characterized in that: In step four, the operation of sending component control commands is abstracted into the interface function void CS_SendCtrl, which has no constraints on the formal parameters and calls the data structure defined by the structure for sending component control commands. The operation of the receiving component to collect data is abstracted into the interface function void CS_AcqData, which has no constraints on the formal parameters and calls the data structure defined by the receiving component to collect data.

10. A method for describing spacecraft components and equipment for intelligent synthesis according to claim 1, characterized in that: In step four, the operations of component data validity judgment and communication fault diagnosis and handling are uniformly abstracted into the interface function void CS_ComDiagMain, where the physical meaning of each parameter is message validity msgvalid, communication fault diagnosis and handling structure *ioComDiag, component data source code communication status comstatus, and the number of messages for validity checking comCnt.

Images