IVI Configuration with PXI-4110 in TestStand

Hello All,
Set-Up:
PXI-1033 connected through MXI to a PC running Windows 7. LabVIEW 2014. TestStand 2014 (32-bit). PXI-4110 Power Supply and PXI-4070 DMM.
In MAX I can open both soft panels and control both units and they work great.  In LabVIEW I can control both cards as well. 
In MAX I have set up a driver and logical name for my DMM. This unit works great within TestStand using an IVI DMM step.
I then proceeded to setup the 4110 in MAX with an IVI driver and logical name. Here are my settings:
Name: ni4410_PS
Hardware: Added hardware asset and select the PS. This one is checked, no other assets are checked.
Software Module: NI-DCPower, 4110 is listed as a device that is supported.
Virtual Names: This is where I am confused, Under physical name there are four options that come up (0, 1, 2, and 3). This power supply only has 3 outputs so I am unsure why four come up. I have made 4 virtual names, one for each of the options. I named them ch0, ch1, ch2, and ch3 respectively.
When I put an IVI Power Supply step in TestStand everything seems to be working. I open the configuration window and set my values for each channel. If I try to validate the setup by unchecking simulate and click on init I do not get an error.  As soon as I clic on 'Configure' or 'Show Soft Front Panel' I get the following error:
"The IVI Configure operation failed for lgical name 'NI PS 1'. Details: Extention capability not supported by instrument driver. (Base) (-30717)"
Any information would be appreciated.  I tried playing with it for a couple hours yesterday and had a couple co workers try to help.  We are all under the assumption that this should be working.  
Thank You!!
Jesse
Solved!
Go to Solution.

Hi jesserzamora,
Have you seen this link: http://digital.ni.com/public.nsf/allkb/331F2717DBCD1F858625758200745773?OpenDocument
It discusses a similar failure with the IVI Power Supply step in TestStand. 
Julia P.

Similar Messages

  • NI DC Soft Front Panel, minorbug, minor bug with PXI-4110

    Hi
    The NI DC Soft Front Panel V14.0, with the PXI-4110, the negative voltage scroll, works as expected to -10V, but then rolls over to 0. If one changes in -1V steps, it goes.... -8, -9, -10, -1, -2 ..... instead of -8, -9, -10, -11, -12 ...
    While at it, a simple thing I miss is a on/off button for all three voltages.
    (Also, imo, it would be logical to get negative voltages with the down arrow, not up).
    My 2C
    Solved!
    Go to Solution.

    Hello Janaf,
    I fully agree with both of your statements, I have filed a Correction Action Report which you can monitor in next releases of DCPower to see if this is fixed with the SFP. Number of CAR: 512257
    I added notes that only manual insertion of numbers less than -10 works and that it was not logical to use increment arrow or up arrow to decrease the voltage output.
    Best Regards
    Jonas Mäki
    Applications Engineering
    National Instruments

  • Hardware configuration with PXI

    I need to control the operation of a chemical pump using the Labview.
    The control panel consist of:
    1. Pump, on/off
    2. Two Heaters on/off
    3. Tank level indicator, sensys co.
    4. pressure transmitter, sensys co.
    5. vibration transmitter, sensys co.
    Its first time for me. What are the parameters I should check on? What other hardware I will require?

    Hello, 
    As Christian said, the best method of obtaining the correct hardware/software that you will need for this application is through our customer service center. I would recommend having the specifications or data sheets of the sensors that you are using available to allow the customer service representative to better assist you.  Also you will need to know the power requirements to turn the pump and heaters on/off.  There are simply too many specifics that need to be addressed to try and assist over discussion forums.  
    Thank you, 
    Justin 
    Justin
    National Instruments
    Product Support Engineer - Conditioned Measurements

  • How do you configure multiple PXIe chassis to share Tclk synch with the 6672 timing module?

    Hi,
    I have two PXIe chassis, each with a number of digitizers (configured through NI-SCOPE). Each chassis has a PXIe 6672 timing module. I have downloaded the sample VI from:
    http://zone.ni.com/devzone/cda/epd/p/id/5254
    which deals with PXI chassis. My question is this: in the VIs at the above link (and in fact all VIs I've seen for using the 6672 for sharing triggers), the VI needs access to the resource identifiers for both Master and Slave timing modules, how do I access the (remote) slave resource identifier from the master chassis? I feel like I'm missing something obvious, but can I do this using just an ethernet connection, or do I need another module to enable the master chassis to view the devices on the slave chassis in MAX? 
    Thanks for any help you can provide,
    Cillian

    Those example VIs are written to be used when a single host PC is controlling multiple chassis so there is just one computer running the program.  Since both of your chassis have their own controllers it will be necessary to run a program on each (one as master, the other as slave).  You can modify the code from that example to create and Master and Slave VIs.  For the Master you will call the VIs as specified in case 0 of the example; for the Slave you will call the VIs as specified in the default, 1 case of the example.
    You will also want to send a signal from the Master to the Slave to let the Slave know that the clock is being generated.  You could use TCP/IP or a PFI line to do this.  The basic order of events should be as follows:
    1. VI runs on Slave to configure it to accept a clock.
    2. VI runs on Master to begin outputing the clock.
    3. Master sends a signal to Slave to let it know that the clock is being generated.
    4. Continue with the rest of your program.
    Let me know if you have any questions about this.
    Barron
    Applications Engineering
    National Instruments

  • Can I install Windows onto a PXI controller originally configured with Pharlap?

    We recently upgraded several PXI systems, replacing PXI-8196 controllers with PXI-8106 controllers. The old PXI-8196 controllers were running RTOS, but we would like to install Windows XP on them for use as ancillary DAQ systems.
    Is there any reason why this would not be possible? Are there any hardware/BIOS differences between stricly-RT PXI systems and Windows/Dual-Boot PXI systems? I imagine we'd be replacing the hard drives (the stock 20GB's probably wouldn't cut it for a windows machine), so we could make sure that they're formatted as NTFS instead of FAT32. But once we have the new drives, we should be able to install Windows XP without any problems, right?

    Hi Phil,
    The only catch is that our RT controllers do not come with a license for Windows, you would need to get your own, other than that, the hardware is perfectly capable of running windows. Keep in mind that dual boot is also an option:
    Dual-Booting Windows XP and LabVIEW RT on a PXI Controller
    Thanks
    Scott M.
    Applications Engineer
    National Instruments

  • What is the proper way to close all open sessions of a NI PXI-4110 for a given Device alias?

    I've found that, when programming the NI PXI-4110 that, if a the VI "niDCPower Initialize With Channels VI" (NI-DCPower pallette) is called with a device
    alias that all ready has one or more sessions open (due to an abort or other programming error) a device reference results from the reference out that has a (*) where "*" is post-fixed to the device reference where and is an integer starting that increments with each initialize call. In my clean up, I would like to close all open sessions. For example, let's said the device alias is "NIPower_1" in NI Max, and there are 5 open sessions; NIPower_1, NIPower_1 (1), NIPower_1 (2), NIPower_1 (3), and NIPower_1 (4). A simple initialize or reset (using niDCPower Initialize With Channels VI, or, niDCPower Initialize With Channels VI, etc.) What is the proper way to close all open sessions?
    Thanks in advance. Been struggleing with this for days!

    When you Initialize a session to a device that already has a session open, NI-DCPower closes the previous session and returns a new one. You can verify this very easily: try to use the first session after the second session was opened.
    Unfortunately, there is a small leak and that is what you encountered: the previous session remains registered with LabVIEW, since we unregister inside the Close VI and this was never called. So the name of the session still shows in the control like you noted: NIPower_1, NIPower_1 (1), NIPower_1 (2), NIPower_1 (3), and NIPower_1 (4), etc.
    There may be a way to iterate over the registered sessions, but I couldn't find it. However, you can unregister them by calling "IVI Delete Session". Look for it inside "niDCPower Close.vi". If you don't have the list of open sessions, but you have the device name, then you can just append (1), (2) and so forth and call "IVI Delete Session" in a loop. There's no problem calling it on sessions that were never added.
    However - I consider all this a hack. What you should do is write code that does not leak sessions. Anything you open, you should close. If you find yourself in a situation where there are a lot of leaked sessions during development, relaunching LabVIEW will clear it out. If relaunching LabVIEW is too much of an annoyance, then write a VI that does what I described above and run it when needed. You can even make it "smarter" by getting the names of all the NI-DCPower devices in your system using the System Configuration or niModInst APIs.
    Hope this helps.
    Marcos Kirsch
    Principal Software Engineer
    Core Modular Instruments Software
    National Instruments

  • Error -1074118625 with PXI-4071 and PXI-2527

    When using the LabVIEW IVI drivers for PXI-4071 and PXI-2527, I receive an error -1074118625 in TestStand.  The sequence initializes the MUX, init DMM, connects the MUX, waits for debounce, and then upon reading from the DMM, I receive this error.
    Error: niDMM Read Waveform (waveform data).viExplanation could not be found for the requested status code.
    Verify that the requested status code is correct.
    [Error Code: -1074118625, User-defined error code.]
    This sequence of events is successfully used multiple times elsewhere in the TestStand.  This error does not appear in any knowledgebase article nor in any help.  Any explanation would be greatly appreciated.
    Solved!
    Go to Solution.

    I found this with google that seems like it might apply:
    http://digital.ni.com/public.nsf/allkb/A593DEBFD86A69C68625727900748EEC

  • Missing IVI configuration in MAX

    Could somebody please enlighten me as to the specific combination of spells, incantations, gestures, and begging that will get the IVI configuration sub-tree to appear in NI-MAX?
    It has disappeared on me. Usually, I can reinstall stuff (MAX, the IVI Engine, etc) in various orders and eventually get it back again. But I seem to have lost the magic touch now.
    I swear to God, as soon as I find a few spare cycles, this whole IVI thing is out the window. It's just not worth the hassle. I can write my own instrument drivers. It's really not that hard.
    - Ron

    I'm running MAX 3.0.2.3005, which came with NI 488.2 2.20 (the last version I can find that doesn't have the new MAX.) I'm trying to recreate the configuration that I had working before. In particular, I'm trying to avoid the new IVI Compliance Package, because I know it doesn't let me set the voltage attribute on a power supply using the TestStand IVI Tools step.
    The file you mention does not exist. Various attempts at installing, removing, reinstalling and repairing NI 488.2 and IVI Engine 1.83 don't seem to create it. But there is no error message to report. Actually, the entire IVI Engine is apparently not being installed. Programs that use the IVI engine can't find it either.

  • Triggerring PXI-4110 to measure 1 current value while HSDIO PXI-6552 generating waveform

    Hi,
    Some question about PXI-4110 to measure current while PXI-6552 is generating the waveform. 
    1. Let say, I need to measure 3 points of current values, i.e. while PXI-6552 is generating sample-1000, 2000 and 3500. On the edge of sample 1000,2000 and 3500, the PXI-6552 will send a pulse via PFI line or via PXI backplane trigger line. My question is, is it possible to trigger PXI-4110 (hardware trigger or software trigger) to measure current values at these points ?
    2. Let say I need to measure the current on 0ms (start of waveform generation by PXI-6552) , 1ms, 2ms, 3ms, 4ms... and so on for 1000 points of measurement, code diagram as shown at the figure below. It is possible for the VI "niDCPower Measure Multiple" to measure exactly at 1ms, 2ms, 3ms .. ? How much time will have to spend to complete acquire 1 point of measurement by "niDCPower Measure Multiple" ?
    Thanks for viewing this post. Your advice on hardware used or software method is much appreciated. Thanks in advance.  
    Message Edited by engwei on 02-02-2009 04:24 AM
    Attachments:
    [email protected] ‏46 KB

    Hi engwei,
    1. Unfortunately, the 4110 does not support hardware triggering. Therefore you cannot implement direct triggering through the backplane or anything like that. However, there are a couple of possible workarounds you can try:
    a) Use software triggering: Say your 6552 is generating in one while loop, and your 4110 is to measure in another while loop. You can use a software syncrhonization method like notifiers to send a notification to your 4110 loop when your 6552 has generated the desired sample. This method, however, will not be very deterministic because the delay between the trigger and the response depends on your processor speed and load. Therefore, if you have other applications running in the background (like antivirus) it will increase the delay.
    b) Use hardware triggering on another device: If you have another device that supports hardware triggering (like maybe an M-series multifunction DAQ module), you can configure this device to be triggered by a signal from the 6552, perform a very quick task (like a very short finite acquisition) then immediately execute the DCPower VI to perform the measurement. The trigger can be configured to be re-triggerable for multiple usage. This will most likely have a smaller time delay then the first option, but there will still be a delay (the time it takes to perform the short finite acquisiton on the M-series). Please refer to the attached screenshot for an idea of how to implement this.
    2. To make your 4110 measure at specific time intervals, you can use one of the methods discussed above. As for how long it will take to acquire 1 measurement point, you may find this link helpful: http://zone.ni.com/devzone/cda/tut/p/id/7034
    This article is meant for the PXI-4130 but the 4110 has the same maximum sampling rate (3 kHz) and so the section discussing the speed should apply for both devices.
    Under the Software Measurement Rate section, it is stated that the default behavior of the VI is to take an average of 10 samples. This corresponds to a maximum sampling rate of 300 samples/second. However, if you configure it to not do averaging (take only 1 sample) then the maximum rate of 3000 samples/second can be achieved.
    It is also important to note that your program can only achieve this maximum sampling rate if your software loop takes less time to execute than the actual physical sampling. For example, if you want to sample at 3000 samples/second, that means that taking one sample takes 1/3000 seconds or 333 microseconds. If you software execution time is less than 333 microseconds, then you can achieve this maximum rate (because the speed is limited by the hardware, not the software). However, if your software takes more than 333 microseconds to execute, then the software loop time will define the maximum sampling rate you can get, which will be lower than 3000 samples/second.
    I hope this answers your question.
    Best regards,
    Vern Yew
    Applications Engineer, NI ASEAN
    Best regards,
    Vern Yew
    Applications Engineer
    Attachments:
    untitled.JPG ‏18 KB

  • Problems with PXI after motherboar​d replacemen​t

    Hello,
    My PXI system consists
    of PXI-1045, PXI-8360 and five NI
    PXI intruments (5152, 4065, 6552, 2532, 5404). I was working with this
    system without problems for a long time. However, the motherboard of my
    PC had a specific problem with the ethernet connenction and I decided to
    replace the motherboard with a new one (same model). After the
    replacement (the pc finally was fully functional), I tried to power on
    the PXI chassis, but  I couldn't "see" any module in PXI chassism, using
    the MAX. I must tell thatI didn't change the hard disk of the
    pc, or anything else just the motherboard.After some experiments, I
    finally fix the probrem with the following solution: First I unplugged
    all the modules from PXI chassis. After that, I plugged one module and I
    reboot the pc. After that I plugged the second one module and I reboot
    the pc. And so on...
    This was the only solution
    that I found in order to indentify all the modules of the PXI chassis.
    My question is why happend this
    thing? Where are the PXI modules' adresses stored? Also, is the
    procedure I used correct, or I had to do something else in order to make
    the system work?

    Hello,
    Im glad that your system is up and running, ideally that behavior should not have occured. For future troubleshooting, also check Windows Device Manager to see if your devices show up if MAX does not detect them (Windows may have initially failed to detect the hardware). In a PXI system, the pxisys.ini file provides mappings from PCI logical addresses (PCI bus, device, and function numbers) to corresponding PXI slot numbers, allowing device driver software to identify the slot of a PXI module. There is a unique pxisys.ini file for every combination of PXI chassis and controller. See the link provided below for additional information regarding how to configure PXI systems in MAX.
    1. Configuring Your PXI System in MAX 3.x and Above: http://zone.ni.com/devzone/cda/tut/p/id/11136
    Best regards,
    Ali M
    Applications Engineer
    National Instruments

  • How do you configure multiple PXI 1011 chassis' in MAX?

    I have two PXI 1011 chassis'. The first has the MXI-3 card hooked to a MXI-3 PC card through fiber. The second chassis has an 8176 controller and the 6052e GPIB card. Both chassis have multiple SCXI cards. The problem is the configuration in MAX. MAX 3 picks up the MXI-3 card and chassis with all the SCXI modules, but will not pick up the 8176 chassis. This 8176 is hooked to the PC through a CAT5 ethernet switch.I know there are problems with multiple chassis configuration, but I'm sure I'm just missing something here.

    Hi,
    So it sounds like you have two PXI systems that are not connected or related to each other, is that right? Since your PXI chassis connected via MXI-3 is working fine, we�ll take that out of the equation.
    It sounds like you are trying to configure your PXI-8176 system as a Remote System through an Ethernet connection. Is your PXI-8176 running Windows (if so which version) or Real-Time (RT) operating system?
    If you are running Windows XP on the PXI-8176 and also on your computer you can use XP Remote Desktop to control your PXI-8176 system through Ethernet (see the following link for information on that):
    http://digital.ni.com/public.nsf/websearch/C074C33​F4DE3FA5186256D3D007788DA?OpenDocument
    Another option is to use Remote Device Access (RDA) to cont
    rol your SCXI modules and DAQ board (6052E). RDA will only work with Traditional NI-DAQ, it is not supported in NI-DAQmx. I�ve included a couple of links for KB�s that have more information on RDA for you.
    http://digital.ni.com/public.nsf/websearch/3a4d2f5​f4354e53a862568c0006a8bc0?OpenDocument
    http://digital.ni.com/public.nsf/websearch/5CC9792​C6CD4A34C862565BC0072D5DF?OpenDocument
    If you ordered your controller only with Real-Time on it you can use the following document to configure and troubleshoot your PXI-8176 RT system.
    http://www.ni.com/support/install/install_configur​e_6.htm
    I hope this helps you.
    Regards,
    Doug K.
    National Instruments

  • Measuring sub 125 microamps using PXI 4110 - Is it possible?

    I have a question concerning the PXI 4110.  We are trying to use this card to both provide voltage to a device while at the same time using it to monitor the real time current being supplied.  What we have found that it is capable of providing voltage from 0 to 6 volts, but have not been able to read below ~500 micro-amps.  The data sheet says it has a resolution of 0.01 ma or 10 micro amps, but we have not been able to get the card to read consistently under the 500 micro-amps.
    Is there a minimum current draw required before the 10 micro-amp range becomes true? 
    Here is what we are trying to monitor using this card:
    Voltage supplied between 3.5 to 6 volts.
    When device is asleep, current draw is between 50 to 100 micro amps.
    When device is awake, current draw can be as high as 100 mili-amps.
    Will this card work?  Is there a better solution to this? 
    Thanks

    Hi John,
    Thanks for the additional information. Based on your sampling rate you should be fine with a software or hardware timed device. The answer that you will need to determine is how accurately you need to measure your sleep current. The issue is that you do not know the mode that your DUT will be in to change your current range. At this time our power supplies have output and measure ranges that are coupled together. This means that when you change to a lower range your output current will be limited to the max of that range, which can be an issue when the DUT 'wakes up'.
    I would recommend is to select a device that can remain in the higher current range (100mA or greater) and have the measurement capability that meets your needs. You would need to know that you would need to measure the sleep current within +/- X uA. When selecting the device you will then want to look at its measure accuracy on the range you will use. The calculation would be +/- (Measurement*Gain Error + Offset Error). You will find that the largest portion of the error will be offset due to the range you will be using. You also need to take into account the resolution of the instrument because that is the smallest possible change you can measure
    One comment on offset error is that for a given test setup/temperature/humidity/etc and test voltage it will stay fairly constant. This means that you can characterize the offset of your system if all of those factors remain constant. I would recommend that you would set up your test, including all fixturing/cabling excluding the DUT. You can set the supply to your test voltage and measure the current. In this setup the ideal current would be 0uA because it is an 'open', but due to leakages in the system there will be an offset. You can take this reading as a baseline 'zero' and subtract it from future readings to improve your measurements. You will want to be careful of Dielectric Absorption (DA) because it can mislead you when making measurements like this, but it is less of an issue when talking about uA and more of an issue when measuring pA. It would be a good idea to repeat this characterization periodically to ensure that your measurements are accurate, ideally once per DUT, but you can scale that back as necessary.
    I hope this is helpful. It is a good idea to evaluate the hardware in your test setup to ensure that the measurements meet your needs. I would also add the PXI-4132 to your list of options to consider for its 100mA range. I think that these other devices would be better than the PXI-4110 in your application because of the low current measurements you need. If you can use the additional channels the PXIe-4140/4141 are good options, if not the PXI-4132 would be a good option. You should also consider the different connectors for PXI vs PXIe and what will work for your chassis.  
    Steve B

  • I'm having trouble with a multi channel acquisition and download with PXI-5922

    I am having trouble with getting data out from both channels of a PXI-5922.  My software seems to be working, but when I do the fetch there is no data for the second channel.  I am using the same format for all of the channelList inputs (0,1).  I've checked the instrument handles and anything else I can think of, but this is my first time trying to collect data on 2 channels of a digitizer.  Any help would be appreciated.

    Hi schliepe,
    Try checking your code against an existing example. The
    Developer Zone Example: Independent
    Channel Configuration with NI-SCOPE is a good VI to reference. Also note
    that there are several examples that come with the NI-SCOPE driver. They can be
    found in Windows by going to Start »
    Programs » National Instruments » NI SCOPE » Examples. Additionally, if you find that the examples are not working either, verify that both channels are functioning by running the
    NI-SCOPE Soft Front Panel.
    Please post back if you have any questions. Have a great
    day!
    Ryan D.
    District Sales Manager for Boston & Northern New England
    National Instruments

  • CTR works with PXI 8196,PXIe 8102, fails with PXIe 8100 - why?

    My client has reported a problem.  
    For years he has used a PXI 8196 RT Controller with PXI 6602 Counter card and my software has given good results.  They have 20+ of these systems and they have worked well.
    Now they are moving to PXIe 810x controllers, for cost reasons.
    WIth a PXIe 8102, the same code also works perfectly, measuring total counts over a period, as well as instantaneous frequency.
    With a PXIe 8100 - the exact same code reports DIFFERENT answers. The reported frequency is always 1% HIGHER than actual (For example, a known 4500 Hz input is reported as 4500 Hz on 8102, but as 4545 Hz on 8100.
    This happens on any channel, and swapping just the controller will make the problem come and go.
    Here is the CONFIGURE code, where the channels are set up (again, this has worked for years).
    Here is the SAMPLE code:
    Basically the CONFIG code configures the thing to count edges.   I do this because they need an accurate count over a 20-minute period, in addition to instantaneous frequency readings.
    The AVG TIME is a user-settable number defining how long a period to average, when showing the "instantaneous" frequency.
    So, I create a buffer for N samples, corresponding to that period.
    At SAMPLE time, I read the counter.  I replace the oldest value in the buffer with the newest, then subtract the newest - oldest to get the total counts in the sample period.
    The PULSES PER COUNT item is a scaler, to account for a 60-tooth wheel, or something.
    So, this same code has worked perfectly for years, until I plug an 8100 code in.  Then the result changes by 1 %, and EXACTLY 1%?
    The CPU burden on the bad controller is 31%.
    Any ideas?
    Steve Bird
    Culverson Software - Elegant software that is a pleasure to use.
    Culverson.com
    Blog for (mostly LabVIEW) programmers: Tips And Tricks

    Well, the controllers are not in my own hands.  I have an 8196 controller and on that, the CPU time is between 2 and 4%.
    But the 8100 and 8102 controllers are in my client's hands.
    I haven't gotten any hard timing numbers other than I saw the 31% figure reported on the video monitor.
    It's hard to believe that it would be EXACTLY 1% if it was CPU overburden.
    My software includes a calibration facility; here is a run from the good 8102:
    Here is a run from the 8100:
    This was with a reference digital freq generator.  You can see the one case where everything is within 0.1 Hz.
    the other case has everything EXACTLY 1% higher.  My only explanation is that the scan engine is running 1% slower.
    Steve Bird
    Culverson Software - Elegant software that is a pleasure to use.
    Culverson.com
    Blog for (mostly LabVIEW) programmers: Tips And Tricks

  • Pxi 4110 and dcpower express vi

    hi everyone,
    I'm really new to labview and I have to use a pxi 4110 to supply dc voltage with a square wave (or whatever shape I chose).
    I treid using the "dcpower express vi" but I can't understand how to connect the generated signal. at now I have the wave and I put a block which transforms the wave from dynamic data to array.. but it doesn't work! 
    i tried watchin g the examples, but none of them uses power express...
    thanks for any help!!

    As bronzacuerta mentioned, the PXI-4110 is not intended to generate a square waveform, or any specific waveform. It is intended to regulate a constant voltage or current, adjusting for changing loads. By changing the output using the NI-DCPower API, you may be able to approximate a square waveform, but it will not be a very good one, both in terms of rise/fall times and due to software-timed output updates.
    A potentially better option (based on speed/flexibility/accuracy requirements) instead of a Multifunction DAQ card is a signal generator.
    Tobias
    Staff Software Engineer
    Modular Instruments
    National Instruments
    Tobias
    Staff Software Engineer
    Modular Instruments R&D
    National Instruments

Maybe you are looking for