Labview pauses

I have developed a LabView ver. 7 program which inputs digital data at about 1MByte/sec from a NI 6534 DIO card and writes it to hard drive via. USB-2. I am running it under Win. XP and the application has to run for hours without missing any data.
The VI will freeze or pause every 1 hr, 3 min and about 20 seconds. It stays paused for 10 -15 seconds, long enough to cause a DIO error, either 10800, 10802 or 10845 each time it pauses.
I have run a similar program under Win 98 in the past with out this problem. I have searched for programs running in the background such as firewalls, antivirus, etc and uninstalled all that I can find.
The first occurrence of the pause occurs at a random time after starting LV and then at 01:03:20 thereafter so It does not appear to be LV related.
Has anyone seen this behavior before?

Ok... this is some good info on your system.
Off the top of my head, I am now curious as to how you're storing your data that is acquired. How are you buffering it and how are you saving it to disk. Are you building arrays at run time?
A constantly increasing page fault total usually is an indicator of dynamic memory allocation at run-time. Your program may also be deallocating the memory which could possibly be why your memory sizes don't change much. LabVIEW would be doing this all for you based on your program design, which may be the cause of the problem.
I believe you said you had LV version 6... I'm not sure what version it is available in but there is a tool in the latest version that will show where data buffering takes place--where data on your wires is being copied. As a general rule, it's best to avoid making copies of the data as much as possible.
There is also an article by NI on how to set up your data structures and arrays when using them in loops so as to help LabVIEW manage the data as efficiently as possible. I would definitely recommend reading that and seeing how your program matches up to the suggestions made in the article. If you have poor implementation of a data array inside of an acquisition loop it can cause quite a bit of dynamic memory allocation/deallocation which in turn can cause random unforseen delays due to interaction with the OS when it tries to allocate that memory.

Similar Messages

Why does LabVIEW pause while I operate the slide control?

I have a slide control inside a while loop. Something on the screen reacts immediately to the control as I slide it. This used to work, but now everything pauses while the control is being operated except for the control's own digital display. Even an indicator wired directly to the control, and also inside the loop, pauses until the control is let go then suddenly jumps to the control's current value. Both an indicator and a probe wired to the iteration count show the same thing.
When I copied that same control into another VI with only a loop and an indicator, it works fine just as before.
I've checked all the VI setup stuff and I can't see anything in the diagram that would cause this. I a
lso tried deleting all of the control's local variables and attribute nodes to no avail.
I'm using LabVIEW 5.0 in NT Workstation 4.0
Does anyone have any idea what's going on.
I'd appreciate any help.
thanks,
Louis

Do you have a small wait inside of the while loop? I don't have any problem in version 5.1 or 6 when I put one inside. I typically use a delay of about 25 msec.

LabVIEW pauses during acquisition

To avoid burying the lead, I'm going to state the problem I'm having straight off. The program I'm written pauses exactly every 10 seconds while running, always on a time where the seconds are around 3.6 (see below, as low as 3.4 and as high as 3.8). the pause is very short, easy to miss. I only noticed it because we recorded over the pause a few times and the data columns got swapped.
The timing of the pause appears to be independant of the sample rate. I've gone as high as 200k and was able to repeat it as low as 50k. Below 50k I cannot reproduce the error reliably. Once the error does occur it happens exactly every 10 seconds (down to the millisecond). For example, on one run I get the error at 11:06:13.681, it will occur again at 11:06:23.681, at xxxx:33.681, xxxx:43.681, etc...
Program explanation: Currently the software acquires data from some 9 sensors at 100 kHz, 3 sensors at 1000 Hz, controls 4 relays, and outputs a TTL signal on demand. Initially the software just monitors the sensors and writes the data to a plot. When I hit the "fire" button the software shuts of the plots and records the data to several TTL files, one for each rate. I had some problems early on with errors when trying to plot data at the same time as I was recording it. In my research on this timing issue I believe it is being caused by having the "write to measurement file" in the while loop. Not really certain of how to pull them out and stream the data to the file yet, but that's next on my list. Anyway, the program still has some evolving to do as the test program moves forward.
Initially it was written using the "DAQ assistants." Again, in my research I learned that I really want to use the DAQmx functionality. I went ahead and swapped most of them over to DAQmx. As of this writing the things that are active while I'm not recording (have not hit the fire button) do not have any DAQ assistants. I'll be changing the assistants under the lower case structure to DAQmx in the near future, I'm going to figure out how to move it outside the while loop first while I know it works.
Does the software work at this point? Yes, it is currently being used and recording data in a satisfactory manner. However, I know that I have to move forward with it and create additional functionality, possibly record at higher speeds, so I want to resolve these bugs.
Possible causes:
1) Buffer overun. Perhaps increasing the buffer size will solve the problem.
2) PC Memory. I know win7 is a memory hog. The laptop only has 6 GB of ram, all it has on it is labview and office.
3) The DAQ assistants under the case structure are causing problems? Could it also be that I originally did this with DAQ assistants and swapped them to DAQmx with the right-click "Convert to DAQmx?"
4) I'm plotting an excessive number of points on the chart and that's causing the issue, maybe a redraw issue?
I'm using a cDAQ-9188 with 3 9222, a 9221, two 9481s, and a 9402. and running LabVIEW on an Inspiron N5110 with a core I7 and 6 GB of ram and 64 bit windows 7.
Attachments:
DAQ_R6.zip ‏211 KB

