Labview 2012 image control freezes in executable

Hi there,
I've put some Image controls on the front panel. On the development system, the background is grey and the ROI tools responsive.
The executable howeve, has black backgrounds and the image control is not responsive any more.
LV 2012, Windows 7, 64 Bit. It does not matter if the file is compiled on a server or locally.
Sometimes the compiler fails because of "file permission errors". If not, the problem still persists.
What do I do wrong ?
Best regards,
Ted
Attachments:
PanelTest.zip ‏13 KB

Hi there,
I forgot to tell that it's not possible to load any images into the control.
Regards,
Ted

Similar Messages

Using IMAQ Image controls in LabVIEW steps

Hi guys
So far, I was using TestStand 4.0 together with LabVIEW 8.5 and Vision Development Module 8.5 with no problems. Recently, I've updated to LV 8.6 and VDM 8.6. I've started to experience weird problems when using LabVIEW steps with inputs/outputs containing IMAQ Image controls. When I try to click on such a step in seq editor, or try to insert a new step into the sequence, the step initialization takes a very long time (tens of seconds) or freezes completely. I've also tried to upgrade TS to version 4.1, but no difference. Also, my colleague experiences very similar symptoms on the same software setup. The only difference is that on his machine, it takes only a few seconds when you click on the vision step. However, the steps not containing an IMAQ Image control behave normally, i.e. you can't experience any "initialization time" when clicking on them in the sequence.
To illustrate, I'm attaching a simple VI containing nothing more that a single IMAQ Image control. If you don't link it to the connector pane, the VI works fine when inserted as a TS step. If the IMAQ Image control is linked to the connector pane, TS freezes when inserting such a step.
Vladimir
Solved!
Go to Solution.
Attachments:
ft5.vi ‏5 KB

Hello Vladimir,
Thank you for posting on the NI Discussion Forums. This was reported to R&D (#123249) for further investigation. The only workaround I can offer for now is to work with the VIs from version 8.5 of LabVIEW if they have vision controls linked to the connector pane. Thanks for the feedback!
Chris_G
Sr Test Engineer
Medtronic, Inc.

When will the Ingenia Motion Control Library be available in LabVIEW 2012?

http://sine.ni.com/nips/cds/view/p/lang/en/nid/210877
I get the following error when I try to open an Ingenia example in LabVIEW 2012
1) Does anybody know when this library will be available in LV2012?
2) Are there any other motion control librarys available for LabVIEW?
Patur Sivertsen Vase
www.hfjensen.dk

It looks like the block diagrams have been removed so no version of LabVIEW will be able to open it.
Contact the manufacturer if you need assistance:
www.ingeniamc.com/En/Soporte/Soporte-Tecnico.aspx
English home page:
http://www.ingeniamc.com/En/default.aspx?ChangeLanguage=true
-AK2DM
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

Missing vi.lib files in Run-Time LabVIEW 2012

Hi
I've got a problem executing VI's under RT in LabVIEW 2012.
Our system consist of multiple independent modules which are opened and run from a Manager VI. VI paths to the modules are read from an .ini file by the Manager VI.
We have build a single executable (RT Launcher) that takes the path of the Manager VI as argument (Attachment : RT Launcher.png).
The RT Launcher is placed in the ..\National Instruments\LabVIEW 2012 folder as the LabVIEW.exe.
The RT Launcher is called from the CLI.
"C:\Program Files\National Instruments\LabVIEW 2012\RT Launcher.exe" "C:\Workspace\Labview\Manager.vi"
This will run the Manager.vi in the RunTime Environment and the Manager.vi will open the .ini file and execute the Module VI's one by one.
By calling the RT Launcher.exe from the same folder as the LabVIEW.exe, the search paths should be the same.
The system worked fine in LabVIEW 2010.
The Manager VI is opened with broken arrow and the errors indicate that vi.lib sub VIs are missing (attachment : Manager VI errors.png)
I know there are issues regarding object cache and separated compiled code from LV2010 -> LV2011 -> LV2012, but simply can't figure out how to come around this problem.
Can anyone explain the difference and how to solve the problem ?
Thanks
Regards Kahr
Certified LabVIEW Architect
CIM A/S
Solved!
Go to Solution.
Attachments:
RT Launcher.png ‏68 KB
Manager VI errors.png ‏35 KB

