CN115514635A - Plug and play method of 1553B bus - Google Patents

Abstract

The invention relates to a plug-and-play method of a 1553B bus, which comprises the following steps: defining a handshake protocol between a remote terminal of a 1553B bus and a bus controller and an electronic data form format reflecting the communication message requirement of the remote terminal; when the remote terminal accesses a 1553B bus, an electronic data form corresponding to the communication message requirement of the remote terminal is sent to a bus controller according to a handshake protocol; generating a remote terminal message demand and state list according to the received electronic data form, and dynamically arranging the remote terminal through a bus controller; meanwhile, the communication state of the remote terminal is monitored through the bus controller, and related message arrangement of the remote terminal is cancelled after the remote terminal is offline, so that plug and play of a 1553B bus are realized. The invention realizes the requirement interaction between the bus controller and the remote terminal by the way of electronic data single handshake exchange, dynamically arranges 1553B bus message communication, and realizes the plug and play effect.

Description

Plug and play method of 1553B bus

Technical Field

The invention belongs to the field of 1553B bus communication, and particularly relates to a plug-and-play method of a 1553B bus.

Background

The 1553B bus is a high-reliability communication bus and consists of a Bus Controller (BC), a Remote Terminal (RT) and a bus Monitor (MT), and the bus can support 30 RTs at most. The BC realizes the arrangement and management of bus data transmission, the RT completes the data transmission in the bus according to the command of the BC, and the MT realizes the monitoring of bus messages.

The 1553B bus design is usually implemented by appointing the communication requirement information of each RT in advance, and the BC side arranges the bus messages on the basis of the bus requirements of all RTs. The method needs the personnel of both BC and RT to appoint the bus communication message sequence in advance, and in the communication process, the communication is carried out according to the fixed message sequence. When the communication requirement of the RT is changed or the RT is increased or decreased, the BC side needs to readjust the bus message sequence.

Disclosure of Invention

The invention aims to release the coupling of BC and RT, avoid the BC state from being influenced due to the change of RT requirements and realize the plug-and-play effect of 1553B bus RT.

The invention provides a 1553B bus plug and play method, which comprises the following steps:

defining a handshake protocol between a remote terminal of a 1553B bus and a bus controller and an electronic data form format reflecting the communication message requirement of the remote terminal;

when a remote terminal accesses a 1553B bus, an electronic data form corresponding to the communication message requirement of the remote terminal is sent to a bus controller according to a handshake protocol;

generating a remote terminal message demand and state list according to the received electronic data form, and dynamically arranging the remote terminal through a bus controller; meanwhile, the communication state of the remote terminal is monitored through the bus controller, and related message arrangement of the remote terminal is cancelled after the remote terminal is offline, so that plug and play of a 1553B bus are realized.

As an improvement of the above technical solution, the handshake protocol employs a mode based on a service request and a vector word, wherein the vector word uses a single bit and represents a message type.

As an improvement of the above technical solution, the defining a spreadsheet format reflecting the communication message requirements of the remote terminal includes: defining vector words and subaddress messages;

the definition vector word comprises: defining vector word identification, vector word mask and data field;

the vector word identifier is a fixed value and is used for identifying a defined vector word data field in the electronic data sheet;

the vector word mask is defined to define the condition of each bit of the vector word of 1553B and identify the use condition of each bit;

the data field definition is used for defining the use condition of each bit in a 1553B vector word and is used corresponding to the vector word mask definition, and when the bit is used, the data field definition is used for identifying the 1553B message attribute corresponding to the bit and the used sub-address;

the defining a subaddress message comprises: defining a sub-address identification, a T sub-address mask, a T sub-address, an R sub-address mask and an R sub-address;

the sub-address field identification is defined as a fixed value and is used for identifying a sub-address message data field in the electronic data form;

the T sub-address mask and the R sub-address mask are used for defining the use conditions of 32 sending sub-addresses and 32 receiving sub-addresses in a 1553B bus;