Thanks for the response. You make a number of suggestions that I will incorporate into my next revisions. Let me add a bit of detail that I didn't think about on the first post.
The reason I don't append to the file is because I only write one file for each event. LabVIEW is stopped completely between each event while the hardware is reset/moved and a new filename consistent with the test setup naming scheme is input.
Channels swapping, sorry, I should have explained that. Each of the 9 high speed sensors goes into its own column in the resulting file. On occasion the columns get swapped around, for example, column 7 might be in the column 5 position, with 5 pushed to 6, 6 pushed to 7, etc... The way the sensors are arranged it would be physically impossible for the measurements to take place in the recorded order. We duplicated the same setup multiple times to verify the problem and duplicate the error. That's when I noticed that pause.
Good tip on the producer/consumer pattern, that is the way I will proceed. However, I believe the pause bug is independant of the file access and creation. When I just run the VI without hitting "fire" the files are not created. They are only created when I hit the fire button and the case structure turns from false to true. In fact, I went ahead and deleted all the content in the "true" field of that case structure. This took out 100% of the DAQ assistants and left me with only the DAQmx components (attached). The pause bug was still present.
I don't know if I have access to the 2012/2013 project templates. I'll check into that. I'm not sure that I want to do continuous logging though, the event I'm measuring is only about 25 ms and it happens sometime between 0 and 2 seconds after I initiate the firing sequence, I have to record about 2 seconds of data to be sure to get it. Once the event occurs the hardware has to be reset and I like to stop the software as well so I get a new filename associated with the test naming scheme.
What about that DAQmx write on the right side, it controls the 9481 relays. Is it sending data to the relays on every iteration of the while loop? Could that be a component of the problem?
Again, thank you for the response. Your suggestions give me a number of directions to look in for my future iterations.
Attachments:
DAQ_R6_1-2-2014 - no DAQassistant.vi ‏61 KB

Labview pauses when dialog box displayed

When I display a dialog box in LabView, the program waits for the user to click ok. I would like for the program to not wait but keep running after it displays the box. How can I do this and how can I customize the dialog box?

You drop an Invoke Node from the Application palette onto the block diagram, wire up a reference to the subVI, right click the invoke node and select the method. There's an example here that shows how an invoke node is used to make a front panel visible. There are other examples on the developer zone and several have been posted to this forum. You question seems to pop up once week or so and a little searching of the forum will give you a lot of examples.

Why does Labview VI pause intermittently during motor control while loop?

I'm performing some biomechanical testing using Labview to control stepper motor actuators. I have a PCI-7334 controller card and a MID-7604 driver. The testing is run in load control using a while loop that sends a number of steps to the stepper motor that is proportional to the difference between the actual and desired load. The VI intermittently pauses though and sits in active for several seconds (~5 sec to 20 sec). What could cause this problem?
Thank you in advance for your assistance.

