CN109992554B - Method for realizing 1553B bus communication protocol based on general Schema structure description - Google Patents
Method for realizing 1553B bus communication protocol based on general Schema structure description Download PDFInfo
- Publication number
- CN109992554B CN109992554B CN201910183872.9A CN201910183872A CN109992554B CN 109992554 B CN109992554 B CN 109992554B CN 201910183872 A CN201910183872 A CN 201910183872A CN 109992554 B CN109992554 B CN 109992554B
- Authority
- CN
- China
- Prior art keywords
- message
- attribute
- data
- bus
- defining
- 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
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
- G06F13/4204—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus
- G06F13/4221—Bus transfer protocol, e.g. handshake; Synchronisation on a parallel bus being an input/output bus, e.g. ISA bus, EISA bus, PCI bus, SCSI bus
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/03—Protocol definition or specification
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/26—Special purpose or proprietary protocols or architectures
Abstract
The invention discloses a method for realizing a 1553B bus communication protocol based on general Schema structure description, which comprises the following steps: predefining various messages in a 1553B bus communication protocol by adopting a preset format to obtain message encapsulation; packaging various message communication modes by adopting a preset format to obtain interrupted packaging; respectively describing the communication time sequence relation, the bus system setting and the types of user messages of a 1553B bus communication protocol based on message encapsulation and interrupt encapsulation to generate description codes; in the communication entity, the description codes are directly compiled or interpreted to implement a 1553B bus communication protocol. The method of the invention analyzes the 1553B bus communication protocol aiming at the Schema structure, and can be directly applied to project engineering, thereby simplifying project implementation difficulty and solving the problem of protocol understanding ambiguity.
Description
Technical Field
The invention relates to the field of satellite simulation, in particular to a 1553B bus communication protocol implementation method based on general Schema structure description.
Background
The 1553B bus is a high-reliability bus technology and is widely applied to military projects and aerospace engineering projects. The bus communication protocol is an interface specification established in the project implementation process, so that each research unit can be developed according to unified constraint, rule and implementation method to ensure the project implementation progress requirement. However, the bus communication protocol is often submitted in the form of Word text, different understandings can be generated for content understanding by a reference unit, and protocol translation needs to be realized in project engineering subsequently.
Disclosure of Invention
The invention aims to overcome the ending defect and provides a general Schema structure for describing a 1553B bus communication protocol, and the bus communication protocol forms a specific item through the format of an XML text. Each development unit can be directly applied to project engineering after analyzing the Schema structure, thereby simplifying project implementation difficulty and solving the problem of protocol understanding ambiguity.
In order to achieve the above object, the present invention provides a method for implementing a 1553B bus communication protocol described based on a general Schema structure, where the method includes:
predefining various messages in a 1553B bus communication protocol by adopting a preset format to obtain message encapsulation;
packaging various message communication modes by adopting a preset format to obtain interrupted packaging;
respectively describing the communication time sequence relation, the bus system setting and the types of user messages of a 1553B bus communication protocol based on message encapsulation and interrupt encapsulation to generate description codes;
in the communication entity, the description codes are directly compiled or interpreted to implement a 1553B bus communication protocol.
As an improvement of the above method, the message encapsulation is used to predefine all types of messages existing on the bus, including message ID, BC control definition and message data, and specifically defined as follows:
element Message: is a collection of all messages, one message is an MSG element;
element MSG: the method is a definition of a message, wherein the definition comprises a message type Name, a message identifier MSGID, a message control block BC _ CB and message default cache data MSG _ Buffer;
the message type Name is used for explaining the message type in the bus communication protocol file;
message identification MSGID, which is an index to the message in bus communication;
a message control block BC _ CB comprising attributes: retry, DelayTime, FrameTime, and nextmsgnnum, BC control register content BC _ CB _ CSR, first command word CMD1, and second command word CMD 2;
attribute Retry: logic for retrying messages in BC control, the data type is hexadecimal number;
attribute DelayTime: the delay time is used for defining the delay time of the message, namely the current message is sent after the last message is sent for a long time; the data type is integer number;
attribute FrameTime: for defining a cycle time of the message; the data type is integer number;
the attribute NextMsgNum is used for defining the ID of the next message, namely the ID of the message which is sent immediately after the current message is sent; the data type is integer number;
BC control register content BC _ CB _ CSR: for defining BC control block register attributes, comprising:
the attribute IsDelayFrame is used for defining whether the frame is a delay frame or not, and the type is a Boolean type;
attribute Direction, which is used to define whether the message Direction is RT sending or RT receiving, and the type is character string;
the attribute IsStartFrame is used for defining whether the frame is the head frame of a continuous message frame, and the type is Boolean;
the attribute IsEndFrame is used for defining whether the frame is the tail frame of a continuous message frame or not, and the type is a Boolean type;
the attribute IsMCDATA is used for defining whether mode control is performed or not, and the type is Boolean type;
the attribute SelectBus is used for defining default sending on the A bus or the B bus, and the type is a character string;
first command word CMD 1: the method is used for defining the content of a command word 1 in the bus message, including the RT address, the SA sub-address, whether the TR sends or receives the message, and the WordCount message length;
second command word CMD 2: when the message is an RT-to-RT message, defining the content of a command word 2 in the bus message, including the RT address, the element SA _ MC, the element TR and the message length WordCount of the message;
the RT address is as follows: the method comprises the steps of defining the address, integer and 0-31 of a remote terminal to which a message belongs;
the element SA _ MC: the method is used for defining the subaddress to which the message belongs or controlling and shaping the subaddress in a mode of 0-31; if the current message is mode control, the current message is defined as 0 or 31;
the element TR: the message sending and receiving device is used for defining whether the message is sent or received by a remote terminal, and is shaped, wherein 0 is receiving and 1 is sending;
the message length WordCount: the method comprises the following steps of defining data length or mode control codes of a message, wherein the data length or mode control codes are integer 0-31, and the unit is 'word', and 0 represents 32 words;
and the message default cache data MSG _ Buffer is used for writing the default data into the MSG _ Buffer element when the data of the message is not changed or the default data exists.
As an improvement of the above method, the interrupt package is used to define a message response mode or processing logic, including periodically sending and querying vector words, and is specifically defined as follows:
element Interrupt: for defining two message corresponding modes: a periodic message queue MsgQueue and query vector word data MonitorData;
periodic message queue MsgQueue: is a set of periodic messages MQ _ MSG for enumerating all messages that need to be periodically sent or received;
the periodic message MQ _ MSG comprises a message Name, an attribute ischangeBus, an attribute BeginID, an attribute EndID, an attribute FrameTimeMultiple and an optional attribute FilePath;
the attribute isChangeBus is used for defining whether the redundant bus is replaced into a default bus of the message when the current bus is not accessible; the data type is a Boolean type;
attribute begini id: a start message ID number for defining the periodic message; the data type is integer;
attribute EndID: an end message ID number for defining the periodic message; the data type is integer;
attribute FrameTimeMultiple: the unit of the cycle is a bus cycle; the data type is integer;
property FilePath: the path used for simulating the data file defines the data content of the message sending as the data in the file defined by the FilePath; the attribute is an optional attribute, and the data type is a character string;
vector word data monitorerdata: for querying message response means elements; a set comprising an attribute, TargetMsgNum, and an element Operation;
attribute TargetMsgNum: a message ID number for indicating a vector word for fast locating vector word messages;
element Operation: a message which needs to respond to the vector word and indicates an element Name message type, an attribute Mask, an attribute Value, an attribute BeginID and an attribute EndID;
attribute Mask: the data type is hexadecimal, represents a mask used for calculating the vector word and is used for acquiring whether the corresponding position of the current vector word is set to be 1 or not;
attribute Value: the data type is hexadecimal, the Value obtained after vector word and mask calculation is compared with Value, if the Value is the same, the current Operation needs to respond, and if the Value is different, the Operation does not respond; and adding the attribute BeginID message into the periodic message queue in a response mode, and setting a queue tail message of the periodic message queue as EndID.
As an improvement of the above method, the communication timing relationship is a logical description of a data transmission flow initiated by BC and a RT request data transmission flow; the method comprises the following steps: BC sends vector word inquiry periodically, RT changes vector word data and sets service request after preparing response data; BC sends the response message according to the vector word content and the protocol definition; the message encapsulation comprises the following steps: vector word message definition, message ID, period and command word content; the interrupt package includes: and inquiring the content of the vector words, and defining and organizing the communication frames according to the content.
As an improvement of the above method, the bus system setting is a description of the selection of system mode control and the fault handling mode; the method comprises the following steps: the system selection mode controls the sending of the status word and the sending of the vector word; the failure processing mode is that the redundant bus is retried once, if the retry is successful, the redundant bus is switched to be the default bus; the message package comprises mode control definition and message retry logic; the interrupt package includes: it is defined whether to switch the default bus.
As an improvement of the above method, the message type of each user is the description of which users are in the system, the RT address of the user, and the SA subaddress function, period, and data length thereof; the method comprises the following steps: defining a management unit as BC, a load controller and a GNC unit as RT; the RT address of the load controller is 1, and the RT address of the GNC unit is 2; the load controller message has data injection, SA subaddress is 2, BC- > RT, length 32 word; 2s telemetering data, wherein the SA subaddress is 5, RT- > BC, the length is 128 words, the service request is carried out, and the vector word bit3 is set; track and status parameter message, BC- > RT, length 32 words, period 1 s; the message encapsulation comprises the following steps: defining a data injection message, a 2s telemetry message and a track status parameter message; the interrupt package includes: periodic message response logic and a vector word query message response mechanism are defined.
A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the above-mentioned method when executing the computer program.
A computer-readable storage medium, characterized in that it stores a computer program which, when executed by a processor, causes the processor to carry out the above-mentioned method.
The invention has the advantages that:
1. the Schame structure of the invention is clear, and the ambiguity of the text understanding of the bus communication protocol does not exist;
2. the Schame disclosed by the invention is rich in structure and good in universality, and can be applied to various 1553B bus communication items;
3. the description file of the 1553B bus communication protocol described by the Schame structure can be directly applied to project development;
4. through the verification in the ground comprehensive test system for Chang' e four-number autonomous Mars effective loads, the bus communication logic of satellite counting tube simulation can be quickly realized, and the desktop test of each stage is completed.
Drawings
Fig. 1 is a 1553B bus communication protocol description file Schema diagram of the invention;
FIG. 2 is a Schema diagram of the message encapsulation of the present invention;
fig. 3 is a Schema diagram of the interrupt package of the present invention.
Detailed Description
The present invention will be described in detail with reference to the accompanying drawings.
The invention analyzes a 1553B bus application layer, provides a general Schema structure, constructs a 1553B bus communication protocol description file of a project level as shown in figure 1, and defines an RT address, an SA subaddress, a bus period, mode control, a message type, a message response mode and the like according to GJB 289A-97. The problems that protocol description is inconsistent in different projects, file understanding is ambiguous and the like are solved. Meanwhile, the method is simple and easy to use, has good universality and is suitable for testing various aerospace vehicles. Through verification, the bus communication protocol of the ChangE fourth lander and the independent Mars mission two devices (the surround device and the landing patrol device) can be quickly and effectively described, and the bus communication protocol is conveniently and reliably embedded into the software design of a satellite counting tube simulation platform, so that the desktop joint test of each stage is completed.
Term(s) for
1553B bus: the bus conforms to the MIL-STD-1553B standard, is a digital time-division command/response type multiplex transmission data bus, and has the national standard of GJB 289A-97.
Word: a word is an information sequence that includes a sync header, a 16-bit information segment, and a parity bit. There are three types of words: an instruction word, a status word and a data word.
Message: a message refers to a transmission sequence comprising one instruction word, one status word (or two instruction words, two status words as they occur when transmitted from a remote terminal to a remote terminal), a number of data words (the number of words varies from 0 to 32) and a status response interval.
BC: a bus controller is a terminal that organizes the transmission of information in a bus system.
RT: remote terminals are all terminals in the bus system that are not bus controllers or bus guardians.
Communication protocol description file design
In engineering projects, the main functions of the 'bus communication protocol' file are to describe a communication time sequence relation, define the communication status and address of each user, and define the function message and message response mode in each user on a standard 1553B bus protocol, namely to define a 1553B bus application layer.
The "bus communication protocol" document defines 3 parts of communication timing relationship, bus system setting and each user message type respectively from the engineering point of view. The 1553B bus communication protocol description file divides the protocol into two layers of message encapsulation and interrupt encapsulation from the perspective of logic realization of a 1553B bus, and comprises contents of parts in a bus communication protocol.
Table 1: 1553B bus communication protocol description file Schema element table
Message encapsulation
"message encapsulation" is to predefine all message types existing on the bus, including message ID, BC control definition, and message data, as shown in fig. 2, specifically defined as follows:
element Message: is the set of all messages, one message is one MSG element.
Element MSG: is a definition of a message, which contains Name (message type), MSGID (message identification), BCCB (message control block), and MSG _ Buffer (message default Buffer data, optional).
The element Name: the name of the message is a description of the type of message in the bus communication protocol file.
Element MSGID: the identity of the message is the index to the message in the bus communication.
Element BC _ CB: the content of the message that needs to be defined in BC control includes attributes (Retry, DelayTime, FrameTime, nextmsgmnum), BC _ CB _ CSR (BC control register content), CMD1, and CMD2 (command word 1 and command word 2).
Element MSG _ Buffer: the message defaults to Buffer data, and when the data of the message is not changed or has the default data, the default data can be written into the MSG _ Buffer element.
Attribute Retry: is one of the attributes of the element BC CB and the data type is hexadecimal. The main function is a logical description of message retries in BC control.
Attribute DelayTime: is one of the attributes of the element BC CB and the data type is an integer number. The function is to define the deferral time of a message, i.e. how long after the last message has been sent the current message is sent.
Attribute FrameTime: is one of the attributes of the element BC CB and the data type is an integer number. The function is to define the cycle time of the message.
Attribute nextmsgnnum: is one of the attributes of the element BC CB and the data type is an integer number. The function is to define the next message ID, namely the message ID which is sent immediately after the current message is sent.
Element BC _ CB _ CSR: the BC control block register attribute is defined by attributes IsDelayFrame (boolean, which defines whether a frame is delayed or not), Direction (string, which defines whether a message Direction is RT transmission or RT reception), IsStartFrame (boolean, which defines whether a frame is the first frame of a consecutive message frame), IsEndFrame (boolean, which defines whether a frame is the last frame of a consecutive message frame), ismcdrame (boolean, which defines whether a mode control is performed or not), and SelectBus (string, which defines whether a default is transmission on the a bus or the B bus).
Element CMD 1: command word 1, which defines the content of command word 1 in the bus message, includes RT address, SA subaddress, TR send or receive, WordCount message length of the message.
Element CMD 2: command word 2, when the message is RT to RT, it is necessary to define the content of command word 2 in the bus message, including the RT address of the message, whether the element SA _ MC, TR is sent or received, and the WordCount message length.
Element RT: and defining the address of the remote terminal to which the message belongs, and shaping the address to 0-31.
And (3) element TR: and defining whether the message is sent or received by the remote terminal, and shaping the message by 0-1.
Element SA _ MC: this field may be the sub-address to which the message belongs or a mode control; if the mode control is performed, the mode code is represented, and the integer is 0 to 31. SA is SubAddress abbreviation, sub-address; MC is ModeControl shorthand, mode control.
Element WordCount: the data length of the message is defined, the integer is 0-31, the unit is 'word', and 0 represents 32 words.
Table 2 Schema elements table for message encapsulation
Interrupt packaging
"interrupt encapsulation" defines the message response mode or processing logic, such as periodically sending and querying vector words, as shown in fig. 3, and is specifically defined as follows:
element Interrupt: two message corresponding modes are defined, namely an MsgQueue periodic message queue and MonitorData query vector word data.
Element MsgQueue: the periodic message queue, which is a set of MQ _ MSG messages, lists all messages that need to be periodically sent or received.
Element MQ _ MSG: and the periodic message elements comprise a Name message type, an attribute isChangeBus, an attribute BeginID, an attribute EndID, an attribute FrameTimeMultiple and an optional attribute FilePath.
Attribute isChangeBus: the data type is a Boolean type, and whether the redundant bus is replaced into a default bus of the message when the current bus is not passed is defined.
Attribute begini id: the data type is integer, defining the start message ID number of this periodic message type.
Attribute EndID: the data type is integer, and the end message ID number of the cycle message type is defined.
Attribute FrameTimeMultiple: the data type is integer, defining the message type cycle in bus cycles (vector word cycles). For example, < FrameTimeMultiple >2</FrameTimeMultiple >, which means that the message period is 2 bus periods.
Property FilePath: this attribute is an optional attribute and the data type is a string. The path of the analog data file is represented, and the main function is to define the content of the message transmission data as the data in the file defined by the FilePath.
Element MonitorData: the vector word queries the message response mode element. Including the set of attributes TaretMsgNum and element Operation.
Attribute TargetMsgNum: a message ID number indicating the vector word is used to quickly locate the vector word message.
Element Operation: a message is required that responds to the vector word indicating the element Name message type, attribute Mask, attribute Value, attribute BeginID, attribute EndID.
Attribute Mask: the data type is hexadecimal and represents the mask used to compute the vector word. For obtaining whether the corresponding position of the current vector word is 1.
Attribute Value: the data type is hexadecimal, the Value obtained after vector word and mask calculation is compared with Value, if the Value is the same, the current Operation needs to respond, and if the Value is different, the Operation does not respond. And adding the attribute BeginID message into the periodic message queue in a response mode, and setting a queue tail message of the periodic message queue as EndID.
Table 3 interrupt packaged Schema elements table
Communication timing relationship
Is the logic description of the data transmission flow initiated by BC and the RT request data transmission flow
For example: the BC sends vector word inquiry periodically, and the RT changes vector word data and sets service request after preparing response data. The BC then sends the responsive message as defined by protocol based on the vector word content.
Message encapsulation
Vector word message definitions including message ID, period, command word content.
Interrupt packaging
The vector word content is queried and communication frames (message queues) are organized according to the content definition.
Bus system arrangement
Selection of system mode control and failure handling modes are described
For example: the system selection mode control includes transmitting a status word, transmitting a vector word, and the like. The failure handling mode is to retry on the redundant bus once, and if the retry is successful, the redundant bus is switched to be the default bus.
Message encapsulation
Vector word message definitions including message ID, period, command word content.
Interrupt packaging
The vector word content is queried and communication frames (message queues) are organized according to the content definition.
Message type of each user
It is described which users are in the system, the RT addresses of the users, and their SA sub-address functions, periods, data lengths, etc.
For example: the management unit is defined as BC, the load controller, and the GNC unit is defined as RT. The load controller RT address is 1 and the GNC unit RT address is 2. The load controller message has data injection, SA subaddress is 2, BC- > RT, length 32 word; 2s telemetering data, wherein the SA subaddress is 5, RT- > BC, the length is 128 words, the service request is carried out, and the vector word bit3 is set; track and status parameter message, BC- > RT, length 32 words, period 1 s.
Message encapsulation
Defining data injection messages, 2s telemetry messages, track status parameter messages
Interrupt packaging
Defining periodic message response logic and vector word query message response mechanism
Finally, it should be noted that the above embodiments are only used for illustrating the technical solutions of the present invention and are not limited. Although the present invention has been described in detail with reference to the embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (7)
1. A method for implementing 1553B bus communication protocol described based on general Schema structure includes:
predefining various messages in a 1553B bus communication protocol by adopting a preset format to obtain message encapsulation;
packaging various message communication modes by adopting a preset format to obtain interrupted packaging;
respectively describing the communication time sequence relation, the bus system setting and the types of user messages of a 1553B bus communication protocol based on message encapsulation and interrupt encapsulation to generate description codes;
in a communication entity, the description codes are directly compiled or interpreted to be executed, so that a 1553B bus communication protocol is realized;
the message encapsulation is used for predefining all types of messages existing on a bus, wherein the messages include message ID, BC control definition and message data, and the message encapsulation is specifically defined as follows:
element Message: is a collection of all messages, one message is an MSG element;
element MSG: the method is a definition of a message, wherein the definition comprises a message type Name, a message identifier MSGID, a message control block BC _ CB and message default cache data MSG _ Buffer;
the message type Name is used for explaining the message type in the bus communication protocol file;
message identification MSGID, which is an index to the message in bus communication;
a message control block BC _ CB comprising attributes: retry, DelayTime, FrameTime, and nextmsgnnum, BC control register content BC _ CB _ CSR, first command word CMD1, and second command word CMD 2;
attribute Retry: logic for retrying messages in BC control, the data type is hexadecimal number;
attribute DelayTime: the delay time is used for defining the delay time of the message, namely the current message is sent after the last message is sent for a long time; the data type is integer number;
attribute FrameTime: for defining a cycle time of the message; the data type is integer number;
the attribute NextMsgNum is used for defining the ID of the next message, namely the ID of the message which is sent immediately after the current message is sent; the data type is integer number;
BC control register content BC _ CB _ CSR: for defining BC control block register attributes, comprising:
the attribute IsDelayFrame is used for defining whether the frame is a delay frame or not, and the type is a Boolean type;
attribute Direction, which is used to define whether the message Direction is RT sending or RT receiving, and the type is character string;
the attribute IsStartFrame is used for defining whether the frame is the head frame of a continuous message frame, and the type is Boolean;
the attribute IsEndFrame is used for defining whether the frame is the tail frame of a continuous message frame or not, and the type is a Boolean type;
the attribute IsMCDATA is used for defining whether mode control is performed or not, and the type is Boolean type;
the attribute SelectBus is used for defining default sending on the A bus or the B bus, and the type is a character string;
first command word CMD 1: the method is used for defining the content of a command word 1 in the bus message, including the RT address, the SA sub-address, whether the TR sends or receives the message, and the WordCount message length;
second command word CMD 2: when the message is an RT-to-RT message, defining the content of a command word 2 in the bus message, including the RT address, the element SA _ MC, the element TR and the message length WordCount of the message;
the RT address is as follows: the method comprises the steps of defining the address, integer and 0-31 of a remote terminal to which a message belongs;
the element SA _ MC: the method is used for defining the subaddress to which the message belongs or controlling and shaping the subaddress in a mode of 0-31; if the current message is mode control, the current message is defined as 0 or 31;
the element TR: the message sending and receiving device is used for defining whether the message is sent or received by a remote terminal, and is shaped, wherein 0 is receiving and 1 is sending;
the message length WordCount: the method comprises the following steps of defining data length or mode control codes of a message, wherein the data length or mode control codes are integer 0-31, and the unit is 'word', and 0 represents 32 words;
and the message default cache data MSG _ Buffer is used for writing the default data into the MSG _ Buffer element when the data of the message is not changed or the default data exists.
2. The method according to claim 1, wherein the interrupt package is used to define a message response mode or processing logic, and includes periodically sending and querying vector words, and is specifically defined as follows:
element Interrupt: for defining two message corresponding modes: a periodic message queue MsgQueue and query vector word data MonitorData;
periodic message queue MsgQueue: is a set of periodic messages MQ _ MSG for enumerating all messages that need to be periodically sent or received;
the periodic message MQ _ MSG comprises a message Name, an attribute ischangeBus, an attribute BeginID, an attribute EndID, an attribute FrameTimeMultiple and an optional attribute FilePath;
the attribute isChangeBus is used for defining whether the redundant bus is replaced into a default bus of the message when the current bus is not accessible; the data type is a Boolean type;
attribute begini id: a start message ID number for defining the periodic message; the data type is integer;
attribute EndID: an end message ID number for defining the periodic message; the data type is integer;
attribute FrameTimeMultiple: the unit of the cycle is a bus cycle; the data type is integer;
property FilePath: the path used for simulating the data file defines the data content of the message sending as the data in the file defined by the FilePath; the attribute is an optional attribute, and the data type is a character string;
vector word data monitorerdata: for querying message response means elements; a set comprising an attribute, TargetMsgNum, and an element Operation;
attribute TargetMsgNum: a message ID number for indicating a vector word for fast locating vector word messages;
element Operation: a message which needs to respond to the vector word and indicates an element Name message type, an attribute Mask, an attribute Value, an attribute BeginID and an attribute EndID;
attribute Mask: the data type is hexadecimal, represents a mask used for calculating the vector word and is used for acquiring whether the corresponding position of the current vector word is set to be 1 or not;
attribute Value: the data type is hexadecimal, the Value obtained after vector word and mask calculation is compared with Value, if the Value is the same, the current Operation needs to respond, and if the Value is different, the Operation does not respond; and adding the attribute BeginID message into the periodic message queue in a response mode, and setting a queue tail message of the periodic message queue as EndID.
3. The method according to claim 2, wherein the communication timing relationship is a logical description between a BC-initiated data transmission procedure and an RT request data transmission procedure; the method comprises the following steps: BC sends vector word inquiry periodically, RT changes vector word data and sets service request after preparing response data; BC sends the response message according to the vector word content and the protocol definition; the message encapsulation comprises the following steps: vector word message definition, message ID, period and command word content; the interrupt package includes: the vector word content is queried and the communication frames are defined and organized according to the content.
4. The method according to claim 2, wherein the bus system setting is a description of a selection of system mode control and a fault handling mode; the method comprises the following steps: the system selection mode controls the sending of the status word and the sending of the vector word; the failure processing mode is that the redundant bus is retried once, if the retry is successful, the redundant bus is switched to be the default bus; the message package comprises mode control definition and message retry logic; the interrupt package includes: it is defined whether to switch the default bus.
5. The method according to claim 2, wherein each user message type is a description of which users are in the system, RT addresses of the users, and SA subaddress functions, cycles, and data lengths of the users; the method comprises the following steps: defining a management unit as BC, a load controller and a GNC unit as RT; the RT address of the load controller is 1, and the RT address of the GNC unit is 2; the load controller message has data injection, SA subaddress is 2, BC- > RT, length 32 word; 2s telemetering data, wherein the SA subaddress is 5, RT- > BC, the length is 128 words, the service request is carried out, and the vector word bit3 is set; track and status parameter message, BC- > RT, length 32 words, period 1 s; the message encapsulation comprises the following steps: defining a data injection message, a 2s telemetry message and a track status parameter message; the interrupt package includes: periodic message response logic and a vector word query message response mechanism are defined.
6. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1 to 5 when executing the computer program.
7. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, causes the processor to carry out the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910183872.9A CN109992554B (en) | 2019-03-12 | 2019-03-12 | Method for realizing 1553B bus communication protocol based on general Schema structure description |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910183872.9A CN109992554B (en) | 2019-03-12 | 2019-03-12 | Method for realizing 1553B bus communication protocol based on general Schema structure description |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109992554A CN109992554A (en) | 2019-07-09 |
| CN109992554B true CN109992554B (en) | 2020-11-06 |
Family
ID=67130562
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910183872.9A Active CN109992554B (en) | 2019-03-12 | 2019-03-12 | Method for realizing 1553B bus communication protocol based on general Schema structure description |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109992554B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110990311B (en) * | 2019-10-16 | 2022-12-06 | 中国航空工业集团公司洛阳电光设备研究所 | Configurable integrated 1553B bus controller design method |
| CN111556034B (en) * | 2020-04-15 | 2021-08-03 | 成都飞机工业（集团）有限责任公司 | GJB289A bus message dynamic mapping method |
| CN115514635A (en) * | 2022-09-20 | 2022-12-23 | 中国科学院国家空间科学中心 | Plug and play method of 1553B bus |
| CN116074156A (en) * | 2022-12-29 | 2023-05-05 | 北京机电工程研究所 | 1553B protocol design method for avoiding data conflict through time sequence design |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106933580A (en) * | 2017-03-02 | 2017-07-07 | 北京天恒长鹰科技股份有限公司 | A kind of embedded-type software architecture system |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8055907B2 (en) * | 2003-10-24 | 2011-11-08 | Microsoft Corporation | Programming interface for a computer platform |
| CN100458730C (en) * | 2006-12-13 | 2009-02-04 | 北京航空航天大学 | Method and apparatus to realize universal emulation by emulation apparatus based on 1553B bus |
| CN101339500B (en) * | 2008-05-22 | 2010-06-09 | 清华大学 | Data binding application program interface creation method based on XML mode |
| CN101834848B (en) * | 2010-03-29 | 2013-04-24 | 北京航空航天大学 | Method for describing protocol by using XML and protocol resolving system built by same |
| CN103810647A (en) * | 2014-02-13 | 2014-05-21 | 国家电网公司 | Standard message adapter design method and power grid integration display platform construction method |
| CN104050265A (en) * | 2014-06-20 | 2014-09-17 | 国家电网公司 | General bus adaptor construction method based on IEC 61968 standards |
| CN104331530B (en) * | 2014-09-03 | 2017-11-24 | 中国人民解放军63892部队 | A kind of electronic warfare Scene Simulation Platform and method of work based on XML descriptions |
| CN104699613B (en) * | 2015-03-26 | 2017-08-04 | 北京航空航天大学 | A kind of spacecraft-testing demand automatic creation system and its method |
| CN105337968A (en) * | 2015-10-19 | 2016-02-17 | 江苏中威科技软件系统有限公司 | Cross platform communication protocol code conversion method and system |
-
2019
- 2019-03-12 CN CN201910183872.9A patent/CN109992554B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106933580A (en) * | 2017-03-02 | 2017-07-07 | 北京天恒长鹰科技股份有限公司 | A kind of embedded-type software architecture system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109992554A (en) | 2019-07-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109992554B (en) | Method for realizing 1553B bus communication protocol based on general Schema structure description | |
| CN111930676B (en) | Method, device, system and storage medium for communication among multiple processors | |
| CN102750249B (en) | The method that host computer communicates with slave computer, Apparatus and system | |
| US20200210224A1 (en) | Methods and apparatus for verifying completion of groups of data transactions between processors | |
| US7069305B2 (en) | Computer system and a data transfer method thereof using remote direct memory access | |
| CN105141603A (en) | Communication data transmission method and system | |
| CN115396527B (en) | PCIE and SRIO protocol conversion system and method based on FPGA | |
| CN113259268A (en) | Network port and serial port data forwarding gateway and method supporting redundancy architecture | |
| US6185521B1 (en) | System and method for emulating mainframe channel programs by open systems computer systems | |
| CN105630424A (en) | Data processing method, device and system | |
| US5961614A (en) | System for data transfer through an I/O device using a memory access controller which receives and stores indication of a data status signal | |
| WO2020221033A1 (en) | Method for managing remote storage device by means of management device | |
| US20050091405A1 (en) | Method and system for using multiple data type representations to deliver data objects to components in a distributed system | |
| US6654380B1 (en) | Data exchange unit | |
| US7089234B2 (en) | Communicating state information in a network employing extended queries and extended responses | |
| CN102075452B (en) | Method, device and system for transmitting information | |
| CN113220238B (en) | Method for realizing universal SAS controller interface | |
| CN108540545B (en) | Spatial data bidirectional double asynchronous transmission method in cloud computing environment based on multiple agents | |
| US5497176A (en) | Method of transferring detailed data by tablet driver | |
| CN115766888A (en) | Data communication method and system | |
| CN107635009A (en) | Method of servicing, system, request of data device and the data supplying device of middleware | |
| JPH09269936A (en) | Remote reading processing method and device therefor | |
| JPH0351938A (en) | Host computer device | |
| JP3674720B2 (en) | Data transfer method in parallel computer | |
| CN113949604A (en) | Modbus gateway instruction processing method and device and gateway equipment |
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 |