the T sub-address and the R sub-address respectively comprise definitions of 32 sub-addresses, and are arranged in sequence to describe the communication requirements of the sub-addresses.

As an improvement of the above technical solution, the content defined by the subaddress message further includes:

the message attribute is to define the message as a sending message or a receiving message, the sending message is a message transmitted to the bus controller by the remote terminal, and the receiving message is a message transmitted to the remote terminal by the bus controller;

a message type representing the application layer definition for the message;

the on-line mark is used for marking that the message is in an on-line state or an off-line state under the default condition, and the message is in the on-line state under the default condition;

the message quantity is defined as the number of continuously transmitted messages and indicates that the subaddress message consists of a plurality of continuous messages; the data field supports single message and multi-message definitions and message number definitions of large data blocks of special applications;

the number of data words, which represents the number of data words of a message sent by a sub-address, is defined as all 0 and represents 32 words; and

message period, defined as the minimum message interval expected by the remote terminal, should be able to identify message definitions without communication period, i.e. message requirements constrained by the way of service requests.

As one improvement of the above technical solution, the message requirement and status list of the remote terminal is generated according to the received electronic data form, and the remote terminal is dynamically arranged through the bus controller; meanwhile, the communication state of the remote terminal is monitored through the bus controller, and the related message arrangement of the remote terminal is cancelled after the remote terminal is offline, and the method comprises the following steps:

step 1) analyzing the received electronic data form through a bus controller to generate a remote terminal message demand list and a remote terminal state list;

step 2) generating a message sequence according to the remote terminal message demand list and the remote terminal state list, generating a bus message according to the message sequence, arranging the message sequence through a bus controller according to the bus message, realizing dynamic arrangement of the remote terminal, and establishing a communication relation with the remote terminal;

and 3) monitoring the communication state of the remote terminal by the bus controller, judging that the remote terminal is offline when no response occurs after long time timeout, clearing the related information of the remote terminal, and identifying the offline state of the remote terminal.

As an improvement of the above technical solution, the remote terminal message requirement list generated in step 1) includes the following elements:

message state, remote terminal number, subaddress, message type, message communication time, number of messages, message length, offset address in RAM area where message is located, offset address of valid data in message, control word, cycle attribute, cycle time, cycle count and cycle flag.

As an improvement of the above technical solution, the remote terminal state list generated in step 1) includes the following elements:

whether the remote terminal is on-line, bus state, current bus, message list start number, total number of messages, data injection message number, remote terminal communication state, number of vector words, and vector word information.

As an improvement of the above technical solution, in the step 2), the bus message is generated by inserting the message sequence into the frame.

As an improvement of the above technical solution, in the plug and play process of the 1553B bus, the bus message arrangement includes:

judging whether the frame is a vector word frame;

if the vector word frame exists, checking whether a vector word message request exists, if the vector word message request exists, arranging a communication frame according to the vector word, and if the vector word message request does not exist, exiting the processing;

if the vector word frame is not the vector word frame, processing the remote terminal communication frame message;

wherein the vector word frames represent communication frames comprised of vector word messages and the remote terminal communication frames represent communication frames comprised of remote terminal messages other than vector words.

Compared with the prior art, the invention has the advantages that:

1. the method realizes the dynamic and timely control of the BC on-line or off-line of the RT by defining a handshake protocol between the remote terminal RT of the 1553B bus and the BC of the bus controller and an electronic data form format reflecting the communication message requirement of the remote terminal;

2. the scheme removes the coupling of the BC and the RT, avoids the BC state from being influenced due to the change of the RT requirement, is more beneficial to the independent design of the BC and the RT in the engineering implementation, and simplifies the mutual interface coordination work.

Drawings

FIG. 1 is a 1553B bus plug and play scenario workflow diagram of the method of the present invention;

FIG. 2 is a flow chart of a 1553B bus message arrangement using the method of the present invention;

fig. 3 is a schematic diagram of a conventional BC management process in the prior art.

Detailed Description