Without the subVIs it is hard to see what is going on.
Some general comments:
1. Block diagrams should be limited to the size of one screen. Yours is over 4 times as wide as my 27" screen.
2. Sequence structures should be avoided. LabVIEW is a datflow language and only rarely are sequence structures required. There is almost certainly a way to write your program without them.
3. The use of local variables should be avoided. Again, they have a place but most likely they are not needed in your program. They are prone to race conditions, make extra data copies, and force execution in the UI thread.
4. Floating point data types are not recommended as case selectors. They will be rounded and coerced to integers.
5. Learn about the Producer/Consumer Design Pattern and state machines.
One possible cause of your slowdown is having the Write to Spreadsheet File.vi inside the while loop. This VI is convenient to use but it opens, writes, and closes the file each time it is called. I have no way to tell how much data you write on each iteration but as the file grows the OS may need to re-allocate space for the file or fragment the file. These operations can be slow.
Do you really want to Abort the program in the False case? This will leave any outputs in the last state they had been set. This could have your motor(s) running, clutch engaged, ... In programs which control physical hardware an orderly shutdown procedure is usually better: set all outputs to a safe condition, close files, close DAQ tasks, and indicate the status to the user. Calling Stop allows none of this to happen.
Lynn

All labview code pauses when a window is being drug, then resumes when released.

My code seems to pause when I am draging labview windows around on my computer (by the windows title bar). I preformed a count down timer to show that when drug and then release the window, that time/code did not continue.

This will also happen if you are calling a dll that is not thread safe and must be run the user inerface thread.
To check this, double click on the Call Library function, and in the configuration dialog, there's a dialog ring to select which thread to run in. If it's set to 'Run in UI Thread', that will cause the execution pause. You can try switching it to 'Reentrant' and see if it works, but if the dll was not written to be thread safe, this will cause problems.
Let us know how it turns out.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

I would like to display the pause button in an executable built with the LabVIEW 6.0.2 application builder.

When we upgraded to LabVIEW 6.0.2 (Windows) the executables no longer had the pause button in them. This was a useful feature but I can't find an option to display this button in the Application Builder. Please let me know if this option has been removed and whether I need to allow for pauses to be built into the programming. Thanks.

A well designed application shouldn't need to be aborted the hard way but if you want this feature, you can enable it in the application builder settings.
Under the "VI Settings" tab, select your Top Level VI and press "Edit build settings...".
Change the item "User can abort VI" to "Yes".
LabVIEW, C'est LabVIEW

How to pause and restart a timed loop in Labview

I am trying to pause and then restart a timed process (series of stepd that happen at precise times), which is implemented using a timed loop.
I was wondering if anybody out there can give me a hint.
Thanks

Roxanne,
Well, it's not exactly a "pause", but here's a way to stop and re-start your Timed Loop.
See the attached example in LV2010.
A While Loop and a Queue are used to allow you to start and re-start the Timed Loop.
The "Stop Timed Structure" vi is used to stop the Timed Loop.
Releasing the Queue stops the While Loop when you end the program.
Note that the example is very similar to the NI template "Producer/Consumer Design Pattern (Events)". (File>>New)
steve
Help the forum when you get help. Click the "Solution?" icon on the reply that answers your
question. Give "Kudos" to replies that help.
Attachments:
timed loop.vi ‏39 KB

Calling exe pauses Labview execution

I've written a program that needs to call another program. When that program opens, it pauses the now "background" vi, but I need it to continue running in the background. If I chose 'F' for 'Wait until completetion' the main program doesn't pause, but the window (from the exe I called) never opens.
Can this be done?

TNeilson wrote:
Well, I'm not quite sure what your vi does here. The actual call doesn't really look like you did anything that I didn't do, and your program ends after the calculator is loaded. Basically, I just want my program to load another program but continue running. One would think this wouldn't be that challenging, but so far, I've had no luck.
I didn't realize I'd need to provide an example of how to use the Run Program.vi that I referenced.
An example is now attached.
LV v7.1.1 and you will need to provide it with the aforementioned Run Program.vi
Attachments:
Example Using Run Program.vi ‏27 KB

How to hide only pause button on toolbar in run time

hello,
I had hide all the buttons like run, run continuous, abort vi and others by navigating to VI Properties and unchecking the corresponding options.
when i run the vi, all becomes hide except pause button and i didn't find any option for hiding it manually as well as programatically.
can any one tell me how to hide pause button. i have an urgent requirement for same.
Thanks & Regards,
Samriddh Sarbalhi
Solved!
Go to Solution.

wprice wrote:
I just found that the option called "Show Toolbar When Running" is located under VI Properties > Windows Appearance > Customize. I disabled it and it worked. Thanks!
So, the option I mentioned is still available, but only at a different place.
I was shocked on seeing your earlier reply, "There is no such option in LabVIEW 9.0 or higher.".
- Partha
LabVIEW - Wires that catch bugs!

How to make a pop up that pause the program (during pop up) and click button to continue OR stop the program

Hi people,
I am using LabVIEW to create a testing program to test a power system. The testing lasts for a loop of 90 minutes.
I would like to make a pop up when the testing is completed. When the pop up message appear, the whole program should be paused (NOT STOP) and when the two buttons (continue, stop) are pressed, the program should continue to run OR stop. [To start another loop of testing in order to make sure data collected is accurate and consistent.]
How do I make this kind of pop up window? I have totally no idea how to work on this. I will be very appreciated if someone could give me some suggestions/help regarding this.
Thank you.
Regards,
Vanessa

VanessaWen wrote:
Hi Blokk,
In my actual program I have 3 while loops. In while loop A, it is used as counter, to transfer rows of data from an array (row by row) to loop B. For loop B, device drivers are used so that my program can be used to control the devices (it is for automated instrument testing). Loop C is then used for DAQ, data at different test points will be recorded at every second.
I would prefer something simple in controlling all the while loops as my program is quite complex.
Thank you so much.
Vanessa
I do not see why you need these 3 while loops. This task could be done with a single while loop, or max 2. Why you need loop A? You could generate data from this array inside loop B. You must use the DAQ and device control part in separate while loops? Maybe you could simplify you code to have one single while loop: at every iteration you could send a new control command to your device(s), and after this do a DAQ measurement.

(1) Would like to pause syringe pump at certain volume while still collecting diameter data, (2) Would like to delay chart and numerical indicator output until after syringe pump is run

Hello:
I am using Labview to control a New Era Pump Systems automatic syringe pump and to record diameter measurements from a LaserMike optical comparator. My program is fully functional, the code is attached with all auxilliary files in the NE-50X folder. I mostly understand my program, I used drivers for the NE-50X pump found on the NI website to build my code and added to it as needed. My program currently does the following:
After I push the white Run button, I am prompted for a file name. After I enter one, Labview begins collecting data from the LaserMike and syringe pump and outputs them to their respective numerical indicators and waveform charts. Then I can change the syringe pump flow rate and syringe diameter on the front panel. Once I push the green RUN button on the front panel, the syringe pump runs, and the balloon diameter vs. syringe volume XY graph begins to record. I can then reverse the direction of the pump and/or pause the pump however many times I like, while Labview still records diameter from the LaserMike. Pushing the red STOP button on the front panel terminates the program and stops the pump.
Here are three things I would like to change about my program that I don't know how/what to do:
1) I would like the LaserMike and syringe pump to output to their respective numerical indicators and charts only AFTER the green RUN button on the front panel has been pushed and the pump is running.
2) I would like to be able to pause the syringe pump at two specific volumes while Labview continues to collect data from the LaserMike. I do not mind if I would have to push RUN to manually restart the program. I just want the pump to stall for a few seconds once the syringe pump dispenses a certain volume without the program terminating.
3) I would like the program to terminate once a certain volume has been dispensed. I would also like the syringe pump to return to zero, its starting position, after each test so that each test is identical.
If anyone has ideas about how to do any of these three things, your help is greatly appreciated.
Attachments:
Balloon Diameter.vi ‏132 KB
NE-50X.llb ‏994 KB

1. You can set a boolean value when the Run button is pressed and use that boolean value to determine whether or not your indicator is updated.
2. You check the value of your syringe volume every loop iteration and pause the pump if a certain value is reached. You can have the program wait for the user to press a button to restart. You can also have it pause for a period of time and continue automatically.
3. Just like #2, you can wait for a certain value and stop the overall loop once that value has been reached.
Your program is an excellent candidate for event handling. I have attached a link to a tutorial.
Brian R.
District Sales Manager
Washington DC
National Instruments

Why does while loop pause during operation

Hi everyone,
I have written the attached code which will eventually be a part of a bigger program. The program is intended to log some test value, in this case just the date and time to a csv file when a button is pressed (log in WHITE, loop1). Loop2 is intended to read a test value from a line in the first csv file and then add an extra test value to the end of that line when the serial number matches and then saves that line to a new csv file. This all works well but loop2 seems to pause a few times before continuing when either of the log button is pressed. I tried putting the code in 1 while loop with no success. Can anybody see what I am doing wrong?
Attachments:
ResinV10_csv.vi ‏25 KB

Maiz wrote:
Can anybody see what I am doing wrong?
In addition to waht has been said already, your code is extremely convoluted.
How often does the "read" file change? Do you really need to read the entire file with thousands of rows every ms just to look at one row?. If the file never changes, you could read it once before the loop.
The way do do array opearions is mind boggling. You take one row, Index out the first element twice in parallel (once is enough!), then you index out the first element, built it into an array of one element, and compare that array with a scalar. Would't comparing the orignal element with the scalar be equivalent?
Index array is resizable, you only need one instance.
Getting five elements in a row just to build them back into a 1D array seems rather pointless. If the array has only five elements, there is nothing to do, and if it has more elements, you cold use "array subset", and if it has fewer elements, use "reshape array" to size 5.
The correct format for reading strings is %s (not %.10f).
Since you want both loops to run at the same speed, why don't you put it all in one loop? (this even eliminates the local variable) Then you could use a parallel loop for the file saving, using queues in order not to slow down the main loop. In the parallel loop, open the files before the loop, use lowlevel writes inside the loop, and close the files once the program stops.
Can you explain your setup and what the program is supposed to do? I am sure it could be done with 20% of the current code.
LabVIEW Champion . Do more with less code and in less time .

Pulling in a variable into TestStand from an externally running LabView Vi ?

Hello,
My coworker has a problem and I'm tyring to help him.
We have a functional test written by an outside company, using TestStand 4.1
He has a LabView Vi with an Thermotron driver that monitors a chamber temp and outputs an INTERVAL number ( 1 intervel every x minutes)
That interval number is written to text file.
We would like to loop the Main function of the TestStand sequence based on that Interval number, but I'm unsure how to read that variable from within Test Stand.
I can either pull interval numbers from the text file, or set up logic in the VI to make a true / false flag based on interval numbers
i.e. interval 30 - 60 run the test....61 to 75 pause (dont run test)....76 to 125 run test...etc
Can you tell me how I might pull that interval into TestStand ?
Is there a way without incorporating the stand alone VI in question into the Test Seq ?
Thank you for any advice in advance !
Solved!
Go to Solution.

Hi,
Are you saying that you want to read this value stored in your text file and use this value to set the number if iteration of your test sequence loop.
You will need a piece of software that will obtain the value from your file and then pass this back into TestStand to store in a teststand variable, probably a local. TestStand doesn't have the built in function to directly read the data from your file.
Therefore you will need a code module attached to say an Action Step Type. The code module can be written in any one of the supported language, as you mentioned LabVIEW then maybe this is your perferred language. So your VI need to obtain the data from your file and return the value back to TestStand and you do this by sending your data out of your VI via its connector pane and then in teststand assigning a Teststand variable to your output connection of your VI.
I am assuming you have the basic knowledge of setting up a Step in TestStand.
Regards
Ray Farmer

LabVIEW 8 does not close ref's the same as LabVIEW 7!?!

