Discharge a battery 3V with Labview to test the battery life?

Similar Questions

• Problem with audio video in the Microsoft Life cam vx5000

  I have a Microsoft lifecam vx 5000, and after installing and trying out I can't with the microphone. The camera works perfectly well and the individual with no picture speech Recorder works great. However when I record avideo, it will only save sounds in the first 7 seconds. What should I do?

  Hi, Jillian

  1. How do you save the video?

  2. use any third-party program or functionality built into the web camera to record videos?

  I suggest you reinstall the software of web cam on the computer and check if it works.

  http://www.Microsoft.com/hardware/download/download.aspx?category=ice&type=LifeCam&SKU=RKA-00001

  File of Microsoft LifeCam Readme and troubleshooting information

  http://www.Microsoft.com/hardware/digitalcommunication/LifeCam/Readme/en-us/default.mspx

  I hope this helps!

  Halima S - Microsoft technical support.

  Visit our Microsoft answers feedback Forum and let us know what you think.

• temperature measurement with labview on four location using NTC thermistor

  
  

  Hello
  My project is the measure of the temperature of a thermistor on-site 4 difference.
  The measures must be 0 for 100 * C.

  details.
  

  • For the sensor, I must use only NTC thermistor.
  • I have to do an application with Labview.
  • the application must give me the right measure in real time, and it should save the sample in a database.
  • This measure is taken max 20 feet form the pc.
  
  I'm new with this.
  Can someone help me with sensor circuits.
  How can use DAQ with the thermistor.
  Can I use EMANT300 Low-Cost USB DAQ Module 24 bit?

  Please give an idea

• Can what cards I use to develop communication SPI with Labview?

  First of all, I'm an intern is currently working on a project that involves communication with an SPI interface. I have absolutely no experience with SPI, but I finally decided to try. I work for about 6 months with labview and understand the function of basis of a large number of its resources.

  The problem:

  We want to connect Labview to an evaluation Committee that is connected to the PC via USB (but it can also be adapted to connect through SPI). The evaluation board mainly reads and writes if sign up for issuers that are connected to it by a Module assessment. The program which is already which is the Studio of SmartRF (that works via USB), but as we want to link all the functions in Labview we redevelop a platform to do so. If shortly, we want to make a Studio of SmartRF version in Labview. We want to be able to get all the information that makes the program and others... and all this is possible through SPI.

  Here is a link in case you are interested what is SmartRF Studio: SmartRF Studio link

  My question is which card do you recommend for what we are trying to accomplish? We are looking for something not very expensive but who fail to meet our requirements.

  I think of the NI USB 8451, but please make suggestions.

  Thanks a lot in advance and please stay tuned to my many questions coming about how to accomplish this enormous task with no knowledge whatsoever of SPI or how to mix with Labview only one student. I am reading as much as I can find, so all the links will also be very much appreciated. If anyone has any experience with NI USB 8451 with Labview be kind enough to guide me

  Sincerely,

  Gisela

  If you have very little experience with LabVIEW and SPI, the 8451 is a good choice. It's expensive, but it's really easy to use and configure.

  The Aardvark is also a good choice. There pilots LabVIEW is also easy to use in LabVIEW. The disadvantages is that it doesn't have a lot outside of simply making SPI or I2C - in other words, it doesn't have a lot of GPIO. This can be important when control of multiple SPI devices, because it requires to select them lines individual slave.

  Dinah is really more than a product of laboratory, or something that is meant to be placed inside a camera. It is expensive, compared to the other two, but it doesn't have native drivers in LabVIEW. On the contrary, it comes with a DLL you can call from LabVIEW. I wrote a set of LabVIEW drivers for it, but I can't distribute.

  There are other products on the market, which some will resemble a device series to your computer. For example, you would use VISA to communicate with the SPI controller, and it would appropriate communication of SPI.

  Among the three mentioned here, I would suggest that you go with the neither of the Aardvark, one.