The invention provides a 1553B bus plug and play scheme design, which comprises the following steps:

a handshake protocol between RT and BC is defined, as well as a spreadsheet (RT EDS) format that reflects RT communication message requirements. When the RT accesses the bus, the RT EDS is sent to the BC according to a handshake protocol. And the BC communicates with the dynamically arranged messages according to the RT EDS, so that the plug-and-play effect of the 1553B bus is realized.

The RT defines own communication requirements according to an RT EDS format; the BC completes 1553B message arrangement according to the RT EDS and simultaneously monitors the communication state of the RT; revoking the RT's associated message arrangements after the RT is taken offline. The method comprises the following steps:

step 1) the RT generates an RT EDS reflecting the communication requirement of the RT according to an EDS format.

And step 2) the RT and the BC send the RT EDS to the BC through a handshake protocol.

And 3) the BC analyzes the RT EDS to generate an RT message demand list and an RT state list.

And 4) arranging a message sequence by the BC according to the RT message demand list and the RT state list, realizing the dynamic arrangement of the RT messages and establishing a communication relation with the RT.

And 5) the BC monitors the communication state of the RT, judges that the RT is offline when no response occurs after long time overtime, clears the related information of the RT and identifies the offline state of the RT.

The RT EDS definition reflecting the RT communication requirements in step 1) is shown in table 1:

TABLE 1 RT EDS Format

1) Vector word identification: fixed to 0xEDED (1110110111101101).

2) Vector word mask: arranging 16 bits in the order of high order to low order, the bit Dx =1/0 indicates use/non-use of the xth

A service request for bits.

3) Vector words define the data fields: indicating the correspondence of the sub-address to the service request bit. The corresponding vector words mask are arranged in units of bytes. Dx =1/0 of the vector word mask indicates the xth byte valid/invalid. In the xth byte, the low bit of 6 is effective and is a T/R + sub-address number, and the high bit of 2 is 0.

4) Sub-address field identification: fixed at 0x1212 (0001001000010010).

5) T sub-address mask and R sub-address mask: each 2 word has 32 bits (31 to 0) arranged in the order of upper to lower bits, and a bit Dx =1/0 indicates use/non-use of the corresponding sub-address x.

6) The T sub-address definition and the R sub-address definition each include 32 sub-address definitions arranged in the order of 31-0, each sub-address defining two words. If the sub-address is not used, all 0's are set.

7) The 1 st word format in the subaddress definition is shown in table 2.

Table 2 subaddress defines word 1 format

a) The T/R and the message type correspond to the T/R and the message type in the message demand list, and the function of establishing connection is achieved.

b) U/D: refers to messages scheduled on the main bus cycle, with default being either on line (1) or off line (0). Normally the default is 0, if the default is 1, then the message will be scheduled and will run unconditionally periodically unless it is actively taken off-line afterwards.

c) Number of messages transmitted continuously: meaning that the subaddress message consists of several consecutive messages. The single message is 1, the data block message is 8, the special number is designated by RT, and all 0's represent 16 pieces.

d) The number of data words, all 0's, represents 32 words.

8) Word 2 is the RT expected minimum message interval in ms.

a) All 1 s represent 65.535 seconds. All 0 s indicate messages that have no periodicity requirements and need to be transmitted according to conditions.

And C) handshaking protocol of BC and RT in the step 2).

The handshake protocol between BC and RT is based on the way the service requests and vector words, which use a single bit to represent one message type.

The step 3) RT message requirement list and RT state list element definition.

The RT message requirement list includes the following element definitions:

message state, RT number, subaddress, message type, message communication time, number of messages, message length, offset address in RAM area where message is located, offset address of valid data in message, control word, cycle attribute, cycle time, cycle count, cycle mark.

The RT status list includes the following element definitions:

whether the RT is on-line, the bus state, the current bus, the message list start number, the total number of messages, the data injection message number, the RT communication state, the number of vector words and the vector word information.

