CN107623728B - FC-AE-ASM data universal analysis method based on product interface control file - Google Patents
FC-AE-ASM data universal analysis method based on product interface control file Download PDFInfo
- Publication number
- CN107623728B CN107623728B CN201710800697.4A CN201710800697A CN107623728B CN 107623728 B CN107623728 B CN 107623728B CN 201710800697 A CN201710800697 A CN 201710800697A CN 107623728 B CN107623728 B CN 107623728B
- Authority
- CN
- China
- Prior art keywords
- data
- signal
- name
- field
- value
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to a FC-AE-ASM data general analysis method based on a product interface control file, which comprises an interface control file database conversion method and a data analysis method, wherein the database conversion method comprises the steps of dividing data types, establishing a message name general table, establishing a data information table and establishing a discrete signal table, and the data analysis method comprises the following steps: establishing a structure array, reading the MsgID, comparing the MsgID with the message number field, acquiring the data length according to the element type, acquiring a discrete signal data value and acquiring a data signal data value. The invention can be applied to all automatic product testing systems containing FC-AE-ASM data, and has strong universality; when the product state changes, only the corresponding content of the interface control file database needs to be changed, and the automatic test system cannot be influenced.
Description
Technical Field
The invention relates to the technical field of FC-AE-ASM bus testing, in particular to a FC-AE-ASM data universal analysis method based on a product interface control file.
Background
The interface control file is the core of the avionic product, and in order to realize the test and fault diagnosis of the product, the monitoring data of the product interface needs to be analyzed based on the interface control file. With the continuous improvement of the requirements of avionic products on communication speed and reliability, FC-AE-ASM has been widely applied to various models, and currently, the analysis of FC-AE-ASM data is mostly embedded in a special test system of each product, and the following two problems mainly exist: firstly, interface data analysis methods cannot be shared among test systems of different products, analysis codes need to be written respectively aiming at different interface control files, and reusability of the test systems is reduced; and secondly, when the interface control file is changed, the interface data analysis method of the test system needs to be re-developed, so that the test efficiency and reliability of the test system are reduced.
Disclosure of Invention
The invention aims to provide a FC-AE-ASM data universal analysis method based on a product interface control file, which adopts a universal processing flow to realize automatic analysis of FC-AE-ASM data of different avionic products according to a configured interface control file.
The technical problem to be solved by the invention is realized by adopting the following technical scheme:
the FC-AE-ASM data general analysis method based on the product interface control file comprises an interface control file database conversion method and a data analysis method.
The interface control file database conversion method comprises the following steps:
s1) partition data type: dividing all element signals contained in the message in the interface control file into data signals and discrete signals according to data types, wherein the data signals can be divided into BNR1, BNR2, BC1 and BC2 according to data formats;
s2) creating a message name summary table, comprising the steps of:
s21) establishing a table named as 'message name' in Microsoft Office Access;
s22) establishing a 'message name' and a 'message number' field in the table;
s23) filling the message name and the message number of each message in the interface control file into the corresponding field;
s24) adding 32 fields in the table from "element 0 signal name" to "element 15 signal name", "element 0 signal type" to "element 15 signal type";
s25) filling element signals contained in each message in the interface control file into the field of "element n signal name" in element sequence, and filling "discrete signal" or "data" in the field of "element n signal type" according to the data type of the element signals, wherein n is 0 and 1 … … 15;
s3), creating a data information table, comprising the steps of:
s31) establishing a table named as 'data' in Microsoft Office Access;
s32) establishing 7 fields including 'signal name', 'data format', 'data length', 'MSB', 'unit', 'most significant bit' and 'least significant bit' in the table;
s33) filling signal names of all data types in the message name table into the signal name field, and filling information of signal format, data bit length, MSB, unit, most significant data bit and least significant data bit into other corresponding fields in the table according to the description of each signal parameter in the interface control file.
S4), creating a discrete signal table, comprising the steps of:
s41) establishing a table in Microsoft Office Access, and naming by element signal names;
s42) establishing 4 fields including 'name', 'digit', 'lowest bit' and 'highest bit' in the table;
s43) filling the data name, the occupied digit number, the most significant bit and the least significant bit contained in the element signal into the corresponding fields in the table;
s44) adding 2 to the table based on the maximum value among the number of bits occupied by each dataMaximum value of occupied digitA field with the field names "value 0", "value 1" … "value 2Maximum value of occupied digit-1”；
S45) filling the actual meaning of the concrete representation into the corresponding field according to the description of the corresponding meaning of each data value in the interface control file;
s46) establishing a perfect signal name table for each element signal of the type discrete signal, as per steps S41) to S45).
The data analysis method comprises the following steps:
sa) establishing a structure array Element [16], wherein each structure comprises a character string variable representing a signal name of an Element, a character string variable representing a type of the Element, a long integer variable representing a data length of the Element and a long integer variable representing a value of the Element;
sb) reads a word representing MsgID of the FC-AE-ASM data frame, and converts the 16-ary representation string into an integer;
sc) compares the MsgID with the value of the "message number" field in the "message name" table, where the "message name" and the "message number" are established and assigned in step S22), step S23), and in the case of the same value, assigns the character strings of the "Element 0 signal name" to "Element 15 signal name" fields to the Element signal names in the arrays Element [0] to Element [15], and assigns the character strings of the "Element 0 signal type" to "Element 15 signal type" fields to the Element types in the arrays Element [0] to Element [15 ].
Sd) acquiring a data length according to an element type, comprising the steps of:
sd1) if the Element type in the array Element [ n ] is a discrete signal, the data length in the structure body is 16;
sd2) if the Element type in the array Element [ n ] is data, comparing the Element signal name in the structure with the value of the "Element n signal name" field in step S25), and assigning the value in the "data length" field to the data length of the structure if the values are the same;
where n is 0, 1 … 15.
Se) obtaining discrete signal data values, comprising the steps of:
se1) when the Element type in the Element [ n ] is a discrete signal, entering a corresponding table according to the Element signal name in the structure body, wherein n is 0, 1 … 15;
se2) connecting PayLoad (PayLoad) fields in FC-AE-ASM data frames to form a character string;
se3) dividing the character string obtained in the step Se2) from high order to low order according to the value of each field of 'digit', 'highest order' and 'lowest order' recorded in the discrete signal table in the step S4), wherein each divided character string is a character string represented by 16-system corresponding to the data name represented by the 'name' field in the record;
se4) converting each character string into integer X, and then converting the integer X into a character string form of "value X", so that the value of the "value X" field in the record is the actual meaning of the data corresponding to the data name.
Sf) acquiring data signal data values, comprising the steps of:
sf1), when the Element type in the Element [ n ] is data, entering the data table in step S31), wherein n is 0 and 1 … 15;
sf2) comparing the element signal name in the structure body with the value of the 'signal name' field in the table, and obtaining the value of the rest fields in the record when the element signal name in the structure body is the same as the value of the 'signal name' field in the table;
sf3) connecting PayLoad fields in the FC-AE-ASM data frames to form a character string;
sf4) intercepting character strings with corresponding lengths from high order to low order in the character strings obtained in the step Sf2) according to the value of the 'data length' field in the record;
sf5) converting the character string obtained in the step Sf3) into a 16-system long integer, and calculating an actual numerical value according to the information of the 'data format' field, the 'MSB' field, the 'most significant bit' field and the 'least significant bit' field in the record.
Step Sf5) applying the BNR algorithm to the BNE data format type:
Dhighest order*MSB+DHighest order-1*MSB*2-1+…+DLowest position*MSB*2Lowest order-highest order
And solving to obtain an actual numerical value.
Applying the BC algorithm to the BC data format type:
(-1)*Dhighest order*MSB+DHighest order-1*MSB+DHighest order-2*MSB*2-1+…+DLowest position*MSB*2Lowest order-highest order +1
And solving to obtain an actual numerical value.
Compared with the prior art, the invention has the advantages that the invention can be applied to all automatic test systems of products containing analysis of FC-AE-ASM data, and has strong universality; when the product state changes, only the corresponding content of the interface control file database needs to be changed, and the automatic test system cannot be influenced.
Drawings
The invention is further illustrated with reference to the following figures and examples.
FIG. 1 is a message name table field illustration of the present invention;
FIG. 2 is a table field illustration of a data signal according to the present invention;
FIG. 3 is a table field illustration of the discrete signal of the present invention;
FIG. 4 is a flow chart of data parsing according to the present invention.
Detailed Description
In order to make the technical means, the creation characteristics, the achievement purposes and the effects of the invention easy to understand, the invention is further explained below.
The fibre channel avionics environment (FC-AE) is a family of protocols established by the fibre channel standards development organization, and the FC-AE-ASM protocol is an upper layer protocol in the FC-AE network and is used for supporting definite, safe and low-delay communication among various processors, sensors and displays in the fibre channel avionics environment. The invention comprises an interface control file database conversion method and a data analysis method, and can be applied to all automatic product test systems containing FC-AE-ASM data.
Message name table field description diagram as shown in fig. 1:
establishing a 'message name' table, wherein the table comprises a 'message number', a 'message name', an 'element signal name' and an 'element type', wherein:
the message number corresponds to the MsgID in the ASM frame and corresponds to a message sent by a certain node in the FC-AE network;
the "message name" represents a data block name in the ICD file (i.e., signal interface control file), which indicates the function and meaning of the data block;
the 'element signal name' is the name of a valid data block which is actually transmitted, each data block at most comprises 16 or 32 elements, each element has 16 bits, each data block at most comprises 16 elements, each element has 16 bits or 32 bits, a discrete signal has 16 bits, and a digital signal has 16 bits or 32 bits;
the "element type" is divided into discrete signals and data.
Adding 32 fields from 'element 0 signal name' to 'element 15 signal name' and 'element 0 signal type' to 'element 15 signal type' in the table;
filling element signals contained in each message in the interface control file into an element n signal name field according to element sequence, and filling discrete signals or data in the element n signal type field according to the element signal data type, wherein n is 0 and 1 … … 15;
the 'message name' table contains the complete frame FC-AE-ASM frame information of a certain message name in the signal interface control file.
The data signal table field description shown in fig. 2 illustrates:
the method comprises the steps of establishing a data table, establishing signal names, data formats, data lengths, MSBs, units, most significant bits and least significant bits in the data table, and setting 7 fields:
the signal name is the element signal name in the message name table;
the data formats comprise BNR1, BNR2, BC1 and BC 2;
the "data length" includes 16 bits or 32 bits;
the "MSB" represents the most significant bit of data;
the unit places a unit of the signal corresponding to the signal name;
the most significant bit "and the least significant bit" correspond to the most significant bit and the least significant bit, respectively, of 32-bit (D31-D0) or 16-bit (D15-D0) data.
The "data" table stores all the parsing information about a certain message.
The discrete signal table field description shown in fig. 3 illustrates:
establishing a discrete signal table, wherein the table name is an element signal name with an element type corresponding to a discrete signal, establishing four fields of a name, a digit, a highest bit and a lowest bit in the table, and establishing a value 0 and a value 1Number of bits-1 "and 2Number of bitsA plurality of fields, wherein:
the name fills in a data name contained in the 16-bit discrete signal;
the "number of bits" represents the number of bits occupied by data;
the highest bit and the lowest bit respectively correspond to the highest bit and the lowest bit occupied by the discrete signal data, and the actual meaning of the concrete representation is filled in the corresponding field according to the description of the corresponding meaning of each data numerical value in the interface control file.
The "value 0", "value 1". or.. - "value 2"Number of bits-1 "and 2Number of bitsThe actual meaning information represented by the value is stored under each field.
And establishing a plurality of discrete signal tables according to the discrete signal categories in the interface control file, so that the actual meaning information corresponding to the data can be conveniently searched in data analysis.
By establishing a complete 'message name' table, a 'data' table and a discrete signal table, all message data in the interface control file can be classified and parameterized, and the interface control file is an important reference document for analyzing ASM frame information.
The software flow and working principle of the present invention are explained below:
the data parsing flowchart shown in fig. 4 includes the steps of:
sa) establishing a structure array Element [16], wherein each structure comprises a character string variable representing a signal name of an Element, a character string variable representing a type of the Element, a long integer variable representing a data length of the Element and a long integer variable representing a value of the Element;
sb) reading a start character of the FC-AE-ASM data frame, if the reading is successful, reading a word representing MsgID, and converting the character string represented by the 16 system into integer;
sc) comparing the MsgID with the value of the 'message number' field in the 'message name' table, assigning the character strings of the 'Element 0 signal name' to 'Element 15 signal name' fields to the Element signal names in the arrays Element [0] to Element [15] and assigning the character strings of the 'Element 0 signal type' to 'Element 15 signal type' fields to the Element types in the arrays Element [0] to Element [15] under the condition of the same numerical value;
sd) acquiring a data length according to an element type, comprising the steps of:
sd1) if the Element type in the array Element [ n ] is a discrete signal, the data length in the structure body is 16;
sd2) if the Element type in the array Element [ n ] is data, comparing the Element signal name in the structure with the value of the "Element n signal name" field in the "message name" table, and assigning the value in the "data length" field to the data length of the structure if the values are the same;
where n is 0, 1 … 15.
Se) obtaining discrete signal data values, comprising the steps of:
se1) when the Element type in the Element [ n ] is a discrete signal, entering a corresponding table according to the Element signal name in the structure body, wherein n is 0, 1 … 15;
se2) connecting PayLoad (PayLoad) fields in FC-AE-ASM data frames to form a character string;
se3) according to the values of the fields of 'number of bits', 'highest bit' and 'lowest bit' recorded in the discrete signal table, dividing the character string obtained in step Se2) from high bit to low bit, wherein each divided character string is a character string represented by 16 systems corresponding to the data name represented by the 'name' field in the record;
se4) converting each character string into integer X, and then converting the integer X into a character string form of "value X", so that the value of the "value X" field in the record is the actual meaning of the data corresponding to the data name.
Sf) acquiring data signal data values, comprising the steps of:
sf1) when the Element type in the Element [ n ] is data, entering the data table, wherein n is 0 and 1 … 15;
sf2) comparing the element signal name in the structure body with the value of the 'signal name' field in the table, and obtaining the value of the rest fields in the record when the element signal name in the structure body is the same as the value of the 'signal name' field in the table;
sf3) connecting PayLoad (PayLoad) fields in the FC-AE-ASM data frame to form a character string;
sf4) intercepting character strings with corresponding lengths from high order to low order in the character strings obtained in the step Sf2) according to the value of the 'data length' field in the record;
sf5) converting the character string obtained in the step Sf3) into a 16-system long integer, and calculating an actual numerical value according to the information of the 'data format' field, the 'MSB' field, the 'most significant bit' field and the 'least significant bit' field in the record.
If the 'data format' is BRN, applying a BRN algorithm:
Dhighest order*MSB+DHighest order-1*MSB*2-1+…+DLowest position*MSB*2Lowest order-highest order
If the 'data format' is BC, applying the BC algorithm:
(-1)*Dhighest order*MSB+DHighest order-1*MSB+DHighest order-2*MSB*2-1+…+DLowest position*MSB*2Lowest order-highest order +1
The value obtained by resolving is the actual data value of the message.
And (4) circulating the step Se) and the step Sf), reading all data values of the discrete signals or the data signals, correspondingly searching the actual meanings represented by the data values in the discrete signal table or the data table, and displaying the actual meanings on an interface of a computer or an industrial personal computer, namely finishing the universal analysis of the FC-AE-ASM data.
The foregoing shows and describes the general principles, essential features, and advantages of the invention. It will be understood by those skilled in the art that the present invention is not limited to the embodiments described above, which are merely illustrative of the principles of the invention, but that various changes and modifications may be made without departing from the spirit and scope of the invention, which fall within the scope of the invention as claimed. The scope of the invention is defined by the appended claims and equivalents thereof.
Claims (1)
1. The FC-AE-ASM data general analysis method based on the product interface control file is characterized in that: the method comprises an interface control file database conversion method and a data analysis method, wherein the interface control file database conversion method comprises the following steps:
s1) dividing the data type;
s2) establishing a message name summary table;
s3) establishing a data information table;
s4) establishing a discrete signal table;
the data analysis method comprises the following steps:
sa) establishing a structure array;
sb) reading the MsgID;
sc) comparing the MsgID with the message number field;
sd) acquiring the data length according to the element type;
se) obtaining discrete signal data values;
sf) acquiring a data value of the data signal;
said step S1) dividing all element signals contained in the message in the interface control file into data signals and discrete signals according to the data type, the data signals can be divided into BNR1, BNR2, BC1 and BC2 according to the data format, said BNR1 and BNR2 data types are based on the BNR algorithm
DHighest order*MSB+DHighest order-1*MSB*2-1+…+DLowest position*MSB*2Lowest order-highest order
Solving the obtained data signal type;
the BC1 and BC2 types are applied with BC algorithm
(-1)*DHighest order*MSB+DHighest order-1*MSB+DHighest order-2*MSB*2-1+…+DLowest position*MSB*2Lowest order-highest order +1Solving the obtained data signal type;
the step S2) includes the steps of:
s21) establishing a table named as 'message name' in Microsoft Office Access;
s22) establishing a 'message name' and a 'message number' field in the table;
s23) filling the message name and the message number of each message in the interface control file into the corresponding field;
s24) adding 32 fields in the table from "element 0 signal name" to "element 15 signal name", "element 0 signal type" to "element 15 signal type";
s25) filling element signals contained in each message in the interface control file into the field of "element n signal name" in element sequence, and filling "discrete signal" or "data" in the field of "element n signal type" according to the data type of the element signals, wherein n is 0 and 1 … … 15;
the step S3) of creating a data information table includes the steps of:
s31) establishing a table named as 'data' in Microsoft Office Access;
s32) establishing 7 fields including 'signal name', 'data format', 'data length', 'MSB', 'unit', 'most significant bit' and 'least significant bit' in the table;
s33) filling element signal names with all data types as data in the message name table into a signal name field, and filling information of signal format, data bit length, MSB, unit, highest significant data bit and lowest significant data bit into other corresponding fields in the table according to the description of each signal parameter in the interface control file;
the step S4) includes the steps of:
s41) establishing a table in Microsoft Office Access, and naming by element signal names;
s42) establishing 4 fields including 'name', 'digit', 'lowest bit' and 'highest bit' in the table;
s43) filling the data name, the occupied digit number, the most significant bit and the least significant bit contained in the element signal into the corresponding fields in the table;
s44) adding 2 to the table based on the maximum value among the number of bits occupied by each dataMaximum value of occupied digitA field with the field names "value 0", "value 1" … "value 2Maximum value of occupied digit-1”；
S45) filling the actual meaning of the concrete representation into the corresponding field according to the description of the corresponding meaning of each data value in the interface control file;
s46) establishing a perfect signal name list for each element signal with the type of discrete signal according to the steps S41) to S45);
said step Sa) consists in establishing a structure array Element [16], each structure including a string variable representing a signal name of an Element, a string variable representing a type of an Element, a long integer variable representing a data length of an Element, and a long integer variable representing a value of an Element;
said step Sb) consists in reading the words representing the MsgID of the FC-AE-ASM data frame, converting the string represented in 16-ary into integer;
said step Sc) consists in comparing the MsgID with the value of the "message number" field in the "message name" table, wherein the "message name" and "message number" are established and assigned in step S22), step S23), in case of the same value, assigning the strings of the "Element 0 signal name" to "Element 15 signal name" fields to the Element signal names in said arrays Element [0] to Element [15], and assigning the strings of the "Element 0 signal type" to "Element 15 signal type" fields to the Element types in said arrays Element [0] to Element [15 ];
said step Sd) comprises the steps of:
sd1) if the Element type in the array Element [ n ] is a discrete signal, the data length in the structure body is 16;
sd2) if the Element type in the array Element [ n ] is data, comparing the Element signal name in the structure with the value of the "Element n signal name" field in step S25), and assigning the value in the "data length" field to the data length of the structure if the values are the same, where n is 0, 1 … 15;
the step Se) comprises the following steps:
se1) when the Element type in the Element [ n ] is a discrete signal, entering a corresponding table according to the Element signal name in the structure body, wherein n is 0, 1 … 15;
se2) connecting PayLoad fields in FC-AE-ASM data frames to form a character string;
se3) dividing the character string obtained in the step Se2) from high order to low order according to the value of each field of 'digit', 'highest order' and 'lowest order' recorded in the discrete signal table in the step S4), wherein each divided character string is a character string represented by 16-system corresponding to the data name represented by the 'name' field in the record;
se4) converting each character string into integer X, and then converting the integer X into a character string form of "numerical value X", so that the value of the "numerical value X" field in the record is the actual meaning of the data corresponding to the data name;
the step Sf) comprises the following steps:
sf1), when the Element type in the Element [ n ] is data, entering the data table in step S31), wherein n is 0 and 1 … 15;
sf2) comparing the element signal name in the structure body with the value of the 'signal name' field in the table, and obtaining the value of the rest fields in the record when the element signal name in the structure body is the same as the value of the 'signal name' field in the table;
sf3) connecting PayLoad fields in the FC-AE-ASM data frames to form a character string;
sf4) intercepting character strings with corresponding lengths from high order to low order in the character strings obtained in the step Sf2) according to the value of the 'data length' field in the record;
sf5) converting the character string obtained in the step Sf3) into a 16-system long integer, and calculating an actual numerical value according to the information of the 'data format' field, the 'MSB' field, the 'most significant bit' field and the 'least significant bit' field in the record.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710800697.4A CN107623728B (en) | 2017-09-07 | 2017-09-07 | FC-AE-ASM data universal analysis method based on product interface control file |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710800697.4A CN107623728B (en) | 2017-09-07 | 2017-09-07 | FC-AE-ASM data universal analysis method based on product interface control file |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107623728A CN107623728A (en) | 2018-01-23 |
| CN107623728B true CN107623728B (en) | 2020-07-03 |
Family
ID=61089580
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710800697.4A Active CN107623728B (en) | 2017-09-07 | 2017-09-07 | FC-AE-ASM data universal analysis method based on product interface control file |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107623728B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109688208B (en) * | 2018-12-12 | 2021-12-24 | 中国航空工业集团公司西安航空计算技术研究所 | Data loading method based on FC-AE-ASM message |
| CN111371596B (en) * | 2020-02-25 | 2022-07-05 | 中国航空无线电电子研究所 | Data distribution service software based on FC-AE bus |
| CN111683075B (en) * | 2020-06-01 | 2022-08-12 | 沈阳航盛科技有限责任公司 | Data encryption method based on FC-AE-ASM protocol communication |
| CN112685031A (en) * | 2020-12-31 | 2021-04-20 | 江苏兴邦能源科技有限公司 | Analysis method and system for DBC file of fuel cell test system |
| CN115600323B (en) * | 2022-11-15 | 2023-03-31 | 南京芯传汇电子科技有限公司 | Aviation system simulation method and system, electronic device and readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102523129A (en) * | 2011-12-05 | 2012-06-27 | 西北工业大学 | Universal avionics bus test analysis method and device |
| CN103049414A (en) * | 2012-12-28 | 2013-04-17 | 中国航空工业集团公司第六三一研究所 | Method for converting and transmitting data between FC (fiber channel) bus and CAN (controller area network) bus |
| CN104750758A (en) * | 2013-12-31 | 2015-07-01 | 深圳航天东方红海特卫星有限公司 | Micro satellite test data packet general analysis processing method and system |
| CN106100919A (en) * | 2016-05-27 | 2016-11-09 | 中国航空工业集团公司沈阳飞机设计研究所 | A kind of FC bus testing system and FC bus test method |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4280759B2 (en) * | 2006-07-27 | 2009-06-17 | キヤノン株式会社 | Information processing apparatus and user interface control method |
-
2017
- 2017-09-07 CN CN201710800697.4A patent/CN107623728B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102523129A (en) * | 2011-12-05 | 2012-06-27 | 西北工业大学 | Universal avionics bus test analysis method and device |
| CN103049414A (en) * | 2012-12-28 | 2013-04-17 | 中国航空工业集团公司第六三一研究所 | Method for converting and transmitting data between FC (fiber channel) bus and CAN (controller area network) bus |
| CN104750758A (en) * | 2013-12-31 | 2015-07-01 | 深圳航天东方红海特卫星有限公司 | Micro satellite test data packet general analysis processing method and system |
| CN106100919A (en) * | 2016-05-27 | 2016-11-09 | 中国航空工业集团公司沈阳飞机设计研究所 | A kind of FC bus testing system and FC bus test method |
Non-Patent Citations (1)
| Title |
|---|
| 《基于ICD的通用化航电测试软件研究》;申鹏亮等;《测控技术》;20131130;第32卷(第11期);摘要、第124-126页第1-4小节 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107623728A (en) | 2018-01-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107623728B (en) | FC-AE-ASM data universal analysis method based on product interface control file | |
| CN109325009B (en) | Log analysis method and device | |
| US10387475B2 (en) | System for organizing and fast searching of massive amounts of data | |
| CN113778449A (en) | Avionics interface data adaptation conversion system | |
| CN111339370B (en) | Quick decoding method for airplane QAR data | |
| WO2008156640A2 (en) | A method and apparatus for encoding data | |
| CN116301881B (en) | DBC-based protocol layer code generation method and generation tool | |
| JP2017513252A (en) | Optimized data condenser and method | |
| CN109067649B (en) | Node processing method and device, storage medium and electronic equipment | |
| JP4756003B2 (en) | Data compression / transfer apparatus, data compression / transfer system, data compression / transfer method, and data compression / transfer program | |
| CN108494700B (en) | Cross-link data transmission method and device, computer equipment and storage medium | |
| CN107273423B (en) | Multimedia message data processing method, device and system | |
| CN110955709B (en) | Data processing method and device and electronic equipment | |
| CN113157695A (en) | Data processing method and device, readable medium and electronic equipment | |
| CN111221894A (en) | Configuration-based time sequence database storage method and device and server | |
| CN114499759B (en) | Message generation method and device, electronic equipment and storage medium | |
| CN111416781B (en) | Information processing method and related equipment | |
| CN113364511B (en) | Equilibrium transfer computing method and system based on CCSDS packet telemetry | |
| US10798227B2 (en) | Centralized chromatic pluralizing of internet of things (IOT) communication | |
| CN114726893B (en) | Internet of things application layer access method and system capable of supporting multiple underlying bearer protocols | |
| CN116483375A (en) | File analysis method, device, equipment and medium | |
| CN116467178B (en) | Database detection method, apparatus, electronic device and computer readable medium | |
| CN111897827B (en) | Data updating method and system for data warehouse and electronic equipment | |
| JPH04113797A (en) | Data collection system | |
| US10762294B2 (en) | Universally unique resources with no dictionary management |
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 |