• Def sequence (table grapes) with loops, clocked by the relatively long software.

  Hello and apologies in advance I am an infrequent user of LabVIEW.

  Running on a VI to control a peristaltic pump and valve used to control some for a biosensor nanogap Microfluidic devices. I have the pump and the valve works manually (i.e., I adjust the values on the fly) but I am now trying to allow the user to define a sequence of steps that are then executed one after the other.

  User input: number, flow, duration of valve, pump direction (boolean).  Ideally the user can then run several different steps by adding more steps, so I thought of an indexed cluster array where each element represents a step?

  I would like the user to enter the time in minutes and seconds. The minimum will usually be 30 seconds and could be as long as an hour. I'm not sure of the best strategy for the timed loop, if I understand the use of the block 'waiting (ms)' can cause problems. I thought about getting a timestamp, a value added to it and the comparison? Are there any other suggestions?

  Any advice would be appreciated.

  I use an acquisition of data USB-6009.

  PS the VI LabVIEW is probably an education version, so may cause problems when opening?

  Just ask yourself how you should architect your code? Using a table of parameters of the step is an eay easy to do. And the wait is not necessarily a bad thing, it depends on your application and if you need the calendar to be exact in a certain way. You can use wait it until Mrs several place for synchronization.

  You can lookin to a State Machine architecture to make the best UI feature.

  The Computer of State Simple model that comes with LabVIEW is really the best way for new developers to become familiar with LabVIEW using a semi scalable architecture.

  Here is a large example of the works of a state machine:

  • States: Init, slowed down, exit, DoThing1, DoThing2, DoThing3
  • Each State contains code that could take some time. Ideally, not too long because this is how long your code might not meet.
  • The idle state contains a structure of event for all of the user interactions.
  • The front panel has a button that says "do the 1 thing.
  1. Loop iteration 0: Application starts, the first State is Init. Init State made the initialization stuff and tells the application to go to the idle state when finished.
  2. Iteration of the loop 1: request goes to the idle state. He's sitting there, waiting for the structure of the event.
  3. Time passes, and then the user presses the button 'do 1 thing ". There is no code or minimal code, within the occurrence of the event. The output of this state of the event tells the application to go to the State of DoThing1.
  4. Iteration of the loop 3: Application passes to the State of DoThing1. Here, there is code that does a few things. The output of DoThing1 State tells the application to return to the idle state.
  5. Iteration of the loop 4: Application goes to a State of rest where he waits again to the structure of the event.
  • Each State can tell the application to go to any State they want. You want to reset? Return to the Init State. You want to put an end to the program? Go to the exit State. You want each State to start another (such as a sequence)? Have DoThing1 out of DoThing2, which DoThing3, which outputs Idle.

  You can create a report that runs the cluster setting input and operates it. The risk with a long wait, is that the code will not be able to receive entries to user during this waiting period. So if you make a long wait, you can use a VI of elapsed time to check several times if the wait is over.

• Read file test.txt (binary or what?) with LabVIEW 8.6

  Dear friends!

  Please, how to read the attached file (test.txt) with LabVIEW 8.6.  In the same VI, can I convert it in a txt file real with the results presented in the rows and columns? Please, any idea? I need help!

  The rebooting of the trace file is binary.

  Unfortunately, without a description of the real file by developers RELAP format, I don't think you are going to get very far on the decoding of the file.

  You must get directly in contact with the authors RELAP.

  Here's the blurb to the RELAP Manual:

  3.1.4.2 the reboot-Plot file.

  The restart-trace file contains almost all the parameters of calculation

  (Sub fractions, pressures, temperatures, flow rates, etc.) for transient computing together.

  A common misconception is that a parameter must be specified using a minor in change request

  in order to be available in the reboot-trace file when the calculation is complete. Affects a minor change request

  only the printed output. The restart-trace file is accessible repeatedly that the new data should arise. However,.

  during a calculation, the data are written to the reboot-trace only for minor editing file (and the plot point)

  frequency. Once a calculation has been performed, it is not possible to recover data between data

  written to the file to restart-track of the points. Therefore, it is important to choose a minor edit (and plot the point)

  frequency that provides the plot to an interval appropriate to the problem is resolved. In practice,.

  the minor change (and plot point) frequency must be changed during the calculation as the product of the problem

  from one phase to the other. Common points must be selected in the phases of problem where rapid

  RELAP5-3D/2.4

  INEEL-EXT-98-00834-V5 3-18

  setting changes are expected. For the economy, less common points must be selected in the phases

  where the conditions of rest are expected.

  Calculations are usually made using several reboots. (See Volume II for the restart entry

  requirements.) For example, a new problem runs from 0 to 10 seconds. This first part is analyzed and

  Run again from time zero that errors will be corrected. When a managed to 10 seconds has been calculated, a

  restart run is made (for example, 10 to 30 seconds), and so on. RELAP5-3D

  © offers you the possibility of

  change of almost any feature of the model at any point of restart. When changes to the model are incorporated on

  reboot, reboot-plot file reflects those changes only after the decimal point in the calculation, where they have been

  implementation. In the example above, if an injection system is added to the model to 10 seconds, then data

  for added components exists only for the time after 10 seconds. Changes, deletions and additions of model

  are constantly being implemented. If a model change is done in 10 seconds, the revised model remains in

  effect unless other changes are made to subsequent restart points.

  When a calculation is completed, the restart-trace file becomes a valuable document of the

  calculation. If lost, replacement would require reperforming the calculation, usually to the considerable

  loads. At a later date, the file can be accessed and previously compressed data can be obtained as

  necessary to extend the analysis. Therefore, it is recommended that files of restart-track of the important calculations

  be protected safely and permanently.