And in the step 4), the BC generates a message sequence in real time according to the RT message demand list and the RT state list, and generates the message sequence into bus messages by inserting the message sequence into frames, so as to control the operation of the bus. And realizing the plug and play of RT.

And in the step 5), the BC monitors the bus communication state and cancels the relevant information of the off-line RT in real time.

The technical scheme provided by the invention is further illustrated by combining the following embodiments.

Example 1

Fig. 1 is a flowchart of a plug and play method for completing a 1553B bus according to embodiment 1 of the present invention. Fig. 3 is a flowchart illustrating a conventional BC management function in the prior art. Comparing the two figures, the invention realizes the plug-and-play effect of the RT of the 1553B bus by defining the handshake protocol between the RT and the BC of the 1553B bus and the spreadsheet format reflecting the RT communication message requirement to avoid the BC state from being influenced due to the change of the RT requirement.

Fig. 2 is a flow chart showing message arrangement for implementing 1553B bus according to embodiment 1 of the present invention.

The invention realizes the required interaction between the Bus Controller (BC) and the Remote Terminal (RT) by an Electronic Data Sheet (EDS) handshake exchange mode. BC obtains the communication requirement of RT through EDS of RT, and 1553B bus message communication is dynamically arranged according to the communication requirement, so that the plug-and-play effect of RT is realized.

In order to achieve the above object, the present invention provides a plug and play design of 1553B bus, including:

a handshake protocol between RT and BC is defined, as well as RT EDS format reflecting RT message requirements. The RT describes its own communication requirements in terms of RT EDS format. And the BC acquires the RT EDS according to a handshake protocol, analyzes and determines the message requirement of the RT. The BC dynamically arranges the message sequence according to the message requirement of the RT, establishes a communication relation with the RT and realizes the plug-and-play effect of the RT.

In the above technical solution, the plug and play design of the 1553B bus includes the following steps:

step 1) RT generates EDS of itself;

step 2) the RT and the BC send the communication requirement EDS of the RT to the BC through a handshake protocol;

step 3), the BC analyzes the message demand EDS of the RT to form an RT message demand list and an RT state list;

step 4), the BC realizes the autonomous arrangement of the RT messages through the RT message demand list and the RT state list, and completes the autonomous access of the RT;

and 5) the BC monitors the message state of the RT, if the RT has no communication for a long time, the RT is judged to be offline, the related message of the RT is cleared, the offline state of the RT is identified, and the automatic revocation of the RT is realized.

In the above technical solution, step 1 specifically includes: the RT generates an EDS (electronic data System) with the communication requirement of the RT according to an EDS format of the RT;

RT EDS is defined as shown in table 3:

TABLE 3

Vector word mask description: used vector word bit position 1, unused vector word bit zero clearing

Vector word data field description, as shown in table 4: 16 bytes in total

TABLE 4

Byte 1	Byte 2	……	Byte 15	Byte 16
					Corresponding bit0 (MSB)		……		Corresponding bit15 (LSB)

Vector words define the data fields: indicating the correspondence of the sub-address to the service request bit. The corresponding vector words mask are arranged in units of bytes. Dx =1/0 of the vector word mask indicates the xth byte valid/invalid. In the xth byte, the low bit of 6 is effective and is a T/R + sub-address number, and the high bit of 2 is 0.

Sub-address mask description: as shown in table 5: position 1 of used transmitting sub-address bit, and zero clearing of unused transmitting sub-address bit

TABLE 5

Bit0(MSB)	Bit 14	……	Bit1	Bit31(LSB)
					Sub-address 31		……		Sub-address 0

Sub-address definition description: as shown in table 6:

the subaddress defines the 1 st word format: as shown in table 7;

TABLE 7

T/R: transmitting or receiving 1: indicating transmission; 0: indicating reception

Message type: application layer definition of message types

U/D: a scheduled message is either online (1) or offline (0) by default. If the default is 0, then the line can be arranged through inputting an instruction subsequently; if the default is 1, then the message will be scheduled and will run unconditionally periodically unless it is later actively taken offline.

