IHAL: Instrumentation Hardware Abstraction Language

1. IHAL: Instrumentation Hardware Abstraction Language Updates John Hamilton; Tim Darr; Mike Graul Knowledge Based Systems, Inc. March 2008

2. IHAL Review Instrumentation Hardware Abstraction Language Vendor-neutral format for describing and configuring instrumentation hardware and networks Supports system interoperability Supports post-mortem test recreation Supports automated hardware replacement

3. IHAL Application Viewpoints IHAL as specification language Hardware functional description Configuration and calibration T&E Instrumentation network specification Numerous “high-level” applications IHAL as control language Instrument control/setup from within an ISS Supports the O(mn)  O(m+n) concept IHAL as query language Query instrument(s) for current configuration

4. IHAL Design Criteria XML-based Support for generic instrument function A hardware function can be composed of sub-functions at any level of decomposition Support for common functions with specific parameters (e.g., ADC and signal conditioner) Concept of an instrument pool (catalog) Concept of an instrumentation network (configuration)

5. IHAL Design Criteria (cont.) Concept of an instrument use Support for generic parameters Support for configurable parameters Support for connectors and connections Support parameter value specification of any instrument that is part of an existing configuration

6. IHAL Design Review Two major aspects: Pool and Use Pool Describes all available instrumentation “out of the box” (i.e. the catalog) Describes configurability of each instrument Use Describes specific, configured instrumentation networks

7. IHAL Design Review, cont’d Logical separation of physical hardware attributes from instrumentation functions.

8. IHAL Improvements Split into multiple xsd files Developed Schema for Transducers Eliminated first-class hardware elements But kept first-class functions! Added Pool for Hardware Functions http://www.kbsi.com/ihal/ihal.htm

9. IHAL Transducer Schema • Represents transducers and sensors • Extensible to vendor specific transducers and sensors • Easily integrates with MIMOSA, SensorML, TML or other standards • Consists of the following sub-schemas • Common-Electrical • Attributes and structures common to electrical devices • Electrical connections, current characteristics, voltage characteristics, impedance characteristics, frequency characteristics, etc. • Common-Physical • Attributes and structures common to physical devices • Environmental characteristics (operating temperatures), dimensions, weight, physical connections, etc. • Common-Transducer • Attributes and structures common to all transducers • Manufacturer name, part number, • Acceleration Measurement • Attributes and structures specific to acceleration measurement • Sensitivity, range (min, max), units, etc. • Pressure-Transducer • Attributes and structures specific to pressure measurement • Accuracy, sensitivity, range, units, etc.

10. IHAL Transducer Pool

11. IHAL Instrument Pool

12. IHAL Function Pool

13. IHAL and iNet Metadata Serve a role similar to vendor formats Auto-generate IHAL configuration from MDL Single IHAL file could contain proposed networks for multiple vendors.

14. IHAL Future Work • Build out current schemas • Add more transducer / sensor types • Temperature • Flow • Position • Strain, load • Add more hardware functions • Instance Documents • RCC Standardization Task?

15. Points of Contact • KBSI • John Hamilton (JLHamilton@kbsi.com) • Timothy Darr (TDarr@kbsi.com) • Ronald Fernandes (RFernandes@kbsi.com) • Mike Graul (MGraul@kbsi.com) • EAFB • Charles Jones (charles.jones@edwards.af.mil)