CN115622836B - Fieldbus data conversion transmission system and method for aerospace field - Google Patents

Fieldbus data conversion transmission system and method for aerospace field Download PDF

Info

Publication number
CN115622836B
CN115622836B CN202211636247.3A CN202211636247A CN115622836B CN 115622836 B CN115622836 B CN 115622836B CN 202211636247 A CN202211636247 A CN 202211636247A CN 115622836 B CN115622836 B CN 115622836B
Authority
CN
China
Prior art keywords
data
field bus
conversion
bus
transmitted
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
Application number
CN202211636247.3A
Other languages
Chinese (zh)
Other versions
CN115622836A (en
Inventor
赵也倪
褚怡芳
李华磊
张弛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Dongfang Space Jiangsu Aerospace Power Co ltd
Dongfang Space Technology Shandong Co Ltd
Orienspace Hainan Technology Co Ltd
Orienspace Technology Beijing Co Ltd
Original Assignee
Dongfang Space Technology Shandong Co Ltd
Orienspace Hainan Technology Co Ltd
Orienspace Technology Beijing Co Ltd
Orienspace Xian Aerospace Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Dongfang Space Technology Shandong Co Ltd, Orienspace Hainan Technology Co Ltd, Orienspace Technology Beijing Co Ltd, Orienspace Xian Aerospace Technology Co Ltd filed Critical Dongfang Space Technology Shandong Co Ltd
Priority to CN202211636247.3A priority Critical patent/CN115622836B/en
Publication of CN115622836A publication Critical patent/CN115622836A/en
Application granted granted Critical
Publication of CN115622836B publication Critical patent/CN115622836B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40006—Architecture of a communication node
    • H04L12/40032—Details regarding a bus interface enhancer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B10/00—Transmission systems employing electromagnetic waves other than radio-waves, e.g. infrared, visible or ultraviolet light, or employing corpuscular radiation, e.g. quantum communication
    • H04B10/07—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems
    • H04B10/071—Arrangements for monitoring or testing transmission systems; Arrangements for fault measurement of transmission systems using a reflected signal, e.g. using optical time domain reflectometers [OTDR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40169—Flexible bus arrangements
    • 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/08—Protocols for interworking; Protocol conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L2012/40208—Bus networks characterized by the use of a particular bus standard
    • H04L2012/40215—Controller Area Network CAN
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L2012/40267—Bus for use in transportation systems
    • H04L2012/4028—Bus for use in transportation systems the transportation system being an aircraft
    • 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
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Abstract

The application provides a field bus data conversion transmission system and method for the aerospace field, the system comprises: the data conversion and transmission devices are respectively arranged at different rocket cabin sections and are used for forwarding field bus data of the rocket cabin sections; the data conversion and transmission device comprises a Zynq SoC chip, wherein the Zynq SoC chip comprises a PS end and a PL end, the PS end is used for operating protocol conversion software and providing a two-way CAN bus interface, and the PL end is used for providing four ways of 422 bus interfaces, one way of 1553B bus interface and an optical fiber reflection memory; the Zynq SoC chip is used for storing the first field bus data received by the bus interface into the optical fiber reflection memory for transmission to other rocket cabin sections or reading the second field bus data from the optical fiber reflection memory for transmission to the associated rocket cabin sections, so that the cost and the volume of the data transfer system can be reduced, and the universality of the data transfer system is improved.

Description

Fieldbus data conversion transmission system and method for aerospace field
Technical Field
The application relates to the technical field of aerospace craft testing, in particular to a field bus data conversion transmission system and method for the field of aerospace.
Background
The individual aerospace craft generally adopts a multi-bus form for data transmission, and before assembling each cabin section of the aerospace craft, a function test of each cabin section is required. Because each cabin section is respectively positioned in different test plants before assembly, communication of each cabin section needs to be realized through a corresponding data transfer system. The existing data transfer system usually adopts industrial personal computers respectively arranged in different cabin sections to realize data interaction of each cabin section. Fig. 1 is a schematic diagram of a conventional process for realizing the same-type data interaction of different cabin segments based on an industrial personal computer, wherein as shown in fig. 1, the industrial personal computer a receives data of a current cabin segment through a CAN board card, converts the data into corresponding data through software, writes the data into an optical fiber reflection memory board card, and transmits the data to the industrial personal computer B, and the industrial personal computer B reads the data from the optical fiber reflection memory board card and transmits the data to another cabin segment through the CAN board card through the software; fig. 2 is a schematic diagram of a conventional process for realizing interaction of different types of data in different cabin segments based on an industrial personal computer, where, as shown in fig. 2, the industrial personal computer a receives data of a current cabin segment through a CAN board card, converts the data into corresponding data through software, writes the data into an optical fiber reflection memory board card, and transmits the data to the industrial personal computer B, and the industrial personal computer B reads the data from the optical fiber reflection memory board card, converts the data into 422 data through the software, and transmits the data to another cabin segment through the 422 board card.
Although the mode for realizing the data interaction of each cabin section based on the industrial personal computer can basically realize the data interaction of the aerospace craft, the scale of the industrial personal computer is large, and an industrial personal computer host, a display and each functional board card need to be equipped, so that the data transfer device is high in cost and large in size, different conversion protocols need to be customized for different types of service tests, and the universality is poor.
Disclosure of Invention
The application provides a field bus data conversion transmission system and method for the aerospace field, and aims to solve the problems of high cost, large size and poor universality of the existing data transfer system.
The application provides a fieldbus data conversion transmission system for aerospace field, includes:
the data conversion and transmission devices are respectively arranged on different rocket cabin sections and are used for transmitting first field bus data of the associated rocket cabin section to other rocket cabin sections or receiving second field bus data from other rocket cabin sections and transmitting the second field bus data to the associated rocket cabin section;
the data conversion and transmission device comprises a Zynq SoC chip, wherein the Zynq SoC chip comprises a PS end and a PL end, the PS end is used for operating protocol conversion software and providing a two-way CAN bus interface, and the PL end is used for providing four ways of 422 bus interfaces, one way of 1553B bus interfaces and an optical fiber reflection memory; the Zynq SoC chip is used for storing the first field bus data received by the CAN bus interface, the 422 bus interface and the 1553B bus interface into the optical fiber reflection memory for transmission to other rocket cabin sections, or reading the second field bus data from the optical fiber reflection memory for transmission to associated rocket cabin sections.
According to the field bus data conversion and transmission system for the aerospace field, the Zynq SoC chip is further used for performing type conversion on the first field bus data based on the protocol conversion software under the condition that the first field bus data needs to be subjected to type conversion.
According to the field bus data conversion and transmission system for the aerospace field, the PS end is further used for being connected with a standard Ethernet to conduct software and hardware configuration and state query on the data conversion and transmission device.
The application also provides a field bus data conversion and transmission method for the aerospace field, which is applied to the field bus data conversion and transmission system for the aerospace field, and the method comprises the following steps:
s1, under the condition that a first data conversion transmission device receives interactive information sent by a first rocket cabin segment associated with the first data conversion transmission device, determining the type of the interactive information based on the data format of the interactive information; if the interactive information is a data reading instruction, executing the step S2; if the interactive information is the field bus data to be transmitted, executing the step S3;
s2, writing the data reading instruction into a corresponding first optical fiber reflection memory by the first data conversion transmission device, and executing the step S4;
s3, the first data conversion transmission device determines whether data type conversion is needed or not based on the field bus data to be transmitted; if so, converting the field bus data to be transmitted into a target data type and storing the target data type in a corresponding first optical fiber reflection memory; if not, directly storing the field bus data to be transmitted in the first optical fiber reflection memory; after the storage is finished, executing the step S6;
s4, a second data conversion transmission device obtains a data reading instruction in the first optical fiber reflection memory through a corresponding second optical fiber reflection memory, obtains target field bus data from a second rocket cabin segment associated with the second optical fiber reflection memory based on the data reading instruction and feeds the target field bus data back to the first data conversion transmission device, and the step S5 is executed;
s5, a first data conversion and transmission device transmits the target field bus data to the first rocket cabin section;
and S6, the second data conversion and transmission device acquires the field bus data to be transmitted in the first optical fiber reflection memory through the corresponding second optical fiber reflection memory and transmits the field bus data to be transmitted to the second rocket cabin section.
According to the fieldbus data conversion transmission method for the aerospace field, the determining of the type of the interaction information based on the data format of the interaction information specifically includes:
determining the type of a bus interface receiving the interaction information, and determining a data length threshold value corresponding to the interaction information based on the type of the bus interface;
and determining the type of the interactive information based on the comparison result of the data length of the interactive information and the corresponding data length threshold.
According to the fieldbus data conversion transmission method for the aerospace field, the determining the type of the interaction information based on the comparison result of the data length of the interaction information and the corresponding data length threshold specifically includes:
if the data length of the interactive information is smaller than the corresponding data length threshold, the interactive information is a data reading instruction; otherwise, the interactive information is the field bus data to be transmitted.
According to the field bus data conversion and transmission method for the aerospace field, whether data type conversion needs to be carried out or not is determined based on the field bus data to be transmitted, and the method specifically comprises the following steps:
determining a target data type of the field bus data to be transmitted based on a value of a receiving channel indicating bit or a receiving address indicating bit of the field bus data to be transmitted;
determining the current data type of the field bus data to be transmitted based on the bus interface type of the received field bus data to be transmitted;
if the current data type is different from the target data type, the field bus data to be transmitted needs to be subjected to data type conversion; otherwise, it is not needed.
According to the fieldbus data conversion transmission method for the aerospace field, the method for acquiring target fieldbus data from the second rocket cabin segment associated with the target fieldbus data based on the data reading instruction and feeding the target fieldbus data back to the first data conversion transmission device specifically comprises the following steps:
determining target equipment to be read in the second rocket cabin section and a corresponding reading address based on reading address indication bits of the reading instruction;
and sending a data reading instruction to the target device based on the reading address to acquire target field bus data.
According to the field bus data conversion and transmission method for the aerospace field, the field bus data to be transmitted is transmitted to the second rocket cabin section, and the method specifically comprises the following steps:
and determining a target bus interface of the second data conversion transmission device based on the value of the receiving channel indicator bit or the receiving address indicator bit of the fieldbus data to be transmitted, and transmitting the fieldbus data to be transmitted to the second rocket cabin section through the target bus interface.
According to the field bus data conversion and transmission method for the aerospace field, the field bus data to be transmitted are directly stored in the first optical fiber reflection memory, and the method specifically comprises the following steps:
and under the condition that the field bus data to be transmitted is 422 data, generating an interrupt based on a preset received data length threshold and a preset received time length threshold so as to write the 422 data into the first optical fiber reflective memory.
The application provides a field bus data conversion transmission system and method for the aerospace field, the system includes: the data conversion and transmission devices are respectively arranged on different rocket cabin sections and are used for transmitting first field bus data of the associated rocket cabin section to other rocket cabin sections or receiving second field bus data from other rocket cabin sections and transmitting the second field bus data to the associated rocket cabin section; the data conversion and transmission device comprises a Zynq SoC chip, wherein the Zynq SoC chip comprises a PS end and a PL end, the PS end is used for operating protocol conversion software and providing a two-way CAN bus interface, and the PL end is used for providing four ways of 422 bus interfaces, one way of 1553B bus interfaces and an optical fiber reflection memory; the Zynq SoC chip is used for storing the first field bus data received by the CAN bus interface, the 422 bus interface and the 1553B bus interface into the optical fiber reflective memory for transmission to other rocket cabin sections or reading the second field bus data from the optical fiber reflective memory for transmission to associated rocket cabin sections, so that the cost and the volume of the data transfer system CAN be reduced, and meanwhile, the universality of the data transfer system is improved.
Drawings
In order to more clearly illustrate the technical solutions in the present application or prior art, the drawings used in the embodiments or the description of the prior art are briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
FIG. 1 is a schematic flow diagram of a conventional industrial personal computer-based process for realizing interaction of the same kind of data in different cabin segments;
FIG. 2 is a schematic flow chart of the prior art for realizing interaction of different types of data of different cabin sections based on an industrial personal computer;
fig. 3 is a schematic structural diagram of a fieldbus data conversion transmission system for the aerospace field provided in the present application;
fig. 4 is a schematic flowchart of a fieldbus data conversion transmission method provided in this application for the field of aerospace;
FIG. 5 is a schematic diagram of a 422 bus data transmission flow provided herein;
fig. 6 is a schematic diagram of a data transmission flow of a CAN bus provided in the present application;
FIG. 7 is a schematic diagram of a 1553B bus data transmission process provided by the present application;
FIG. 8 is a second schematic diagram of a 1553B bus data transmission process provided by the present application;
FIG. 9 is a schematic diagram of a data transmission flow between 422 and a CAN bus provided by the present application;
FIG. 10 is a schematic diagram of a data transmission process for 422 and 1553B buses provided by the present application;
fig. 11 is a second schematic diagram illustrating a data transmission flow of 422B and 1553B buses provided by the present application;
FIG. 12 is a schematic diagram of a data transmission process of the CAN bus and 1553B bus provided by the present application;
fig. 13 is a second schematic diagram of data transmission flow of CAN and 1553B buses provided by the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be described clearly and completely with reference to the accompanying drawings in the present application, and it is obvious that the described embodiments are some, but not all embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Fig. 3 is a schematic structural diagram of a fieldbus data conversion and transmission system for the aerospace field, where, as shown in fig. 3, the system includes:
the data conversion and transmission devices are respectively arranged on different rocket cabin sections and are used for transmitting first field bus data of the associated rocket cabin section to other rocket cabin sections or receiving second field bus data from other rocket cabin sections and transmitting the second field bus data to the associated rocket cabin section;
the data conversion and transmission device comprises a Zynq SoC chip, wherein the Zynq SoC chip comprises a PS end and a PL end, the PS end is used for operating protocol conversion software and providing a two-way CAN bus interface, and the PL end is used for providing four ways of 422 bus interfaces, one way of 1553B bus interfaces and an optical fiber reflection memory; the Zynq SoC chip is used for storing the first field bus data received by the CAN bus interface, the 422 bus interface and the 1553B bus interface into the optical fiber reflection memory for transmission to other rocket cabin sections, or reading the second field bus data from the optical fiber reflection memory for transmission to associated rocket cabin sections.
Specifically, the field bus data conversion and transmission system for the aerospace field of the embodiment of the application adopts an embedded system to replace a traditional industrial personal computer equipment group, realizes information conversion and transmission of different rocket cabin sections through a plurality of data conversion and transmission devices respectively arranged in different rocket cabin sections, and the data conversion and transmission devices are used for transmitting first field bus data of an associated rocket cabin section to other rocket cabin sections or receiving second field bus data from other rocket cabin sections and transmitting the second field bus data to the associated rocket cabin section. Meanwhile, in order to minimize the data conversion and transmission device, a Zynq SOC-based hardware platform is adopted, and specifically, the data conversion and transmission device comprises a Zynq SoC chip which comprises a PS end and a PL end, wherein the PS end is used for running protocol conversion software and providing a two-way CAN bus interface, and the PL end is used for providing four-way 422 bus interfaces, one-way 1553B bus interface and an optical fiber reflective memory. The field bus board card is made into a fixed bus interface and is arranged on the embedded hardware equipment, so that the size and the cost of the data conversion and transmission device can be further reduced, the power consumption of the data conversion and transmission device can be reduced, and the data interaction between the data conversion and transmission devices and the data interaction inside the data conversion and transmission device are more efficient due to the adoption of the unified chip.
The Zynq SoC chip is used for storing the first field bus data received by the CAN bus interface, the 422 bus interface and the 1553B bus interface into the optical fiber reflection memory for transmission to other rocket cabin sections, or reading the second field bus data from the optical fiber reflection memory for transmission to associated rocket cabin sections, and the real-time interaction of the bus data of different rocket cabin sections CAN be realized based on the optical fiber reflection memory. It can be understood that the optical fiber reflective memories of different data conversion and transmission devices may directly perform data interaction through an optical fiber, or may perform data forwarding through a corresponding optical fiber reflective memory terminal, which is not specifically limited in this embodiment of the present application. The Zynq SoC chip is also used for carrying out type conversion on the first field bus data based on protocol conversion software running in the PS terminal under the condition that the first field bus data needs to be subjected to type conversion, and therefore the universality of the data conversion transmission device is improved. Based on an embedded real-time operating system, the data conversion and transmission device can realize the receiving and sending of multi-thread field bus data and the operation of optical fiber reflection memory data so as to meet the requirement of data transmission real-time property in the aerospace field.
The PS end is also used for connecting a standard Ethernet to carry out software and hardware configuration and state query on the data conversion transmission device, the software and hardware configuration comprises the configuration of protocol conversion software, and the state query comprises the acquisition of communication history records and software and hardware configuration information of a rocket cabin section so as to carry out function and information verification on the data conversion transmission device. Based on this, the versatility of the data conversion transmission device can be further improved. It can be understood that the data conversion and transmission device further includes a power supply module, and specific parameters of the power supply module can be set according to needs, which is not specifically limited in this embodiment of the present application.
The field bus data conversion transmission system for the aerospace field provided by the embodiment of the application comprises: the system comprises: the data conversion and transmission devices are respectively arranged on different rocket cabin sections and are used for transmitting first field bus data of the associated rocket cabin section to other rocket cabin sections or receiving second field bus data from other rocket cabin sections and transmitting the second field bus data to the associated rocket cabin section; the data conversion and transmission device comprises a Zynq SoC chip, wherein the Zynq SoC chip comprises a PS end and a PL end, the PS end is used for operating protocol conversion software and providing a two-way CAN bus interface, and the PL end is used for providing four ways of 422 bus interfaces, one way of 1553B bus interfaces and an optical fiber reflection memory; the Zynq SoC chip is used for storing the first field bus data received by the CAN bus interface, the 422 bus interface and the 1553B bus interface into the optical fiber reflection memory for transmission to other rocket cabin sections, or reading the second field bus data from the optical fiber reflection memory for transmission to associated rocket cabin sections, so that the cost and the volume of the data transfer system CAN be reduced, and meanwhile, the universality of the data transfer system is improved.
Fig. 4 is a schematic flow chart of a fieldbus data conversion and transmission method for the aerospace field, which is provided in this application and is applied to the fieldbus data conversion and transmission system for the aerospace field according to the foregoing embodiment, as shown in fig. 4, the method includes:
s1, under the condition that a first data conversion transmission device receives interactive information sent by a first rocket cabin segment associated with the first data conversion transmission device, determining the type of the interactive information based on the data format of the interactive information; if the interactive information is a data reading instruction, executing the step S2; if the interactive information is the field bus data to be transmitted, executing the step S3;
specifically, the first data conversion and transmission device is connected with a corresponding bus in the rocket cabin segment (i.e. the first rocket cabin segment) associated with the first data conversion and transmission device through a corresponding bus interface (i.e. the aforementioned CAN bus interface, 422 bus interface and 1553B bus interface) so as to receive the interaction information sent by the first rocket cabin segment. It can be understood that, in the case of receiving the mutual information sent by the first rocket cabin segment, the first data conversion transmission device can accurately determine the bus interface receiving the mutual information. Meanwhile, the first data conversion and transmission device can also determine the type of the interactive information based on the data format of the interactive information, wherein the type of the interactive information comprises a data reading instruction and field bus data to be transmitted. The determining the type of the interactive information based on the data format of the interactive information specifically includes:
determining the type of a bus interface receiving the interaction information, and determining a data length threshold corresponding to the interaction information based on the type of the bus interface; and determining the type of the interactive information based on the comparison result of the data length of the interactive information and the corresponding data length threshold.
It can be understood that, because there is an obvious difference between the data length of the data reading instruction and the data length of the fieldbus data, and there is also a difference between the data lengths of the data reading instructions corresponding to different types of fieldbus, based on this, the embodiment of the present application sets corresponding data length thresholds for different fieldbus in advance to be used for determining whether the interaction information corresponding to the fieldbus is the data reading instruction or the fieldbus data. Based on the foregoing, after receiving the interactive information sent by the first rocket cabin segment, the first data conversion transmission device can quickly determine the bus interface type of the received interactive information, and then determine the data length threshold corresponding to the interactive information based on the bus interface type. After the data length threshold corresponding to the interactive information is determined, the type of the interactive information can be determined based on the comparison result of the data length of the interactive information and the corresponding data length threshold. More specifically, the determining the type of the interaction information based on the comparison result between the data length of the interaction information and the corresponding data length threshold specifically includes:
if the data length of the interactive information is smaller than the corresponding data length threshold, the interactive information is a data reading instruction; otherwise, the interactive information is the field bus data to be transmitted. Based on the method, the type of the interactive information can be accurately determined, and then targeted processing is carried out.
S2, writing the data reading instruction into a corresponding first optical fiber reflection memory by the first data conversion transmission device, and executing the step S4;
s3, the first data conversion transmission device determines whether data type conversion is needed or not based on the field bus data to be transmitted; if yes, converting the field bus data to be transmitted into a target data type and storing the target data type in a corresponding first optical fiber reflection memory; if not, directly storing the field bus data to be transmitted in the first optical fiber reflection memory; after the storage is finished, executing the step S6;
s4, a second data conversion transmission device acquires a data reading instruction in the first optical fiber reflection memory through a corresponding second optical fiber reflection memory, acquires target field bus data from a second rocket cabin segment associated with the second optical fiber reflection memory based on the data reading instruction and feeds the target field bus data back to the first data conversion transmission device, and the step S5 is executed;
s5, a first data conversion transmission device transmits the target field bus data to the first rocket cabin section;
and S6, the second data conversion and transmission device acquires the field bus data to be transmitted in the first optical fiber reflection memory through the corresponding second optical fiber reflection memory and transmits the field bus data to be transmitted to the second rocket cabin section.
Specifically, if the interaction information is a data reading instruction, the first data conversion transmission device writes the data reading instruction into a corresponding first optical fiber reflective memory, and correspondingly, the second data conversion transmission device obtains the data reading instruction in the first optical fiber reflective memory through a corresponding second optical fiber reflective memory, obtains target field bus data from a second rocket cabin segment associated with the second data conversion transmission device based on the data reading instruction, and feeds the target field bus data back to the first data conversion transmission device, and the first data conversion transmission device transmits the target field bus data to the first rocket cabin segment.
If the interactive information is the field bus data to be transmitted, the first data conversion transmission device firstly determines whether data type conversion is needed or not based on the field bus data to be transmitted; if so, converting the field bus data to be transmitted into a target data type and storing the target data type in a corresponding first optical fiber reflection memory; if not, directly storing the field bus data to be transmitted in the first optical fiber reflection memory; and after the storage is finished, the second data conversion transmission device acquires the field bus data to be transmitted in the first optical fiber reflection memory through the corresponding second optical fiber reflection memory and transmits the field bus data to be transmitted to the second rocket cabin section. Based on the method, the real-time interaction of the rocket cabin field bus data can be realized.
It can be understood that two situations can be faced in the actual bus data interaction process of the rocket cabin, wherein the first situation is the same bus data conversion transmission, and the second situation is the different bus data conversion transmission. Based on this, in the embodiment of the present application, when the interaction information is to-be-transmitted fieldbus data, it is further determined whether data type conversion is required based on the to-be-transmitted fieldbus data, and it is determined whether data type conversion is required based on the to-be-transmitted fieldbus data, which specifically includes:
determining a target data type of the field bus data to be transmitted based on a value of a receiving channel indicating bit or a receiving address indicating bit of the field bus data to be transmitted;
determining the current data type of the field bus data to be transmitted based on the bus interface type of the received field bus data to be transmitted;
if the current data type is different from the target data type, the field bus data to be transmitted needs to be subjected to data type conversion; otherwise, it is not needed.
According to the bus data interaction method and device, based on bus data interaction characteristics in the aerospace field, corresponding communication protocol formats are set for different bus data interaction scenes, and based on the communication protocol formats, the first data conversion transmission device can perform efficient communication with the second data conversion transmission device based on received field bus data, so that bus data interaction efficiency of a rocket cabin section is improved.
Specifically, fig. 5 to 8 are schematic diagrams of a process of data conversion and transmission of the same bus, where fig. 5 is a schematic diagram of a 422 bus data transmission process provided by the present application, fig. 6 is a schematic diagram of a CAN bus data transmission process provided by the present application, fig. 7 is a schematic diagram of a 1553B bus data transmission process provided by the present application, and fig. 8 is a second schematic diagram of a 1553B bus data transmission process provided by the present application. In fig. 5 to 8, the a device refers to a first data conversion transmission apparatus, and the B device refers to a second data conversion transmission apparatus. As can be seen from fig. 5 to 8, the same bus data does not need to be converted, and the main requirement is to transmit data over long distance. The following description of the corresponding communication protocol format will be made for the interaction scenario shown in fig. 5-8:
for the 422 bus data transmission mode shown in fig. 5, the corresponding communication protocol format is shown in table 1:
TABLE 1 fiber-reflective memory protocol Format between A device and B device
422. Data base address offset Description of data content
0 32. Bit unsigned integer, 422 receiving channel, effective value 1 to 4
4 32. Bit unsigned integer, 422 data length
8~N Received data
Based on the communication protocol format in table 1, the device a in the embodiment of the present application can quickly determine the receiving channel indicator bit of 422 bus data, and write the 422 bus data into the fiber reflective memory so as to synchronize the 422 bus data to the device B through the fiber reflective memory terminal. It should be noted that, since the 422 bus data belongs to the mode of serial data transmission, and the fiber mirror memory is similar to the mode of block writing, in order to simulate the 422 data transmission mode to the maximum extent, it is necessary to read a small number of bytes frequently through the fiber mirror memory. Correspondingly, when the fieldbus data to be transmitted is 422 data, the directly storing the fieldbus data to be transmitted in the first optical fiber reflective memory specifically includes:
generating an interrupt based on a preset receive data length threshold and a receive time length threshold to write the 422 data to the first fiber optic reflective memory. That is, as long as the data length of the received 422 bus data meets a preset received data length threshold or the time for receiving 422 bus data meets a preset received time length threshold, an interrupt is generated to write the 422 bus data into the first fiber optic reflective memory. Therefore, the real-time performance of bus data transmission can be guaranteed to the maximum extent.
For the transmission mode of CAN bus data shown in fig. 6, the corresponding communication protocol format is shown in table 2:
TABLE 2 fiber-optic reflective memory switching formats for device A and device B
CAN data base address offset Description of data content
0 32. Bit unsigned integer, CAN receiving channel, effective value 1 to 2
4 32. Bit unsigned integer, CAN message arbitration ID
8 32. Bit unsigned integer, CAN data length, effective value 0 to 8
12 Received data 1, default 0x00
13 Received data 2, default 0x00
14 Received data 3, default 0x00
15 Received data 4, default 0x00
16 Received data 5, default 0x00
17 Received data 6, default 0x00
18 Received data 7, default 0x00
19 Received data 8, default 0x00
Based on the communication protocol format in table 2, the device a in the embodiment of the present application CAN quickly determine the receiving channel indicator bit of the CAN bus data, and write the CAN bus data into the optical fiber reflective memory so as to synchronize the CAN bus data to the device B through the optical fiber reflective memory terminal.
When 1553B bus data is transmitted, information and role types need to be distinguished, and 1553B is bus control type equipment, and a bus controller BC is hung on a bus and is unique. Therefore, when a device is used as an RT (i.e. remote terminal) terminal, a device B will be used as a BC terminal, whereas a device is used as a BC terminal and a device B is used as an RT terminal. Therefore, the transmission mode of 1553B bus data is divided into two cases: the transmission mode of 1553B bus data shown in fig. 7 is a case where a device as an RT receives 1553B BC data and transmits the BC data to a device B, and a corresponding communication protocol format is shown in table 3:
TABLE 3 1553B BC- > RT fiber reflection memory protocol format
1553B BC->RT message base address offset Description of data content
0 32. Bit unsigned integer, 1553B receiving channels, and effective value of 1 to 2
4 32. Bit unsigned integer, 1553B RT address, effective value 0 to 31
8 32. Bit unsigned integer, 1553B subaddress, effective value 0 to 31
12 32. Bit unsigned integer, 1553B message length, effective values of 1 to 32
16 16. Bit unsigned integer, received data 1, default 0x0000
18 16. Bit unsigned integer, received data 2, default 0x0000
20 16. Bit unsigned integer, received data 3, default 0x0000
22 16. Bit unsigned integer, received data 4, default 0x0000
24 16. Bit unsigned integer, received data 5, default 0x0000
26 16. Bit unsigned integer, received data 6, default 0x0000
28 16. Bit unsigned integer, received data 7, default 0x0000
30 16. Bit unsigned integer, received data 8, default 0x0000
32 16. Bit unsigned integer, received data 9, default 0x0000
34 16. Bit unsigned integer, received data 10, default 0x0000
36 16. Bit unsigned integer, received data 11, default 0x0000
38 16. Bit unsigned integer, received data 12, default 0x0000
40 16. Bit unsigned integer, received data 13, default 0x0000
42 16. Bit unsigned integer, received data 14, default 0x0000
44 16. Bit unsigned integer, received data 15, default 0x0000
46 16. Bit unsigned integer, received data 16, default 0x0000
48 16. Bit unsigned shaping, received data 17,default 0x0000
50 16. Bit unsigned integer, received data 18, default 0x0000
52 16. Bit unsigned integer, received data 19, default 0x0000
54 16. Bit unsigned integer, received data 20, default 0x0000
56 16. Bit unsigned integer, received data 21, default 0x0000
58 16. Bit unsigned integer, received data 22, default 0x0000
60 16. Bit unsigned integer, received data 23, default 0x0000
62 16. Bit unsigned integer, received data 24, default 0x0000
64 16. Bit unsigned integer, received data 25, default 0x0000
66 16. Bit unsigned integer, received data 26, default 0x0000
68 16. Bit unsigned integer, received data 27, default 0x0000
70 16. Bit unsigned integer, received data 28, default 0x0000
72 16. Bit unsigned integer, received data 29, default 0x0000
74 16. Bit unsigned integer, received data 30, default 0x0000
76 16. Bit unsigned integer, received data 31, default 0x0000
78 16. Bit unsigned integer, received data 32, default 0x0000
Based on the communication protocol format in table 3, the device a in the embodiment of the present application can quickly determine the receiving channel indication bit and the receiving address indication bit of the 1553B bus data, and write the 1553B bus data into the optical fiber reflective memory so as to synchronize the 1553B bus data to the device B through the optical fiber reflective memory terminal.
The transmission mode of 1553B bus data shown in fig. 8 is a case where the device a receives feedback data of the device B as the RT end, and at this time, the device B periodically queries and feeds back data content of the RT device as the BC end, and a corresponding communication protocol format is shown in table 4:
TABLE 4 1553B RT- > BC fiber reflection memory protocol format
1553B RT->BC message base address offset Description of data content
0 32. Bit unsigned integer, 1553B receiving channel j, effective value 1 to 2
4 32. Bit unsigned integer, 1553B subaddress i, effective value 0 to 31
8 16. Bit unsigned integer, received data 1, default 0x0000
10 16. Bit unsigned integer, received data 2, default 0x0000
12 16. Bit unsigned integer, received data 3, default 0x0000
14 16. Bit unsigned integer, received data 4, default 0x0000
16 16. Bit unsigned integer, received data 5, default 0x0000
18 16. Bit unsigned integer, received data 6, default 0x0000
20 16. Bit unsigned integer, received data 7, default 0x0000
22 16. Bit unsigned integer, received data 8, default 0x0000
24 16. Bit unsigned integer, received data 9, default 0x0000
26 16. Bit unsigned integer, received data 10, default 0x0000
28 16. Bit unsigned integer, received data 11, default 0x0000
30 16. Bit unsigned integer, received data 12, default 0x0000
32 16. Bit unsigned integer, received data 13, default 0x0000
34 16. Bit unsigned integer, received data 14, default 0x0000
36 16. Bit unsigned integer, received data 15, default 0x0000
38 16. Bit unsigned integer, received numberBy 16, default 0x0000
40 16. Bit unsigned integer, received data 17, default 0x0000
42 16. Bit unsigned integer, received data 18, default 0x0000
44 16. Bit unsigned integer, received data 19, default 0x0000
46 16. Bit unsigned integer, received data 20, default 0x0000
48 16. Bit unsigned integer, received data 21, default 0x0000
50 16. Bit unsigned integer, received data 22, default 0x0000
52 16. Bit unsigned integer, received data 23, default 0x0000
54 16. Bit unsigned integer, received data 24, default 0x0000
56 16. Bit unsigned integer, received data 25, default 0x0000
58 16. Bit unsigned integer, received data 26, default 0x0000
60 16. Bit unsigned integer, received data 27, default 0x0000
62 16. Bit unsigned integer, received data 28, default 0x0000
64 16. Bit unsigned integer, received data 29, default 0x0000
66 16. Bit unsigned integer, received data 30, default 0x0000
68 16. Bit unsigned integer, received data 31, default 0x0000
70 16. Bit unsigned integer, received data 32, default 0x0000
72 32. Bit unsigned integer, 1553B subaddress i, effective value 0 to 31
76 16. Bit unsigned integer, received data 1, default 0x0000
... ......
Based on the communication protocol format in table 4, the device a in the embodiment of the present application can quickly determine a receiving channel indication bit and a receiving address indication bit of 1553B bus data, and obtain 1553B bus data from the device B to feed back to the BC device.
Fig. 9-13 are schematic diagrams of different bus data conversion transmission processes, wherein fig. 9 is a schematic diagram of a 422 and CAN bus data transmission process provided by the present application, fig. 10 is one of a schematic diagram of a 422 and 1553B bus data transmission process provided by the present application, fig. 11 is a second schematic diagram of a 422 and 1553B bus data transmission process provided by the present application, fig. 12 is one of a schematic diagram of a CAN and 1553B bus data transmission process provided by the present application, and fig. 13 is a second schematic diagram of a CAN and 1553B bus data transmission process provided by the present application. As in fig. 5-8, the a device in fig. 9-13 refers to a first data conversion transmission apparatus and the B device refers to a second data conversion transmission apparatus. As can be seen from fig. 9-13, different types of data buses have different required data formats, and therefore, an external device that is actually connected to the data buses can be normally converted into target bus data according to a certain encoding requirement. The following description of the corresponding communication protocol format will be made for the interaction scenario shown in fig. 9-13:
for the 422 and CAN bus data transmission modes shown in FIG. 9, the corresponding communication protocol formats are shown in tables 6-7:
TABLE 6 422- > fiber-reflective memory protocol Format between A device/A device and B device
422->Device A message base address offset Description of data content
0 32. Bit unsigned integer, CAN receiving channel, effective value 1 to 2
4 32. Bit unsigned integer, CAN arbitration ID information
8 32. Bit unsigned integer, 422 data length, effective value 1 to 8
12 8. Bit unsigned integer, data to convert 1, default 0x00
13 8. Bit unsigned integer, data to convert 2, default 0x00
14 8. Bit unsigned integer, data to convert 3, default 0x00
15 8. Bit unsigned integer, data to convert 4, default 0x00
16 8. Bit unsigned integer, data to convert 5, default 0x00
17 8. Bit unsigned integer, data to convert 6, default 0x00
18 8. Bit unsigned integer, data to convert 7, default 0x00
19 8. Bit unsigned integer, data to convert 8, default 0x00
TABLE 7 CAN-B device protocol Format
CAN->B device Protocol Description of data content
CAN arbitration ID bit 0-2 message type, 00-to-422, 01-to-1553B BC write message, 10-1553B BC read message, 11- 1553B RT write messages bit 3-8, wherein the target data length is 0-63, when the target data length is 0, the representative length is 64, and if the target data length is 0, the representative length is 64 For the 1553B data transmission mode, the length must be an integral multiple bit of 2 to 11: sequence number of current data packet, effective value is When the rotation is 422, the rotation speed is 12 to 7, bit 13: channel value 422 indicating transmission when it is a branch 1553B message, bit 12-16: representing an RT address, bit 16-20: representing RT subaddress, bit 21-bit 25 representing data length
CAN data 1 8. Bit unsigned integer, default 0x00
CAN data 2 8. Bit unsigned integer, default 0x00
CAN data 3 8. Bit unsigned integer, default 0x00
CAN data 4 8. Bit unsigned integer, default 0x00
CAN data 5 8. Bit unsigned integer, default 0x00
CAN data 6 8. Bit unsigned integer, default 0x00
CAN data 7 8. Bit unsigned integer, default 0x00
CAN data 8 8. Bit unsigned integer, default 0x00
Based on the communication protocol formats in tables 6 to 7, after receiving 422 bus data, the device a according to the embodiment of the present application CAN combine and convert the 422 bus data into CAN bus data and write the CAN bus data into the optical fiber reflective memory, so as to synchronize the CAN bus data to the device B through the optical fiber reflective memory terminal. Otherwise, the embodiments of the present application are not described herein again.
Based on the foregoing, the transmission modes of the 422 and 1553B bus data are also divided into two cases, fig. 10 shows the transmission modes of the 422 and 1553B bus data when the B device is used as the RT end, and the corresponding communication protocol formats are shown in tables 8-9:
TABLE 8 fibre-optic reflective memory protocol Format between 422- > A device/A device and B device
422->1553B RT numberAccording to base address offset Description of data content
0 1553B RT addresses to be written in have effective values of 0 to 31
4 Data 1, default 0x0000
6 Data 2, default 0x0000
8 Data 3, default 0x0000
10 Data 4, default 0x0000
……
66 Data 32, default 0x0000
TABLE 9 fiber-reflective memory protocol Format between B device- > A device
1553B RT ->422. Data base address offset Description of data content
0 The 1553B RT addresses are read, and the effective values are 0 to 31
4 Data 1, default 0x0000
6 Data 2, default 0x0000
8 Data 3, default 0x0000
10 Data 4, default 0x0000
……
66 Data 32, default 0x0000
Based on the communication protocol formats in tables 8 to 9, after receiving the 422 bus data, the device a according to the embodiment of the present application can convert the 422 bus data into 1553B bus data and write the 1553B bus data into the optical fiber reflective memory, so as to synchronize the 1553B bus data to the device B through the optical fiber reflective memory terminal. Otherwise, the embodiments of the present application are not described herein again.
Fig. 11 shows the transmission modes of 422 and 1553B bus data when the B device is used as the BC side, and the corresponding communication protocol formats are shown in tables 10 to 12:
TABLE 10 422- > fiber-optic reflective memory protocol Format between A device write data/A device and B device
422->1553B BC data base address offset Description of data content
0 1553B RT addresses to be written in have effective values of 0 to 31
4 1553B RT subaddress to be written, effective value 0-31
8 1553B data to be written has the length and effective value of 0-31
12 Data 1, default 0x0000
14 Data 2, default 0x0000
16 Data 3, default 0x0000
18 Data 4, default 0x0000
……
74 Data 32, default 0x0000
TABLE 11 422- > A device read data read instruction
422->1553B BC data base address offset Description of data content
0 1553B RT addresses to be read, effective values of 0 to 31
4 1553B RT subaddresses to be read have effective values of 0-31
8 1553B data length to be read, and effective value of 0-31
Table 12B device- > a device 1553B reads data content
1553B BC ->422. Data base address offset Description of data content
0 The effective value of the read 1553B RT address is 0 to 31
4 The effective value of the read 1553B RT subaddress is 0 to 31
8 The read 1553B data length has effective value of 0-31
12 Data 1, default 0x0000
14 Data 2, default 0x0000
16 Data 3, default 0x0000
18 Data 4, default 0x0000
……
74 Data 32, default 0x0000
As can be seen from fig. 11, when the device B serves as the BC terminal, the interaction information received by the device a (i.e., the first data conversion and transmission device) may be a data reading instruction, and may also be fieldbus data to be transmitted. On this basis, based on the communication protocol formats in tables 10 to 12, after receiving 422 bus data, the device a according to the embodiment of the present application can convert the 422 bus data into 1553B bus data and write the 1553B bus data into the optical fiber reflective memory so as to synchronize the 1553B bus data to the device B through the optical fiber reflective memory terminal. Meanwhile, when a data reading instruction is received, target fieldbus data can be acquired from the B device based on the data reading instruction. Otherwise, the embodiments of the present application are not described herein again.
Also, based on the foregoing, the transmission modes of the data of the CAN and 1553B buses are also divided into two cases, fig. 12 shows the transmission modes of the data of the CAN and 1553B buses when the B device is used as the BC terminal, and the corresponding communication protocol formats are shown in table 13:
TABLE 13 fiber-reflective memory protocol Format between device A and device B
CAN ->1553B read BC data base address offset Description of data content
0 1553B RT addresses to be written in, effective values of 0-31
4 1553B RT subaddresses to be written in, effective value 0 to 31
8 1553B data to be written has the length and effective value of 0-31
12 Data 1, default 0x0000
14 Data 2, default 0x0000
16 Data 3, default 0x0000
18 Data 4, default 0x0000
……
74 Data 32, default 0x0000
The protocols of the CAN- > A equipment and the A equipment- > CAN are detailed in a table 7. As can be seen from fig. 12, similar to the situation shown in fig. 11, when the device B serves as the BC terminal, the interaction information received by the device a (i.e., the first data conversion and transmission device) may be a data reading command, and may also be fieldbus data to be transmitted. On this basis, based on the communication protocol formats in tables 7 and 13, after receiving CAN bus data, the device a in the embodiment of the present application CAN convert the CAN bus data into 1553B bus data and write the 1553B bus data into the optical fiber reflective memory so as to synchronize the 1553B bus data to the device B through the optical fiber reflective memory terminal. Meanwhile, when a data reading instruction is received, target fieldbus data can be acquired from the B device based on the data reading instruction. Otherwise, the embodiments of the present application are not described herein again.
Fig. 13 shows transmission modes of data of the CAN and 1553B buses when the B device is used as the RT terminal, and the corresponding communication protocol formats are shown in table 14:
table 14 format of fiber-optic reflective memory protocol between device-B device/B device-a device
Data base address offset Description of data content
0 1553B RT addresses to be written in, effective values of 0-31
4 1553B RT subaddress to be written, effective value 0-31
8 1553B data to be written has a length, and effective values of 0 to 31
12 Data 1, default 0x0000
14 Data 2, default 0x0000
16 Data 3, default 0x0000
18 Data 4, default 0x0000
……
74 Data 32, default 0x0000
The protocols of the CAN- > A equipment and the A equipment- > CAN are detailed in a table 7. Based on fig. 13, similar to the situation shown in fig. 10, based on the communication protocol formats in tables 7 and 14, the device a according to the embodiment of the present invention CAN convert CAN bus data into 1553B bus data and write the 1553B bus data into the optical fiber reflective memory so as to synchronize the 1553B bus data to the device B through the optical fiber reflective memory terminal. Otherwise, the embodiments of the present application are not described herein again.
On the basis of the communication protocol, for the embodiment of the present application, the acquiring target fieldbus data from the second rocket cabin segment associated therewith based on the data reading instruction and feeding back the target fieldbus data to the first data conversion transmission device specifically includes:
determining target equipment to be read in the second rocket cabin section and a corresponding reading address based on a reading address indicating bit of the reading instruction; and sending a data reading instruction to the target device based on the reading address to acquire target field bus data. Based on this, can realize the quick accurate reading of target fieldbus data.
Meanwhile, the transmitting the fieldbus data to be transmitted to the second rocket cabin section specifically comprises:
and determining a target bus interface of the second data conversion transmission device based on the value of the receiving channel indicator bit or the receiving address indicator bit of the fieldbus data to be transmitted, and transmitting the fieldbus data to be transmitted to the second rocket cabin section through the target bus interface. Therefore, the field bus data to be transmitted can be accurately and efficiently transmitted to the second rocket cabin section, and the efficiency and the accuracy of bus data interaction of the rocket cabin section are improved.
The method provided by the embodiment of the application comprises the following steps: s1, under the condition that a first data conversion transmission device receives interactive information sent by a first rocket cabin segment associated with the first data conversion transmission device, determining the type of the interactive information based on the data format of the interactive information; if the interactive information is a data reading instruction, executing the step S2; if the interactive information is the field bus data to be transmitted, executing step S3; s2, writing the data reading instruction into a corresponding first optical fiber reflection memory by the first data conversion transmission device, and executing the step S4; s3, the first data conversion transmission device determines whether data type conversion is needed or not based on the field bus data to be transmitted; if yes, converting the field bus data to be transmitted into a target data type and storing the target data type in a corresponding first optical fiber reflection memory; if not, directly storing the field bus data to be transmitted in the first optical fiber reflection memory; after the storage is finished, executing the step S6; s4, a second data conversion transmission device acquires a data reading instruction in the first optical fiber reflection memory through a corresponding second optical fiber reflection memory, acquires target field bus data from a second rocket cabin segment associated with the second optical fiber reflection memory based on the data reading instruction and feeds the target field bus data back to the first data conversion transmission device, and the step S5 is executed; s5, a first data conversion and transmission device transmits the target field bus data to the first rocket cabin section; and S6, the second data conversion transmission device acquires the field bus data to be transmitted in the first optical fiber reflection memory through the corresponding second optical fiber reflection memory and transmits the field bus data to be transmitted to the second rocket cabin section, so that the accurate and efficient transmission of the bus data of different rocket cabin sections can be realized based on the field bus data conversion transmission system, the universality of the field bus data conversion transmission system is improved on the basis of reducing the volume and the cost of the field bus data conversion transmission system, and the efficiency and the accuracy of the rocket cabin section bus data interaction are ensured.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present application.

Claims (7)

1. A field bus data conversion and transmission method for the aerospace field is applied to a field bus data conversion and transmission system for the aerospace field, and the system comprises: the data conversion and transmission devices are respectively arranged on different rocket cabin sections and are used for transmitting first field bus data of the associated rocket cabin section to other rocket cabin sections or receiving second field bus data from other rocket cabin sections and transmitting the second field bus data to the associated rocket cabin section; the data conversion and transmission device comprises a Zynq SoC chip, wherein the Zynq SoC chip comprises a PS end and a PL end, the PS end is used for operating protocol conversion software and providing a two-way CAN bus interface, and the PL end is used for providing four ways of 422 bus interfaces, one way of 1553B bus interfaces and an optical fiber reflection memory; the Zynq SoC chip is used for storing the first field bus data received by the CAN bus interface, the 422 bus interface and the 1553B bus interface into the optical fiber reflection memory for transmission to other rocket cabin sections, or reading the second field bus data from the optical fiber reflection memory for transmission to associated rocket cabin sections; the Zynq SoC chip is also used for carrying out type conversion on the first field bus data based on the protocol conversion software under the condition that the first field bus data needs to be subjected to type conversion; the PS end is also used for connecting a standard Ethernet to carry out software and hardware configuration and state query on the data conversion transmission device;
the method comprises the following steps:
s1, under the condition that a first data conversion transmission device receives interactive information sent by a first rocket cabin segment associated with the first data conversion transmission device, determining the type of the interactive information based on the data format of the interactive information; if the interactive information is a data reading instruction, executing the step S2; if the interactive information is the field bus data to be transmitted, executing the step S3;
s2, writing the data reading instruction into a corresponding first optical fiber reflection memory by the first data conversion transmission device, and executing the step S4;
s3, the first data conversion transmission device determines whether data type conversion is needed or not based on the field bus data to be transmitted; if so, converting the field bus data to be transmitted into a target data type and storing the target data type in a corresponding first optical fiber reflection memory; if not, directly storing the field bus data to be transmitted in the first optical fiber reflection memory; after the storage is finished, executing the step S6;
s4, a second data conversion transmission device acquires a data reading instruction in the first optical fiber reflection memory through a corresponding second optical fiber reflection memory, acquires target field bus data from a second rocket cabin segment associated with the second optical fiber reflection memory based on the data reading instruction and feeds the target field bus data back to the first data conversion transmission device, and the step S5 is executed;
s5, a first data conversion and transmission device transmits the target field bus data to the first rocket cabin section;
and S6, the second data conversion and transmission device acquires the field bus data to be transmitted in the first optical fiber reflection memory through the corresponding second optical fiber reflection memory and transmits the field bus data to be transmitted to the second rocket cabin section.
2. The field bus data conversion and transmission method for the aerospace field according to claim 1, wherein the determining the type of the interaction information based on the data format of the interaction information specifically includes:
determining the type of a bus interface receiving the interaction information, and determining a data length threshold value corresponding to the interaction information based on the type of the bus interface;
and determining the type of the interactive information based on the comparison result of the data length of the interactive information and the corresponding data length threshold.
3. The method for converting and transmitting fieldbus data in the aerospace field according to claim 2, wherein the determining the type of the interaction information based on the comparison result between the data length of the interaction information and the corresponding data length threshold specifically includes:
if the data length of the interactive information is smaller than the corresponding data length threshold, the interactive information is a data reading instruction; otherwise, the interactive information is the field bus data to be transmitted.
4. The field bus data conversion and transmission method for the aerospace field according to claim 3, wherein the determining whether data type conversion is required based on the field bus data to be transmitted specifically includes:
determining the target data type of the field bus data to be transmitted based on the value of a receiving channel indicating bit or a receiving address indicating bit of the field bus data to be transmitted;
determining the current data type of the field bus data to be transmitted based on the bus interface type of the received field bus data to be transmitted;
if the current data type is different from the target data type, the field bus data to be transmitted needs to be subjected to data type conversion; otherwise, it is not needed.
5. The fieldbus data conversion transmission method for the aerospace field according to claim 4, wherein the acquiring target fieldbus data from the second rocket cabin segment associated therewith based on the data reading instruction and feeding back the target fieldbus data to the first data conversion transmission device specifically includes:
determining target equipment to be read in the second rocket cabin section and a corresponding reading address based on reading address indication bits of the reading instruction;
and sending a data reading instruction to the target device based on the reading address to acquire target field bus data.
6. The method for converting and transmitting fieldbus data in the aerospace field according to claim 5, wherein transmitting the fieldbus data to be transmitted to the second rocket cabin segment specifically comprises:
and determining a target bus interface of the second data conversion transmission device based on the value of the receiving channel indicator bit or the receiving address indicator bit of the fieldbus data to be transmitted, and transmitting the fieldbus data to be transmitted to the second rocket cabin section through the target bus interface.
7. The method for converting and transmitting fieldbus data in the aerospace field according to claim 6, wherein the directly storing the fieldbus data to be transmitted in the first optical fiber reflective memory specifically includes:
and under the condition that the field bus data to be transmitted is 422 data, generating an interrupt based on a preset received data length threshold and a preset received time length threshold so as to write the 422 data into the first optical fiber reflective memory.
CN202211636247.3A 2022-12-20 2022-12-20 Fieldbus data conversion transmission system and method for aerospace field Active CN115622836B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211636247.3A CN115622836B (en) 2022-12-20 2022-12-20 Fieldbus data conversion transmission system and method for aerospace field

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211636247.3A CN115622836B (en) 2022-12-20 2022-12-20 Fieldbus data conversion transmission system and method for aerospace field

Publications (2)

Publication Number Publication Date
CN115622836A CN115622836A (en) 2023-01-17
CN115622836B true CN115622836B (en) 2023-04-14

Family

ID=84879600

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211636247.3A Active CN115622836B (en) 2022-12-20 2022-12-20 Fieldbus data conversion transmission system and method for aerospace field

Country Status (1)

Country Link
CN (1) CN115622836B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110514243A (en) * 2019-08-20 2019-11-29 重庆零壹空间科技集团有限公司 A kind of carrier rocket collecting method, system, terminal device and medium
CN110988564A (en) * 2019-12-24 2020-04-10 北京中科宇航探索技术有限公司 Subsection rocket electrical system and test method thereof
CN111581138A (en) * 2020-04-20 2020-08-25 北京空间飞行器总体设计部 Passage structure for bus data transmission among multiple spacecraft
CN115333988A (en) * 2022-10-13 2022-11-11 东方空间技术(北京)有限公司 Test method, system and equipment for rocket interstage communication signals

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10530605B2 (en) * 2015-08-06 2020-01-07 Tower-Sec Ltd. Means and methods for regulating can communication

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110514243A (en) * 2019-08-20 2019-11-29 重庆零壹空间科技集团有限公司 A kind of carrier rocket collecting method, system, terminal device and medium
CN110988564A (en) * 2019-12-24 2020-04-10 北京中科宇航探索技术有限公司 Subsection rocket electrical system and test method thereof
CN111581138A (en) * 2020-04-20 2020-08-25 北京空间飞行器总体设计部 Passage structure for bus data transmission among multiple spacecraft
CN115333988A (en) * 2022-10-13 2022-11-11 东方空间技术(北京)有限公司 Test method, system and equipment for rocket interstage communication signals

Also Published As

Publication number Publication date
CN115622836A (en) 2023-01-17

Similar Documents

Publication Publication Date Title
US7730245B2 (en) Method and system for setting addresses for slave devices in data communication system
CN106959935B (en) Method compatible with I2C communication and IPMB communication
CN106126465A (en) A kind of data transmission method and device
CN115622836B (en) Fieldbus data conversion transmission system and method for aerospace field
US11956097B2 (en) Battery management system and method for data transmission in a battery management system
US20180361574A1 (en) Intelligent digital controller of flexible material cutting robot and realization method
CN110659242A (en) MIL-STD-1553B bus protocol controller
CN117033296A (en) Internal unified communication system and method for multi-CPU board card device
CN108228520B (en) BMC-oriented I2C controller fast transmission method
US20030149819A1 (en) Method and apparatus for ascertaining the status of multiple devices simultaneously over a data bus
CN115129552A (en) Method, device, equipment and storage medium for monitoring transmission state of I2C bus
CN212486527U (en) Slave station conversion device based on MODBUS protocol
US20130067130A1 (en) Bus control apparatus and bus control method
CN114500148B (en) Conversion device, access method, electronic equipment and storage medium of PA equipment
EP0055741B1 (en) Input/output system and method of communication for peripheral devices in data processing system
RU72772U1 (en) MAIN CONTROLLER MODULE OF THE SERIAL INTERFACE
CN111324563A (en) PCIe equipment physical lane combination system and method
CN113986807B (en) Protocol conversion method and protocol converter for USB bus and PC104 bus
CN116756078B (en) Notification method and device of pcie data packet and storage medium
RU2682435C1 (en) Data transmission interface
CN216904917U (en) PCI-X standard reflective memory optical fiber network real-time communication board card
CN202205196U (en) Serial apparatus general communication bus system
CN216792886U (en) Data transmission relay equipment and data transmission system
CN115617722B (en) System and method for realizing sharing DMA linked list by multiple PCIE devices
CN220419954U (en) Multi-serial-port double-backup data storage processing system

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
CP03 Change of name, title or address

Address after: 100176 room 12b03, 12b floor, building 40, yard 1, Desheng North Street, Beijing Economic and Technological Development Zone, Beijing

Patentee after: Oriental space technology (Beijing) Co.,Ltd.

Country or region after: China

Patentee after: Dongfang space technology (Shandong) Co.,Ltd.

Patentee after: Dongfang Space (Jiangsu) Aerospace Power Co.,Ltd.

Patentee after: Orient Space (Hainan) Technology Co.,Ltd.

Address before: 100176 room 12b03, 12b floor, building 40, yard 1, Desheng North Street, Beijing Economic and Technological Development Zone, Beijing

Patentee before: Oriental space technology (Beijing) Co.,Ltd.

Country or region before: China

Patentee before: Dongfang space technology (Shandong) Co.,Ltd.

Patentee before: Oriental space (Xi'an) Aerospace Technology Co.,Ltd.

Patentee before: Orient Space (Hainan) Technology Co.,Ltd.

CP03 Change of name, title or address