Hi Kahr.
It sounds like you are making some dynamic calls to VI's, eg. by using 'Open VI Reference'. My answer is based on that assumption.
You are absolutely right. In LabVIEW2010 we introduced a function called 'Separating Compiled Code from VI'. At that time none of the VIs from VI.lib had that option enabled. In LabVIEW2011, many VI's in VI.lib have, by default, a separation of compiled code and VI. This option cannot be changed (greyed out) for these VI's as well. This feature was introduced in order to simplify source code control.
Separating Compiled Code from VIs and Other File Types
The drawback is, that it is no longer possible to call VI's dynamically from an application (executable), when this option in enabled, since the compiled code no longer exists. The method of calling a VI dynamically from an application has been (and still is) used to make some kind of a plug-and-play architecture, meaning we have one EXE-file that only gets distributed once and a set of subVI's that gets redistributed according to new versions (new features added to the subVI), meaning we can make changes in the subVI without having to redistribute the EXE-file.
With the release of LabVIEW2011 and LabVIEW2012 we can no longer distribute VI's that uses functions from vi.lib, this also include DAQmx calls even though the DAQmx driver is installed.
The simple explaining is, that it has never been intended that VI's got distributed. Eg, when Microsoft is making a new software update for Windows7, they don't send out the source code to all the users.
The solution is therefore to wrap up the source code into 'something' that includes all the compiled files. In LabVIEW we do that in a couple of different ways.
1) Include the VI's in the EXE-file.
When building the application, we have the option to include files, that normally is not included in builds. If we call a SubVI dynamically this will not automatically be included! However, the drawback of this method is, that if you need to change something in one of your SubVI's, you would need to build and distribute the entire application. Thereby, we are not making use of the plug-and-play architecture that we originally wanted. However, this method will fix the error.
Error 1003 When Using VI Server in a LabVIEW Application
2) Now, if we still want the plug-and-play architecture in LabVIEW2011+2012 (and this will properly be the same for the next many released of LabVIEW), this can still easily be achieved by making a Source Distribution. When we make a Source Distribution, we can include the VI's from VI.lib and thereby the compiled code. When using this method, two important things should be remembered:
a) Make the files into a LLB file. This will pack all the VI's into one single file, that is easy to distribute.
Go to Destinations ==> Destination Type ==> LLB.
b) Make sure not to 'Exclude files from vi.lib', as this method will then simply not work.
Go to Additional Exclusions ==> Remove checker mark in 'Exclude files from vi.lib'.
How Can I Call a VI Dynamically from an Executable Without Including Those VIs in the Build?
I have made a small example to demonstrate this:
Example: Using vi.lib
This example has two mainVIs and two EXE-applications. Build the two EXE-files, but do NOT build the source distribution yet.
1) Main(IncludeSubInExE). This version has included the subVI in the build distribution for the EXE-file. When running this EXE everything works fine, even when calling the subVI dynamically. However, since the subVI is build into the exe, we would have to redistribute the exe for every new version of the subVI. This breaks the hole idea.
2) Main. The subVI is no longer included in the build. When running and trying to call the subVI, you will get this error (on both your developer and run-time machine):
Now, build the Source Distribution and run this EXE again. The exe is running perfectly with no errors.
I hope this answers your question.
Best Regards
Alex E. Petersen
Certified LabVIEW Developer (CLD)
Application Engineer
Image House PantoInspect
Attachments:
Using vi.lib.zip ‏83 KB

Issues with windows 7 after Labview 2012 installation

Hi
I am having some issues after installing Labview 2012 on machines running Windows 7. Firstly, after installing a program on a user's machine, the machine sometimes takes 20 minutes to boot up before the user can log on. The 'Please Wait' message appears during this time. This is also the case on the development machine.
Secondly, on the development machine, I am having an issue when trying to run compiled programs created in Labview. When installing, everything works fine but when I go to open the program, it appears on the task bar for a brief period before closing. It does not appear in the task manager either. I have tried this on 2 other machines with windows 7 and Labview installed and still get the same issue.
Any help on these matters would be much appreciated. Thank you

