CN113268367B - On-orbit monitoring and maintaining method for 1553B bus RT terminal address lookup table - Google Patents
On-orbit monitoring and maintaining method for 1553B bus RT terminal address lookup table Download PDFInfo
- Publication number
- CN113268367B CN113268367B CN202110453602.2A CN202110453602A CN113268367B CN 113268367 B CN113268367 B CN 113268367B CN 202110453602 A CN202110453602 A CN 202110453602A CN 113268367 B CN113268367 B CN 113268367B
- Authority
- CN
- China
- Prior art keywords
- lookup table
- address lookup
- bus
- sub
- orbit
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0751—Error or fault detection not based on redundancy
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
- G06F12/0238—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory
- G06F12/0246—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory in block erasable memory, e.g. flash memory
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention relates to an on-orbit monitoring and maintaining method for a 1553B bus RT terminal address lookup table, provides an on-orbit monitoring and maintaining mechanism for the RT terminal address lookup table, improves the operation reliability of the 1553B bus, can be used for system reliability design in the aviation and aerospace fields, and belongs to the field of system reliability. The invention realizes the autonomous monitoring of the running state of the subaddress lookup table by the on-orbit spacecraft, if the monitoring is abnormal, the on-orbit autonomous processing is executed first, if the autonomous processing is invalid for a plurality of times, the monitoring abnormal result is downloaded to the ground for rechecking, and after the ground rechecking lookup table or the data block is abnormal, a one-key reset function is provided for ground intervention. The method can effectively improve the on-orbit monitoring and quick repairing capability of 1553B bus faults in the spacecraft system and improve the reliability of long-term on-orbit operation of the spacecraft system.
Description
Technical Field
The invention relates to an on-orbit monitoring and maintaining method for a 1553B bus RT terminal address lookup table, provides an on-orbit monitoring and maintaining mechanism for the RT terminal address lookup table, improves the operation reliability of the 1553B bus, can be used for system reliability design in the aviation and aerospace fields, and belongs to the field of system reliability.
Background
Currently, spacecraft systems such as manned, deep space exploration, high orbit, remote sensing and the like widely adopt 1553B buses to build a system data network. In a spacecraft system based on a 1553B bus, the RT terminal address lookup table plays a decisive role in the correctness of spacecraft data communication. Due to the severe space radiation environment, the spacecraft happens when encountering a single event on orbit, so that the sub-address lookup table or the data block area is overturned or permanently damaged, thereby causing continuous errors of data communication in the spacecraft system, further causing system faults and affecting the task of the whole spacecraft and even safety. How to cope with the abnormal situation of the sub-address lookup table caused by the single event effectively solves the problem that the reliability of the 1553B bus running on track becomes a difficult problem for system design.
Disclosure of Invention
The invention solves the technical problems that: the on-orbit monitoring and maintaining method for the 1553B bus RT terminal address lookup table is provided, the on-orbit fault of the 1553B bus caused by space radiation single particles is effectively monitored and repaired, the running state of the sub-address lookup table is autonomously monitored by the on-orbit spacecraft, if the monitoring is abnormal, on-orbit autonomous processing is firstly executed, if the autonomous processing is invalid for many times, the monitoring abnormal result is downloaded to ground for rechecking, and after the ground rechecking lookup table or a data block is abnormal, a one-key reset function is provided for ground intervention.
The technical scheme of the invention is as follows: an on-orbit monitoring and maintaining method for a 1553B bus RT terminal address lookup table comprises the following steps:
step (1), determining a maintenance mode of the running state of the shared memory, defining a maintenance state word MemStatus of the shared memory, using all bit states of integer quantity to represent allocation and use states of the shared memory space, defaulting all initial running states of the shared memory space to be idle, and entering the step (2);
step (2), defining an RT end message initialization configuration data structure S1553RTMsgConf, wherein the data structure comprises a sub-address, a receiving/transmitting/broadcasting mark, a message length and a message ending interrupt mark, and entering step (3);
step (3), determining a message initialization configuration binding table MsgConfTable according to a 1553B bus communication protocol of the RT end, and entering step (4);
step (4), determining a 1553B chip initialization function RtInit of an RT working mode, initializing the 1553B chip RT mode based on MemStatus determined in the step (1) and MsgConfTable determined in the step (3), setting the working state of the chip and distributing a sub-address lookup table, and entering the step (5);
step (5), determining an RT terminal address lookup table validity detection function ChkLookup, traversing all the sub-addresses of the MsgConfTable determined in the step (3), performing validity detection operation of a receiving/transmitting/broadcasting sub-address lookup table and a sub-address control word, and entering the step (6);
step (6), at the starting time, executing the initialization operation of the software variable and the hardware interface, and entering step (7);
step (7), resetting the invalid accumulated count variable cntchkivolid detected by the subaddress lookup table, and entering step (8);
step (8), calling a 1553B chip initialization function RtInit to finish the initialization of the bus chip, and entering the RT working state by the bus chip to enter the step (9);
step (9), periodically calling an RT terminal address lookup table validity detection function ChkLookup, wherein all sub-address lookup tables and sub-address control words are expected values, and the detection result is valid, otherwise, the detection result is invalid; if the detection result is valid, resetting the variable cntchkivolid, and repeating the step (9); if the detection result is invalid, accumulating the variable cntchkivolid, and entering a step (10);
step (10), if the variable cntchkivolid is less than 3, returning to the step (8); otherwise, downloading the invalid result detected by the subaddress lookup table in the step (9) to the ground through a telemetry channel, and entering the step (11);
step (11), ground analysis causes the sub address lookup table to detect invalid fault reasons, and the step (12) is carried out by setting bad block setting of the data block or switching of the shared memory A/B area or other treatment measures according to the fault reasons;
step (12), the ground implements the treatment measure formulated in the step (11) by a remote control injection mode, and the step (13) is entered;
and (13) performing 1553B chip reset operation on the ground by remote control, and returning to the step (7).
Further, in the step (1), the shared memory maintenance status word MemStatus is an integer variable or an integer array.
Further, in the step (3), the message initialization configuration binding table MsgConfTable type belongs to the data structure S1553RTMsgConf.
Further, in the step (4), a 1553B chip initialization function RtInit is implemented based on the configuration information.
Further, in the step (5), the detection function ChkLookup is used to complete the detection of the valid state of the memory value in the fixed address lookup table region of the shared memory.
Further, in the step (7), the accumulated count variable cntchkivolid is used to record the number of times that the subaddress lookup table is invalid in detection, and is cleared only when the start time is initialized or when the ground remote control is received to execute the 1553B chip reset operation.
Further, in the step (10), the variable cntchkivolid < 3 indicates that the number of times of invalidation detection of the sub-address lookup table is within 3, and the 1553B chip reset operation is independently completed on orbit; the times reach 3 times, alarm information is generated, and the alarm information is sent to the ground for disposal.
Further, in the step (11), the fault cause includes single event upset or locking of the shared memory area caused by space radiation, rewriting of the sub address lookup table area by processor exception, and memory access exception caused by chip select signal exception.
Further, in the step (11), the bad data block is set to set the designated bit of the shared memory maintenance status word MemStatus to 1 by remote control injection, which indicates that the ground has determined that the corresponding shared memory data block is unavailable.
Further, in the step (11), the a/B area of the shared memory is switched to a B/a area that is used currently and is switched to a backup B/a area by a remote control injection mode, so as to cope with the situation that a fixed area is unavailable due to single event locking.
Compared with the prior art, the invention has the advantages that:
(1) According to the on-orbit monitoring and maintaining method for the 1553B bus RT terminal address lookup table, validity detection is carried out on the RT terminal address lookup table during system operation, abnormal conditions of the sub-address lookup table can be timely identified, on-orbit autonomous handling capability is achieved, and on-orbit reliability of a 1553B bus fault of a spacecraft is improved;
(2) According to the on-orbit monitoring and maintaining method for the 1553B bus RT terminal address lookup table, unified management of a shared memory and automatic allocation of a sub address lookup table are achieved, a one-key reset function is provided for ground intervention, and the capacity of quickly repairing faults of the 1553B bus of a spacecraft is improved.
Drawings
FIG. 1 is a flow chart of the present invention;
fig. 2 is a schematic diagram of the project implementation principle.
Detailed Description
In order to better understand the technical solutions described above, the following detailed description of the technical solutions of the present application is provided through the accompanying drawings and specific embodiments, and it should be understood that the specific features of the embodiments and embodiments of the present application are detailed descriptions of the technical solutions of the present application, and not limit the technical solutions of the present application, and the technical features of the embodiments and embodiments of the present application may be combined with each other without conflict.
The following is a description of an in-orbit monitoring and maintenance method for a 1553B bus RT terminal address lookup table provided in the embodiments of the present application with reference to the accompanying drawings, and a specific implementation manner may include (as shown in fig. 1-2):
in the scheme provided by the embodiment of the application, as shown in fig. 1, an on-track monitoring and maintaining method for a 1553B bus RT terminal address lookup table is implemented by the following steps:
(1) Determining a maintenance mode of the running state of the shared memory, defining a maintenance state word MemStatus of the shared memory, using all bit states of the integer quantity to represent the allocation and use states of the shared memory space, defaulting all initial running states of the shared memory space to be idle, and entering the step (2). The running state of the shared memory is uniformly maintained by taking data blocks (32 16-bit words) as a unit, the running state of each data block is represented by 1 bit (the bit is 0 to represent idle, and the bit is 1 to represent occupied or fault), and the 4K word shared memory can be represented by 16 bytes; the shared memory maintenance status word MemStatus is defined as follows:
TABLE 1 shared memory maintenance status word MemStatus definition
(2) Defining an RT end message initialization configuration data structure S1553RTMsgConf, wherein the data structure comprises a sub-address, a receiving/transmitting/broadcasting mark, a message length and a message ending interrupt mark, and entering step (3). The data structure S1553RTMsgConf is defined as follows:
table 2 data structure S1553RTMsgConf definition
(3) And (4) determining a message initialization configuration binding table MsgConfTable according to a 1553B bus communication protocol of the RT end, and entering the step (4). The binding table MsgConfTable is exemplified as follows:
table 3 binding table MsgConfTable example
(4) Determining a 1553B chip initialization function RtInit of an RT working mode, initializing the 1553B chip RT mode based on MemStatus determined in the step (1) and MsgConfTable determined in the step (3), setting the working state of the chip and distributing a sub-address lookup table, and entering the step (5). The initialization function performs stack allocation and sub-address lookup table allocation according to the MemStatus state.
(5) Determining an RT terminal address lookup table validity detection function ChkLookup, traversing all the sub-addresses of the MsgConfTable determined in the step (3), performing validity detection operation of a receiving/transmitting/broadcasting sub-address lookup table and a sub-address control word, and entering the step (6). Wherein, the contents of the sub-address lookup table should always be the value allocated for initialization for single message; for the circulation cache information, the contents of the sub-address lookup table are regularly changed, the content value range is positioned between the starting address and the ending address of the circulation cache, and the circulation cache information is increased to the ending address and then automatically rewound to the starting address; the contents of the sub-address control words should not change since initialization, always being the value assigned for initialization.
(6) At the starting time, the initialization operation of the software variable and the hardware interface is executed, and the step (7) is entered. The steps (1-5) are method design stages, and the steps (6-13) are method implementation stages.
(7) And (4) clearing the subaddress lookup table detection invalid accumulated count variable cntchkivolid, and entering the step (8). There are two occasions for cntchkivolid to clear: and the system starting time and the ground reset operation time of the 1553B chip are executed by remote control.
(8) And (3) calling a 1553B chip initialization function RtInit to finish the initialization of the bus chip, and entering the RT working state by the bus chip to enter the step (9).
(9) Periodically calling an RT terminal address lookup table validity detection function ChkLookup, wherein all sub-address lookup tables and sub-address control words are expected values, and if the sub-address lookup tables and the sub-address control words are valid, the detection result is indicated to be valid, otherwise, the detection result is indicated to be invalid; if the detection result is valid, resetting the variable cntchkivolid, and repeating the step (9); if the detection result is invalid, the variable cntchkivolid is accumulated, and the step (10) is entered. Judging conditions: the sub-address lookup table content of the single message should be the value allocated for initialization; the sub-address lookup table content value range of the circular buffer memory message is positioned between the starting address and the ending address of the circular buffer memory; the sub-address control word content should be an initialized value.
(10) If the variable cntchkkylald is less than 3, returning to the step (8); otherwise, the invalid result detected by the subaddress lookup table in the step (9) is downloaded to the ground through a telemetry channel, and the step (11) is entered. 3 on-orbit autonomous treatment opportunities are reserved, and if the number of the on-orbit autonomous treatment opportunities exceeds 3, the on-orbit autonomous treatment is no longer carried out.
(11) And (3) the ground analysis causes the sub-address lookup table to detect invalid fault reasons, and the step (12) is performed by making data block bad block setting or shared memory A/B area switching or other treatment measures according to the fault reasons.
(12) And (3) carrying out treatment measures formulated in the step (11) on the ground through a remote control injection mode, and entering the step (13).
(13) And (3) performing 1553B chip reset operation on the ground through remote control, and returning to the step (7). A schematic diagram of the project implementation principle is shown in fig. 2.
It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.
What is not described in detail in the present specification is a well known technology to those skilled in the art.
Claims (10)
1. An on-orbit monitoring and maintaining method for a 1553B bus RT terminal address lookup table is characterized by comprising the following steps:
step (1), determining a maintenance mode of the running state of the shared memory, defining a maintenance state word MemStatus of the shared memory, using all bit states of integer quantity to represent allocation and use states of the shared memory space, defaulting all initial running states of the shared memory space to be idle, and entering the step (2);
step (2), defining an RT end message initialization configuration data structure S1553RTMsgConf, wherein the data structure comprises a sub-address, a receiving/transmitting/broadcasting mark, a message length and a message ending interrupt mark, and entering step (3);
step (3), determining a message initialization configuration binding table MsgConfTable according to a 1553B bus communication protocol of the RT end, and entering step (4);
step (4), determining a 1553B chip initialization function RtInit of an RT working mode, initializing the 1553B chip RT mode based on MemStatus determined in the step (1) and MsgConfTable determined in the step (3), setting the working state of the chip and distributing a sub-address lookup table, and entering the step (5);
step (5), determining an RT terminal address lookup table validity detection function ChkLookup, traversing all the sub-addresses of the MsgConfTable determined in the step (3), performing validity detection operation of a receiving/transmitting/broadcasting sub-address lookup table and a sub-address control word, and entering the step (6);
step (6), at the starting time, executing the initialization operation of the software variable and the hardware interface, and entering step (7);
step (7), resetting the invalid accumulated count variable cntchkivolid detected by the subaddress lookup table, and entering step (8);
step (8), calling a 1553B chip initialization function RtInit to finish the initialization of the bus chip, and entering the RT working state by the bus chip to enter the step (9);
step (9), periodically calling an RT terminal address lookup table validity detection function ChkLookup, wherein all sub-address lookup tables and sub-address control words are expected values, and the detection result is valid, otherwise, the detection result is invalid; if the detection result is valid, resetting the variable cntchkivolid, and repeating the step (9); if the detection result is invalid, accumulating the variable cntchkivolid, and entering a step (10);
step (10), if the variable cntchkivolid is less than 3, returning to the step (8); otherwise, downloading the invalid result detected by the subaddress lookup table in the step (9) to the ground through a telemetry channel, and entering the step (11);
step (11), ground analysis causes the sub address lookup table to detect invalid fault reasons, and the step (12) is carried out by setting bad block setting of the data block or switching of the shared memory A/B area or other treatment measures according to the fault reasons;
step (12), the ground implements the treatment measure formulated in the step (11) by a remote control injection mode, and the step (13) is entered;
and (13) performing 1553B chip reset operation on the ground by remote control, and returning to the step (7).
2. The on-orbit monitoring and maintenance method for a 1553B bus RT terminal address lookup table according to claim 1, wherein the method comprises the following steps: in the step (1), the shared memory maintenance status word MemStatus is an integer variable or an integer array.
3. The on-orbit monitoring and maintenance method for a 1553B bus RT terminal address lookup table according to claim 1, wherein the method comprises the following steps: in the step (3), the message initialization configuration binding table MsgConfTable type belongs to the data structure S1553RTMsgConf.
4. The on-orbit monitoring and maintenance method for a 1553B bus RT terminal address lookup table according to claim 1, wherein the method comprises the following steps: in the step (4), a 1553B chip initialization function RtInit is realized based on the configuration information.
5. The on-orbit monitoring and maintenance method for a 1553B bus RT terminal address lookup table according to claim 1, wherein the method comprises the following steps: in the step (5), the detection function ChkLookup is used to complete the detection of the valid state of the memory value in the fixed address lookup table region of the shared memory.
6. The on-orbit monitoring and maintenance method for a 1553B bus RT terminal address lookup table according to claim 1, wherein the method comprises the following steps: in the step (7), the accumulated count variable cntchkivolid is used for recording the number of times that the subaddress lookup table is invalid in detection, and is cleared only when the start time is initialized or when the ground remote control is received to execute 1553B chip reset operation.
7. The on-orbit monitoring and maintenance method for a 1553B bus RT terminal address lookup table according to claim 1, wherein the method comprises the following steps: in the step (10), a variable cntchkivolid < 3 indicates that the number of times of invalidation detection of the sub-address lookup table is within 3, and the 1553B chip reset operation is independently completed on orbit; the times reach 3 times, alarm information is generated, and the alarm information is sent to the ground for disposal.
8. The on-orbit monitoring and maintenance method for a 1553B bus RT terminal address lookup table according to claim 1, wherein the method comprises the following steps: in the step (11), the fault causes include single event upset or locking of the shared memory area caused by space radiation, rewriting of the sub address lookup table area by processor abnormality, and memory access abnormality caused by chip selection signal abnormality.
9. The on-orbit monitoring and maintenance method for a 1553B bus RT terminal address lookup table according to claim 1, wherein the method comprises the following steps: in the step (11), the bad block of the data block is set to set the designated bit of the shared memory maintenance status word MemStatus to 1 by remote control injection, which characterizes that the ground has determined that the corresponding shared memory data block is unavailable.
10. The on-orbit monitoring and maintenance method for a 1553B bus RT terminal address lookup table according to claim 1, wherein the method comprises the following steps: in the step (11), the a/B area of the shared memory is switched to a B/a area that is currently used and is switched to a backup B/a area by a remote control injection mode, so as to cope with the situation that a fixed area is unavailable due to single event locking.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110453602.2A CN113268367B (en) | 2021-04-26 | 2021-04-26 | On-orbit monitoring and maintaining method for 1553B bus RT terminal address lookup table |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110453602.2A CN113268367B (en) | 2021-04-26 | 2021-04-26 | On-orbit monitoring and maintaining method for 1553B bus RT terminal address lookup table |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113268367A CN113268367A (en) | 2021-08-17 |
| CN113268367B true CN113268367B (en) | 2023-07-14 |
Family
ID=77229414
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110453602.2A Active CN113268367B (en) | 2021-04-26 | 2021-04-26 | On-orbit monitoring and maintaining method for 1553B bus RT terminal address lookup table |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113268367B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113934650B (en) * | 2021-08-31 | 2023-07-18 | 北京控制工程研究所 | 1553B memory dynamic allocation method based on CCSDS |
| CN116886532B (en) * | 2023-09-07 | 2023-11-10 | 空间液态金属科技发展(江苏)有限公司 | Adaptive configuration method for network configuration information of aerospace Ethernet switch |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103226484A (en) * | 2013-04-15 | 2013-07-31 | 浙江大学 | On-orbit update method for satellite-borne integrated electronic system program |
| CN104717023A (en) * | 2015-04-03 | 2015-06-17 | 上海航天测控通信研究所 | Communication performance predictable 1553B bus engineering telemetric data acquiring method |
| CN106452843A (en) * | 2016-09-14 | 2017-02-22 | 北京控制工程研究所 | On-orbit fault monitoring and diagnosing method for 1553B bus network |
| CN106649173A (en) * | 2016-10-10 | 2017-05-10 | 上海航天控制技术研究所 | High-reliability in-orbit self-correction system and method for on-board computer on the basis of 1553B bus |
| CN106919463A (en) * | 2017-01-23 | 2017-07-04 | 北京空间飞行器总体设计部 | A kind of spacecraft BC ends 1553B bus chip RAM method for reconfiguration |
| CN108282550A (en) * | 2018-02-02 | 2018-07-13 | 北京控制工程研究所 | A kind of 1553B buses far set null terminator Null address search table auto-allocation method and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109491856B (en) * | 2017-09-12 | 2022-08-02 | 中兴通讯股份有限公司 | Bus monitoring system, method and device |
-
2021
- 2021-04-26 CN CN202110453602.2A patent/CN113268367B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103226484A (en) * | 2013-04-15 | 2013-07-31 | 浙江大学 | On-orbit update method for satellite-borne integrated electronic system program |
| CN104717023A (en) * | 2015-04-03 | 2015-06-17 | 上海航天测控通信研究所 | Communication performance predictable 1553B bus engineering telemetric data acquiring method |
| CN106452843A (en) * | 2016-09-14 | 2017-02-22 | 北京控制工程研究所 | On-orbit fault monitoring and diagnosing method for 1553B bus network |
| CN106649173A (en) * | 2016-10-10 | 2017-05-10 | 上海航天控制技术研究所 | High-reliability in-orbit self-correction system and method for on-board computer on the basis of 1553B bus |
| CN106919463A (en) * | 2017-01-23 | 2017-07-04 | 北京空间飞行器总体设计部 | A kind of spacecraft BC ends 1553B bus chip RAM method for reconfiguration |
| CN108282550A (en) * | 2018-02-02 | 2018-07-13 | 北京控制工程研究所 | A kind of 1553B buses far set null terminator Null address search table auto-allocation method and system |
Non-Patent Citations (1)
| Title |
|---|
| 航天器遥测数据异常检测综述;彭喜元 等;《仪器仪表学报》;第37卷(第09期);1929-1945 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113268367A (en) | 2021-08-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113268367B (en) | On-orbit monitoring and maintaining method for 1553B bus RT terminal address lookup table | |
| US7506314B2 (en) | Method for automatically collecting trace detail and history data | |
| US20060031487A1 (en) | Apparatuses for generation and collection of information, and computer-readable recording medium | |
| CN101504592B (en) | Storage subsystem and control method thereof | |
| US6697972B1 (en) | Method for monitoring fault of operating system and application program | |
| US6526447B1 (en) | Apparatus for restarting interrupted data transfer and method therefor | |
| US6985969B1 (en) | Receiving data on a networked computer in a reduced power state | |
| US11726946B2 (en) | I2C bus communication control method, device and system, and readable storage medium | |
| US20060212754A1 (en) | Multiprocessor system | |
| CN112583683B (en) | Master-slave CAN FD bus application layer communication method and system and electronic equipment | |
| US5293487A (en) | Network adapter with high throughput data transfer circuit to optimize network data transfers, with host receive ring resource monitoring and reporting | |
| US7864790B2 (en) | Method and apparatus for improving the management of data packets | |
| CN114328102A (en) | Equipment state monitoring method, device, equipment and computer readable storage medium | |
| CN104346264A (en) | System and method for processing system event logs | |
| CN100488109C (en) | Performance data additional collecting system and method in telecommunication network management | |
| US5935260A (en) | Method and apparatus for providing system level errors in a large disk array storage system | |
| CN104899157A (en) | Memory overflow detection method and system | |
| US20130339591A1 (en) | Relaying apparatus, relay history recording method, and data processing apparatus | |
| KR20170117326A (en) | Direct memory access control device for at least one processing unit having a random access memory | |
| CN110633161A (en) | Broadcast processing method and device | |
| CN111813734B (en) | 1553B bus communication method and system without message interval limitation | |
| US5524206A (en) | Sub-CPU monitoring system including dual port memory | |
| CN114741218A (en) | Method, device, equipment, system and medium for extracting abnormal index of operating system | |
| CN115495301A (en) | Fault processing method, device, equipment and system | |
| JPS5926158B2 (en) | Overload control method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |