The Experts below are selected from a list of 28830 Experts worldwide ranked by ideXlab platform

Wilfried Elmenreich - One of the best experts on this subject based on the ideXlab platform.

  • A standard for real-time smart transducer Interface
    Computer Standards & Interfaces, 2006
    Co-Authors: Wilfried Elmenreich, Wolfgang Haidinger, Hermann Kopetz, Thomas Losert, Roman Obermaisser, Michael Paulitsch, P. Peti
    Abstract:

    Abstract In order to handle the inherent complexity of the multitude of available different transducer components, a generic Interface approach is necessary. Such a universal smart transducer Interface should provide precisely defined Interfaces between smart transducers and their users, which are simple and precisely specified within the value domain and the temporal domain. The Object Management Group adopted a smart transducer Interface standard that incorporates (i) real-time characteristics and functionalities for the smart transducer network (ii) online diagnostic service capability (iii) support for start-up and dynamic configuration (iv) a uniform naming and addressing scheme for all relevant data in the smart transducer system (v) a generic Interface that enables the smart transducer system to interact with other systems via CORBA. This paper describes the main concepts and implementation experiences of this smart transducer Interface. The approach integrates a time-triggered communication protocol with an appropriate access scheme, the so-called Interface File system. This Interface File system provides a unique naming and addressing scheme enabling access to internal transducer data via a CORBA gateway.

  • ISORC - Modeling distributed embedded applications on an Interface File system
    Seventh IEEE International Symposium onObject-Oriented Real-Time Distributed Computing 2004. Proceedings., 1
    Co-Authors: Wilfried Elmenreich, S. Pitzek, Martin Schlager
    Abstract:

    This paper presents a framework for generic modeling of distributed embedded applications. An application is decomposed into services and mapped on a set of distributed nodes, whereas each node hosts one or more services. Each service is described by four Interfaces: a real-time input/output, a configuration and planning (CP), and a diagnostic and management (DM) Interface. The overall application is described by a cluster configuration description that specifies the interaction of services within and across nodes. The application requirements, the service properties of a node, and the interaction of the services as well as the application mapping are described formally with XML descriptions. The XML format allows a language-neutral and extensible semantic description of Interfaces supporting the implementation of context-aware tools for modeling, scheduling, monitoring, simulation, and validation. A central concept of the model is the Interface File system (IFS) that acts as a distributed shared memory and transparently implements the Interfaces to services from other nodes. In principle, the communication system that updates the data in the IFS data is not bound to a specific implementation as long as it fulfills the given timing requirements. The presented concepts are applied in a case study that uses the time-triggered fieldbus protocol TTP/A for the implementation of a small sensor fusion application

  • A comparison of LIN and TTP/A
    2000 IEEE International Workshop on Factory Communication Systems. Proceedings (Cat. No.00TH8531), 1
    Co-Authors: Hermann Kopetz, Wilfried Elmenreich, C. Mack
    Abstract:

    The paper compares two novel field-bus protocols for low-cost single-chip smart sensor and actuator nodes, LIN and TTP/A. Both protocols are central-master UART protocols, where the master with its precise oscillator establishes the stable time-base required by the slaves to synchronize their imprecise on-chip oscillators. While LIN provides the basic services needed for real-time communication, the TTP/A standard additionally specifies an Interface-File system to perform on-line configuration, diagnostics and maintenance of smart sensor nodes. With TTP/A it is thus possible to produce preprogrammed simple transducer nodes or generic smart transducer nodes that can be configured dynamically to the given application requirements.

  • ISORC - A universal smart transducer Interface: TTP/A
    Proceedings Third IEEE International Symposium on Object-Oriented Real-Time Distributed Computing (ISORC 2000) (Cat. No. PR00607), 1
    Co-Authors: Hermann Kopetz, Michael Holzmann, Wilfried Elmenreich
    Abstract:

    The primary goal of a universal smart transducer Interface is the provision of a framework that helps to reduce the complexity of large distributed real-time systems by introducing precisely specified (in the value domain and in the temporal domain) and small Interfaces between smart transducers and their users. This paper presents a universal smart transducer Interface that can be implemented on top of different real-time communication systems. It integrates a time-triggered communication protocol with an Interface File system that provides the sources and sinks for the exchanged information. The final section discusses an implementation of this Interface on a low cost (less than 1 $) commercial off the shelf microcontroller.