• Problem with my laptop battery life

  Hey owners of Toshiba! Is anyone having problems with their battery life? My laptop does not work as long as it should! Or so it seems. Any ideas what could be the problem? What is the machine?

  Try to let the battery discharge completely before recharging it. When you decide to use the power of the battery, remove the power adapter when the battery is fully charged and running on battery power until this that completely discharged and not only for 10 minutes, for example

• Experiences over seven years with the battery life in laptop computers Tecra

  Seven years ago, I bought a Tecra 780DVD, five years ago a Tecra 8100 and two years ago a Tecra S1. They re all still in regular use and I ve used now six packs of lithium ion batteries. My experience suggests that these four guidelines are worth observing:

  1. it is preferable to the hibernation and remove the battery if the laptop will be inactive for more than 2 or 3 days.
  2 operating time vary a lot between the samples of battery even with the same operating conditions.
  3 leave the charger plugged in with the full light on doesn't seem to hurt (despite some of the recommendations).
  4. better is not the first time, that it is unable to charge the battery of junk. The trick described below may reset the battery and get more useful life out of it.

  Tecras see the end of battery life by battery light flashes orange or stay off when you try to reload. Last week when I returned from vacation what happened the 780 (now the WiFi print server) and I felt like déjà vu because all 4 batteries (three on the 780) and the other on the 8100 that I ve had previously fail expired the same way they failed to charge after 7 to 14 days of hibernation with the battery left in. In my view, that it can hardly be a coincidence.

  I still had another 780 old farm and an old battery for 8100 that both failed about two years ago I did some tests. The batteries two 780 showed 10-11 volts on a voltmeter, but when I put them in the laptop and plugged in the charger, the led load always flashed. However, when I plugged the laptop battery already started the grid only, the hanging lamp orange and after an hour or two went green.

  I think this shock treatment can have done in battery electronics forget they were supposed to be dead. Anyway, I did with all three batteries and then ran to see how long d last. The results were:

  (1) the 780 battery failed last week (after 36 months used) can now run the laptop for an hour.
  (2) the 8100 battery (with the active service of 16 months, but 'believed dead' for two years) will now run for 10 minutes or more.
  (3) the 780 battery believed dead for two years (after 19 months used) appears to load but t does not work the laptop. Half of the battery ended up hot and half cold, so now I guess that it s really dead.

  Hoping others will compare notes, I've summarized below how long my battery packs lasted before they refused to pay more.

  Tecra780DVD:
  Original battery: 30 months (discarded too soon. Might have gotten more if I had tried to trick reset).
  First replacement: 19 months (stored for two years, after which reset didn't work).
  Second alternative: 36 months (after reset now works for an hour).

  Tecra 8100:
  Original battery: 16 months (stored for 2 years. After reset now lasts 10 minutes).
  First replacement: 41 months and always well run.

  Tecra S1:
  Original battery: 29 months and always well run.

  All are genuine Toshiba and operating conditions are quite similar for all. Laptops tend to run 4-8 hours per day with the charger plugged and maybe half an hour on battery only. Sometimes we forget and the charger remains connected all night.

  I m now wish I d tried the trick of reset on all batteries as soon as they failed, but at least I seem to have rescued two batteries. Even a moment of execution as short as 10 min is useful on a laptop that s especially power sector. It protects against power failure and you can keep your battery in the fridge until you need it for a trip.

  David Tong
  Leeds, UK.

  Hello Johnson

  It seems that you are very big fan of Toshiba laptops :)
  Thanks a lot for this long case study and share this information with us.
  I'm sure that this info helps many users of the community.
  Our community needs more users like you. ;)

  Best regards