Number of messages transmitted continuously: meaning that the subaddress message consists of several consecutive messages. The single message is 1, the special number is specified by RT, all 0's represent 16. If the item is not 1, the length of the first n-1 messages is 32, and the length of the last message refers to the data word number option.

Number of data words: the word count of the message is indicated for a single message, and the word count of the last message is indicated for a plurality of messages. All 0 s represent 32 words.

Word 2 is the RT expected minimum message interval in ms. All 1 s represent 65.535 seconds. All 0 s indicate messages that have no periodicity requirements and need to be transmitted according to conditions.

In the above technical solution, step 2 specifically includes: the handshake protocol between BC and RT is based on the way the service requests and vector words, the data words in the vector word messages represent one message type with a single bit.

After the RT EDS is generated, the RT sets the bit of the transmission EDS of the vector word to be 1, and provides a service request to the BC.

The BC inquires the service request condition of each RT periodically, if the RT has the service request, the vector word is read, the judgment is carried out according to bit, and if the RT is the request for sending the EDS message, the BC arranges the EDS message sent by the RT.

In the above technical solution, step 3 specifically includes: and the BC analyzes the EDS after receiving the RT EDS and generates an RT message demand list and an RT state list.

The RT message list format is shown in table 8:

TABLE 8

The RT status list format is shown in table 9:

TABLE 9

Serial number	Name(s)	Length of	Remarks to note
				1.	rt_state	1	Current state of the RT
2.	bus_state	1	Bus state
				3.	current_bus	1	Currently used bus
4.	injectTlbnum	2	Data injection message number
				5.	looptblnum	2	Long embracing hoop message number
6.	busStartNum	2	Bus list start position
				7.	busmesCnt	1	Number of messages of this RT in the bus List
8.	vector_num	1	Number of vector words
				9.	vector_inf[16]	2*16	Message number corresponding to vector word
10.	err_cnt	1	Long embracing ring error counting

In the above technical solution, step 4 specifically includes: and the BC periodically inquires the vector words of the current online RT and the service request state, and if the RT has the vector word service request, arranges the responded vector word message according to the vector words recorded in the RT state list.

The BC completes the periodic timing of the periodic messages in the message list through the self timer.

And the BC period inquires the period timing condition of the period message in the message list, and arranges the bus message of the timing period on the bus according to the content of the message list.

In the above technical solution, step 5 specifically includes: and the BC judges the communication state of the on-line RT through the long-loop test message.

The RT is appointed to realize the long hugging test function through the sub-address 30, namely the RT receives the long hugging message sent by the BC through the receiving sub-address 30 and then sends the long hugging message to the BC through the sending sub-address 30. The BC periodically arranges the long embracing ring message of the line RT, firstly sends the RT long embracing ring receiving message, and arranges the RT long embracing ring sending message after a period of time.

And the BC judges the content of the long embracing data, if the data is abnormal, the long embracing error is recorded, and if the RT is abnormal for 10 continuous times, the RT is considered to be offline.

And after monitoring the RT is offline, the BC removes all the messages of the RT in the message list. And completing the autonomous offline of the RT.

Let EDS inquiry period be about 1 second, bus period is agreed to be 125ms.

Take RT2 plug and play access as an example. The bus requirements for RT2 are: sending 2 messages with the length of 32 words by the sending sub-address 2 in a cycle of 2 seconds; sending the subaddress for 3 periods of 375ms to send 1 message with the length of 12 words; sub-address 5 sends 5 messages of length 32 words in a cycle of 5 seconds; the sending sub-address 16 sends 2 messages with the length of 32 words in a period of 250 ms; the sending sub-address 24 sends 4 messages of length 32 words in cycle 4 seconds, the receiving sub-address 5 receives 2 messages of length 32 words in cycle 2 seconds, and the receiving sub-address 9 receives 1 message of length 32 words in cycle 2 seconds.

RT2 generated the EDS as follows:

