Improving Test Performance through Instrument Driver State Management
|
|
- Dulcie Katrina Pearson
- 8 years ago
- Views:
Transcription
1 Application Note 122 Improving Test Performance through Instrument Driver State Management Instrument Drivers John Pasquarette With the popularity of test programming tools such as LabVIEW and LabWindows /CVI, instrument drivers have emerged as a key development tool for automated test developers. Through the efforts of the VXIplug&play Systems Alliance, standards for instrument driver naming conventions, file formats, and development frameworks have been agreed on to guarantee interoperability between instrument drivers supplied by instrument vendors. The focus of these instrument drivers is primarily on ease of programming. Instrument drivers provide a high-level programming interface for instruments, replacing low-level GPIB and VXI instrument commands. With these intuitive, high-level functions, test developers can more quickly create modular test programs. Because a driver s primary purpose is to simplify programming, instrument drivers many times do not execute at peak performance for the instrument. The high-level instrument driver functions have a tendency to combine multiple instrument settings and actions into a single function, resulting in time-consuming instrument overhead from redundant reconfiguration and command processing operations. LabWindows/CVI Version 5.0 introduces new instrument driver development tools and technologies to address many of these issues through a new state-management instrument driver architecture. These drivers can be compiled as DLLs and called from LabVIEW, LabWindows/CVI, Visual Basic, Visual C++ or any Windows development tools. Drawbacks and Limitations Due to user demand, many vendors are now providing drivers with their instruments. Users can optimize drivers because vendors deliver them in source code. Thus, users can eliminate code segments that introduce unnecessary overhead in the driver. Although optimizing drivers can speed overall system throughput, this method has some drawbacks. Inexperienced end-users sometimes find it difficult to fully understand driver source code. In addition, instrument vendors have not defined a single format for writing drivers the variations in source code structure and sometimes inconsistent quality can make it difficult for end-users to comprehend and optimize source code for instruments from several vendors. Although VXIplug&play introduced a number of standards for packaging and delivering drivers with their instruments, none of the standards address internal coding practice and structure for drivers. Therefore, even though drivers may appear to be the same on the outside, they are almost always completely different on the inside. As PCs and general-purpose test software tools continue to advance, demand from test developers for more advanced capabilities is increasing. Test engineers are looking to solve very advanced testing requirements with standard, off-the-shelf tools, instead of using the proprietary, expensive, home-grown systems they may have built in the past. In addition, highly competitive industries, such as telecommunications and semiconductor, demand faster and faster testing times to keep up with production. The new, higher-complexity system demands are uncovering many of the drawbacks of the current industry-standard instrument driver architecture. Clearly, it is time for a change. Product and company names are trademarks or trade names of their respective companies A-01 Copyright 1998 National Instruments Corporation. All rights reserved. June 1998
2 Objectives of State Drivers The new instrument driver development tools introduced in LabWindows/CVI 5.0 are targeted at solving many of the long-standing limitations with today s instrument driver architecture, as outlined in the following objectives: 1. Improve the run-time performance of drivers without sacrificing ease of use High-level instrument control functions are very intuitive and easy to use when building test programs. Any approach to improving instrument driver performance must not sacrifice this fundamental programming model. State drivers developed in LabWindows/CVI 5.0 have the same high-level programming interface that you are accustomed to today. However, state drivers have a built-in state cache that tracks the state of instrument settings at runtime. By knowing which state your instrument is in, you can minimize the number of steps it takes to reconfigure it to a new state. State drivers do this automatically, resulting in major run-time improvements over test programs written with traditional instrument drivers. In some cases, test execution time was sliced in half. 2. Simplify instrument driver development Although developing instrument drivers is not a difficult process, it can be very tedious and time-consuming, requiring a lot of resources. Instrument vendors who have recently begun delivering drivers with their instruments through the efforts of the VXIplug&play Systems Alliance are finding the investment to be more than they originally expected. End-users also find developing a complete, full-function driver for their instruments is too time-consuming, and will many times develop a driver implementing only those few functions required for their particular application. These partial drivers are not very useful for other users. LabWindows/CVI introduces an instrument driver wizard that automatically generates much of the code required for an instrument driver. 3. Improve instrument driver quality By automatically generating driver code with a wizard, developers will invariably find fewer bugs in their instrument drivers. More importantly, because the wizard generates code to follow a particular structure, instrument driver source code begins to look the same for all instruments, making it easier to support and maintain drivers in general. 4. Improve programming flexibility with drivers Because state drivers must keep track of all instrument states or settings, you now have access to all low-level instrument settings if needed (in addition to the high-level functions described earlier). The new state drivers not only keep track of the state of your instrument, but also manage your instrument settings in a number of different ways. For example, you can configure a state driver to operate in Test Development mode or Production mode. In test development mode, the driver automatically performs a number of checks to eliminate common programming errors when using a driver. For example, by enabling range-checking, your driver automatically checks each value that you send to your instrument to make sure it is in within a valid range before it is sent. By enabling coercion, the driver automatically coerces any values that you try to send to the instrument that are within range but invalid (e.g., you are trying to set the resolution on your DMM to 4 digits when it only understands 3½ or 4½. The driver automatically coerces your value to 4½). By enabling status-checking, the driver automatically checks the status of your instrument after each command you send to it to verify that no errors have occurred. Each of these modes is helpful when you are developing a test, to catch common instrument programming errors automatically. However, when you are finished with your test program and you want to deploy it on the production floor, you simply turn off these error-checking modes so that the driver executes at top speed. 5. Ready for advanced system development State drivers developed in LabWindows/CVI 5.0 are multithread safe, so you can use them in advanced, multithreaded parallel testing systems. In addition, state drivers developed with the Instrument Driver Development Wizard also perform simulation, so you can begin developing test programs with your instrument driver even if you do not have access to the instrument itself. 2
3 How State-Caching Drivers Work As a test program developer, you use a state driver exactly the same way that you would use traditional VXIplug&play drivers the high-level programming interface is identical. However, the inside of the instrument driver is very different. State drivers are built on an attribute model, meaning every high-level configuration function callable by end-users is actually broken down into a collection of low-level SetAttribute function calls inside the driver. Each SetAttribute call is funneled through a support library that manages the state of the instrument to determine if the attribute actually needs to be changed (or if the particular attribute is already configured on the instrument, the command is ignored). The architecture diagram below introduces the state driver structure. User Application LabWindows/CVI, LabVIEW, Visual Basic... High-level programming AOI (for ease of use) Instrument Driver Attribute Model (for performance) State Management Library (Engine) VISA State Cache Figure 1. How the State Management Engine Works The internal architecture of state drivers is split between the instrument driver code itself and the state management library, or engine, which manages the instrument settings and driver modes. For example, a high-level function for a function generator might have four parameters, or attributes, that it sets for generating a waveform waveform shape, frequency, amplitude, and DC offset. As you can imagine, this function is very easy to use. However, if you use this function in a common testing scenario to implement a frequency sweep, in which you continuously call this function to increment the frequency value of the waveform, you introduce tremendous overhead in your instrument. Each time you try to change the frequency, you must also reset the sinewave shape, amplitude, and offset even if they don t need to change. The state management engine is the key to eliminating this overhead. Here is how it works: GenerateWFM (shape=sine, freq=1000, amp=1.0, offset=0.0) is actually broken down in the driver source code into four separate attribute calls: SetAttribute (shape, sine) SetAttribute (freq, 1000) SetAttribute (amp, 1.0) SetAttribute (offset, 0.0) 3
4 Each time an attribute call is made, the following operations occur: 1. SetAttribute (freq, 1000) calls into the engine to set the frequency attribute to If state-caching is ON, the engine checks to make sure the freq is not 100; if freq=1000, skip the command and continue to next. 3. If range-checking is ON, the engine checks to make sure 1000 is within range. 4. If log coercions is ON, the engine logs any coercions the driver makes to a log file. 5. If simulation is OFF, the engine sends the command to the instrument. 6. If status-checking is ON, the engine queries the instrument for its status to make sure no errors have occurred. The engine keeps track of the instrument states and the driver modes and then orchestrates the actual setting of the attribute accordingly. Because the state management engine handles the majority of the operations, the source code for the driver is very simple. The complexity of state caching is hidden both from the driver developer (because of the wizard) and from the driver user. A Word on State Integrity State-caching is a simple concept in theory, with many challenges when implemented in practice. Some test engineers are skeptical that an instrument driver can accurately track the state of every setting of a particular instrument at all times. The state-caching model in LabWindows/CVI 5.0 is a very flexible model with many different back doors and open entry points designed for handling peculiar instrument operations. It is important that test engineers understand the flexibility and practicality of the state-caching model implemented in LabWindows/CVI 5.0. Some of the common questions concerning state-caching are: Is it possible to track the values of every instrument setting at all times in software? IVI drivers do not attempt to track every value in software at all times. The cached values are built up in memory as your program runs. Each attribute stored in memory has a value that is either valid or invalid. When you initialize an IVI instrument driver, all attribute cache values are marked as invalid. Therefore, the first time your program accesses an attribute (sets it or gets it), the driver automatically communicates with the instrument directly and sets the initial value in the cache. These state-caching drivers have attribute tables that identify which attributes are dependent on other attributes. For example, when you change the range on a DMM, the resolution is also affected. In this case, the new value for range is stored in the cache, and the value for the resolution attribute is invalidated in the cache, because the software cannot be sure which new state the resolution attribute was set to. The next time your program accesses the resolution attribute, the IVI driver communicates with the instrument to get it or set it. By following this simple model of building up attribute values in software and maintaining an attribute dependency table, the states of instruments can be effectively tracked in memory. How does the IVI architecture handle range-checking of attribute values? Each driver contains range tables for each attribute. Range tables store valid values for each attribute. The engine uses range tables to verify that user-set values are within range for the instrument. There are three different types of range tables discrete, ranged, and coerced. Discrete tables are for attributes that have only discrete values as possible settings, such as the function attribute on a DMM. The function attribute can be set only to certain values volts DC, volts AC, amperes DC, and so on. Ranged attributes are attributes whose values must fall within upper and lower limits. Coerced attributes are attributes with values that fall within a specified range in specified values. For example, the horizontal timebase setting on an oscilloscope may fall between nanoseconds and seconds in 1x, 2x, and 5x increments. Coerced range tables automatically coerce any values to these appropriate values for the instrument before sending the values to the instrument. Even with this advanced level of range-checking, more flexibility is required to handle real instruments. For example, some attributes have dynamic range tables. Some attribute ranges depend on the mode in which the instrument is configured. The range of a DMM depends on the measurement function in which the DMM is configured. IVI drivers dynamically check these modes and direct the driver to use the appropriate range table, based on the settings of the instrument. In some cases, even this approach will not work. In these cases, the driver developer can simply call a function for dynamically computing the valid range of the attribute based on any number of settings. 4
5 How does the IVI architecture handle difficult attributes? Even with this simplified approach to state-caching, certain attributes on certain instruments can be problematic. To handle these cases, the IVI architecture provides a number of flexible options for the test programmer. One common example is attributes whose values are coerced by the instrument. Obviously, when instruments coerce the value of a setting after receiving a command from the user, it is very difficult for the software to actually match the values that are stored in the instrument. Coercion is handled in the following manner in IVI: 1. For instruments that coerce attribute values in a known method, IVI drivers contain complete range tables to track this coercion. For example, for oscilloscopes that accept horizontal timebase settings only in 1x, 2x, or 5x increments, the driver contains a range table structure that coerces the value to the appropriate 1x, 2x, or 5x increment before sending it to the instrument, as described above. However, for some attributes, coercion cannot be described in a simple range table structure. For these attributes, the driver developer can create a function to programmatically determine what the new value should be and coerce it before sending it to the instrument. In these cases, the coercion function may need to query the instrument to determine particular modes and attribute values, and use these values in the coercion algorithms. 2. For instruments that coerce attribute values consistently using an algorithm that cannot be determined (i.e., every time I send the instrument the value X it coerces it to Y, but I can t figure out the algorithm used to make that conversion), the IVI architecture implements a very flexible caching mechanism using the flag COERCED_BY_INSTRUMENT_ONLY. For example, imagine an instrument setting that is coerced by the instrument so that every time you send the instrument value X, the instrument coerces it to Y. Likewise, every time you send the value Y to the instrument, the instrument will accept it as Y. In this example, the state cache actually stores the source of the value that it is has recorded. For example, when you first send the value X to the instrument, the state cache stores X as a value set by the driver, while the instrument coerces X to Y internally. If you then try to get the value from the instrument, the driver will query the instrument and return Y (because it knows that Y is the actual value) and stores Y in the cache as the value that it got from the instrument. In the future, if you try to get the value from the instrument again, the driver will return Y without accessing the instrument. If you try to send X or Y to the instrument, the driver knows that the instrument is already set to this value and does not communicate with the instrument. 3. For instruments that coerce attribute values in a completely unknown method in which the dependency of attribute values cannot be determined, IVI allows you to disable caching for these particular attributes. If there is no way to accurately track the actual value of an attribute based on the value that the driver sends to the instrument, it is not practical to try to store values in software to match the instrument settings. For these examples, state-caching can simply be disabled. 4. For very complex, ill-behaved instruments that do not follow any correlation between the values you send them and the internal values that are stored, state-caching can be disabled for the entire driver. Note: Examples 2, 3, and 4 above represent very difficult instrument programming examples. The IVI state-caching architecture handles these situations using the flexible options described. However, instruments that fall into these categories are not only hard to cache instrument values for, but also hard to program in general because of their inconsistent behavior. How does state-caching handle catastrophic events, such as someone turning off the VXI chassis? The IVI architecture does not have anything specifically designed to handle these types of events. Again, all driver functions return errors that can be checked, similar to standard programming practices. In addition, when catastrophic events occur, such as the chassis losing power, the current value of the state cache is only one of many problems that you will have to handle. What about ill-behaved instruments with unpredictable behavior? When writing a driver for an instrument that is poorly documented or ill-behaved, we recommend that many of the state-caching features simply be disabled in the driver to avoid problems. Of course, a structured architecture for controlling instruments, such as IVI, will quickly bring to light any instruments that have poorly documented or poorly implemented programming interfaces. These types of instruments are not only difficult to write a state-caching driver for, but also difficult to program in general. Hopefully, more rigid requirements on instrument drivers such as IVI will prompt instrument vendors to develop, implement, and document their instrument programming interfaces better. 5
6 Are state-caching drivers difficult to write? The automated development tools described in the next section make state-caching driver development possible. The wizard in LabWindows/CVI 5.0 automates much of the coding required, so the instrument driver developer can focus on the important aspects of the driver learning how the instrument and its attributes operate. Developing a State-Caching Driver with the Instrument Driver Development Wizard As you can see, state-caching drivers add a number of improvements in terms of test execution speed and test development tools. The next obvious question is How do I develop a state-caching driver? LabWindows/CVI 5.0 introduces a new instrument driver development wizard that automates the process of writing a state-caching instrument driver. The driver wizard operates in two steps the first step generates the basic structure of the instrument driver files (the source file, the header files, and the function panel files) and the second step is a browser/code generator that inserts functions into the source file based on the instrument attributes (i.e., setting, getting, and checking attribute values). The initial steps of the wizard prompt the user for values in a series of dialog boxes to generate the driver files. For example, the wizard asks you which type of instrument driver you are writing (scope, DMM, function generator, etc.), and provides a suggested template of functions as a starting point to help you architect the driver API. Some of the dialogs from the startup wizard are shown below. 6
7 7
8 Once you have gone through the initial wizard dialogs, the attribute browser presents all of the instrument attributes and each function associated with the attributes. From the browser window, you can easily navigate through the driver source code. Simply right-click to generate function code for a particular attribute callback function, or view the source code of an existing attribute callback function. The browser makes it very easy to visualize the structure of your instrument driver and quickly navigate to code segments. 8
9 Conclusion State drivers address many of the long-standing drawbacks and limitations of VXIplug&play drivers. However, this new approach to developing and implementing instrument drivers introduces very little change in how test developers actually use instrument drivers. With automated development tools such as the Instrument Driver Development Wizard in LabWindows/CVI 5.0, more advanced, better-performing, higher-quality instrument drivers will be developed much faster than is currently possible today. 9
10
Eight Ways to Increase GPIB System Performance
Application Note 133 Eight Ways to Increase GPIB System Performance Amar Patel Introduction When building an automated measurement system, you can never have too much performance. Increasing performance
More informationLAN extensions for Instrumentation
LAN extensions for Instrumentation LXI: It s About Your Time It took years for Ethernet and the Web to transform the way we work. Now it s time for both to transform test systems. That s why leading test
More informationGetting Started Guide
Getting Started Guide Your Guide to Getting Started with IVI Drivers Revision 1.0 Contents Chapter 1 Introduction............................................. 9 Purpose.................................................
More informationVIRTUAL INSTRUMENTATION
VIRTUAL INSTRUMENTATION João Paiva dos Santos joao.santos@ipbeja.pt Lab SPEPSI Instituto Politécnico de Beja Beja, 15th May, 2014 Overview What and why Hardware Software Some standards Remote use Example
More informationOctober 21 November 5 November 14 December 12. Washington DC Boston Chicago San Jose. ni.com
October 21 November 5 November 14 December 12 Washington DC Boston Chicago San Jose 1 Evaluating Software Tools and Architectures to Design Test Systems A Sample Modular Software Architecture
More informationUsing InstallAware 7. To Patch Software Products. August 2007
Using InstallAware 7 To Patch Software Products August 2007 The information contained in this document represents the current view of InstallAware Software Corporation on the issues discussed as of the
More informationMatrox Imaging White Paper
Vision library or vision specific IDE: Which is right for you? Abstract Commercial machine vision software is currently classified along two lines: the conventional vision library and the vision specific
More informationPRAGMA ENGINEERING Srl. Next-Generation ATS (Sistemi ATE di Nuova Generazione)
Rome 30/05/2007 PRAGMA ENGINEERING Srl Next-Generation ATS (Sistemi ATE di Nuova Generazione) Rome 30/05/2007 Mission & Vision Pragma Engineering supplies design and development services, manufacturing
More informationDataSocket Simplifies Live Data Transfer for LabVIEW
DataSocket Simplifies Live Data Transfer for LabVIEW Many typical instrumentation solutions involve a single local application for acquisition, logging, analysis, and presentation. However, because of
More informationSimplifying development through activity-based change management
IBM Rational ClearCase and IBM Rational ClearQuest October 2004 Simplifying development through activity-based change management Allan Tate Product Manager IBM Software Group Karen Wade SCM Product Marketing
More informationTest Executive And Development Studio Integrated Test Executive and Application Development Environment
Test Executive And Development Studio Integrated Test Executive and Application Development Environment MARVINTEST.COM ATEASY 9.0 ATEasy offers a rapid application development framework and a test executive
More informationUsing MCC GPIB Products with LabVIEW
Using Products with LabVIEW * This application note applies to PCI-GPIB-1M, PCI-GPIB-300K, PCM-GPIB, as well as to ISA- and PC104- boards How NI Compatibility Works National Instruments (NI) provides the
More informationIntegrating the Internet into Your Measurement System. DataSocket Technical Overview
Integrating the Internet into Your Measurement System DataSocket Technical Overview Introduction The Internet continues to become more integrated into our daily lives. This is particularly true for scientists
More informationGetting Started with the LabVIEW Mobile Module
Getting Started with the LabVIEW Mobile Module Contents The LabVIEW Mobile Module extends the LabVIEW graphical development environment to Mobile devices so you can create applications that run on Windows
More informationGetting Started with IVI Drivers
Getting Started with IVI Drivers Your Guide to Using IVI with Visual C# and Visual Basic.NET Version 1.1 Copyright IVI Foundation, 2011 All rights reserved The IVI Foundation has full copyright privileges
More informationAntelope Enterprise. Electronic Documents Management System and Workflow Engine
Antelope Enterprise Electronic Documents Management System and Workflow Engine Antelope Enterprise v4 High Availability Edition Information in this document applies to the Antelope Enterprise v4 High Availability.
More informationINTRODUCTION... 3 WHAT IS LXI?... 3 NETWORK BASICS... 4 LXI VS. GPIB... 5 LXI CORE FEATURES... 6 INTERCHANGEABLE VIRTUAL INSTRUMENT (IVI) DRIVERS...
Table of Contents INTRODUCTION... 3 WHAT IS LXI?... 3 NETWORK BASICS... 4 LXI VS. GPIB... 5 LXI CORE FEATURES... 6 INTERCHANGEABLE VIRTUAL INSTRUMENT (IVI) DRIVERS... 7 WHAT IS IVI?... 7 WHAT ARE IVI DRIVERS?...
More informationThe Complete Performance Solution for Microsoft SQL Server
The Complete Performance Solution for Microsoft SQL Server Powerful SSAS Performance Dashboard Innovative Workload and Bottleneck Profiling Capture of all Heavy MDX, XMLA and DMX Aggregation, Partition,
More informationLabWindows /CVI. Instrument Driver Developers Guide. Instrument Driver Developers Guide. LabWindows/CVI Instrument Driver Developers Guide
TM TM LabWindows /CVI Instrument Driver Developers Guide Instrument Driver Developers Guide LabWindows/CVI Instrument Driver Developers Guide April 2003 Edition Part Number 370699A-01 Support Worldwide
More informationA closer look at HP LoadRunner software
Technical white paper A closer look at HP LoadRunner software Table of contents Sizing up the system 2 The limits of manual testing 2 A new take on testing: the HP LoadRunner solution 3 The HP LoadRunner
More informationThis document describes how the Meraki Cloud Controller system enables the construction of large-scale, cost-effective wireless networks.
This document describes how the Meraki Cloud Controller system enables the construction of large-scale, cost-effective wireless networks. Copyright 2009 Meraki, Inc. All rights reserved. Trademarks Meraki
More informationGetting Started Guide
Getting Started Guide Your Guide to Getting Started with IVI Drivers Revision 1.2 Copyright IVI Foundation, 2012 All rights reserved The IVI Foundation has full copyright privileges of the IVI Getting
More informationNetBeans IDE Field Guide
NetBeans IDE Field Guide Copyright 2005 Sun Microsystems, Inc. All rights reserved. Table of Contents Introduction to J2EE Development in NetBeans IDE...1 Configuring the IDE for J2EE Development...2 Getting
More informationUsing Entrust certificates with Microsoft Office and Windows
Entrust Managed Services PKI Using Entrust certificates with Microsoft Office and Windows Document issue: 1.0 Date of issue: May 2009 Copyright 2009 Entrust. All rights reserved. Entrust is a trademark
More informationMAGENTO HOSTING Progressive Server Performance Improvements
MAGENTO HOSTING Progressive Server Performance Improvements Simple Helix, LLC 4092 Memorial Parkway Ste 202 Huntsville, AL 35802 sales@simplehelix.com 1.866.963.0424 www.simplehelix.com 2 Table of Contents
More informationIntroduction to Simulink & Stateflow. Coorous Mohtadi
Introduction to Simulink & Stateflow Coorous Mohtadi 1 Key Message Simulink and Stateflow provide: A powerful environment for modelling real processes... and are fully integrated with the MATLAB environment.
More informationGetting Started with the LabVIEW Mobile Module Version 2009
Getting Started with the LabVIEW Mobile Module Version 2009 Contents The LabVIEW Mobile Module extends the LabVIEW graphical development environment to Mobile devices so you can create applications that
More informationService-Oriented Cloud Automation. White Paper
Service-Oriented Cloud Automation Executive Summary A service-oriented experience starts with an intuitive selfservice IT storefront that enforces process standards while delivering ease and empowerment
More informationDevelopment Hints and Best Practices for Using Instrument Drivers
Application Note Juergen Engelbrecht 17-Jan-13-1MA153_11e Development Hints and Best Practices for Using Instrument Drivers Application Note Products: Instrument Drivers This document answers frequently
More informationGetting Started with Kanban Paul Klipp
Getting Started with Kanban Paul Klipp kanbanery 2 Contents 3/ Getting Started with Kanban 4/ What is Kanban? 7/ Using Kanban Does kanban apply to me? How can it help me? What will I have to change? 10/
More informationIndustry White Paper. Ensuring system availability in RSView Supervisory Edition applications
Industry White Paper Ensuring system availability in RSView Supervisory Edition applications White Paper Ensuring system availability in RSView Supervisory Edition applications Rockwell Software, Visualization
More informationCisco TelePresence Management Suite Extension for Microsoft Exchange Version 4.0.3
Cisco TelePresence Management Suite Extension for Microsoft Exchange Version 4.0.3 Software Release Notes Revised September 2014 Contents Introduction 1 Changes to interoperability 1 Product documentation
More informationHow to Use Rohde & Schwarz Instruments in MATLAB Application Note
How to Use Rohde & Schwarz Instruments in MATLAB Application Note Products: Rohde & Schwarz Instrument Drivers This application note outlines different approaches for remote-controlling Rohde & Schwarz
More informationIndustrialIT System 800xA Engineering
IndustrialIT System 800xA Engineering Overview Features and Benefits Integrated Engineering Environment: Supports the engineering of the entire extended automation system from field devices to plant management
More informationThe Evolution of Load Testing. Why Gomez 360 o Web Load Testing Is a
Technical White Paper: WEb Load Testing To perform as intended, today s mission-critical applications rely on highly available, stable and trusted software services. Load testing ensures that those criteria
More informationOrchestrating Document and Media Management using CMIS
Orchestrating Document and Media Management using CMIS Technical Note - Integrating ActiveVOS with Alfresco CMIS Services AN ACTIVE ENDPOINTS TECHNICAL NOTE 2009 Active Endpoints Inc. ActiveVOS is a trademark
More informationManage Software Development in LabVIEW with Professional Tools
Manage Software Development in LabVIEW with Professional Tools Introduction For many years, National Instruments LabVIEW software has been known as an easy-to-use development tool for building data acquisition
More informationOSA-RTS 2 2015. 2 0 2 1 0 5 1 5 SPHE H RE R A A
SPHEREA Technology National Instruments Automated Test Summit 2 July 2015. Presentation: Tools Overview OSA-RTS Module Presenter: Chris Gorringe. SPHEREA: A GLOBAL COMPANY SPECIALISING IN TEST SYSTEMS
More informationCisco TelePresence Management Suite Extension for Microsoft Exchange Version 4.0.1
Cisco TelePresence Management Suite Extension for Microsoft Exchange Version 4.0.1 Software Release Notes May 2014 Contents Introduction 1 Changes to interoperability 1 Product documentation 2 New features
More informationTutorial: BlackBerry Object API Application Development. Sybase Unwired Platform 2.2 SP04
Tutorial: BlackBerry Object API Application Development Sybase Unwired Platform 2.2 SP04 DOCUMENT ID: DC01214-01-0224-01 LAST REVISED: May 2013 Copyright 2013 by Sybase, Inc. All rights reserved. This
More informationEnd Your Data Center Logging Chaos with VMware vcenter Log Insight
End Your Data Center Logging Chaos with VMware vcenter Log Insight By David Davis, vexpert WHITE PAPER Table of Contents Deploying vcenter Log Insight... 4 vcenter Log Insight Usage Model.... 5 How vcenter
More informationSystem Center Configuration Manager 2007
System Center Configuration Manager 2007 Software Distribution Guide Friday, 26 February 2010 Version 1.0.0.0 Baseline Prepared by Microsoft Copyright This document and/or software ( this Content ) has
More informationHASP Troubleshooting Guide
HASP Troubleshooting Guide Corporate office: Trimble Geospatial Division 10368 Westmoor Drive Westminster, CO 80021 USA www.trimble.com Copyright and trademarks: 2005-2013, Trimble Navigation Limited.
More informationHP Operations Orchestration Software
HP Operations Orchestration Software Software Version: 9.00 HP Project and Portfolio Management Integration Guide Document Release Date: June 2010 Software Release Date: June 2010 Legal Notices Warranty
More informationThe Use of Hardware Abstraction Layers in Automated Calibration Software
The Use of Hardware Abstraction Layers in Automated Calibration Software Speaker: Logan Kunitz Author: Rishee Bhatt National Instruments 11500 N. Mopac Expwy. Austin, TX 78759-3504 (512) 683-6944 Rishee.Bhatt@ni.com
More informationA Guide To Evaluating a Bug Tracking System
A Guide To Evaluating a Bug Tracking System White Paper By Stephen Blair, MetaQuest Software Published: October, 2004 Abstract Evaluating a bug tracking system requires that you understand how specific
More informationThe Benefits of Utilizing a Repository Manager
Sonatype Nexus TM Professional Whitepaper The Benefits of Utilizing a Repository Manager An Introduction to Sonatype Nexus TM Professional SONATYPE www.sonatype.com sales@sonatype.com +1 301-684-8080 12501
More informationReconfigurable Architecture Requirements for Co-Designed Virtual Machines
Reconfigurable Architecture Requirements for Co-Designed Virtual Machines Kenneth B. Kent University of New Brunswick Faculty of Computer Science Fredericton, New Brunswick, Canada ken@unb.ca Micaela Serra
More informationLabVIEW Advanced Programming Techniques
LabVIEW Advanced Programming Techniques SECOND EDITION Rick Bitter Motorola, Schaumburg, Illinois Taqi Mohiuddin MindspeedTechnologies, Lisle, Illinois Matt Nawrocki Motorola, Schaumburg, Illinois @ CRC
More informationProviding Patch Management With N-central. Version 7.1
Providing Patch Management With N-central Version 7.1 Contents Patch Management 3 Introduction 3 Monitoring for Missing Patches 3 Setting up Patch Management in N-central 4 Adding a WSUS Server to N-central
More informationDevelopment Best Practices
Development Best Practices 0 Toad Toad for Oracle v.9.6 Configurations for Oracle Standard Basic Toad Features + Team Coding + PL/SQL Profiler + PL/SQL Debugging + Knowledge Xpert PL/SQL and DBA Toad for
More informationDevelopment Hints and Best Practices for Using Instrument Drivers
Application Note Juergen Engelbrecht 12-Jan-15-1MA153_14e Development Hints and Best Practices for Using Instrument Drivers Application Note Products: Instrument Drivers This document answers frequently
More informationPhysical Security Information Management: A Technical Perspective
P R O X I M E X C O R P O R A T I O N W H ITE PAPER Physical Security Information Management: A Technical Perspective By Ken Cheng 1 Physical Security Information Management: A Technical Perspective Physical
More informationImage Acquisition Toolbox Adaptor Kit User's Guide
Image Acquisition Toolbox Adaptor Kit User's Guide R2015b How to Contact MathWorks Latest news: www.mathworks.com Sales and services: www.mathworks.com/sales_and_services User community: www.mathworks.com/matlabcentral
More informationZend and IBM: Bringing the power of PHP applications to the enterprise
Zend and IBM: Bringing the power of PHP applications to the enterprise A high-performance PHP platform that helps enterprises improve and accelerate web and mobile application development Highlights: Leverages
More informationSynthetic Monitoring Scripting Framework. User Guide
Synthetic Monitoring Scripting Framework User Guide Please direct questions about {Compuware Product} or comments on this document to: APM Customer Support FrontLine Support Login Page: http://go.compuware.com
More informationAzure Scalability Prescriptive Architecture using the Enzo Multitenant Framework
Azure Scalability Prescriptive Architecture using the Enzo Multitenant Framework Many corporations and Independent Software Vendors considering cloud computing adoption face a similar challenge: how should
More information14.1. bs^ir^qfkd=obcib`qflk= Ñçê=emI=rkfuI=~åÇ=léÉåsjp=eçëíë
14.1 bs^ir^qfkd=obcib`qflk= Ñçê=emI=rkfuI=~åÇ=léÉåsjp=eçëíë bî~äì~íáåö=oéñäéåíáçå=ñçê=emi=rkfui=~åç=lééåsjp=eçëíë This guide walks you quickly through key Reflection features. It covers: Getting Connected
More informationTesting Intelligent Device Communications in a Distributed System
Testing Intelligent Device Communications in a Distributed System David Goughnour (Triangle MicroWorks), Joe Stevens (Triangle MicroWorks) dgoughnour@trianglemicroworks.com United States Smart Grid systems
More informationTutorial: Mobile Business Object Development. SAP Mobile Platform 2.3 SP02
Tutorial: Mobile Business Object Development SAP Mobile Platform 2.3 SP02 DOCUMENT ID: DC01927-01-0232-01 LAST REVISED: May 2013 Copyright 2013 by Sybase, Inc. All rights reserved. This publication pertains
More informationAutomating Software License Management
Automating Software License Management Automating license management saves time, resources, and costs. It also consistently produces high quality data and a documentable method for mapping software licenses
More informationBuilding A Very Simple Web Site
Sitecore CMS 6.2 Building A Very Simple Web Site Rev 100601 Sitecore CMS 6. 2 Building A Very Simple Web Site A Self-Study Guide for Developers Table of Contents Chapter 1 Introduction... 3 Chapter 2 Building
More informationSilect Software s MP Author
Silect MP Author for Microsoft System Center Operations Manager Silect Software s MP Author User Guide September 2, 2015 Disclaimer The information in this document is furnished for informational use only,
More informationProviding Patch Management With N-central. Version 7.2
Providing Patch Management With N-central Version 7.2 Contents Patch Management 3 Introduction 3 Monitoring for Missing Patches 3 Setting up Patch Management in N-central 4 Adding a WSUS Server to N-central
More informationAdvantages of Amanda over Proprietary Backup
Advantages of Amanda over Proprietary Backup Gregory Grant Revision 02 Abstract This white paper discusses how Amanda compares to other backup products. It will help you understand some key Amanda differences,
More informationLEVERAGE VBLOCK SYSTEMS FOR Esri s ArcGIS SYSTEM
Leverage Vblock Systems for Esri's ArcGIS System Table of Contents www.vce.com LEVERAGE VBLOCK SYSTEMS FOR Esri s ArcGIS SYSTEM August 2012 1 Contents Executive summary...3 The challenge...3 The solution...3
More informationDEPLOYMENT GUIDE Version 2.1. Deploying F5 with Microsoft SharePoint 2010
DEPLOYMENT GUIDE Version 2.1 Deploying F5 with Microsoft SharePoint 2010 Table of Contents Table of Contents Introducing the F5 Deployment Guide for Microsoft SharePoint 2010 Prerequisites and configuration
More informationSystem Center Configuration Manager
System Center Configuration Manager Software Update Management Guide Friday, 26 February 2010 Version 1.0.0.0 Baseline Prepared by Microsoft Copyright This document and/or software ( this Content ) has
More informationIBM TSM DISASTER RECOVERY BEST PRACTICES WITH EMC DATA DOMAIN DEDUPLICATION STORAGE
White Paper IBM TSM DISASTER RECOVERY BEST PRACTICES WITH EMC DATA DOMAIN DEDUPLICATION STORAGE Abstract This white paper focuses on recovery of an IBM Tivoli Storage Manager (TSM) server and explores
More informationNVIDIA CUDA GETTING STARTED GUIDE FOR MICROSOFT WINDOWS
NVIDIA CUDA GETTING STARTED GUIDE FOR MICROSOFT WINDOWS DU-05349-001_v6.0 February 2014 Installation and Verification on TABLE OF CONTENTS Chapter 1. Introduction...1 1.1. System Requirements... 1 1.2.
More informationUser Guide - English. Embedded MegaRAID Software
User Guide - English Embedded MegaRAID Software April 2015 Comments Suggestions Corrections The User Documentation Department would like to know your opinion of this manual. Your feedback helps us optimize
More informationimc FAMOS 6.3 visualization signal analysis data processing test reporting Comprehensive data analysis and documentation imc productive testing
imc FAMOS 6.3 visualization signal analysis data processing test reporting Comprehensive data analysis and documentation imc productive testing imc FAMOS ensures fast results Comprehensive data processing
More informationEmbedded BI made easy
June, 2015 1 Embedded BI made easy DashXML makes it easy for developers to embed highly customized reports and analytics into applications. DashXML is a fast and flexible framework that exposes Yellowfin
More informationAbout This Guide... 4. Signature Manager Outlook Edition Overview... 5
Contents About This Guide... 4 Signature Manager Outlook Edition Overview... 5 How does it work?... 5 But That's Not All...... 6 And There's More...... 6 Licensing... 7 Licensing Information... 7 System
More informationRSA Authentication Manager 7.1 Microsoft Active Directory Integration Guide
RSA Authentication Manager 7.1 Microsoft Active Directory Integration Guide Contact Information Go to the RSA corporate web site for regional Customer Support telephone and fax numbers: www.rsa.com Trademarks
More informationCisco TelePresence Management Suite Extension for Microsoft Exchange Version 4.0
Cisco TelePresence Management Suite Extension for Microsoft Exchange Version 4.0 Software Release Notes May 2014 Contents Introduction 1 Changes to interoperability 1 Product documentation 1 New features
More informationCitrix EdgeSight for Load Testing User s Guide. Citrx EdgeSight for Load Testing 2.7
Citrix EdgeSight for Load Testing User s Guide Citrx EdgeSight for Load Testing 2.7 Copyright Use of the product documented in this guide is subject to your prior acceptance of the End User License Agreement.
More informationSite Maintenance Using Dreamweaver
Site Maintenance Using Dreamweaver As you know, it is possible to transfer the files that make up your web site from your local computer to the remote server using FTP (file transfer protocol) or some
More information5-Bay Raid Sub-System Smart Removable 3.5" SATA Multiple Bay Data Storage Device User's Manual
5-Bay Raid Sub-System Smart Removable 3.5" SATA Multiple Bay Data Storage Device User's Manual www.vipower.com Table of Contents 1. How the SteelVine (VPMP-75511R/VPMA-75511R) Operates... 1 1-1 SteelVine
More informationVERITAS NetBackup BusinesServer
VERITAS NetBackup BusinesServer A Scalable Backup Solution for UNIX or Heterogeneous Workgroups V E R I T A S W H I T E P A P E R Table of Contents Overview...................................................................................1
More informationCA Process Automation for System z 3.1
PRODUCT SHEET CA Process Automation for System z CA Process Automation for System z 3.1 CA Process Automation for System z helps enable enterprise organizations to design, deploy and administer automation
More informationVAIL-Plant Asset Integrity Management System. Software Development Process
VAIL-Plant Asset Integrity Management System Software Development Process Document Number: VAIL/SDP/2008/008 Engineering For a Safer World P u b l i c Approved by : Ijaz Ul Karim Rao Revision: 0 Page:2-of-15
More informationProtect Microsoft Exchange databases, achieve long-term data retention
Technical white paper Protect Microsoft Exchange databases, achieve long-term data retention HP StoreOnce Backup systems, HP StoreOnce Catalyst, and Symantec NetBackup OpenStorage Table of contents Introduction...
More informationGetting Started with IVI-COM and Python for the Lambda Genesys Power Supply
Page 1 of 16 1. Introduction This is a guide to writing programs using the Python language with the Lambda IVI-COM drivers. Python is praised for being simple but powerful. It is open-source and may be
More informationKaseya Server Instal ation User Guide June 6, 2008
Kaseya Server Installation User Guide June 6, 2008 About Kaseya Kaseya is a global provider of IT automation software for IT Solution Providers and Public and Private Sector IT organizations. Kaseya's
More informationMicrosoft Office System Tip Sheet
Experience the 2007 Microsoft Office System The 2007 Microsoft Office system includes programs, servers, services, and solutions designed to work together to help you succeed. New features in the 2007
More informationHow To Build A Connector On A Website (For A Nonprogrammer)
Index Data's MasterKey Connect Product Description MasterKey Connect is an innovative technology that makes it easy to automate access to services on the web. It allows nonprogrammers to create 'connectors'
More informationDistance-Learning Remote Laboratories using LabVIEW
Distance-Learning Remote Laboratories using LabVIEW Introduction Laboratories, which are found in all engineering and science programs, are an essential part of the education experience. Not only do laboratories
More informationLesson 1 Introduction to Rapid Application Development using Visual Basic
Lesson 1 Introduction to Rapid Application Development using Visual Basic RAD (Rapid Application Development) refers to a development life cycle designed to give much faster development and higher-quality
More informationStoring Measurement Data
Storing Measurement Data File I/O records or reads data in a file. A typical file I/O operation involves the following process. 1. Create or open a file. Indicate where an existing file resides or where
More informationFour Keys to Successful Multicore Optimization for Machine Vision. White Paper
Four Keys to Successful Multicore Optimization for Machine Vision White Paper Optimizing a machine vision application for multicore PCs can be a complex process with unpredictable results. Developers need
More informationRS MDM. Integration Guide. Riversand
RS MDM 2009 Integration Guide This document provides the details about RS MDMCenter integration module and provides details about the overall architecture and principles of integration with the system.
More informationOracle Siebel Marketing and Oracle B2B Cross- Channel Marketing Integration Guide ORACLE WHITE PAPER AUGUST 2014
Oracle Siebel Marketing and Oracle B2B Cross- Channel Marketing Integration Guide ORACLE WHITE PAPER AUGUST 2014 Disclaimer The following is intended to outline our general product direction. It is intended
More informationGetting Started with the Ed-Fi ODS and Ed-Fi ODS API
Getting Started with the Ed-Fi ODS and Ed-Fi ODS API Ed-Fi ODS and Ed-Fi ODS API Version 2.0 - Technical Preview October 2014 2014 Ed-Fi Alliance, LLC. All rights reserved. Ed-Fi is a registered trademark
More informationECU State Manager Module Development and Design for Automotive Platform Software Based on AUTOSAR 4.0
ECU State Manager Module Development and Design for Automotive Platform Software Based on AUTOSAR 4.0 Dhanamjayan P.R. 1, Kuruvilla Jose 2, Manjusree S. 3 1 PG Scholar, Embedded Systems, 2 Specialist,
More informationAdministrator s Guide
SEO Toolkit 1.3.0 for Sitecore CMS 6.5 Administrator s Guide Rev: 2011-06-07 SEO Toolkit 1.3.0 for Sitecore CMS 6.5 Administrator s Guide How to use the Search Engine Optimization Toolkit to optimize your
More informationWhite Paper. The Ten Features Your Web Application Monitoring Software Must Have. Executive Summary
White Paper The Ten Features Your Web Application Monitoring Software Must Have Executive Summary It s hard to find an important business application that doesn t have a web-based version available and
More informationBuilding Applications Using Micro Focus COBOL
Building Applications Using Micro Focus COBOL Abstract If you look through the Micro Focus COBOL documentation, you will see many different executable file types referenced: int, gnt, exe, dll and others.
More informationBasic Concepts. Getting Started with OpenChoicet Solutions 071-1304-01. www.tektronix.com
Basic Concepts Getting Started with OpenChoicet Solutions 071-1304-01 www.tektronix.com Copyright Tektronix. All rights reserved. Licensed software products are owned by Tektronix or its subsidiaries or
More informationGEDAE TM - A Graphical Programming and Autocode Generation Tool for Signal Processor Applications
GEDAE TM - A Graphical Programming and Autocode Generation Tool for Signal Processor Applications Harris Z. Zebrowitz Lockheed Martin Advanced Technology Laboratories 1 Federal Street Camden, NJ 08102
More information