• How to maximize battery life battery with Lithium-ion batteries?

  Hi all

  There are discussions severay about the duration of battery life.
  Toshiba said on http://support.toshiba-tro.de/kb0/FAQ35007L0020R01.htm that:
  Discharge the battery completely before recharging, will allow the battery to be charged to its highest capacity
  But this and other points do not comfirm maximum lifetime of the battery of the http://en.wikipedia.org/wiki/Lithium_ion_battery information

  Question: What is the best option to maximize battery life battery with Lithium-ion batteries?

  Hello

  I wonder why you n check the user's manual t or have you checked it?
  The manual provides many useful tips, it confirms the information provided in document Toshiba

  However, I assume that the information provided in the document of Toshiba relate to Toshiba laptops and the wikipedia article is general information

  I have several laptops at home and I still have the battery charged and completely acquitted in the first three, four times.
  You know, you can compare the situation of a laptop with the batteries of mobile phones battery. It s always advised to load and unload completely the battery because of the effect of stack memory.

  But from my personal experience each battery loses life after 1 performance 1.5 year.

• NI 9148 with LabView module detection

  Hello

  I got the task of creating a deployable (compiled) software to a DAQ system with NI 9148 Ethernet RIO basket background and various modules. The user must have the ability to change the module type and the location of the different tests, so the application must detect (or the user specify) what modules are at what positions.

  I watched the blockset CRY, however this chassis is not supported and the lowest level blocks are protected. Is it possible to read the serial number of the modules connected to the 9148 OR position, type, and if all goes well?

  Thanks for any help!

  Hello Soonxaf,

  What are you helps as a controller-is this RT or Windows? Are you planning on the use of analysis of RIO or LabVIEW FPGA engine?

  If you plan use the analytical engine, so this should help you get started:

  Tutorial: Discovery, Configuration and programming access of the CompactRIO Scan Mode to IO with LabVIEW

  http://www.NI.com/white-paper/9351/en

  Kind regards

• Can I change the default settings for the latency time Serial Windows with LabVIEW

  I have a wireless data collection device that my business is that I am using for the test one of our other wireless products. The device sends data series to a PC via a USB port. I wrote an automated LabVIEW program to test all the functions of my new product. However, after firing in the data, I realized that the serial data coming very fast and requires me to change latency of Windows by default for the port COM 16ms 2ms Miss not nothing. It's pretty easy for me to do locally on my machine, but much more difficult for me to spec for an off-site CM.

  Is it possible to have my LabVIEW program change the latency time of the COM Windows port of 16 ms to 2 ms automatically?

  Are you talking about the FTDI driver? I know that they allow these changes through registry settings. Thus the approach would probably be to have a small registry script that updates the parameter of function. Most likely, this will have to be run with elevated privileges, as these parameters resident generally in the HKLM or HKCR rather than the HKCU one hive.