Hi
Firstly, looking at the issue with the slow Windows 7 boot up time, as Norbert_B suggested the Windows Event Log is a good starting point to find the root of the problem. The following link describes how to launch “Event Viewer” and some common problems:
http://itexpertvoice.com/home/what%E2%80%99s-taking-so-long-how-to-fight-slow-startup-times-in-windo...
Aside from that, if your computer is part of a domain, the problem may be connected with certain Windows Services that start automatically on boot up. I recommend trying the following steps:
Open up “Control Panel” go to “System and Security” then “Administrative Tools” from here launch “Services”.
Sort the list by name and scroll down to “Network Store Interface Service” right click and select “Properties”. Under the startup type dropdown select “Automatic (Delayed Start)”.
Next scroll down to the “WebClient” service again under “Properties” this time select “Disabled” under the startup type.
As for the problem with running LabVIEW executables, I have a few questions:
Do you get any error codes when it closes automatically?
Does this occur for multiple executables or just one in particular?
Does the code run without a problem within LabVIEW?
Have you tried to update LabVIEW?
What hardware are you running?
Without this information I can only think it may be caused by the Windows Data Execution Prevention (DEP) security feature. So you can try the following steps:
Right click on “Computer” and select “Properties”.
Click on “Advanced System Settings” and select the “Advanced tab, then under the performance section click “Settings”.
Click the “Data Execution Prevention” tab.
Make sure it is activated for essential Windows programs and services only, or you have an exception for your EXE.
You may also find the following link helpful on debugging applications:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/debug_apps_dlls/
Let me know if these solve the problems.
Andrew.N
Applications Engineer
National Instruments

Bind FPGA host reference to type definition in labVIEW 2012 crashes labVIEW

Hi,
I am using FPGA target device 5641R and labview FPGA 2012 with 5640R ver 1.7.
On the configure window of open FPGA VI reference function, choosing the dynmaic mode shows broken arrow when wired to the 5640R configuration VIs (i.e. Configure timebase, Configure ADC default, Configure ADC NCO functions). So i tried the other option which is binding the FPGA host reference to type definition and choose the control from path C:\Program Files\National Instruments\LabVIEW 2012\instr.lib\ni5640R\Configuration\NI-5640R VIs\ni5640R FPGA VI Reference.ctl. But after that when i try to save the VI on which open FPGA VI reference function is placed, labVIEW crashes. I am unable to figure out the reason. Earlier I was working with labVIEW 2011 and it was working fine there. Any suggestions would be highly appretiated.
Please see the attached images for more details.
Thanks
Attachments:
1.png ‏33 KB
2.png ‏71 KB
3.png ‏40 KB

Check out this thread. It looks like someone else ran into a similar issue and made changes that fixed their application.
http://forums.ni.com/t5/IF-RIO/correct-5640r-template-use-recommendation/td-p/1331918
Jeff B.
Applications Engineer
National Instruments

Saving image in image control

Hi Everyone,
The labview image control has a right-click context menu that includes the option so save the image. I've found that this works fine in the development environment. If I click it, a file dialog opens allowing me to chose where to save the image. However, once an exe is built, the option will still be there but clicking it seems to do nothing. Is this a known bug or could it be a problem with my installation?
I'm running Labview 2012 SP1.
Thanks for the help,
-Gary
Solved!
Go to Solution.

That seems dumb. Should there be a CAR for this? I was under the impression this worked in an EXE as well.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Is Labview 2012 run-time on TPC-2206?

When I go to Uninstall programs on my TPC-2206 I see Labview Run-Time 2009, 2010 and 2011. Labview 2012 Run-Time does not show up in the list. When I download and install it, I still only see the above plus a generic National Instruments program. The new TPC-2206 touch panels we have show a generic National Instruments program in the program list, but I don't know how to find out if that is Labview 2012 Run-Time. I can't find anywhere on the NI website that lists what Run-Time software is already loaded on the Touch Panels.

