RoutledgeHandbooks 9781482207330 Chapter46 2

This article was downloaded by: 10.3.97.
143
On: 03 Oct 2023
Access details: subscription number
Publisher: CRC Press
Informa Ltd Registered in England and Wales Registered Number: 1072954 Registered office: 5 Howick Place, London SW1P 1WG, UK
Industrial Communication Technology Handbook
Richard Zurawski
ARINC 629
Publication details
https://www.routledgehandbooks.com/doi/10.1201/b17365-55
Michael Paulitsch
Published online on: 26 Aug 2014
How to cite :- Michael Paulitsch. 26 Aug 2014, ARINC 629 from: Industrial Communication
Technology Handbook CRC Press
Accessed on: 03 Oct 2023
https://www.routledgehandbooks.com/doi/10.1201/b17365-55
PLEASE SCROLL DOWN FOR DOCUMENT
Full terms and conditions of use: https://www.routledgehandbooks.com/legal-notices/terms
This Document PDF may be used for research, teaching and private study purposes. Any substantial or systematic reproductions,
re-distribution, re-selling, loan or sub-licensing, systematic supply or distribution in any form to anyone is expressly forbidden.
The publisher does not give any warranty express or implied or make any representation that the contents will be complete or
accurate or up to date. The publisher shall not be liable for an loss, actions, claims, proceedings, demand or costs or damages
whatsoever or howsoever caused arising directly or indirectly in connection with or arising out of the use of this material.
46
Downloaded By: 10.3.97.143 At: 20:36 03 Oct 2023; For: 9781482207330, chapter46, 10.1201/b17365-55
ARINC 629
46.1 Physical Layer...................................................................................46-1
Requirements for Physical Layer • Physical Layer
Entities • Physical Layer Signaling
46.2 Data Link Layer................................................................................46-4
Message Format • Open Systems Interconnection OSI-Compatible
Format • ARINC 629 Non-OSI Data Transfer
46.3 Medium Access Layer.....................................................................46-7
Basic Protocol • Combined Protocol • Exceptions •
Comparison and Summary
46.4 Robustness and Fault Tolerance Features..................................46-15
Receive Data Monitoring • Transmit Data Monitoring •
Bus Protocol Monitoring • Protocol Parameter Monitoring
Michael Paulitsch 46.5 ARINC 629 in Boeing 777............................................................46-16
Airbus Group Innovations References...................................................................................................46-19
In the late 1980s, there was a push toward integration of multiple functions on a common computing
and I/O platform, also referred to as integrated modular avionics (IMA). Combined with this push was
a trend to reduce wiring and integrate formerly dedicated buses into system-level communication buses.
The advantages are decreased size, cost, and weight; increased reliability; less-frequent maintenance; and
more flexibility. The ARINC 629 communication network was the answer in aerospace to the request of
integrated system-level buses. The predecessor ARINC 429 [3] had a single sender and multiple receiver
topological and logical approach, and ARINC 629 extends the capabilities of the network to support a
multiple-sender, multiple-receiver architecture while guaranteeing timely communication. And all this
in an environment where high reliability, high availability, and high integrity are required to ensure
safety of an aircraft. In addition, ARINC 629 uses current coupling for an electrical physical connection
avoiding error-prone physical connections. ARINC 629 is a time division multiplex system. It includes
multiple transmitters with broadcast-type, autonomous terminal access.
46.1 Physical Layer

ARINC 629 physical layer specifies the functional, electrical/optical, and mechanical characteristics
of the physical layer entities. The physical layer entities and media in conjunction with the terminal
controller form a complete communication path. ARINC 629 supports three different physical entity
types as part of its physical layers: a current mode bus, a voltage mode bus, and a fiber-optic mode bus.
ARINC 629 deploys 2 Mbit/s serial data transmission rate specified for twisted pair conductors.
The standard also supports the use of fiber optics. Within each line-replaceable unit (LRU), a single
ARINC 629 terminal and the main computational component interact via shared memory. To rein-
force the approach of collision avoidance adopted at the data link level, multiple timers and redundant
circuitry are employed within each terminal to prevent single hardware faults causing multiple terminals
46-1
© 2015 by Taylor & Francis Group, LLC

46-2 Avionics and Aerospace
LRU/LRM/component
OSI LAN perspective perspective
LLC Subsystem
ARINC 629 Terminal ARINC 629

MAC
data-link controller terminal
PLS SIM
Media-
ARINC 629
AUI specific
physical layers
components
PMA
MDI
Coupler
Medium
Figure 46.1 Scope of ARINC 629 physical layers. LLC, link layer control; MAC, medium access control;
PLS, physical layer signaling; AUI, attachment unit interface; PMA, physical medium attachment; MDI, media-
dependent interface. (From Airlines Electronic Engineering Committee, Multi-transmitter data bus—Technical
description—ARINC specification 629P1-5, Standard 629P1-5, Aeronautical Radio, Inc (ARINC), Annapolis, MD,
March 31, 1999.)
to transmit simultaneously. At the physical layer, mechanisms and signals support higher-level data link-
level protocols. The maximum number of terminals permissible on the bus is 120. Figure 46.1 illustrates
the scope of the physical layer specifications and the mapping of the logical communication layers onto
hardware. In the following, we describe the physical layer requirements, entities, and interface essentials
for higher layers.
46.1.1 Requirements for Physical Layer

The ARINC 629 system requirements that pertain to the physical layer are as follows [2]:
1. The serial transmission rate should be 2.0 Mbit/s with an accuracy of ±0.01%.
2. The bit error rate should not exceed 1 bit in 108 bits. This error rate includes both detected and
undetected errors.
3. Each terminal should be capable of receiving the transmissions of every other terminal on
the network.
4. The network should support the reliability goals for flight-critical functions, and shortening and
opening of a stub at any terminal output should not cause any adverse effect on the bus. A proba-
bility of an undetected single point of failure of the terminal affecting the bus should be extremely
unlikely. Any terminal should provide an isolation barrier between subsystem and bus, which
means that any failure of the subsystem only affects data validity.
5. The installation should provide flexibility in a manner that physical reconfiguration of the network
(addition or removal of terminals) should still satisfy the network reliability requirements.
6. The network should meet the RTCA DO-160 [7] standard pertinent to the specific application.
7. The bus medium should enable a receive portion of the transmitting terminal controller to discern
simultaneous transmission by other terminal controllers for collision recovery purposes.
8. The bus medium should also enable a receive portion of the transmitting terminal controller to
independently monitor the transmitted data directly from the bus for wraparound transmission
monitoring.

