Top Banner

of 20

Aero Protocols

Apr 09, 2018

Download

Documents

shanthu78
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
  • 8/8/2019 Aero Protocols

    1/20

    Highlights Introduction to protocol

    Overview of AFDX ARINC-429

    CAN

  • 8/8/2019 Aero Protocols

    2/20

    Introduction to Protocol

    Agreement about the exchange of

    information in a distributed system.

    Protocol defines. precise formatfor valid messages(a syntax).

    the procedure rules for the data exchange (a grammar).

    a vocabularyof valid messages that can be exchanged, with their meaning (semantics).

  • 8/8/2019 Aero Protocols

    3/20

    AFDX

    Stands forAvionics Full DupleX Switched

    Ethernet.

    AFDX concepts introduced by Airbus.

    Is based upon Ethernet.

    Separated into. Avionics Subsystem.

    AFDX End System (End System).

    AFDX Interconnect.

  • 8/8/2019 Aero Protocols

    4/20

    AFDX

  • 8/8/2019 Aero Protocols

    5/20

    AFDX

  • 8/8/2019 Aero Protocols

    6/20

    AFDX

  • 8/8/2019 Aero Protocols

    7/20

    AFDX

  • 8/8/2019 Aero Protocols

    8/20

    AFDX

  • 8/8/2019 Aero Protocols

    9/20

    AFDX

  • 8/8/2019 Aero Protocols

    10/20

    AFDX

  • 8/8/2019 Aero Protocols

    11/20

  • 8/8/2019 Aero Protocols

    12/20

    ARINC 429

    Parity.

    SSM.

    DATA & PAD.

    SDI

    LABEL

  • 8/8/2019 Aero Protocols

    13/20

    ARINC 429

  • 8/8/2019 Aero Protocols

    14/20

    CAN

    CAN stands forControllerArea Network.

    CAN was first developed by Robert BoschGmbH, Germany in 1986.

    The first CAN silicon was then fabricated in 1987by Intel

    CAN STANDARDS Standard CAN (Version 2.0A). Uses 11 bit identifiers

    Extended CAN (Version 2.0B). Uses 29 bit identifiers

  • 8/8/2019 Aero Protocols

    15/20

    Tohelp protectyour privacy, PowerPointprevented thisexternalpicturefrom being automatically downloaded.To download and display thispicture,click Optionsin the MessageBar, and then click Enableexternalcontent.

    CAN

    There are three types ofCAN controllers

    Message format \ CAN chip type Part A Part BPassive Part B

    11 bit ID ok ok ok

    29 bit ID ERROR!! tolerated on the bus, but ignored ok

  • 8/8/2019 Aero Protocols

    16/20

    Tohelp protectyour privacy, PowerPointprevented thisexternalpicturefrom being automatically downloaded.To download and display thispicture,click Optionsin the MessageBar, and then click Enableexternalcontent.

    CAN

    11 BIT CAN Frame format

  • 8/8/2019 Aero Protocols

    17/20

    Tohelp protectyour privacy, PowerPointprevented thisexternalpicturefrom being automatically downloaded.To download and display thispicture,click Optionsin the MessageBar, and then click Enableexternalcontent.

    CAN

    29 BIT CAN Frame format

  • 8/8/2019 Aero Protocols

    18/20

    Tohelp protectyour privacy, PowerPointprevented thisexternalpicturefrom being automatically downloaded.To download and display thispicture,click Optionsin the MessageBar, and then click Enableexternalcontent.

    CAN

    Bit Timing

  • 8/8/2019 Aero Protocols

    19/20

    Tohelp protectyour privacy, PowerPointprevented thisexternalpicturefrom being automatically downloaded.To download and display thispicture,click Optionsin the MessageBar, and then click Enableexternalcontent.

    CAN

    ERRORClassification

    Bit errors:

    Bit stuffing error- normally a transmitting node inserts a high after five consecutive low bits(and a

    low after five consecutive high). This is called bit stuffing. A receiving node that detects violation

    (more than five consecutive bits will see a bit stuffing violation.

    Bit error- A transmitting node always reads back the message as it is sending. If it detects a differentbit value on the bus than it sent, and the bit is not part of the arbitration field or in the

    acknowledgement field, and error is detected.

    Message errors:

    Checksum error- each receiving node checks CAN messages for checksum errors.

    Frame error- There are certain predefined bit values that must be transmitted at certain points within

    any CAN Message Frame. If a receiver detects an invalid bit in one of these positions a Form Error

    (sometimes also known as a Format Error) will be flagged.

    Acknowledgement Error- If a transmitter determines that a message has not been ACKnowledged

    then an ACK Error is flagged.

  • 8/8/2019 Aero Protocols

    20/20

    Tohelp protectyour privacy, PowerPointprevented thisexternalpicturefrom being automatically downloaded.To download and display thispicture,click Optionsin the MessageBar, and then click Enableexternalcontent.

    CAN

    CONTROLLERERROR STATES

    The mode of the controller is controlled by two error counters

    the transmit error counter (tx_count) and the receive error counter (rx_count). The

    following rules apply:

    The CAN controller is in error active mode if tx_count 127) AND tx_count 255.