Hello!
I have been struggling with a difference between LabVIEW 7 and 8 in how the Close Reference functions for Active X objects. In order to fully understand the problem, let me first explain the process of how I got here.
I have an application in beta testing and we noticed a huge memory leak in LabVIEW 8, 8.2. I took a snippet of the code and worked on it a while to reduce the memory leak. I was closing every reference and could not explain it so I wrote the same code in VB and saw no memory leaks. I implemented the same code in LabVIEW 8 and still saw a memory leak. The code opens a graph control from a third party vendor and draws it. Each time the graph is drawn in LabVIEW 8, it costs about 30-40k. We have 8 graphs in our application bringing each iteration to 240-320k. The users are going to be reviewing between 96-384 samples in one sitting but we have no control over when the program quits. 384 samples reviewed in the graphs is 92,160k as a minimum. I was frustrated and about to send it to the thrid party vendor, AB Sciex, but they only had LabVIEW 7.1. So I converted it back to 8.0 and then to 7.1.1. I ran the code in 7.1.1 and there were little to no memory leaks! I even tried it in LabVIEW 7.0 and it worked the same as 7.1.1.
I monitored the memory of LabVIEW through the task monitor in Windows XP. I have tried it on a few XP machines and a 2000 machine and same answer on all. I also built a Task Monitor tool using .NET to graph the memory of the LabVIEW process. I verified that running the .NET example as an exe and the windows based task monitor behave the same and produce the same result.
So, I have an example that works in VB, LabVIEW 7.0 and 7.1.1. but 8.0 and 8.2 cause memory leaks! I have tried numerous things to force the removal of the references but nothing seems to have worked. Here is a list of things I have tried in LabVIEW 8 to force the closing of the reference:
- Error detection after each property node/invoke node to catch any errors for the mem leaks
- Deallocate Memory function is placed in every VI.
- All VIs running in the User interface thread to avoid thread collision, also tried running in the IO thread.
- Debugging turned off on all VIs.
- All references converted to controls (instead of constants) and made not visible on the front panel. I hoped this would not force an update to the FP or memory.
- All Open and Close references are in seperate SubVIs for memory deallocation.
- Time delay of 3 seconds in between each property node/invoke node to make sure deallocation can occur.
- Forced recompile and saved all. Rebooted in between all attempts and changes above.
- Put all code and ocx control in a SubVI and called it through the main program as a SubPanel. I can see memory deallocation, but its not a full deallocation. It deallocates about 40k, but the load eats up 80-90k. VB and LV7 deallocate about 20k, increase 55k for the load, then drops 30k after the load and results in about 3-4k in memory for LabVIEW.
I am hoping through this post that someone can help me out with understanding why LabVIEW 8 would handle closing references differently than that of LabVIEW 7. I feel as though i have attempted nearly everything I can to get LabVIEW 8 to work with this example. I have an open reference (ha thats funny) with NI to look at this but wanted to see if any of you had any thoughts? Thanks!
Try it out for yourself here please....
LabVIEW 7.1 Code (1.1Mb)
LabVIEW 8.2 Code (1.1Mb)
Third Party program(77MB)
Memory graphs between 7 and 8 (50k)
Memory Monitor Tool 8.2exe (700k)
Kevin Shirey
PVI Systems Inc.
Certified LabVIEW Developer

Thanks for the reply,
On the first issue, I believe this made sense as it made no difference, but was a recomendation from NI so I tried it.
On the second issue, I just put in a close ref on the input to the Variant to Data function. This ensures that the reference being passed iin will be empty. The Variant to Data function only creates a new instance of the type of reference being passed in. At this point in the code, the reference has already been closed from a previous VI and I am only using it as a type, as I know it doesn't replace the reference. This was a good check though and looked at all my other variant to data functions just in case but still the same results in LV82.
Third thing is that I tried the profiling tools but it didn't offer a way to track active x data or the memory leak at all. They offered me how much average memory and max they used.
thanks on the fourth. I put in some extra error dialogs now there in case something does happen.
As far as the error detection VIs, they work very well for what I need them for. I like to put in unique error tags in each VI. So long as the error check VIs are in place after each routine, I know exactly where the error occurs because of the error code. So when an error occurs, a dialog box comes up with the LabVIEW error code, VI path and unique error code. It also provides an option to debug which is very cool. It will open the vi with the error and pause it. Then open the block diagram and turn on the light bulb and wait for you to unpause it. This lets you see exactly where the error happened so you can come back to it. It also can record it to a log file or ignore all errors of this type. There is still some things I need to do to it, but its been a work in progress over the years.
What boggles my mind is that the code has no memory leak in LabVIEW 7, 7.1 but has a loss of 40-50k each iteration i LabVIEW 8,8.2. If you have any other suggestions, I am certainly open to trying them.
I am currently investigating a subpanel option to encapsulate all the active x code in another VI and calling it dynamically. Its too early to tell how much this will change things, but I believe the memory leak is because the ocx control of the graph on the main panel is not being released because the main VI never goes idle. If this is true, then the ocx control will be forced to close and deallocate memory because of the dynamic call. When I have the results, I will post em.
Thanks!!
Kevin Shirey
PVI Systems Inc.
Certified LabVIEW Developer

Labview pauses

Similar Messages

Maybe you are looking for