0x1ACF,0xC000,0x008F,0x0000,0xEDED,0x8000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x003A,0x1212,0x0501,0x002C,0x0000,0x0000,0x0000,0x0000,0xC640,0x07D0,0xC631,0x0177,0x0000,0x0000,0xC6A0,0x1388,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0xC640,0x00FA,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0xC680,0x0FA0,0x0000,0x0000,0xC6A0,0x1388,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0220,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x1E40,0x07D0,0x0000,＝0x0000,0x0000,0x0000,0x0000,0x0000,0x0A20,0x07D0,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,＝0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000。

the contract vector word bit15 flags EDS transmission.

RT writes and sends EDS mark to vector word buffer: 0x8000; and sets the service request bit.

BC schedules vector word query messages for all RTs with a period of 1 second.

After receiving the EDS sending request of the RT2, the BC software arranges the EDS sending message of the RT: as shown in table 10.

Table 10, after RT2 proposes sending EDS vector words, BC schedules RT2 to send vector word messages

After receiving the EDS message of the RT2, the BC determines and analyzes the EDS, generates an RT2 message demand list, taking an example that the RT2 sub-address 2 sends 2 message demands with a length of 32 words in a cycle of 2 seconds, and the message demand list is as follows:

State＝0xAA

RtNum＝2

Sub＝2

Type＝17

Form＝RT->BC

Time＝100us

Cnt＝2

Len＝32

Mesaddr＝0x0200

Dataoffsetaddr＝02

Controlword＝0x7F27

command1＝0x1420

command2＝0x00

periodic＝0xAA

period_len＝0x7D0

period_cnt＝0x000

period_flag＝0xAA

time_out＝0x55

the state list for RT2 is generated as follows:

rt_state＝0xAA

bus_state＝0xFF

current_bus＝0x0A

injectTlbnum＝

looptblnum＝0x43

busStartNum＝0x3C

busmesCnt＝9

vector_num＝0

vector_inf[16]＝0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000,0x0000

err_cnt＝0x0

BC sets RT2 as the on-line state, arranges the long embracing hoop message every second,

the BC schedules the RT2 bus messages according to the RT2 message requirements as shown in table 11: communication messages within 6 seconds after RT2 is on line.

TABLE 11

RT2 stops sending messages

BC, after monitoring the continuous abnormality of RT long looping messages, clearing all messages of RT1,

the BC completes the plug-and-play of RT 2.

It can be seen from the above description that the present invention realizes the interaction between the Bus Controller (BC) and the Remote Terminal (RT) by way of handshake exchange of Electronic Data Sheet (EDS), and meanwhile, BC obtains the communication requirement of RT by EDS of RT, and accordingly dynamically arranges 1553B bus message communication, and realizes the plug and play effect of RT.

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 (9)

1. A1553B bus plug and play method is characterized by comprising the following steps:

defining a handshake protocol between a remote terminal of a 1553B bus and a bus controller and an electronic data form format reflecting the communication message requirement of the remote terminal;

when the remote terminal accesses a 1553B bus, an electronic data form corresponding to the communication message requirement of the remote terminal is sent to a bus controller according to a handshake protocol;

generating a remote terminal message demand and state list according to the received electronic data form, and dynamically arranging the remote terminal through a bus controller; meanwhile, the communication state of the remote terminal is monitored through the bus controller, and related message arrangement of the remote terminal is cancelled after the remote terminal is offline, so that plug and play of a 1553B bus are realized.

2. A 1553B bus plug and play method according to claim 1, characterized in that the handshake protocol is based on service requests and vector words, wherein a vector word uses a single bit to represent a message type.

3. The 1553B bus plug and play method of claim 1, wherein defining a spreadsheet format reflecting the communication message requirements of the remote terminal comprises: defining vector words and subaddress messages;

the definition vector word comprises: defining vector word identification, vector word mask and data field;

the vector word identifier is a fixed value and is used for identifying a defined vector word data field in the electronic data sheet;

the vector word mask is defined to define the condition of each bit of the vector word of 1553B and identify the use condition of each bit;