ARINC 629 46-3
9. The bus medium should enable detection of bus quiet (BQ) and bus active (BA) for higher protocol
layers and provide signals indicating these states. BQ indicates no sending activity on the bus.
BA means a signal is present.
46.1.2 Physical Layer Entities

ARINC 629 specifies three physical layer entity (PLE) types [2]:
Current mode bus: The current mode bus uses the principle of current induction to induce current
pulses (so-called doublets) in the conductors of an unshielded twisted pair cable. The advantage
of current induction is the nonintrusive coupling for linking terminals to the medium. That is,
with current induction, neither cables have to be spliced nor tap connectors are required.
Voltage mode bus: The voltage mode bus implementation is characterized coupling via breaking
the cable and insertion of T couplers or splicing of cable conductors for a (typically) shielded
cable. Conduction is based on application of voltage.
Fiber-optic mode bus: The optical mode bus implementation utilizes electro-optic transceivers to
inject pulses of light into an optical fiber either via use of optical coupler or tap and splicing
of connectors.
Current mode and fiber-optic bus are defined in detail in the ARINC 629 specification, while a volt-
age mode bus is not specified.
46.1.2.1 Current Mode Bus

The current mode bus allows up to 120 terminals and supports a physical bus lengths of up to 100 m and
stub lengths of up to 40 m.
The serial interface module (SIM) should convert Manchester biphase logic transition transmitter by
the terminal controller into analog signals called doublets. These doublets are induced via the stub cable
into the bus via the current mode coupler (CMC). Similarly, on the receiving side, signals on the bus
are flowing from the bus via the CMC and the stub back to the terminal controller. The SIM provides
power to the CMC by conditioning its supply voltage of ±15 V. The SIM also performs fault checking
(monitoring) on itself and performs built-in self-test (BIST) when commanded to do so.
Tables 46.1 and 46.2 present an overview of the stub and bus cable requirements. Figure 46.13 also
shows a CMC deployed.
46.1.2.2 Fiber-Optic Mode Bus

The optical bus is characterized by passing optical signals through a passive fiber-optic network of either
topology (star, linear, or other). Fiber optics has the advantage of immunity to lightning and electro-
magnetic interference. It also uses passive coupling techniques. Table 46.3 provides an overview of the
fiber-optic common characteristics. Details on the transmitter, receiver, and transmission media char-
acteristics can be found in [2].
Table 46.1 Stub Cable Requirements
Description Parameter Value
Insulation rating 600 V RMS
Attenuation <1.8 dB (CMC to SIM/pair) (F = 6 MHz)
Velocity of propagation >0.75 × c (where c = 2.9979 × 108 m/s)
DC resistance <1 Ω (CMC to SIM/pair)
Source: Airlines Electronic Engineering Committee, Multi-
transmitter data bus—Technical description—ARINC specification
629P1-5, Standard 629P1-5, Aeronautical Radio, Inc (ARINC),
Annapolis, MD, March 31, 1999.

Table 46.2 Current Mode Cable Requirements

Description Nonshielded Cable Parameter Value Shielded Cable Parameter Value
Insulation rating 600 V RMS 600 V RMS
Characteristic impedance ZO = 130 Ω ± 2% ZO = 130 Ω ± 2%
(per twisted pair)
Attenuation <2.8 dB/100 m (F = 6 MHz) <2.6 dB/100 m (F = 6 MHz)

Velocity of propagation >0.78 × c (where c = 2.9979 × 108 m/s) >0.70 × c (where c = 2.9979 × 108 m/s)
Conductor size #20 American wire gauge (AWG) #20 AWG stranded
stranded
Twists 6 ± 0.7 transpositions/ft 6 ± 0.7 transpositions/ft
Source: Airlines Electronic Engineering Committee, Multi-transmitter data bus—Technical description—
ARINC specification 629P1-5, Standard 629P1-5, Aeronautical Radio, Inc (ARINC), Annapolis, MD,
March 31, 1999.
Table 46.3 Common Characteristics of Fiber-Optic Mode Bus

Description Value Unit
Data rate 2% ± 0.01% Mbit/s
Nominal bit rate 500 ± 0.050 ns
Nominal pulse width 62.5 ns
Minimum intermessage gap 3.6875 μs
Upper peak wavelength limit 900 nm
Lower peak wavelength limit 770 nm
Maximum spectral width 80 nm
Source: Airlines Electronic Engineering Committee, Multi-transmitter
data bus—Technical description—ARINC specification 629P1-5,
Standard 629P1-5, Aeronautical Radio, Inc (ARINC), Annapolis, MD,
March 31, 1999.
46.1.3 Physical Layer Signaling

Physical layer signaling specifies the interface between PLE and higher communication layers (or the
terminal controller and the SIM when speaking of component perspectives).
The medium access control (MAC) sublayer bus access protocols (see Section 46.3) are reliant on the
indication of bus activity from the physical layer for operation. The presence of a signal on the bus is
called bus active, while a period of no activity is called bus quiet. Messages are communicated in serial
digital pulse code modulation by means of complementary TTL compatible lines, TXO/TXN, and RXI/
RXN. The data code used is Manchester II biphase, where a logic one is encoded 1/0 (a half bit time high
followed by a half bit time low). A logic zero is encoded 0/1 (a half bit time low followed by a half bit time
high). Transitions occur always at the midpoint of each bit time.
MAC sublayer messages are comprised of word strings. A message consists of 1–31 word strings,
which are described in detail in the next section. The physical layer should ensure that no gaps are
p
resent between successive bit-level encoded words in a word string.
46.2 Data Link Layer

This and the next section describe the two main functions associated with the ARINC 629 data link
control procedure to be performed in the medium access sublayer: the media access management and
data encapsulation (framing, addressing, and error detection).

ARINC 629 46-5
3 Word wordstring 4 Word wordstring
4
Label Data Data bit Label Data Data Data
½ bit
presync
3 bits 4 bits
pulse 12 bits label
1 bit
HI LO sync label priority

Ext (CID)
3 bits 1 bit
LO-HI sync 16 bits data parity
Figure 46.2 Example message with two word strings.
46.2.1 Message Format

