176,100 research outputs found

    Electromechanical actuation for thrust vector control applications

    Get PDF
    At present, actuation systems for the Thrust Vector Control (TVC) for launch vehicles are hydraulic systems. The Advanced Launch System (ALS), a joint initiative between NASA and the Air Force, is a launch vehicle that is designed to be cost effective, highly reliable and operationally efficient with a goal of reducing the cost per pound to orbit. As part of this initiative, an electromechanical actuation system is being developed as an attractive alternative to the hydraulic systems used today. NASA-Lewis is developing and demonstrating an Induction Motor Controller Actuation System with a 40 hp peak rating. The controller will integrate 20 kHz resonant link Power Management and Distribution (PMAD) technology and Pulse Population Modulation (PPM) techniques to implement Field Oriented Vector Control (FOVC) of a new advanced induction motor. Through PPM, multiphase variable frequency, variable voltage waveforms can be synthesized from the 20 kHz source. FOVC shows that varying both the voltage and frequency and their ratio (V/F), permits independent control of both torque and speed while operating at maximum efficiency at any point on the torque-speed curve. The driver and the FOVC will be microprocessor controlled. For increased system reliability, a Built-in Test (BITE) capability will be included. This involves introducing testability into the design of a system such that testing is calibrated and exercised during the design, manufacturing, maintenance and prelaunch activities. An actuator will be integrated with the motor controller for performance testing of the EMA TVC system. The design and fabrication of the motor controller is being done by General Dynamics Space Systems Division. The University of Wisconsin-Madison will assist in the design of the advanced induction motor and in the implementation of the FOVC theory. A 75 hp electronically controlled dynamometer will be used to test the motor controller in all four quadrants of operation using flight type control algorithms. Integrated testing of the controller and actuator will be conducted at a facility yet to be named. The EMA system described above is discussed in detail

    Reusing Test-Cases on Different Levels of Abstraction in a Model Based Development Tool

    Full text link
    Seamless model based development aims to use models during all phases of the development process of a system. During the development process in a component-based approach, components of a system are described at qualitatively differing abstraction levels: during requirements engineering component models are rather abstract high-level and underspecified, while during implementation the component models are rather concrete and fully specified in order to enable code generation. An important issue that arises is assuring that the concrete models correspond to abstract models. In this paper, we propose a method to assure that concrete models for system components refine more abstract models for the same components. In particular we advocate a framework for reusing testcases at different abstraction levels. Our approach, even if it cannot completely prove the refinement, can be used to ensure confidence in the development process. In particular we are targeting the refinement of requirements which are represented as very abstract models. Besides a formal model of our approach, we discuss our experiences with the development of an Adaptive Cruise Control (ACC) system in a model driven development process. This uses extensions which we implemented for our model-based development tool and which are briefly presented in this paper.Comment: In Proceedings MBT 2012, arXiv:1202.582

    Experiments towards model-based testing using Plan 9: Labelled transition file systems, stacking file systems, on-the-fly coverage measuring

    Get PDF
    We report on experiments that we did on Plan 9/Inferno to gain more experience with the file-system-as-tool-interface approach. We reimplemented functionality that we earlier worked on in Unix, trying to use Plan 9 file system interfaces. The application domain for those experiments was model-based testing.\ud \ud The idea we wanted to experiment with consists of building small, reusable pieces of functionality which are then composed to achieve the intended functionality. In particular we want to experiment with the idea of 'stacking' file servers (fs) on top of each other, where the upper fs acts as a 'filter' on the data and structure provided by the lower fs.\ud \ud For this experiment we designed a file system interface (ltsfs) that gives fine-grained access to a labelled transition system, and made two implementations of it.\ud We developed a small fs that, when 'stacked' on top of the ltsfs, extends it with additional files, and an application that uses the resulting file system.\ud \ud The hope was that an interface like the one offered by ltsfs could be used as a general interface between (specification language specific) programs that give access to state spaces and (specification language independent) programs that use (walk) those state spaces like simulators, model checkers, or test derivation programs.\ud \ud Initial results (obtained on a less-than-modern machine) suggest that, although the approach by itself is definitely feasible in principle, in practice the fine-grained access offered by ltsfs may involve many file (9p) transactions which may seriously affect performance. In Unix we used a more conservative approach where the access was less fine-grained which likely explains why there we did not suffer from this problem.\ud \ud In addition we report on experiments to use acid to obtain coverage information that is updated on-the-fly while the program is running. This worked quite well. The main observation from those experiments is that the basic block notion of this approach, which has a more 'semantical' nature, differs from the more 'syntactical' nature of the basic block notion in Unix coverage measurement tools\ud like tcov or gcov

    The PMS project: Poor Man's Supercomputer

    Get PDF
    We briefly describe the Poor Man's Supercomputer (PMS) project carried out at Eotvos University, Budapest. The goal was to develop a cost effective, scalable, fast parallel computer to perform numerical calculations of physical problems that can be implemented on a lattice with nearest neighbour interactions. To this end we developed the PMS architecture using PC components and designed a special, low cost communication hardware and the driver software for Linux OS. Our first implementation of PMS includes 32 nodes (PMS1). The performance of PMS1 was tested by Lattice Gauge Theory simulations. Using SU(3) pure gauge theory or bosonic MSSM on PMS1 we obtained 3/Mflopand0.45/Mflop and 0.45Mflop price-to-sustained performance for double and single precision operations, respectively. The design of the special hardware and the communication driver are freely available upon request for non-profit organizations.Comment: Latex, 13 pages, 6 figures included, minor additions, typos correcte

    Maintaining standards in on-demand testing using item response theory

    Get PDF

    Motorcycle safety research project: Interim summary report 3: training and licensing interventions for risk taking and hazard perception for motorcyclists

    Get PDF
    Motorcycle trauma is a serious road safety issue in Queensland and throughout Australia. In 2009, Queensland Transport (later Transport and Main Roads or TMR) appointed CARRS-Q to provide a three-year program of Road Safety Research Services for Motorcycle Rider Safety. Funding for this research originated from the Motor Accident Insurance Commission. This program of research was undertaken to produce knowledge to assist TMR to improve motorcycle safety by further strengthening the licensing and training system to make learner riders safer by developing a pre-learner package (Deliverable 1), and by evaluating the QRide CAP program to ensure that it is maximally effective and contributes to the best possible training for new riders (Deliverable 2). The focus of this report is Deliverable 3 of the overall program of research. It identifies potential new licensing components that will reduce the incidence of risky riding and improve higher-order cognitive skills in new riders
    • 

    corecore