Design and Evaluation of a HMI based on LabView for a system of acquisition on VME for application of physics of high energies.
Rodrigo Uribe Valladares 1, Ramon Gmez Jimenez1, Gerardo Herrera Corral 2, Ana Luz Muoz Zurita1. Facultad de Ingeniera Mecnica y Elctrica, U .Torren Universidad Autnoma de Coahuila (Mxico) 2 Departamento de Fsica de Altas Energas CINVESTAV-Cd Mxico. (Mxico) Email: rodrigo_u_V@hotmail.com ABSTRACT. With LabVIEW, applications for industrial control, data acquisition and interfaces of human-machine can be developed (HMIs) using a single surroundings of development, and therefore assuring the maximum reusability abilities. From the VI's and macros elaborated by the company THEY FALL Nuclear, development an interface man machine (HMI) to monitor a group of 16 channels of ADC and TDC, on the visual atmosphere LabView de National Instruments. The capacities of LabVIEW and the ease of use of the graphical programming cause that LabVIEW is an excellent option for applications that they require: Measures and analysis, advanced Control, Communication, HMI/SCADA. With LabVIEW you can easily transfer data from/towards PLC (PLCs), interfaces for operators, and to enterprise offices. LabVIEW is compatible with multiple protocols of bus of industrial field and Ethernet, such as Modbus, OPC, Ethernet/IP, Modbus, EtherCAT, CANopen, Serial TCP/IP and. Therefore, you are not forced to use a protocol or specific standard to communicate with PLCs existing or other devices of automatization. LabVIEW also can place services neither PACs NOR Web, to be able to connect to the controllers of remote way through a navigator of Web or any application of PC client. One appears in this work, a report of the design and the result of the evaluation of stability, performance and used of application HMI; same that counts on the functions of registry of data, monitoring in real time, export from data to archives RAW and DAT. Also the technique of integration of the HMI to the hardware and the application of data acquisition of a particle detector is described. INTRODUCTION. Establishing a common language is often the first step to master a domain. This is especially true in the area of human-machine interface (HMI) design. HMI is the means by which a user operates a machine, system, or process (via hardwired panels or a computerized console). It also encompasses decision-support devices, such as operating procedures.Bandwidth availability from the modern HMI hardware and software has grown exponentially over the last few decades, and experts agree current Internet and web technologies cannot yet provide what most existing HMI users need: high data rates, high animation capability, and sub-second screen changes. Since humans cannot absorb information at the same rate as HMI bandwidth, it is important to design HMIs that better support the operator. In the petrochemical industry in U.S. alone, we estimate inadequacies in the means to deal with abnormal situations (including HMIs used to identify, diagnose, and deal with those situations) cost between $10 billion-$20 billion to the industry each year. HMI design is a key component of sensible system design. And since a systems architecture is driven by the design of its interfaces, and the HMI is one of the major interfaces of an interactive system, the HMIs design will have enormous weight on the architecture and design of the larger system.
1
This usually comes as somewhat of a shock to us design engineers, since we are used to looking first at functionality, flow diagrams, and electrical diagrams, and only later worry about the systems appearance. The trick is to realize the system is there to support its users in achieving a set of the organizations operating goals. One of those goals, at least for commercial organizations, is to attain a near-optimal productivity. An HMI comprises all elements a user will touch, see, or use to carry out tasks. This implies we need to consider components in the HMI design we would not traditionally consider part of the HMI to ensure the resulting product will support users who want to achieve the organizations operational and safety goals. To design successful HMIs, you need to know and understand a suitable design process. But it is also critical to understand how the HMIs users perceive and remember things, and how they make decisions. It is also important to realize how well they understand the process and the systems they use. You will need to identify beforehand the types of mistakes they could make. Finally, having a good understanding of operator monitoring activities will be useful in designing interactive monitoring functions. Acquiring information Visual perception refers to how users see and acquire information relevant to what they are trying to achieve. Legibility of information is influenced by factors such as contrast, font stroke width, and ambient lighting. Designers have traditionally used character height as the main means to affect legibility in HMIs. The use of color is another difficult area in HMI design. Designers often rely on colors to convey information but sometimes fail to realize their limitations. Nearly 8% of men and 0.5% of women suffer some form of color blindness. So using bold-colored text or coding information with color will not work for those users. Also, as people age, their visual acuity declines. Older operators tend to require larger character height (within the 16 to 22 minutes range) and also tend to require more lighting than younger operators. Internal or mental models refer to the way people understand elements of their own world. If you explain to a child how a car goes faster while driving, you could say refer to depressing the accelerator. Yet if the child asks more questions, you will need to go into how the accelerator changes the amount of fuel reaching combustion chambers into the engine. Unless you are well versed in engine mechanics, things could get fuzzy. Mental models differ from person to person and are many times incomplete, even for experienced workers. Mental models are usually goal-oriented. Therefore, it can be a mistake to rely on a single individual, even an experienced person, as the main source of knowledge for specifying an HMIs content. Reducing human error Human error is a contributing factor in most accidents occurring in high-risk domains. One popular error taxonomy that is a proven tool to reduce human error is to classify errors as slips or mistakes. A slip (or error of omission) corresponds to the case where the operator carries out a well known task but somehow omits one of the steps, or performs a wrong one. Mistakes (or errors of commission) occur when either the operator does not know how to do something and must therefore improvise, or when the environment (information the HMI provides) leads them down the wrong path.
One study suggests operators wait for an exception to occur on the process and then act to rectify it. More recent studies identify two types of operator behaviors: management by exception and management by awareness.Management by exception refers to operators who wait for an exception to occur and then deal with it. This reduces effort expended to monitor the process. The risk is operators are out of touch with the process and cannot avert a problem before it becomes quite noticeable. Management by awareness means the operator will continuously monitor key variables to get a feel for the process and ensure it runs smoothly. The advantage is it is easier to catch a developing situation before it becomes unmanageable. The disadvantage is this approach requires a dedicated operator and is difficult to practice when the process is unstable. In most cases, well-motivated and well-trained operators will use a mixture of approaches. And when the process is more stable, they will rely more on management by awareness, and management by exception will be more appropriate during times of transition. Obviously, individual differences will continue. So information required to manage the process by exception should always be visible to the operator. Information required to manage the process by awareness should always be available upon the operators request. Contrary to the information required to support management by exception, the information required here tends to be associated to trend graphs and will occupy more real estate area. It should thus be possible to call it up whenever the operator wants to manage the process by awareness (1). VME Acquire. Data acquisition and control is an important aspect of most systems such as manufacturing, control, research, or anything that accepts data and controls. Adding FPGAs to data acquisition provides pre- and post-algorithmic processing on data. In choosing how to construct the system, a number of items must be considered. The hardware elements chosen should have features that make the modules easy to program and handle, while the FPGAs should be reprogrammable when required. These requirements, along with module density and sophistication, cost, and availability with the latest A/D and D/As, formed the basis for our own search for a suitable data acquisition system. Our company, Joerger Enterprises, chose VME as the fundamental module type because of the wide availability of interoperable and reliable boards and the standards longevity. VME was designed in the 1980s, but the VITA standards body has constantly updated it to provide the latest features. These upgrades were always downward compatible so that older modules remained usable. Its latest pure bus-based version, VME64x, is both VME- and VXI-compatible. (The latter is ideal for test and measurement.) VME also offers some EMI/RFI noise protection a definite requirement in high-frequency data acquisition applications. However, VME wasnt our only choice for the modules. We also considered standards based upon PCI, VXS (VITA 41), VPX (VITA 46), GbE (VITA 31.1), and even PC-based computer motherboard modules. Analysis and Results. In this paper we have the graphics of implementation in the final state and you can observed the results of images in different software and the table of data is digital by the implementation of Flash ADC of two steps. An important result is the develop of circuit in PCB this is realized the implementation
Fig 1. PCB in CAD.
Fig 2 Flash ADC in PCB
Fig 3 Signal of PMT digitalized by ADC
Fig 4. Proof Signal of Flash ADC
Fig 5. Proof Signal and Measure Signal of Flash ADC
Fig 6. Real Signal of High Frequency
REFERENCES.
[1] Walt Kester, Analog-DIgital Conversion, Analog Devices, Inc. 2004, ISBN 0916550-27-3. [2] Dan Sheingold, Analog-Digital Conversion Handbook.3rd Edition Analog Devices and Prentice-Hall, 1986, ISBN-0-13-032848-0. [3] H. Nyquist, Certain Factors Affecting Telegraph Speed, Bell System Technical Journal, Vol. 3, 1924. [4] G.A. Gray and G.W. Zeoli, Quantization and Saturation Noise due to A/D Conversion, IEEE Trans. Aerospace and Electronic Systems, Jan. 1971. [5] M. Morris Mano, Diseo Logico, Prentice Hall 1982.