A. Shapiro - One of the best experts on this subject based on the ideXlab platform.

  • Standard Interface File handbook
    1992
    Co-Authors: A. Shapiro, H.c. Huria
    Abstract:

    This handbook documents many of the standard Interface File formats that have been adopted by the US Department of Energy to facilitate communications between and portability of, various large reactor physics and radiation transport software packages. The emphasis is on those Files needed for use of the VENTURE/PC diffusion-depletion code system. File structures, contents and some practical advice on use of the various Files are provided.

  • VENTURE/PC manual: A multidimensional multigroup neutron diffusion code system
    1991
    Co-Authors: A. Shapiro, H.c. Huria, K.w. Cho
    Abstract:

    VENTURE/PC is a recompilation of part of the Oak Ridge BOLD VENTURE code system, which will operate on an IBM PC or compatible computer. Neutron diffusion theory solutions are obtained for multidimensional, multigroup problems. This manual contains information associated with operating the code system. The purpose of the various modules used in the code system, and the input for these modules are discussed. The PC code structure is also given. Version 2 included several enhancements not given in the original version of the code. In particular, flux iterations can be done in core rather than by reading and writing to disk, for problems which allow sufficient memory for such in-core iterations. This speeds up the iteration process. Version 3 does not include any of the special processors used in the previous versions. These special processors utilized formatted input for various elements of the code system. All such input data is now entered through the Input Processor, which produces standard Interface Files for the various modules in the code system. In addition, a Standard Interface File Handbook is included in the documentation which is distributed with the code, to assist in developing the input for the Input Processor.

  • VENTURE/PC manual: A multidimensional multigroup neutron diffusion code system. Version 3
    1991
    Co-Authors: A. Shapiro, H.c. Huria, K.w. Cho
    Abstract:

    VENTURE/PC is a recompilation of part of the Oak Ridge BOLD VENTURE code system, which will operate on an IBM PC or compatible computer. Neutron diffusion theory solutions are obtained for multidimensional, multigroup problems. This manual contains information associated with operating the code system. The purpose of the various modules used in the code system, and the input for these modules are discussed. The PC code structure is also given. Version 2 included several enhancements not given in the original version of the code. In particular, flux iterations can be done in core rather than by reading and writing to disk, for problems which allow sufficient memory for such in-core iterations. This speeds up the iteration process. Version 3 does not include any of the special processors used in the previous versions. These special processors utilized formatted input for various elements of the code system. All such input data is now entered through the Input Processor, which produces standard Interface Files for the various modules in the code system. In addition, a Standard Interface File Handbook is included in the documentation which is distributed with the code, to assist in developing the input for the Input Processor.

K.w. Cho - One of the best experts on this subject based on the ideXlab platform.

  • VENTURE/PC manual: A multidimensional multigroup neutron diffusion code system
    1991
    Co-Authors: A. Shapiro, H.c. Huria, K.w. Cho
    Abstract:

    VENTURE/PC is a recompilation of part of the Oak Ridge BOLD VENTURE code system, which will operate on an IBM PC or compatible computer. Neutron diffusion theory solutions are obtained for multidimensional, multigroup problems. This manual contains information associated with operating the code system. The purpose of the various modules used in the code system, and the input for these modules are discussed. The PC code structure is also given. Version 2 included several enhancements not given in the original version of the code. In particular, flux iterations can be done in core rather than by reading and writing to disk, for problems which allow sufficient memory for such in-core iterations. This speeds up the iteration process. Version 3 does not include any of the special processors used in the previous versions. These special processors utilized formatted input for various elements of the code system. All such input data is now entered through the Input Processor, which produces standard Interface Files for the various modules in the code system. In addition, a Standard Interface File Handbook is included in the documentation which is distributed with the code, to assist in developing the input for the Input Processor.

  • VENTURE/PC manual: A multidimensional multigroup neutron diffusion code system. Version 3
    1991
    Co-Authors: A. Shapiro, H.c. Huria, K.w. Cho
    Abstract:

    VENTURE/PC is a recompilation of part of the Oak Ridge BOLD VENTURE code system, which will operate on an IBM PC or compatible computer. Neutron diffusion theory solutions are obtained for multidimensional, multigroup problems. This manual contains information associated with operating the code system. The purpose of the various modules used in the code system, and the input for these modules are discussed. The PC code structure is also given. Version 2 included several enhancements not given in the original version of the code. In particular, flux iterations can be done in core rather than by reading and writing to disk, for problems which allow sufficient memory for such in-core iterations. This speeds up the iteration process. Version 3 does not include any of the special processors used in the previous versions. These special processors utilized formatted input for various elements of the code system. All such input data is now entered through the Input Processor, which produces standard Interface Files for the various modules in the code system. In addition, a Standard Interface File Handbook is included in the documentation which is distributed with the code, to assist in developing the input for the Input Processor.