I did try running a Labview 2012 executable after I had put up the post. It did not work, so I knew that Labview 2012 Run-Time was not on it. I put Labview 2012 Run-Time on it, but afterwards when I looked in the Remove/Change programs list in the Control Panel, Labview 2012 Run-Time was not in the list of installed programs. There was a generic National Instruments program, but there was nothing identifying what NI program it was. This was the real problem, because all of the earlier versions of Labview Run-Time were clearly identified in the installed programs list and Labview 2012 Run-Time was not. There is no way to know if Labview 2012 Run-Time is installed except to try to run a Labview 2012 executable.

Problems distributing application using Imaging Source USBCamera and Labview 2010 - Imaging Source sdk required?!

Hi
I've been having trouble with the Imaging Source camera we own when trying to build applications.
Everything works perfectly on the dev PC with appropriate sdk installed.
When I move to building the application (no errors) and deploying it to another PC the activeX control used to interface with the camera does not appear.
Instead I get 'Control could not be loaded' in red text where the control should be.
As far as I can see the activeX component itself is correctly installed on the PC.
If I install the IC Imaging Control sdk the application begins working correctly.
If I uninstall the sdk from the dev PC I get the message about needing a license if I attempt to add the ActiveX control afresh to the program (via the activeX container)
I've posted on the Imaging Source forums and they suggested I try here.
ORIGINAL POST ON IMAGING SOURCE FORUMS:
I'm using a DMK 41BU02 with labview 2010 + IC Labview extension.
The activeX interface for the camera works fine until I deploy it to a PC that does not have the IC Control software installed.
All I see is a 'Control could not be loaded' message where the activeX box should be.
I've installed VB6 redistributable to the client PC so I know the activeX workings should be present on the PC.
If I install IC Control onto the PC the program starts working correctly!
Has anyone compiled software with Labview 2010 successfully?
Is there a trick when creating the application/installer spec?
Thanks in advance
Dan Acres
REPLY
This is correct. I suppose, the LabVIEW setup creating system does not automatically add the used DLL in the "user.lib" directory of your LabVIEW installation path. What does the LabVIEW support say about this, especially in relation to ActiveX controls, that use the Microsoft licensing mechanism?
The dll he mentions is packaged into the support folder in the application spec.
I have also manually copied the dll into the location referenced by the software (Labview 2010\user.lib\xxxx.dll).
This made no difference.
I've got no experience building these kind of thing into applications so I cannot tell if it is caused by a mistake I've made or Labview or if the Imaging Source softwares have done something wrong.
Many thanks in Advance
Dan Acres

Dan,
I think I might have a solution for you and others who need to include the imaging source active-x control in a deployed executable program.
I solved this problem by creating a project that included the dlls and .ocx files required for the Active X Control (these files are in a folder is created once the IC Software is installed C:\Program Files (x86)\Common Files\IC Imaging Control 3.2) and an executable that registers the Active X Control after the main program is installed.
The simple vi that registered the .ocx control for me upon install of my LabVIEW executable was called RegisterActiveXCtrl.vi. All it does is calls the regsvr32 with the path of my .ocx file.
I bundled my main program PCDemo_Stratom.exe and RegICActiveX.exe into an installer and set the option to run RegICActiveX.exe at the end of installation.
The installer must be installed with administrator rights to get the RegICActiveX.exe regsvr32 call to work.
Hope this helps you/others in the future!
Dan A

Custom SharePoint 2010 designer page throws "The data source control failed to execute the insert command" exception while adding the new item after the August 13, 2013 CU has installed