An ARINC 629 message has variable length up to 31 word strings separated by a 4-bit delimiter. Each
word string is made up of one label and several data words. Bus time is decomposed into bus cycles. Each
terminal sends one message per bus cycle.
In detail, label words start with a Hi–Lo sync waveform (3 bit times) followed by the channel identi-
fication (CID, word bits WB4–WB7), then the label, and finally the parity bit (WB20). Data words start
with the Lo–Hi sync waveform (3 bit times) followed by the sign bit (WB4), then the 15-bit data field
(word bits WB5–WB19) with the MSB first, and finally the parity bit (WB20).
Data messages consist of word strings with a gap of 4 bit times between word strings and a 3-bit-time
sync waveform to initialize each label or data word. The first label word of a message should be preceded
by a half-bit-time presync pulse. The beginning of the first transmitted sync waveform following this
4-bit-time gap signifies the beginning of the new word string as indicated in Figure 46.2.
The last bit of each label and data word is a parity bit encoded such that word parity is rendered odd.
46.2.2 Open Systems Interconnection (OSI)-Compatible Format

ARINC 629 supports OSI and non-OSI-compatible formats. Figure 46.3 presents the IEEE Std 802.2
compatible logical link control MAC format. Each MAC should contain two address fields: the source
Label word System status word Data word #1 Data word #2 Data word #3 Data word #n
CID Source address

15 12 11 0 System
status
word
15 11
Attri-
butes
Bit attribute 10 8 Word
10 Spare count
9 Protocol (1 = OSI) 7 0
8 Spare Destination
CID
address
15 12 11 0
LLC protocol data unit
DSAP/SSAP control info
LLC protocol data unit
DSAP/SSAP control info
Figure 46.3 OSI message format. LLC, logical link control; CID, channel identification; DSAP, destination
service access point; SSAP, source service access point. (From Airlines Electronic Engineering Committee, Multi-
transmitter data bus—Technical description—ARINC specification 629P1-5, Standard 629P1-5, Aeronautical
Radio, Inc (ARINC), Annapolis, MD, March 31, 1999.)

address field and the destination address field. The source address field identifies the sending terminal.
The destination address field specifies the terminal(s) intended recipients. An address can either be an
individual or a group address.
The system status word (SSW) describes the systems health and operating environment. The five
high-order bits of the SSW identify a system operating with a partial malfunction or in a temporary
state that causes the systems data to transmit predefined valid values (i.e., stale data).
The protocol indication field (attribute field, bit number 9) indicates whether the frame is an OSI-
compatible frame. The word count field indicates the length of the message. The CRC field contains a
frame check sequence based on a 16-bit cyclic redundancy check value.
Receivers of all terminals not transmitting data monitor all labels being transmitted on the bus. For
all labels of interest, the receiver uses the memory mapping information associated with that label to
store data directly in the user system’s memory. Details of mapping into memory and configuration
formats can be found in [2].
46.2.3 ARINC 629 Non-OSI Data Transfer

Non-OSI data transfer supports broadcast and directed data. Frames are defined at least 1 digital word
containing 20 bits, but only 16 are available to the user, as described in Section 46.2.1. There are multiple
predefined word formats for different applications, which are exemplary specified in [2].
Two events are important during normal operation of periodic transmissions on the bus. These are
the minor frame and major frame. Minor frame is a terminal-oriented or bus-oriented event and refers
to a specific period on the bus (not to a frame in the sense of a network frame that is physically send
or word strings as it is called in ARINC 629). The beginning and end of terminals’ minor frame are
linked to the transmission of a particular terminal. A bus minor frame is identical to the minor frame
of the terminal with the slowest clock for basic protocol (BP) or of the lead terminal in combined
protocol (CP), the first terminal to transmit following the longest quiet time [2]. A major frame is a
series of unique minor frames as is also signaled. Minor and major frames are related to aircraft-level
control loops.
A non-OSI broadcast message includes the following elements: label, CID, word count (if neces-
sary), data status, protocol indication, and information. Figure 46.4 presents the non-OSI broadcast
message format.
CID Source address

