Avionics Data Bus Gateway Layout for Fewer Critical Connections
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing avionics data transmission architectures in vehicles, such as aircraft, are cumbersome and expensive due to the significant number of connections between avionics equipment and computers, particularly when implementing communication protocols like AFDX, and lack a cost-effective and efficient solution for critical data transmission.
Innovation Solution
A data transmission architecture comprising a first fieldbus and a first avionics bus with primary and secondary paths, each having a primary or secondary processing unit, conversion units, and memory, allowing for minimal connections and efficient data transmission through fieldbuses and avionics buses.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a significant number of connections are made between avionics equipment and computer using conventional architectures, then data transmission can be achieved, but the system mass and complexity increase significantly
Solution Approach 1:
The system segments data transmission into two distinct networks: a fieldbus network for non-critical data and an avionics bus network for critical data. This segmentation allows each network to be optimized independently, reducing the need for redundant connections while maintaining safety for critical functions.
Solution Approach 2:
A gateway device acts as an intermediary between the fieldbus network and avionics bus network. It selectively forwards only critical data from the fieldbus to the avionics bus, eliminating the need for direct connections between all fieldbus devices and the computer, thereby reducing system mass.
2Productivity
If communication protocol like AFDX is implemented for all electronic equipment, then data transmission capability is improved, but implementation cost and complexity increase
Solution Approach 1:
Different communication protocols are applied to different parts of the system based on local needs. The fieldbus network uses standard fieldbus protocols for non-critical data, while the avionics bus network uses AFDX for critical data. This localized approach reduces overall complexity while maintaining high performance where needed.
Solution Approach 2:
The gateway serves as a protocol translation intermediary, converting between fieldbus protocols and AFDX. This allows equipment to use simpler, less expensive protocols for non-critical communications while still benefiting from AFDX's high performance for critical data through the gateway.
3Ease of operation
If each piece of equipment is directly connected to the computer, then data access is simplified, but the system has significant mass and complexity
Solution Approach 1:
The gateway acts as an intelligent intermediary that maintains a cached copy of fieldbus data. The computer can access this cached data through the avionics bus without needing direct connections to fieldbus devices, simplifying the connection architecture while maintaining ease of data access.
Solution Approach 2:
The gateway combines multiple functions: it acts as a protocol converter, a data cache, and a selective forwarder. By merging these functions into a single device, the system reduces the number of connections needed while maintaining data access capability.
Data Source
Figure 1~2
Figure 3
Figure 4~6
AI summary
The present invention relates to a data transmission architecture (100) within an avionics system (101) equipping a vehicle (102), the architecture (100) comprising a first fieldbus (A) and a first avionics bus (AVX A). According to the invention, the architecture (100) comprises at least two primary channels (A1, A2, A3, A4), each comprising: ∘ a primary fieldbus interface (IA1, IA2, IA3, IA4) enabling communication between each primary channel (A1, A2, A3, A4) via the first fieldbus (A), the fieldbus interfaces (IA1, IA2, IA3, IA4) being interconnected to the first fieldbus (A), and ∘ a first avionics interface (IAVX1, IAVX2, IAVX3, IAVX4) compatible with the first avionics bus (AVX A).The architecture (100) includes at least one primary computer (5) equipped with a second avionics interface (IAVX5) communicating via the first avionics bus (AVX A) with only one first avionics interface (IAVX1) among the first avionics interfaces (IAVX1, IAVX2, IAVX3, IAVX4).