Study guide
4.3 AFDX / ARINC 664 Part 7 Avionics Full-Duplex Switched Ethernet
EASA Part-66 Module 05 — Digital Techniques / Electronic Instrument Systems Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Numbering Systems
1.1 Numbering Systems: Decimal, Binary, Octal and Hexadecimal 1.2 Binary Arithmetic and Signed Number Representation 1.3 Binary Coded Decimal, Gray Code and Alphanumeric Codes
2 Chapter 2: Data Conversion
2.1 Analogue and Digital Signals, Sampling and Quantisation 2.2 Digital-to-Analogue Converters 2.3 Analogue-to-Digital Converters
3 Chapter 3: ARINC 429 Data Buses
3.1 ARINC 429 Specification, Physical Layer and Topology 3.2 ARINC 429 32-Bit Word Architecture 3.3 ARINC 429 Transmission, Timing and Troubleshooting
4 Chapter 4: Advanced Avionics Data Buses and Aircraft Ethernet
4.1 ARINC 629 Digital Autonomous Terminal Access 4.2 MIL-STD-1553B Military Avionics Data Bus 4.3 AFDX / ARINC 664 Part 7 Avionics Full-Duplex Switched Ethernet
5 Chapter 5: Combinational Logic Gates and Boolean Algebra
5.1 Basic Logic Gates, Truth Tables and Logic Levels 5.2 Boolean Algebra, De Morgan Theorems and Logic Simplification 5.3 Universal Gates and Aircraft Combinational Applications
6 Chapter 6: Sequential Logic, Registers and Logic Diagrams
6.1 Bistable Multivibrators: SR, JK, D and T Flip-Flops 6.2 Shift Registers and Data Storage Elements 6.3 Asynchronous and Synchronous Counters and Logic-Diagram Interpretation
7 Chapter 7: Computer Structure and Microprocessors
7.1 Computer Architecture, Terminology and the Bus System 7.2 Semiconductor Memory Technologies 7.3 Microprocessor Operation, Instruction Cycles and I/O
8 Chapter 8: Integrated Circuits, Multiplexing and Integrated Modular Avionics
8.1 Integrated Circuit Technology, Encoders, Decoders and Scale of Integration 8.2 Multiplexing and Demultiplexing Techniques 8.3 Remote Data Concentrators and Integrated Modular Avionics
9 Chapter 9: Fibre Optics in Aviation
9.1 Physics of Light Transmission and Optical Fibres 9.2 Fibre Cable Types, Signal Degradation and Optical Components 9.3 Fibre Optic Maintenance, Termination, Splicing and Inspection
10 Chapter 10: Electronic Displays and Flight Instrument Layout
10.1 Display Technologies: CRT, LED and LCD 10.2 Electronic Flight Instrument System Architecture 10.3 Cockpit Symbology, Colour Standards and Display Reversion
11 Chapter 11: Electrostatic Sensitive Devices
11.1 Physics of Electrostatic Charge and Device Susceptibility 11.2 ESDS Damage Mechanisms: Catastrophic versus Latent Failures 11.3 ESDS Handling, Storage, Packaging and Workshop Procedures
12 Chapter 12: Software Management Control and Airworthiness
12.1 Aviation Software Classification and RTCA DO-178C / EUROCAE ED-12C 12.2 Software Configuration Management and Part Numbering 12.3 Data Loading, Integrity Verification and Unapproved Changes
13 Chapter 13: Electromagnetic Environment
13.1 Electromagnetic Interference and Compatibility 13.2 High Intensity Radiated Fields and RF Hazards 13.3 Lightning Protection, Bonding and Static Dischargers
14 Chapter 14: Engine Indication, Warning and Monitoring Systems
14.1 Airbus ECAM — Electronic Centralised Aircraft Monitoring 14.2 Boeing EICAS — Engine Indicating and Crew Alerting System 14.3 Comparison, Failure Reversion and Sensor Interfacing
15 Chapter 15: Flight Management, Navigation and Surveillance Systems
15.1 Flight Management System and Control Display Unit 15.2 Inertial Reference, AHRS/ADIRU Context and GPS 15.3 Traffic Collision Avoidance and Terrain Awareness
16 Chapter 16: Fly-By-Wire, BITE, ACARS, Cabin and Information Systems
16.1 Fly-By-Wire Flight Control 16.2 Built-In Test Equipment and Central Maintenance Computers 16.3 ACARS, Cabin Systems and Information Systems
4.3 AFDX / ARINC 664 Part 7 Avionics Full-Duplex Switched Ethernet
Key Takeaways Explain This Topic AI
AFDX is ARINC 664 Part 7, the Module 5 aircraft-network / Ethernet architecture: full-duplex switched Ethernet with deterministic traffic shaping.
A virtual link is a unidirectional path from one End System to one or more destinations; the Bandwidth Allocation Gap is the minimum interval between frames on that link.
Dual independent networks A and B carry redundant frames; the receiving End System performs integrity checking and redundancy management.
Switches police BAG and maximum frame length so a babbling source cannot flood the aircraft network, unlike a shared party-line bus.
Typical civil installations are the Airbus A380, Airbus A350 and Boeing 787 Common Data Network.
Last updated: September 2026
4.3 AFDX / ARINC 664 Part 7 Avionics Full-Duplex Switched Ethernet
The pre-12 June 2024 detailed Appendix I description for 5.4 referred to ARINC, other specifications, and aircraft network / Ethernet ; the current consolidated Appendix I retains only the Data buses heading and levels. A representative civil architecture for that historical study scope is AFDX — Avionics Full-Duplex Switched Ethernet — published as ARINC 664 Part 7 . It is taught here as an aircraft-network example at B1/B2 level 2: not laboratory Ethernet as used in an office, but a deterministic profile of switched Ethernet used as the on-board data network. ExamFinch publishes this material as independent exam preparation; it is not an EASA document and does not claim official approval or partnership.
Typical civil installations you should be able to name are the Airbus A380 , the Airbus A350 , and the Boeing 787 Common Data Network (CDN) . Examination fees remain NAA/Part-147 matters; EASA does not publish a single Module 5 euro price.
Why a switch instead of a shared bus
ARINC 429, ARINC 629 and MIL-STD-1553B are shared-medium buses . All listeners electrically see the same pair (or current loop). Bandwidth is global: one talker occupies the medium. Collisions are prevented by simplex rules (429), unique terminal gaps (629), or a bus controller (1553).
AFDX replaces the party line with a switched fabric :
Each End System (ES) — the avionics computer or remote data concentrator with an AFDX interface — has a dedicated full-duplex link to a switch (or to a pair of switches, one per redundant network).
Full-duplex means the ES can transmit and receive at the same time on that link. There is no CSMA/CD collision domain , because no two End Systems share a half-duplex wire.
The switch is store-and-forward : it receives a frame, checks it, and forwards it only on the ports that the virtual-link table allows.
The physical signalling is Ethernet (typically 100 Mbit/s class 100BASE-TX teaching; some links may be 10 Mbit/s or, on later types, gigabit-class). Treat 100 Mbit/s as the usual Module 5 figure for AFDX links, not 2 Mbit/s (629) or 1 Mbit/s (1553). Cables and connectors are aviation-qualified; you do not randomly fit office CAT-5 into a pressure bulkhead and call it AFDX.
Because the fabric is switched, a technician cannot clip a 429-style high-impedance tap onto the party line and see every frame. Observation is at an End System test connector, a switch monitoring port if the design provides one, or a maintenance network access point described in the AMM. Wrong tool, wrong family.
Virtual links (VL)
A virtual link is a unidirectional logical path from exactly one source End System to one or more destination End Systems . It behaves like a constrained multicast: only the configured source may emit that VL, and only the configured destinations should consume it. Bidirectional exchange uses two VLs , one in each direction — the Ethernet analogue of needing two 429 pairs for two-way traffic, except both VLs can share the same physical switch ports because the switch multiplexes many VLs.
The destination MAC address of an AFDX frame carries the virtual-link identifier . End Systems and switches classify traffic by VL, not by an ARINC 429 octal label and not by a 1553 RT address. IP and UDP ride inside the Ethernet frame as the usual AFDX communications profile; Module 5 does not require you to subnet an office LAN, but it does require you to know that AFDX is a profile of Ethernet , not a new analogue signalling standard.
A VL is not a bidirectional Ethernet collision domain and not a 1553 subaddress. If a question uses those distractors, return to the definition: one source, one or more sinks, unidirectional, identified in the frame, paced by BAG.
Bandwidth Allocation Gap (BAG) and policing
The Bandwidth Allocation Gap is the minimum interval between the start of consecutive frames on one VL . Typical teaching BAG values are powers of two from 1 ms to 128 ms (1, 2, 4, 8, 16, 32, 64, 128 ms). A VL also has a maximum frame length (Lmax) . Together they bound the bandwidth that VL may consume:
Reserved bit rate ≈ (Lmax in bits) / BAG
Worked example. A VL with BAG = 8 ms (0.008 s) and Lmax = 200 bytes = 1600 bits:
1600 bits / 0.008 s = 200 000 bit/s = 200 kbit/s reserved for that VL.
If BAG is halved to 4 ms with the same Lmax, the reservation doubles to 400 kbit/s. If Lmax doubles at the same BAG, the reservation also doubles. The source End System traffic-shapes : it must not emit the next frame on that VL until BAG has expired. The switch polices : if a babbling source violates BAG or Lmax, excess frames are dropped rather than flooding every other computer. That policing is the safety property that ordinary unmanaged office Ethernet does not provide.
Jitter around BAG is bounded by the specification so that receiving partitions in an IMA cabinet can be scheduled. Module 5 will not ask you for a microsecond jitter constant unpublished by EASA; it will ask what BAG is for .
Dual independent networks
AFDX installations use two independent networks, conventionally Network A and Network B : separate cables, separate switches, separate power where the design requires it. An End System typically transmits the same frame on both networks , with a sequence number in the AFDX header. The receiving End System performs integrity checking (discard a corrupted frame) and redundancy management (accept the first valid copy of a sequence number, discard the duplicate that arrives on the partner network).
A single switch failure, loom cut or connector fault can therefore take Network A while Network B continues. That is the Ethernet form of 1553 Bus A/B and 629 dual buses, implemented with two switched fabrics instead of two party lines.
Never improve an installation by bridging A and B together with a commercial Ethernet switch. That destroys independence and can create forwarding loops the aircraft profile never allowed.
A380, A350 and B787 context
The Airbus A380 was the first large civil airliner to use AFDX as the primary avionics network, interconnecting IMA modules, flight-control, cockpit displays and numerous subsystems that would previously have required forests of 429 pairs and 629-style backbones. The A350 continues that Airbus switched-Ethernet architecture. The Boeing 787 Common Data Network is the Boeing teaching example of ARINC 664 / AFDX-style aircraft Ethernet on a twin-aisle type.
429 has not vanished on these aeroplanes. Many sensors and actuators still speak 429 (or analogue) into remote data concentrators; the concentrators then ride the AFDX network. Module 5 therefore treats AFDX as the aircraft network / Ethernet clause, not as a claim that every wire in the aeroplane is Ethernet.
Shared bus versus switched Ethernet — teaching snapshot
- Feature Shared avionics bus (429 / 629 / 1553) AFDX / ARINC 664 P7
- Medium seen by all talkers One pair or current loop Point-to-point links into switches
- Collision control Simplex, TG/SG, or bus controller Full-duplex; no CSMA/CD domain
- Addressing Label, TG identity, or RT address Virtual-link ID in the frame
- Bandwidth sharing Time-multiplex of the whole medium Per-VL BAG and Lmax reservations
- Typical teaching rate 100 kbit/s / 2 Mbit/s / 1 Mbit/s 100 Mbit/s class Ethernet links
- Redundancy Duplicate pairs / dual buses Network A and Network B
- Hangar tap Analyser as extra sink or monitor ES/switch maintenance access, not a party-line clip
- Heritage types 429 ubiquitous; 629 on 777; 1553 military A380, A350, B787 CDN
- Maintenance implications
Configuration of VL tables, BAG values and port maps is loadable software/data. An unapproved change can mis-route or starve a virtual link — which is why Module 5 later treats software management control as a catastrophic-risk subject. On the flight line, confirm that both networks are present, that the End System is powered, that connectors are seated, and that the central maintenance system / BITE names a VL, a switch, or an ES rather than a 429 label. Do not apply 429 twenty-receiver arithmetic to a switch port, and do not apply 1553 response-time windows to Ethernet frames.
Level 2 is this picture: AFDX is ARINC 664 Part 7 aircraft Ethernet; virtual links plus BAG make it deterministic; switches police rather than share a wire; dual networks provide integrity; A380, A350 and 787 are the typical types.