Avionics Bus Architecture With Channel Conversion to Cut Connections
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing avionics data transmission architectures in vehicles are cumbersome and expensive, particularly due to the large number of connections between avionics equipment and computers, and existing communication protocols like AFDX are costly and inefficient for critical equipment.
Innovation Solution
A data transmission architecture comprising a first field bus and a distinct first avionics bus, with primary and secondary channels that convert data frames between the buses, minimizing connections and using a single interface for each computer, allowing for efficient and cost-effective data transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a conventional avionics architecture with multiple connections between each avionics equipment and computer is used, then data transmission reliability is improved, but system mass and complexity increase significantly
Solution Approach 1:
The system is segmented into multiple independent channels (first channel, second channel, third channel, fourth channel), each with its own processing unit and conversion unit. This segmentation allows the system to maintain reliability through redundancy while reducing the complexity of individual connection paths compared to a fully connected architecture.
Solution Approach 2:
Conversion units are introduced as intermediary elements between the field bus and avionics bus. These conversion units translate data frames between different bus protocols, enabling communication between avionics equipment and the computer through a standardized interface while simplifying the overall system architecture.
2Reliability
If AFDX communication protocol is implemented for critical equipment, then data transmission safety is improved, but implementation cost and complexity increase
Solution Approach 1:
The system divides critical data transmission into multiple independent channels (first, second, third, fourth channels), each capable of operating autonomously. This segmentation provides redundancy and safety without requiring full AFDX protocol implementation across all equipment, thereby reducing overall implementation complexity while maintaining safety for critical functions.
Solution Approach 2:
Different channels can be configured with different levels of redundancy and conversion capabilities based on their specific requirements. Critical channels can have full conversion units for safety, while less critical channels can use simpler configurations, optimizing the balance between safety and complexity for each local requirement.
3Productivity
If multiple field interfaces are connected to avionics bus, then data transmission capability is improved, but number of connections and system mass increase
Solution Approach 1:
Multiple field interfaces (first, second, third, fourth field interfaces) are merged into a unified architecture where they all connect to the same avionics bus through standardized conversion units. This merging reduces the total number of connections compared to a fully connected mesh architecture while maintaining the data transmission capability of all interfaces.
Solution Approach 2:
The avionics bus serves as a universal communication medium that can carry data from multiple different field interfaces simultaneously. The conversion units provide multi-functionality by handling protocol translation for different bus types, allowing a single avionics bus to replace multiple dedicated connections.
Data Source
AI summary
An architecture for transmitting data within an avionics system fitted to a vehicle, the architecture comprising a first field bus and a first avionics bus. According to the invention, the architecture comprises at least two primary channels each comprising: a primary field interface enabling communication between each primary channel via the first field bus, the field interfaces being interconnected with the first field bus; and a first avionics interface compatible with the first avionics bus. The architecture comprises at least one primary computer provided with a second avionics interface in communication via the first avionics bus with only one first avionics interface among the first avionics interfaces.