• HP 2004tx g6: laptop won't turn on with AC adapter and the battery

  Here's the thing.
  (1) the laptop doesn't work without battery when it is connected directly to the power adapter.
  (2) light, which would indicate that the laptop is connected to the power adapter is not on the power adapter is plugged in.
  (3) the battery charge light is also not on, which would indicate the battery is charging.

  The battery does not load... Laptop is running on battery backup mode, but not on the AC adapter connector. I tried to connect the battery to an another compatible hp laptop (my laptop and the other test device supports same battery models). It has been very well supported on this laptop. And when he spent in my laptop, laptop was working well, but it does not load in my laptop. But the AC adapter / CC is fine too. So what is the problem? And what I can do to get it sorted?
  My laptop is not guaranteed more. But I replaced battery 4 months back, if this is not a flaw with the battery or the AC adapter.
  The adapter is very good, tested with another laptop.
  The battery is also new and works fine
  Kind regards

  Hey @absol1234ss ,

  Here is the manual, not sure why previous post did not work.

  Thanks for letting me know about the error.

  Thank you.

• Cannot bind to the shared object created with LabVIEW 2009

  I have problems referring to a shared library built from a LabVIEW VI under RHEL 5 with LabVIEW 2009.

  To illustrate the problem, I created a VI with a digital input and output that corresponds to a certain number. Then, I created a draft specification of build to create a shared library with a feature that makes use of this VI square. The shared object is created successfully (square.so).

  When I try to compile a test application written in C, that connects to this library, I get errors in the following link:

  cc  -I/usr/local/natinst/nidaqmxbase/include -I/usr/local/natinst/LabVIEW-2009/cintools build/square.so  test.c   -o test/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(float&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(double&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(double&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_ostream >& std::basic_ostream >::_M_insert(double)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_istream >& std::basic_istream >::_M_extract(float&)@GLIBCXX_3.4.9'/usr/local/lib/liblvrtdark.so.9.0: undefined reference to `std::basic_ostream >& std::basic_ostream >::_M_insert(double)@GLIBCXX_3.4.9'collect2: ld returned 1 exit statusmake: *** [test] Error 1
  

  Running ldd reveals that liblvrtdark.so.9.0 is used for the execution of labview.

  In order to investigate on what could be the cause of the problem, I have compiled the nidaqmx basic examples, and I don't have an error. Current running ldd as reveals that he uses liblvrtdark.so.8.2 for the view of laboratory, time of execution.

  My suspicion is that some components of labview are being compiled with gcc 3.4 while others are being compiled with gcc 4.1 (which is the default compiler in RHEL 5).

  Any ideas how I could fix the build errors?

  Thanks in advance for your suggestions.

  PS.

  I enclose a tar file with the source files and here are the details of the ldd:

  ldd build/square.so         linux-gate.so.1 =>  (0x008de000)        liblvrtdark.so.9.0 => /usr/local/lib/liblvrtdark.so.9.0 (0x00b9c000)        libc.so.6 => /lib/libc.so.6 (0x00110000)        libstdc++.so.6 => /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 (0x009a7000)        libm.so.6 => /lib/libm.so.6 (0x00756000)        libdl.so.2 => /lib/libdl.so.2 (0x00256000)        libpthread.so.0 => /lib/libpthread.so.0 (0x0025a000)        /lib/ld-linux.so.2 (0x00b80000)        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00272000)
  
  ldd /usr/local/natinst/nidaqmxbase/lib/libnidaqmxbase.so.3.3.0         linux-gate.so.1 =>  (0x00e50000)        libnidaqmxbaselv.so => /usr/local/lib/libnidaqmxbaselv.so (0x00248000)        libc.so.6 => /lib/libc.so.6 (0x00689000)        /lib/ld-linux.so.2 (0x00b80000)        liblvrtdark.so.8.2 => /usr/local/lib/liblvrtdark.so.8.2 (0x00e51000)        libdl.so.2 => /lib/libdl.so.2 (0x00813000)        libpthread.so.0 => /lib/libpthread.so.0 (0x001b0000)        libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x009c7000)        libm.so.6 => /lib/libm.so.6 (0x00b0a000)        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0050c000)
  

  Hi mimi,

  I'm happy to report that I managed to get the code to work. I have included some of the steps I experienced the problem in case it might help improve the documentation or future generations.

  In response to your question about the "error 1" reported by do, it's just an indication that detected a compiler error (it probably resembles the return code of the compiler).

  The errors ' undefined reference... @GLIBCXX_3.4.9 "have been narrowed down. The generated labview shared library, the square.so, links to /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 which is a symlink to usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6.0.9. I decided to compare this version of libstdc ++ that included with RHEL:

  strings /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 | grep GLIBCXXGLIBCXX_3.4GLIBCXX_3.4.1GLIBCXX_3.4.2GLIBCXX_3.4.3GLIBCXX_3.4.4GLIBCXX_3.4.5GLIBCXX_3.4.6GLIBCXX_3.4.7GLIBCXX_3.4.8GLIBCXX_3.4.9GLIBCXX_FORCE_NEW
  

  strings /usr/lib/libstdc++.so.6 | grep GLIBCXXGLIBCXX_3.4GLIBCXX_3.4.1GLIBCXX_3.4.2GLIBCXX_3.4.3GLIBCXX_3.4.4GLIBCXX_3.4.5GLIBCXX_3.4.6GLIBCXX_3.4.7GLIBCXX_3.4.8GLIBCXX_FORCE_NEW
  

  So libstdc ++ RedHat does not include a string for GLIBCXX_3.4.9.

  With this in mind, I was able to get my test application to compile using the version of LabVIEW libstdc ++ using the following makefile:

  .PHONY: all cleanCPPFLAGS=-I/usr/local/natinst/nidaqmxbase/include -I/usr/local/natinst/LabVIEW-2009/cintoolsLDFLAGS=build/square.so \        /usr/local/lib/LabVIEW-2009/patchlib/libstdc++.so.6 \        -Wl,--rpath -Wl,/usr/local/lib/LabVIEW-2009/patchlib/
  
  all: test
  
  clean:        rm -f test *.o
  

  When you try to run the application, I got the following error:

  ./test: error while loading shared libraries: /usr/local/lib/liblvrtdark.so.9.0: cannot restore segment prot after reloc: Permission denied
  

  But apparently, it's because of SELinux prohibiting the use of libraries shared with moving text.
  This can be disabled by running /usr/sbin/setenforce 0 as root.

  The test application now works!

  See you soon,.

  RW