H.c. Huria - One of the best experts on this subject based on the ideXlab platform.

  • Standard Interface File handbook
    1992
    Co-Authors: A. Shapiro, H.c. Huria
    Abstract:

    This handbook documents many of the standard Interface File formats that have been adopted by the US Department of Energy to facilitate communications between and portability of, various large reactor physics and radiation transport software packages. The emphasis is on those Files needed for use of the VENTURE/PC diffusion-depletion code system. File structures, contents and some practical advice on use of the various Files are provided.

  • VENTURE/PC manual: A multidimensional multigroup neutron diffusion code system
    1991
    Co-Authors: A. Shapiro, H.c. Huria, K.w. Cho
    Abstract:

    VENTURE/PC is a recompilation of part of the Oak Ridge BOLD VENTURE code system, which will operate on an IBM PC or compatible computer. Neutron diffusion theory solutions are obtained for multidimensional, multigroup problems. This manual contains information associated with operating the code system. The purpose of the various modules used in the code system, and the input for these modules are discussed. The PC code structure is also given. Version 2 included several enhancements not given in the original version of the code. In particular, flux iterations can be done in core rather than by reading and writing to disk, for problems which allow sufficient memory for such in-core iterations. This speeds up the iteration process. Version 3 does not include any of the special processors used in the previous versions. These special processors utilized formatted input for various elements of the code system. All such input data is now entered through the Input Processor, which produces standard Interface Files for the various modules in the code system. In addition, a Standard Interface File Handbook is included in the documentation which is distributed with the code, to assist in developing the input for the Input Processor.

  • VENTURE/PC manual: A multidimensional multigroup neutron diffusion code system. Version 3
    1991
    Co-Authors: A. Shapiro, H.c. Huria, K.w. Cho
    Abstract:

    VENTURE/PC is a recompilation of part of the Oak Ridge BOLD VENTURE code system, which will operate on an IBM PC or compatible computer. Neutron diffusion theory solutions are obtained for multidimensional, multigroup problems. This manual contains information associated with operating the code system. The purpose of the various modules used in the code system, and the input for these modules are discussed. The PC code structure is also given. Version 2 included several enhancements not given in the original version of the code. In particular, flux iterations can be done in core rather than by reading and writing to disk, for problems which allow sufficient memory for such in-core iterations. This speeds up the iteration process. Version 3 does not include any of the special processors used in the previous versions. These special processors utilized formatted input for various elements of the code system. All such input data is now entered through the Input Processor, which produces standard Interface Files for the various modules in the code system. In addition, a Standard Interface File Handbook is included in the documentation which is distributed with the code, to assist in developing the input for the Input Processor.

Hermann Kopetz - One of the best experts on this subject based on the ideXlab platform.

  • A standard for real-time smart transducer Interface
    Computer Standards & Interfaces, 2006
    Co-Authors: Wilfried Elmenreich, Wolfgang Haidinger, Hermann Kopetz, Thomas Losert, Roman Obermaisser, Michael Paulitsch, P. Peti
    Abstract:

    Abstract In order to handle the inherent complexity of the multitude of available different transducer components, a generic Interface approach is necessary. Such a universal smart transducer Interface should provide precisely defined Interfaces between smart transducers and their users, which are simple and precisely specified within the value domain and the temporal domain. The Object Management Group adopted a smart transducer Interface standard that incorporates (i) real-time characteristics and functionalities for the smart transducer network (ii) online diagnostic service capability (iii) support for start-up and dynamic configuration (iv) a uniform naming and addressing scheme for all relevant data in the smart transducer system (v) a generic Interface that enables the smart transducer system to interact with other systems via CORBA. This paper describes the main concepts and implementation experiences of this smart transducer Interface. The approach integrates a time-triggered communication protocol with an appropriate access scheme, the so-called Interface File system. This Interface File system provides a unique naming and addressing scheme enabling access to internal transducer data via a CORBA gateway.

  • A comparison of LIN and TTP/A
    2000 IEEE International Workshop on Factory Communication Systems. Proceedings (Cat. No.00TH8531), 1
    Co-Authors: Hermann Kopetz, Wilfried Elmenreich, C. Mack
    Abstract:

    The paper compares two novel field-bus protocols for low-cost single-chip smart sensor and actuator nodes, LIN and TTP/A. Both protocols are central-master UART protocols, where the master with its precise oscillator establishes the stable time-base required by the slaves to synchronize their imprecise on-chip oscillators. While LIN provides the basic services needed for real-time communication, the TTP/A standard additionally specifies an Interface-File system to perform on-line configuration, diagnostics and maintenance of smart sensor nodes. With TTP/A it is thus possible to produce preprogrammed simple transducer nodes or generic smart transducer nodes that can be configured dynamically to the given application requirements.

  • ISORC - A universal smart transducer Interface: TTP/A
    Proceedings Third IEEE International Symposium on Object-Oriented Real-Time Distributed Computing (ISORC 2000) (Cat. No. PR00607), 1
    Co-Authors: Hermann Kopetz, Michael Holzmann, Wilfried Elmenreich
    Abstract:

    The primary goal of a universal smart transducer Interface is the provision of a framework that helps to reduce the complexity of large distributed real-time systems by introducing precisely specified (in the value domain and in the temporal domain) and small Interfaces between smart transducers and their users. This paper presents a universal smart transducer Interface that can be implemented on top of different real-time communication systems. It integrates a time-triggered communication protocol with an Interface File system that provides the sources and sinks for the exchanged information. The final section discusses an implementation of this Interface on a low cost (less than 1 $) commercial off the shelf microcontroller.