15 12 11 0 System
status
word
15 11
Attri-
Bit attribute butes
10 Spare 10 8
9 Protocol (0 = non-OSI) Word
8 Spare count
7 0
Information CRC
Information [FSW] [UPCOUNT, PVW] data
Figure 46.4 Non-OSI message broadcast format. LLC, logical link control; CID, channel identification;
FSW, function status word; PVW, parameter validity word. (From Airlines Electronic Engineering Committee,
Multi-transmitter data bus—Technical description—ARINC specification 629P1-5, Standard 629P1-5, Aeronautical

ARINC 629 46-7
CID Source address

15 12 11 0 System
status
word
15 11
Attri-
Bit attribute butes
10 Spare 10 8
9 Protocol (0 = non-OSI) Word
8 Spare count
7 0
Destination
CID
address
15 12 11 0
Information
Information CRC
Information [FSW][UPCOUNT, PVW] data
Figure 46.5 Non-OSI directed message format. LLC, logical link control; CID, channel identification;
FSW, function status word; PVW, parameter validity word. (From Airlines Electronic Engineering Committee,
Multi-transmitter data bus—Technical description—ARINC specification 629P1-5, Standard 629P1-5, Aeronautical
Data messages are composed of word string comprising the label word in the first word followed by
16 data bits in the following words. Each position in a word string contains specific data elements that
are specified for an aircraft. These are also sometimes called parameters. Figure 46.5 presents the non-
OSI directed message format.
More detailed description of the syntax of non-OSI messages like labels, channel identifiers and its use,
data status, word count, protocol indication, information, and frame check sequence can be found in [2].
46.3 Medium Access Layer

The ARINC medium access layer is a carrier-sense multiple access/collision avoidance (CSMA/CA)
scheme. Bus access control is distributed among all participating terminals, each of which autono-
mously determines its transmission sequence. Each terminal achieves access by the use of bus access
timers combined status information about the state of the medium. There are two implementations of
ARINC 629, which essentially differ at the MAC layer:
1. Basic mode protocol (BP)

2. Combined mode protocol (CP)
The two protocols differ in how stations access the physical medium and especially in the way they
handle aperiodic data.
46.3.1 Basic Protocol

The BP is a dual-mode protocol in which the bus can operate in either the periodic mode or the aperiodic
mode. The bus system design, that is, factors like the loading factor of the bus, determines which of two
modes that the bus will operate in. Buses designed to operate in the periodic mode will automatically
transition to the aperiodic mode when they are overloaded. The description in this section is a summary
of [2]. It is also slightly more detailed than the description of the CP as it explains also more details about
the background and rationale of timers.

46.3.1.1 Timers for Operation

The three timers that are used to access the physical medium are (1) the transmit interval (TI), (2) the
synchronization gap (SG), and (3) the terminal gap (TG). In more detail,
1. The TI is identical for all terminals on the same bus. It is the longest time of the three timers
and can range from 0.5 to 64.0 ms. It starts every time the terminal starts transmitting. Once
a terminal has transmitted, it should wait the length of time specified by the TI before it can
transmit again. Hence, it is equal to the minimum possible bus cycle time.
For a normally periodic bus, the selected value should be such that data are available on
the bus at a minimum update rate required of the user system. Hence, TI is a transmission
deferral mechanism in periodic mode.
Lower TI decreases efficiency of the bus due to increasing bus protocol overhead. For aperiodic
mode operation, TI should be relatively short, that is, as short as to ensure all users have the
opportunity to transmit as often as possible.
2. The SG is also identical for all terminals on the same bus. SG is the second longest timer. The value
of SG is selected from the TG-relative binary values (BVs) of 16, 32, 64, and 127 (corresponding
to 17.7, 33.7, 65.7, and 127.7 μs for the bit rate of 2 MHz [2,4]). The SG time is effectively dead time
on the bus and should be selected to be as small as possible. However, the selection of SG should
allow for the use of additional terminals on the bus.
SG ensures that all terminals are given access and are chosen to be greater than the maximum
TG. It starts every time BQ is sensed and may be reset before it has expired if bus activity is
sensed. It is restarted the next time the terminal starts to transmit. Allegorically speaking,
SG is used to implement a waiting room protocol in aperiodic mode [6]. All stations enter
a waiting room by waiting the time of length SG before being serviced in the order of a
station’s TG with lower TG values first. Hence, for aperiodic mode, SG provides the deferral
mechanism for sending.
3. The TG is unique for each terminal on the same bus. It is necessary for each terminal on the bus to
have a unique number (N) from 1 to 125 starting at the lowest value. The terminal BV is set to the
binary equivalent of the terminal number plus one (i.e., BV10 = N + 1 [2]). The specific TG values
for the bit rate of 2 MHz are between 3.7 and 127.7 μs. The TG timer is reset by the presence of a
carrier. TG starts only after SG has expired and the bus is quiet. Unlike the SG, TG is reset if bus
activity is sensed. As a consequence, TG and SG should not overlap in time but run consecutively.
Also, the value of 11111112 or 12710 is not used in order that SG be greater than TG.
Figure 46.6 shows the media access flow chart of aperiodic and periodic transmission.
A typical timing diagram for a very simple bus with three terminals operating in periodic mode is
shown in Figure 46.7 (attention: diagram is not to scale). The figure shows the terminals in a steady state
(some time after start-up and initialization).
The order in which terminals achieve bus access is the same for all bus cycles and is determined by
the initialization sequence (if there was no aperiodic mode in between). It does not necessarily (but
can) equate to the relative durations of the terminals’ TG timers. If the sum of all the TGs, transmission
times, and SG is less than TI, then the bus cycle time remains fixed and equal to TI.
If the sum of all the TGs, transmission times, and SG is greater than TI, then the system switches to
operation in aperiodic mode as shown in Figure 46.8. For every bus cycle, the terminals transmit in the
order of their increasing TG durations. Here, TG2 < TG1 < TG3. Each bus cycle consists of a sequence
of transmissions separated by the various TG delays followed by an SG delay that provides synchroni-
zation. Referring to the explanation of the aforementioned waiting room protocol, Figure 46.8 shows
that SG opens the waiting room door and then each terminal is served in the order of increasing
TG values.

ARINC 629 46-9
Start if BQ Start if transmit go-ahead

Start
Reset if (BA and

SG not elapsed) Count TI
on transmit go-ahead
Count SG
Start if BQ and Yes Was a clash

Reset
SG elapsed detected?
if BA
Count TG
Count TG
No
TG elapsed TI + TG elapsed TI elapsed
Conditional wait for TI

If both TG and TI elapsed
Transmit go-ahead
Figure 46.6 BP—media access flow chart (not indicating monitoring). BA, bus active; BQ, bus quiet. (From
Airlines Electronic Engineering Committee, Multi-transmitter data bus—Technical description—ARINC specifi-
cation 629P1-5, Standard 629P1-5, Aeronautical Radio, Inc (ARINC), Annapolis, MD, March 31, 1999.)
Bus cycle
Go ahead Go ahead
TI TI TI
message SG TG1 message

Station 1 Go ahead Go ahead
TI TI TI
TG2 message SG TG2 TG2 message
Station 2 Go ahead Go ahead

TI TI TI
TG3 message SG TG3 TG3 message

Station 3
Figure 46.7 BP—periodic mode.
46.3.1.2 Bus Cycle Start and Initialization

The initialization phase of bus operation may be relatively uncontrolled depending on the sequence
in which local clocks are initialized across multiple terminals. However, as a result of synchro-
nization mechanisms, bus operation will normally settle down to some steady state after a very
short time.

Bus cycle
Go ahead TI Go ahead TI
TG1 message SG TG1 message SG
Station 1
message SG TG2 message SG
Station 2
TG3 message SG TG3 message SG
Station 3
Figure 46.8 BP—aperiodic mode.
46.3.2 Combined Protocol
The CP allows sending of periodic and multiple different quality levels of aperiodic messages. The opera-
tions of the CP are quite complex. It uses five timers in each station. The combination of the five timers
and associated state machines build the kernel of the system network behavior. In the following, we
base our description of the ARINC 629 CP closely on an excellent description from Gallon and others
provided in [5].
46.3.2.1 Bus Cycle

Media access to the bus is cyclic. A bus cycle is started by one of the ARINC 629 stations—also called
the leader in the following. Each bus cycle is divided into four durations also called areas or levels.
The first three levels are for periodic traffic (level l), urgent aperiodic traffic (level 2), and nonurgent
aperiodic traffic (level 3). Level 3 can be divided into two further sublevels: level 3 backlog, for nonur-
gent aperiodic traffic, which could not be sent in the previous bus cycle, and level 3 new for new nonurgent
a periodic traffic. Level 1 traffic has priority and its bus load contribution is evaluated first. Worst-case
estimates can be obtained by summing the maximum bus loads. Level 1 traffic does not change sig-
nificantly between different flight phases. Level 2 and level 3 traffics depend on flight phases. Level 2
traffic is of low periodicity or aperiodic in nature. Level 3 traffic is predominantly aperiodic in nature
with some very low-rate periodic data (long messages). Worst-case assessment is not straightforward.
Each station can transmit at most one message per level. Sending of a message is mandatory at level 1,
but optional at all other levels. The leader station starts the cycle by sending its first periodic message (i.e.,
beginning of level 1). The beginning of this first periodic message is the signal for other (nonleading)
stations of the beginning of the new bus cycle (this signal is called concatenation event). The fourth area
of the bus cycle allows the synchronization of the stations at the end of a cycle in order to define a leader
for the new bus cycle (the definition is made by election on local information).
46.3.2.2 Timers for Operation

In the CP, there are two types of timers:
• Type 1 timers—involving three timers—allow the stations to deal with the bus cycle. The behavior
of these timers is bound to the transmission activity on the bus as the information BA and BQ are
fundamental for the operation of the bus:
• The timer TG controls the access to the bus at levels 1, 2, and 3. Each station has a dif-
ferent value for TG; we have the following relation: ∀i, j, TGj > TGi + 2τ, with τ being the

ARINC 629 46-11
CE 1 Bus cycle
TI
AT
L1
TGi TGj ASG L2 ASG L3b ASG L3n PSG

h i j
TG elapsed = AT elapsed = no more TI elapsed =

beginning of ASG elapsed = aperiodic transmissions end of cycle
transmission new level
PSG elapsed = no more
Leader’s Station j’s
transmissions in this cycle
periodic periodic
submission submission
Figure 46.9 Role of different timers in CP. (From Gallon, L. et al., Modelling and analysis of the ARINC speci-
fication 629 CP MAC layer protocol, in Proceedings of IEEE International Workshop on Factory Communication
Systems, pp. 91–100, Barcelona, Spain, 1997.)
maximum propagation time on the bus. TG allows specifying a static priority scheme and
then implementing a collision avoidance mechanism. As soon as we have the signal BA
(beginning of a bus activity), the timer TG is reset, and as soon as we have the signal BQ
(end of a bus activity), the timer TG is running. The timer TG is also reset when the station
enters a new level of a bus cycle (i.e., when aperiodic synchronization gap [ASG] becomes
elapsed). When the timer TG expires, the station can send a message on the bus (if it has
not already sent a message at this level).
• The timer ASG controls the level changes. Each station has the same value for ASG and ASG >
TGmax. As for the timer TG, as soon as a station gets the signal BA (BQ), the timer ASG is reset
(running). At the time when the ASG becomes elapsed, the station changes level.
• The timer periodic synchronization gap (PSG) allows all the stations to synchronize them-
selves at the end of the bus cycle. Each station has the same value for PSG (PSG = 5 ASG).
As for the timers TG and ASG, as soon as a station gets the signal BA (BQ), the timer PSG
is reset (running). When PSG becomes elapsed, there will be no more transmission in this
bus cycle and a station enters a new bus cycle.
• Type 2 timers concern two timers that have the same value in all the stations and which specify
the bounds of the bus cycle (i.e., constraints imposed by the stations to the different traffics):
• Timer TI defines the periodicity of the cycle. It is started at the beginning of the periodic
transmission and elapses either by a normal runoff or by a CE interruption (beginning of
a new bus cycle). In a permanent normal behavior, the TI of the leader goes to its normal
end and then is restarted immediately (new bus cycle). It is then the leader that imposes
the periodicity of the cycle (TI).
• Timer AT (aperiodic access time-out) defines the last instant in a bus cycle for an aperiodic
transmission start (i.e., AT = TI − (PSG + ASG + MAL), which MAL being the maximum
allowed length for a message).
Figure 46.9 summarizes the definition and the use of the timers.
46.3.2.3 Bus Cycle Start and Initialization
The station that is the leader in one bus cycle normally (i.e., no bus overload, bus initialization, or transient
disturbance) stays the leader for the next cycle. This is because the following three local conditions hold
at a leader, which are the same the conditions a station satisfies to assert itself as a leader: (1) PSG elapsed
(there will be no more transmission in the bus cycle in progress), (2) TI elapsed (the period has finished),
and (3) TG elapsed (the station has the right to access to the bus). Normally, the first station powered up

will become the leader (considering differences between power-up of stations are greater than differences
in TG), but details on the leader election during initialization as described in the next paragraph.
During initialization, which is a transient behavior from the station being switched on to the intro-
duction of the station in a bus cycle (i.e., emitting the first periodic message [at level l]), a station starts
off with PSG and wants to get the information that the message transmission of the stations already
running is ended in the cycle in progress (PSG elapsed). Next, the station starts TI and tries to intro-
duce itself on the bus as nonleader (waiting for a cycle end [CE] and, then, if CE is received, it will start
introducing itself into level 1). In the case of an empty bus, there will not be a CE and then TI will elapse.
When TI elapses, TG is restarted and at the end of TG (TG elapsed), the station becomes the leader and
starts TI and its periodic transmission in level 1. Using TG when TI becomes elapsed allows to control
the phenomenon of collision, which can occur at the initialization if several stations want to join regular
bus operation simultaneously (remember the stations have different TG). But we cannot avoid all the
collisions with this mechanism (which depend on the dephasing between the stations at the switch on,
which can compensate the difference between the TGs of the stations). This protocol avoids collisions
in the permanent state, but stations can exhibit collisions in transient phases like the initialization.
Whenever a collision occurs, there is a signal Bus Clash (BC), which comes from the physical layer, sent
to the MAC entity. The station cannot transmit any more message in this bus cycle, and a reinitialization
procedure at the end of the bus cycle (i.e., after the condition PSG elapsed) is started.
46.3.3 Exceptions
Exceptions can be caused in bus overload situations (the duration of level 1 is greater than TI because
of two long messages), timer drifts, ghost transmissions (e.g., the lightning-induced noise signals), and
failure of a station, which participate to the bus cycle (deaf station and/or dumb station). ARINC 629
implementations deploy significant monitoring mechanisms, but no monitoring is perfect.
46.3.3.1 Architecture of Link Layer

Reference [5] also provides a good overview of the architecture of the link entity, which is represented
in Figure 46.10. The MAC is composed of two main modules: (1) the transmitter scheduler and (2) the
transmitter. The transmitter scheduler is the core of the implementation of the CSMA/CA mechanism
and the cycle bus concept. The signals BA, BQ, and BC are basic signals. The transmitter scheduler
implements the mechanisms for the following bus states:
• Initialization of a station on the bus (start-up and reinitialization of the station on the bus after
power-up)
• Determining of the leader or nonleader of a station
• Commanding the transmitter to emit messages in levels 1, 2, and 3 of the bus cycle (these messages
contain the data from the logical link control)
The architecture of the transmitter scheduler is shown in Figure 46.11, which depicts the transmitter
scheduler architecture, states, and dependencies with its two main modules: the timer module and the
transmitter control module. The timer module comprises the timers TG, ASG, PSG, TI, and AT. The
transmitter control module includes the submodules’ initialization; attribute (leader/nonleader) deter-
mination, levels 1, 2, and 3, and a submodule that memorizes the conditions (elapsed, not elapsed)
of the timers; and the BC occurrences. Figure 46.11 also shows essential interactions for the behavior
of the transmitter scheduler (signals from the physical layer, signals between the timers and the
transmitter control).
46.3.3.2 Example Scenario
Figure 46.12 sketches a stable bus cycle with only three stations i, j, and k. Station i is the leader but it
does not have the smallest TG. Station j has the smallest TG. Station i transmits in levels 1 and 2; station j

ARINC 629 46-13
Logical link control

Transmitter
scheduler Transmitter
Medium access control
Bus quiet (BQ)

Bus active (BA) Messages
Bus clash (BC)
Physical layer
Figure 46.10 MAC architecture of CP. (From Gallon, L. et al., Modelling and analysis of the ARINC speci-
fication 629 CP MAC layer protocol, in Proceedings of IEEE International Workshop on Factory Communication
Systems, pp. 91–100, Barcelona, Spain, 1997.)
Timers Transmitter control
Reset TG TG
Record Initialization (station switch on,
TG elapsed after BC)
TG elapsed, TG not elapsed TG
Reset ASG Attribute (leader/nonleader)deter-

ASG Record ASG
ASG elapsed mination (permanent behavior)
ASG elapsed, ASG not elapsed
Reset PSG
Record PSG
PSG PSG L1 level
PSG elapsed, PSG not elapsed elapsed BC
CE, start TI, elapse TI mem
Record TI TI L2 Level
TI
TI elapsed, TI not elapsed elapsed
Start AT, elapse AT

Record AT L3 backlog level
AT AT
AT elapsed, AT not elapsed elapsed
L3 new level
BA, BQ BA BQ BC
Figure 46.11 CP transmitter scheduler architecture. (From Gallon, L. et al., Modelling and analysis of the
ARINC specification 629 CP MAC layer protocol, in Proceedings of IEEE International Workshop on Factory
Communication Systems, pp. 91–100, Barcelona, Spain, 1997.)
transmits in levels 1, 2, and 3 backlog (which means that it had a message to send in level 3 new during the
previous bus cycle that could not be sent); station k transmits in levels 1 and 2; the three stations have noth-
ing to send in level 3 new. Figure 46.12 neglects the time propagation τ. In Figure 46.12, circles indicate the
actions that are undertaken in the leader and nonleader role. A horizontal piece of line represents a timer.
When a line ends with an arrow, it means that the timer expired; otherwise, there is a reset. We can observe
the following interesting scenario in line with the aforementioned rules and explanations. Station i starts
this bus cycle and the next bus cycle. At level 2, station j sends the first (because it has the smallest TG).

46-14
Bus cycle

Start TI
(TI elapsed) Start AT
(Leader) Reset PSG Reset TG Reset TG Reset TG Reset TG
Reset ASG Reset ASG Reset ASG Reset ASG
TI TI
AT AT
PSG PSG PSG PSG PSG PSG PSG PSG
ASG ASG ASG ASG ASG ASG ASG ASG ASG
i TGl i TGi TGi i
Leader ... Leader
... ...
TGj j TGk k TGj j TGi TGk k TGj j TGj TGj
PSG PSG PSG PSG PSG PSG PSG PSG
ASG ASG ASG ASG ASG ASG ASG ASG ASG
AT AT
TI
Stop TI Start TI
(TI not elapsed) Start AT
(Non leader) Reset PSG
Reset ASG Reset ASG Reset ASG Reset ASG
Reset TG Reset TG Reset TG Reset TG Reset TG
Start TI
LEVEL 1 LEVEL 2 (τ neglected) Level 3 backlog Level Wait Wait
L3 For For
new PSG leader
elapsed
Figure 46.12 CP—normal operation.

Avionics and Aerospace
Downloaded By: 10.3.97.143 At: 20:36 03 Oct 2023; For: 9781482207330, chapter46, 10
ARINC 629 46-15
Table 46.4 Main Features of BP and CP

BP CP
Operations Periodic or aperiodic, or aperiodic Period and aperiodic (optimization of
messages sent in periodic mode bandwidth)
No segregation between periodic Segregation between periodic and aperiodic
and aperiodic messages messages

File transfer Padding in XPP even if no Aperiodic word strings sent on request by the
request; label sent on the bus host, burst of word strings possible
Determinism for periodic messages Guaranteed by TI/SG timers Guaranteed by TI, PSG, and AT timers
Scheduling modes Block, independent, sync, Block, independent, sync
alternate
Source: Airlines Electronic Engineering Committee, Multi-transmitter data bus—Part 2 applications guide—ARINC
specification 629P2-2, Standard 629P2-2, Aeronautical Radio, Inc (ARINC), Annapolis, MD, February 26, 1999.
46.3.4 Comparison and Summary

Table 46.4 presents an overview of main features of the BP and CP.
46.4 Robustness and Fault Tolerance Features

Next to parity for each word string and robustness checks of the physical layer (like amplitude and
coding correctness checks), ARINC 629 requires other robustness and fault tolerance features like
three types of terminal monitoring: (1) receive data monitoring, (2) transmission monitoring, and
(3) protocol check.
46.4.1 Receive Data Monitoring

Receive data monitoring ensures that any received data word that does not have a valid sync pattern,
a valid Manchester II biphase modulation pattern, and a valid parity bit is not delivered to higher layers.
The receivers of all terminals that are not transmitting data should monitor all labels being transmit-
ted on the bus. Receivers should check labels against programmed entries in the receive personality
Programmable Read-Only Memory (PROM). Labels not destined for this terminal should be discarded.
46.4.2 Transmit Data Monitoring

Transmission monitoring of the terminal uses data a terminal’s transmitter has placed on the bus. The
goal of the transmission monitoring is detection of events like prevention of impersonation (which hap-
pens when a transmitter sends with the label of another transmitter) and babbling (the continuous
transmitting of a terminal for an extensive period of time). It detects a label authorized for transmis-
sion and ensures a correct CID. The transmit monitor prevents transmission on the bus whenever an
invalid sync pattern, modulation, or parity condition exists. Furthermore, the monitor also prevents
transmission when the word string length exceeds the specified value, or the message length exceeds
the specified value, or an illegal label is being transmitted. In case of a monitoring error, the transmit-
ter should inhibit the remainder of that message. Additionally, a terminal heuristically distinguishes
between transient and permanent faults leveraging a transmission error counter. In case of seven suc-
cessive unsuccessful tries, the terminal is disabled.

46.4.3 Bus Protocol Monitoring

ARINC 629 also specifies monitoring of essential protocol logic in two separate circuits on the same
protocol chip. Each of these circuits should operate from a separate crystal oscillator and obtain the
essential three controlling parameters from a different source.
These three rules and parameters are as follows:
1. TI has elapsed.
2. The SG—a quiet period on the bus—has existed on the bus.
3. The TG—another quiet period, unique for each terminal—has existed on the bus since the
SG occurred.
During execution, the protocol state machine is extended to agreeing on the rules for the go-ahead
signal for the transmitter despite expected differences due to crystal oscillator and similar effects. This
dual-logic implementation of the protocol machine minimizes the likelihood of a single-point failure
causing a terminal to transmit at the wrong time. The protocol logic should initiate a transmit operation
and maintain order on the bus.
These three simple rules ensure orderly transmission, without collisions or contentions, for peri-
odic operation, aperiodic operation, or transitional operation. Whether the bus is periodic is not
determined by protocol but determined by the loading of the bus and whether variable word strings
are allowed.
46.4.4 Protocol Parameter Monitoring

Dual-protocol circuits should control each protocol parameter steered by the LRU program pin
strapping. This should be compared to programming in the receive personality PROM, which is a
section of memory that contains bus protocol parameters, receive address value, number of word strings
in the message, and other key receive message elements.
46.5 ARINC 629 in Boeing 777

In Boeing 777, multiple new electronics technologies have been introduced in order to provide more
functionality with higher reliability and easier maintainability, which essentially means higher value
for aircraft customers. One of new technologies selected is the new system bus ARINC 629 described in
this chapter in more detail.
ARINC 629 is a time division multiplex system. It includes multiple transmitters with broadcast-
type, autonomous terminal access. While ARINC 629 specifies that up to 120 LRUs may be connected
together, for Boeing 777 a maximum of 44 LRUs connected with couplers are allowed [1, pp. 2–6].
Boeing 777 leverages the current mode coupling physical layer of ARINC 629 (see Section 46.1.2.1)
and utilizes the BP (see Section 46.3.1) in periodic transfer mode mainly during normal operation. LRUs
communicate to the bus using a coupler and terminal as shown in Figure 46.13.
The terminal controller incorporates the following features [1, p. 2–2]:
• Local transmit and receive message control

• Optional transmit and receive vectored interrupts
• Manchester II biphase coded serial data format
• Onboard direct memory access (DMA) capability
• Automatic power-on initialization
• Periodic and aperiodic transfer modes
• Label identification of data permits global parameters on bus
• Receiver monitoring and shutdown on error of transmitted data

ARINC 629 46-17
Current mode coupler

No. n (120 max)
Current mode Line replaceable unit

coupler No. 1 No. n (120 max)

Stub cable
Data bus cable assembly
Line replaceable
unit No. 1
Figure 46.13 Interconnect of systems using ARINC 629. (From Yeh, Y.C., Design considerations in Boeing 777
fly-by-wire computers, in The 3rd IEEE International Symposium on High-Assurance Systems Engineering, HASE’98,
p. 64, Washington, DC, IEEE Computer Society, 1998.)
• Receive parity and format checking

• 2-Mbit continuous transmission collision recovery
• Capable of simultaneous transmission collision recovery
• 180-pin lead ceramic grid array package
• 208-pin lead plastic quad flatpack (PQFP) package
The SIM incorporates the following features [1, p. 2–2]:
• Interface between terminal controller and CMC, which converts serial Manchester encoded data
into differential voltage doublets and vice versa
• Checks amplitude and polarity of doublets transmitted to the coupler
• Checks symmetry and polarity of doublets received from coupler
• Notifies terminal controller of SIM/coupler failure symptoms
• Inhibits coupler transmission if both channels are bad
• Shuts down the coupler power if an overcurrent condition is detected
• Administers BIST sequence to determine coupler health
• Prevents propagation of shorts and hot faults into LRU from the stub
• Packages available for through-hole and surface mounting
The following lists the features of the stub cable assembly [1, pp. 2–3]:
• Four conductors, made up of either two twisted pairs, each separately shielded with one overall
shield, or quad arrangement with all four wires twisted together
• Circumferential shielding at connectors
• Up to 40 m in length using 22 gauges wires, but only up to 17.3 m in Boeing 777 implementation
using 24 gauges wires
The CMC incorporates the following features [1, pp. 2–3]:
• Inductive nonintrusive clip on coupling
• Low bus load and reflection
• Low dynamic signal range

• High noise immunity

• Redundant transmitters and receivers
• Channel-switching capability
• Overcurrent shutdown capability
The bus cable assembly features are the following [1, pp. 2–3]:
• Lightweight twisted pair media (shielded and unshielded)

• Low attenuation
• Impedance-matched fault-tolerant terminations
• Capable of supporting up to 120 mode couplers, but only a maximum of 44 couplers in Boeing 777
implementation
• Up to 100 m in length, but only maximum of 59.6 m in Boeing 777 implementation or 71.8 m on
stretch airplane version
The avionics architecture in Boeing 777 is characterized by functional integration compared to
predecessor aircrafts. Classical avionics at that time had a federated avionics architecture, where a set
of functions is implemented in one or more LRUs. In Boeing 777, this has been replaced by a more
integrated architecture where multiple sets of functions are combined in fewer LRUs, some in common
cabinets instead of many separate boxes.
Left Left Right Right

Primary Seconda-
outboard inboard inboard outboard
EICAS ry EICAS
display display display display
Display buses
Left Center Right

Left AIMS cabinet Right AIMS cabinet
MCDU MCDU MCDU
ARINC 659 - SAFE bus ARINC 659 - SAFE bus
1
Inter-Cabinet Buses
2
3 ARINC 629
4
Left
Middle System
Middle 2 ARINC 629
Right
Left
Middle Fly-by-Wire ARINC 629
Right
Legend:
EICAS…Engine information and crew alert system
MCDU…Management control and display unit Engine- Many other Some flight
AIMS…Aircraft information management system related ACE
ACEss PFC
PF C avionics and control
ACE…Actuator control electronics
systems ACEs PFCs
PFC…Primary flight computer utility systems systems
Figure 46.14 Boeing B 777 avionics overview. EICAS, engine information and crew alert system; MCDU,
management control and display unit; AIMS, aircraft information management system; ACE, actuator control
electronics; PFC, primary flight computer. (Courtesy of Honeywell, Morristown, NJ.)

ARINC 629 46-19
The cabinets and stand-alone LRUs are connected to the airplane interfaces via a combination of
ARINC 429, ARINC 629, display buses, and discrete I/O channels. Figure 46.14 shows the most impor-
tant connected modules; it displays only ARINC 629 and display buses and neither ARINC 429 nor
discrete I/O channels. In addition to the cabinets, other flight deck hardware elements that make up
the avionics system are six flat panel display units, three control and display units, two electronic flight
instrument system (EFIS) display control panels, one display select panel, two cursor control devices,
and two display remote light sensors (not all are depicted in Figure 46.14). The system bus in Boeing 777
is mainly ARINC 629 [2]. As can be seen, multiple groups of bus called system ARINC 629 and fly-by-
wire ARINC 629 buses are deployed. For the flight control ARINC 629, LRUs receive data on all three
ARINC 629 buses but transmit on only one ARINC 629 bus.
References
1. Airlines Electronic Engineering Committee. Multi-transmitter data bus—Part 2 applications
guide—ARINC specification 629P2-2. Standard 629P2-2, Aeronautical Radio, Inc. (ARINC),
Annapolis, MD, February 26, 1999.
2. Airlines Electronic Engineering Committee. Multi-transmitter data bus—Technical description—
ARINC specification 629P1-5. Standard 629P1-5, Aeronautical Radio, Inc (ARINC), Annapolis,
MD, March 31, 1999.
3. Airlines Electronic Engineering Committee. Digital information transfer system (DITS)—Part 1—
Functional description, electrical interface, label assignments and word formats—ARINC speci-
fication 429PART1–16. Standard 629P2-2, Aeronautical Radio, Inc. (ARINC), Annapolis, MD,
September 27, 2001.
4. A. Gabillon and L. Gallon. An availability model for avionic databuses. In Proceedings of the
Workshop on Issues in Security and Petri Nets (WISP), Vol. 23, Eindhoven, The Netherlands, 2003.
5. L. Gallon, G. Juanole, and I. Blum. Modelling and analysis of the ARINC specification 629 CP MAC
layer protocol. In Proceedings of IEEE International Workshop on Factory Communication Systems,
pp. 91–100, Barcelona, Spain, 1997.
6. H. Kopetz. Real-Time Systems: Design Principles for Distributed Embedded Applications. Kluwer
Academic Publishers, Norwell, MA, 1st edn., 1997.
7. Special Committee 135 (SC-135). Environmental conditions and test procedures for airborne equip-
ment. Standard DO-160E, RTCA, Inc., Washington, DC, December 9, 2004.
8. Y. C. Yeh. Design considerations in Boeing 777 fly-by-wire computers. In The 3rd IEEE International
Symposium on High-Assurance Systems Engineering, HASE’98, p. 64, Washington, DC, 1998. IEEE
Computer Society.

RoutledgeHandbooks 9781482207330 Chapter46 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RoutledgeHandbooks 9781482207330 Chapter46 2

Uploaded by

Copyright:

Available Formats

This article was downloaded by: 10.3.97.

Industrial Communication Technology Handbook

PLEASE SCROLL DOWN FOR DOCUMENT

Full terms and conditions of use: https://www.routledgehandbooks.com/legal-notices/terms

46.1 Physical Layer

© 2015 by Taylor & Francis Group, LLC

ARINC 629 Terminal ARINC 629

46.1.1 Requirements for Physical Layer

© 2015 by Taylor & Francis Group, LLC

46.1.2 Physical Layer Entities

46.1.2.1 Current Mode Bus

46.1.2.2 Fiber-Optic Mode Bus

© 2015 by Taylor & Francis Group, LLC

Table 46.2 Current Mode Cable Requirements

Attenuation <2.8 dB/100 m (F = 6 MHz) <2.6 dB/100 m (F = 6 MHz)

Table 46.3 Common Characteristics of Fiber-Optic Mode Bus

46.1.3 Physical Layer Signaling

46.2 Data Link Layer

© 2015 by Taylor & Francis Group, LLC

3 Word wordstring 4 Word wordstring

HI LO sync label priority

Figure 46.2 Example message with two word strings.

46.2.1 Message Format

46.2.2 Open Systems Interconnection (OSI)-Compatible Format

CID Source address

© 2015 by Taylor & Francis Group, LLC

46.2.3 ARINC 629 Non-OSI Data Transfer

CID Source address

Information [FSW] [UPCOUNT, PVW] data

© 2015 by Taylor & Francis Group, LLC

CID Source address

Information [FSW][UPCOUNT, PVW] data

46.3 Medium Access Layer

1. Basic mode protocol (BP)

46.3.1 Basic Protocol

© 2015 by Taylor & Francis Group, LLC

46.3.1.1 Timers for Operation

© 2015 by Taylor & Francis Group, LLC

Start if BQ Start if transmit go-ahead

Reset if (BA and

Start if BQ and Yes Was a clash

TG elapsed TI + TG elapsed TI elapsed

Conditional wait for TI

message SG TG1 message

TG2 message SG TG2 TG2 message

Station 2 Go ahead Go ahead

TG3 message SG TG3 TG3 message

Figure 46.7 BP—periodic mode.

46.3.1.2 Bus Cycle Start and Initialization

© 2015 by Taylor & Francis Group, LLC

TG1 message SG TG1 message SG

message SG TG2 message SG

TG3 message SG TG3 message SG

Figure 46.8 BP—aperiodic mode.

46.3.2.1 Bus Cycle

46.3.2.2 Timers for Operation

© 2015 by Taylor & Francis Group, LLC

TGi TGj ASG L2 ASG L3b ASG L3n PSG

TG elapsed = AT elapsed = no more TI elapsed =

© 2015 by Taylor & Francis Group, LLC

46.3.3.1 Architecture of Link Layer

© 2015 by Taylor & Francis Group, LLC

Logical link control