1 / 16

Proposal for an IEEE 1451 Standards Family Architecture

Proposal for an IEEE 1451 Standards Family Architecture. Lee H. Eccles Boeing Commercial Airplanes Seattle, Washington. Proposal. To produce an IEEE 1451 Functional Standard that gives the characteristics that should be common across the family.

roden
Download Presentation

Proposal for an IEEE 1451 Standards Family Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Proposal for an IEEE 1451 Standards Family Architecture Lee H. Eccles Boeing Commercial Airplanes Seattle, Washington Boston Sensors Expo

  2. Proposal • To produce an IEEE 1451 Functional Standard that gives the characteristics that should be common across the family. • Each individual standard would then only contain the unique features of that standard. Boston Sensors Expo

  3. Proposal Boston Sensors Expo

  4. The Proposed IEEE 1451 Functional Standard Covers • Transducer Types • Transducer Modes of Operation • High Level Addressing Technique • Trigger/Trigger Acknowledgement • Commands • Standard TEDS • Communications Protocols (Level 3 and up) Boston Sensors Expo

  5. Transducer Types and Modes • Transducer Types • Sensor • Event Sensor • Actuator • Transducer Modes of Operation and Attributes • Combining these three types with Attributes covers all transducer types in .2 and .3 Boston Sensors Expo

  6. High Level Addresses • High Level Addressing Technique • A common set of addresses independent of the address used on the physical communications link. • Conceptually similar to IP addresses over Ethernet but significantly less capability is required. Boston Sensors Expo

  7. Trigger andTrigger Acknowledgement • The Functional Standard defines • The high level function of a trigger • A method of requesting trigger acknowledgement • The relationship between a trigger and data • How the trigger is implemented at the physical layer is not defined. Boston Sensors Expo

  8. Commands • A general set of commands is defined • Additional commands can be specified • By a revision to the Functional Standard • By including them in individual standards • A method of adding manufacturer unique commands should be included. Boston Sensors Expo

  9. TEDS • The Functional Standard should contain • The general structure of all TEDS • Most TEDS definitions • The method of accessing TEDS including the Physical Layer TEDS Boston Sensors Expo

  10. Physical Layer TEDS • Contains information that is unique to the particular physical layer. • Examples • IEEE 1451.2 Worst-Case Data Clock Frequency • IEEE p1451.3 Highest supported payload encoding Boston Sensors Expo

  11. Communications Protocols • Patterned after the ISO/OSI model • Layers 3 and higher are covered in the Functional Standard • The Data Link layer (layer 2) and the Physical Layer (layer 1) are covered by the individual standards. Boston Sensors Expo

  12. Each IEEE 1451 Family Member • Identifies the sections of the Functional Standard that must be complied with for this family member. • Defines the Physical and Data Link layers of the communications protocol. • Defines the Physical Layer TEDS if required. • Defines specialized communications protocols. • Defines specialized commands. Boston Sensors Expo

  13. Specialized Protocols • Reasons for specialized protocols • Both IEEE 1451.2 and IEEE p1451.3 require two way communications between the NCAP and the transducer module. • A low power wireless application might require a one-way communications between the transducer module and the NCAP – just to read a sensor. • Proposed rule • Put it in the Functional Standard unless it will never be useful in another family member. Boston Sensors Expo

  14. Transducer Block • Present Situation • The Transducer block for IEEE 1451.2 is in IEEE 1451.1. • The Transducer block for IEEE p1451.3 and IEEE p1451.4 is in their respective standards. • Future • The Transducer Block for the IEEE 1451 Functional Standard would be common for all standards and should be in a revised IEEE 1451.1. Boston Sensors Expo

  15. Issues • After the Functional Standard is approved the individual standards will need to be revised. • IEEE 1451.2 is already defined. • Few, if any, functional changes should be required • IEEE p1451.3 is in the final preparations for release. • Few, if any, functional changes should be required Boston Sensors Expo

  16. Issues • IEEE p1451.4 is in the final preparations for release. • Few, if any, functional changes should be required • Can this standard be included? • Does it continue to stand alone? • IEEE p1451.5 is just getting started • They will need to review and approve the Functional Standard. Boston Sensors Expo

More Related