the data field definition is used for defining the use condition of each bit in a 1553B vector word and is used corresponding to the vector word mask definition, and when the bit is used, the data field definition is used for identifying the 1553B message attribute corresponding to the bit and the used sub-address;

the defining a sub-address message includes: defining a sub-address identification, a T sub-address mask, a T sub-address, an R sub-address mask and an R sub-address;

the sub-address field identification is defined as a fixed value and is used for identifying a sub-address message data field in the electronic data form;

the T sub-address mask and the R sub-address mask are used for defining the use conditions of 32 sending sub-addresses and 32 receiving sub-addresses in a 1553B bus;

the T sub-address and the R sub-address respectively comprise definitions of 32 sub-addresses, and are arranged in sequence to describe the communication requirements of the sub-addresses.

4. The 1553B bus plug and play method of claim 3, wherein the content defined by the subaddress message further comprises:

the message attribute is to define the message as a sending message or a receiving message, the sending message is a message transmitted to the bus controller by the remote terminal, and the receiving message is a message transmitted to the remote terminal by the bus controller;

a message type representing the application layer definition for the message;

the on-line mark is used for marking that the message is in an on-line state or an off-line state under the default condition, and the message is in the on-line state under the default condition;

the message quantity is defined as the number of continuously transmitted messages and indicates that the subaddress message consists of a plurality of continuous messages; the data field supports single message and multi-message definitions and message number definitions of large data blocks of special applications;

the number of data words, which represents the number of data words of a message sent by a sub-address, is defined as all 0 and represents 32 words; and

message period, defined as the minimum message interval expected by the remote terminal, should be able to identify message definitions without communication period, i.e. message requirements constrained by the way of service requests.

5. The 1553B bus plug and play method of claim 1, wherein the message requirement and status list of the remote terminal is generated according to the received electronic data form, and the remote terminal is dynamically arranged by the bus controller; meanwhile, the communication state of the remote terminal is monitored through the bus controller, and the related message arrangement of the remote terminal is cancelled after the remote terminal is off line, and the method comprises the following steps:

step 1) analyzing the received electronic data form through a bus controller to generate a remote terminal message demand list and a remote terminal state list;

step 2) generating a message sequence according to the remote terminal message demand list and the remote terminal state list, generating a bus message according to the message sequence, arranging the message sequence through a bus controller according to the bus message, realizing dynamic arrangement of the remote terminal, and establishing a communication relation with the remote terminal;

and 3) monitoring the communication state of the remote terminal by the bus controller, judging that the remote terminal is offline when no response occurs after long time timeout, clearing related information of the remote terminal, and identifying the offline state of the remote terminal.

6. The 1553B bus plug and play method according to claim 5, wherein the message requirement list generated in step 1) includes the following elements:

message state, remote terminal number, subaddress, message type, message communication time, number of messages, message length, offset address in RAM area where message is located, offset address of valid data in message, control word, cycle attribute, cycle time, cycle count and cycle flag.

7. The 1553B bus plug and play method according to claim 5, wherein the remote terminal status list generated in step 1) includes the following elements:

whether the remote terminal is on-line, bus state, current bus, message list start number, total number of messages, data injection message number, remote terminal communication state, number of vector words, and vector word information.

8. The 1553B bus plug and play method according to claim 5, wherein the message sequence in step 2) is inserted into a frame to generate a bus message.

9. The 1553B bus plug-and-play method of claim 8, wherein during the plug-and-play of the 1553B bus, the bus message arrangement comprises:

judging whether the frame is a vector word frame;

if the vector word frame exists, checking whether a vector word message request exists, if the vector word message request exists, arranging a communication frame according to the vector word, and if the vector word message request does not exist, exiting the processing;

if the vector word frame is not the vector word frame, processing the remote terminal communication frame message;

wherein the vector word frames represent communication frames comprised of vector word messages and the remote terminal communication frames represent communication frames comprised of remote terminal messages other than vector words.

Images