• USB WITH LABVIEW CONNECTIVITY

  All of hell

  My first post.   Very high level question.   I'm working on a product that will have a top (not GPIB) USB interface.  I wonder if I can use LabVEIW to connect to the USB interface when even?  The product is essentially an adapter so I'll use LabVIEW GPIB connected Instruments to test as a power source, but it would be very useful that my LabVEIW code may also exchange information with the product via the USB interface...   As I said, that the USB data would not GPIB will be what we define that it is, but not necessarily GPIB (I guess it could be GPIB, but for the sake of argument lets just say that this is a way of communication, I want to use LabVIEW).   If the answer is Yes, can you point me to any resources that could help me?

  http://digital.NI.com/public.nsf/allkb/044FA220F32774ED86256DB3005850CA

• Generation of C++ with LabVIEW DLL error

  Hi, I am a student at the UC Irvine, learn how to use LabVIEW.  I'm working on a practice project for which I use a PID system to control the temperature of an object.  Things are starting to be a little awkward with the control statements nested, loops, etc., so I thought I have exported a LabVIEW DLL with all the difficult to encode things like interfacing with my instruments and tracing of data or something else and do the calculation and follow-up of the commands in C++.

  The DLL file I made in LabVIEW exploded without a hitch, as far as I can tell, but when it a link to my C++ test program (which at this point is just including the .h file of the LabVIEW for the DLL and an empty main() function), I get a lot of build errors.  I'm using Dev - C++ that uses g ++ to compile the code.

  Here is a picture of my build errors:

  Normal windows applications are not so forgiving on where you can put your DLL under LabVIEW. You must have a DLL or in the Active Directory where the executable file itself (this is your build directory, not the source directory), windows or directory system or any what directory defined in the PATH environment variable. Anythin else probably won't work, or at least not reliably.

  No need to add the cintools directory to your include paths or paths of the library file. You must only that if you decided to leave native LabVIEW DLL export data types, in which case you would need Manager of LabVIEW to prepare the correct data buffers.

  Rolf Kalbermatter