We have the SharePoint Server 2010 with SP1 environment on which the custom SP2010 designer pages were working as expected before the
August 13, 2013 CU has installed. But, getting the below exception while trying to add the new item after the CU has installed.
Error while executing web part: System.NullReferenceException: Object reference not set to an instance of an object.     at Microsoft.SharePoint.WebControls.SPDataSourceView.ExecuteInsert(IDictionary values)     at
System.Web.UI.DataSourceView.Insert(IDictionary values, DataSourceViewOperationCallback callback) 3b64c3a0-48f3-4d4a-af54-d0a2fc4553cc
06/19/2014 16:49:37.65 w3wp.exe (0x1240)                       0x1300 SharePoint Foundation
Runtime                       tkau Unexpected Microsoft.SharePoint.WebPartPages.DataFormWebPartException: The data source control
failed to execute the insert command. 3b64c3a0-48f3-4d4a-af54-d0a2fc4553cc    at Microsoft.SharePoint.WebPartPages.DataFormWebPart.InsertCallback(Int32 affectedRecords, Exception ex)     at System.Web.UI.DataSourceView.Insert(IDictionary
values, DataSourceViewOperationCallback callback)     at Microsoft.SharePoint.WebPartPages.DataFormWebPart.FlatCommit()     at Microsoft.SharePoint.WebPartPages.DataFormWebPart.HandleOnSave(Object sender, EventArgs e)
at Microsoft.SharePoint.WebPartPages.DataFormWebPart.RaisePostBackEvent(String eventArgument)     at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)     at System.Web.UI.Page.ProcessRequestMain(Boolean
inclu... 3b64c3a0-48f3-4d4a-af54-d0a2fc4553cc
06/19/2014 16:49:37.65* w3wp.exe (0x1240)                       0x1300 SharePoint Foundation
Runtime                       tkau Unexpected ...deStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 3b64c3a0-48f3-4d4a-af54-d0a2fc4553cc
I have tried changing the "DataSourceMode" as below, now the insert command is working, but update command is not working.
<SharePoint:SPDataSource runat="server" DataSourceMode="ListItem" />
Also, the lookup dropdown fields are displaying the value as "<a href="Daughterhttp://cpsp10/sites/Employees/_layouts/listform.aspx?PageType=4&ListId={8F62F444-FB6A-4F03-9522-C4696B45DCD1}&ID=10&RootFolder=*">Daughter</a>"
instead of only "Daughter".
Please provide the solution to get rid of this issue.
Thanks
Ramasubbu

Try below:
http://social.technet.microsoft.com/Forums/en-US/ae910269-3a0c-4506-844b-e8bc89d95b71/data-source-control-failed-to-execute-the-insert-command
http://blog.jussipalo.com/2012/01/sharepoint-2010-data-source-control.html
While there can be many causes for this generic error message, in my case the first parameter or ddwrt:DataBind function inside the SharePoint:FormFields element was
'i' and I was working with an Edit Form. Changing it to
'u' as it was with every other FormField fixed the issue.
<SharePoint:FormField runat="server" id="ff1{$Pos}" ControlMode="Edit" FieldName="Esittaja" __designer:bind="{ddwrt:DataBind('u',concat('ff1',$Pos),'Value','ValueChanged','ID',ddwrt:EscapeDelims(string(@ID)),'@Esittaja')}"
/>
Explanation:
DataBind operation type parameters (the first parameter) are listed below:
'i' stands for INSERT,
'u' stands for UPDATE,
'd' stands for DELETE.
http://webcache.googleusercontent.com/search?q=cache:d9HHY4I7omgJ:thearkfloats.blogspot.com/2014/03/sharepoint-2010-data-source-control.html+&cd=4&hl=en&ct=clnk&gl=in
If this helped you resolve your issue, please mark it Answered

Image not displayed correctly in image control at small zoom level

I am displaying an image in an image control with a zoom factor of ~0.015 and it appears as shown in image 1.jpg. When I zoom in a little more to ~0.016 the image is displayed correctly as shown in image 2.jpg. Both images are attached.
Why is the image displayed as a "grey strip" in the first image? What do I need to do to have the image displayed correctly at any zoom factor? I am using LV 2011 with the associated vision development module on Windows 7.
Thanks,
Jonathan-LV
Solved!
Go to Solution.
Attachments:
Image 1.jpg ‏133 KB
Image 2.jpg ‏152 KB

Hi Jonathan,
Did you try resizing your image dimensions, as I suggested in my previous post? Anti-aliasing is an expected behavior; as you zoom out, the image has to be resampled in order to be displayed properly. At some point, LabVIEW assumes that the image has been resampled to the point where it no longer resembles the initial image, and so it greys the image out. In the case of your image, that is not the case. As I said, I believe an acceptable workaround would be to use IMAQ resample to half or quarter the pixel dimensions of your image, at which point it should be able to be displayed at a higher zoom factor.
Best,
Dan N
Applications Engineer
National Instruments

Vision Builder 7.0(IMAQ) : Using fxs in subVIs with references to image control

When using IMAQ fxs (such as 'Write File') in subVIs, if one wanted to use references to an image control, what property or method would be used to feed into the image terminal in the imaq fx on the subVI? Is this possible?
What did work: I was able to directly use the image control on the main feeding an image control on the subvi panel (which is then fed directly to imaq fx)
What did not work: From a refnum control for the image on the main, I used (within the subVI) the value property fed to a 'Variant to Data' with type as image control, then feeding the output of this into imaq fx.

Typically you would update an Image Display control from a subVI using the Value property nodes. However, this method does not currently work with LabVIEW 7 and Vision 7, but the issue will be resolved in the next release of LabVIEW and Vision.
In the meantime, in addition to the solution you found you could also use a global variable to pass images from one VI to another. Using a global variable works, but not in the same way as a reference or property node would. With a reference or property node, you can pass a reference of the control to a subVI and have the subVI update the control's image. Using global variables, the subVI will update the global variable with the new images, but you need a loop monitoring the global variable in your top level VI.
I hope this
helps! Best wishes.
Regards,
Dawna P.
Applications Engineer
National Instruments

Two instances of quirky behavior: array size of empty array and tab control freeze

LV 7.1
Array size of empty array. Adding empty arrays to an array of higher dimension produces a fantom array of non-zero size.
Tab control freeze. An event structure with checked 'lock front panel until the event case completes' option permanently freezes the front panel in certain special circumstances.
Zador

tst wrote:
Tell me if you still think this makes sense.
Whew, let me look at this tonight after I activate the 4D module in my brain.
(I think it makes sense, though ) Generally I look at the product of the dimensions array to determine if an array is empty. You can initialize a multidimensional array with some dimensions at zero and it is reproduced nicely in the array size output. Also the "Empty array" tool correctly identifies it as empty, even if some dimensions are nonzero.
Message Edited by altenbach on 03-15-200612:42 PM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
init.png ‏3 KB

Again mixed signal graph and Labview 2012

I have just experienced a weird change in labview 2012 on the mixed signal graphs. In a preliminary analysis, it seems that the most critical behavior is related to the silver mixed signal graph, although i didn't have the time to test the standard one.
Straight to the point... the property "plot area size" not only resizes the plot area, but also the graph; this is in contrast with what happened previously in LV2011. If the graph belongs to a subpane and if the property "fit control to pane" is enabled, the area resize prevents the graph from correctly fitting the pane.
Any suggestion?
cheers
m.
Attachments:
MixedSignalDisaster.vi ‏13 KB

I think that since this behavior is a regression (working properly until LabVIEW 2011 SP1) this should be fixed as soon as possible through a specific fix, without waiting for the next Service Pack.
This regression has been blocking the development of our application.
Could someone from the NI support give an answer, please?
Vix
In claris non fit interpretatio
Using LV 2013 SP1 on Win 7 64bit
Using LV 8.2.1 on WinXP SP3
Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

Image control- setting images conditionally

Hello All!
I am a Labview newbe and I need help with image control. I have a set of two images- one static png and one animated gif. I want to use these two images as an activity indicator in a picture box or other control. I can send one or the other to the picture box programmatically in the function block screen but I do not understand how to set the image control conditionally for condition "A" and condition "B". The code below is for two separate picture boxes. My goal is to select one image to show in a single box depending on conditions "A" or "B". The two conditions are "not running" and "running". Can this be accomplished with boolean logic? I also hope to use such a control in the future for multiple conditions to help illustrate to the user a specific hardware item to pay attention to. I am using LV 2014 on a Windows 7 box. The built VI will be used on Windows 7 and XP.
-cmengineer

Happy Sunday Evening All!
I have included all files in the zip file. I changed the image for one state to a jpeg and changed the control to a jpeg control. This works to demonstrate the state change but my goal is to use the gif which is shown as decoration in the middle of the vi front panel as the running state indicator.
Now that I have tested it, I think I need to work on the file write operation as well. Instead of getting my four points of data in a row, I get one or another. Always fun!
-cmengineer
Attachments:
MyPTA_Monitor2.zip ‏1554 KB

Labview 2012 image control freezes in executable

Similar Messages

Maybe you are looking for