3D graphs cause LabVIEW 2010 to hang

I've been using LabVIEW 2010 for several weeks without any problems, but today I noticed that it doesn't work at all with anything related to the 3D picture control. Today was the first time that I tried doing anything with the 3D picture tool since installing LV 2010. Dropping any of the 3D Graphs on the front panel of a new VI causes LV2010 to hang. (By hang, I mean the VI window remains open but most UI things no longer work. Right-clicking on the window does not show a context menu. The main menu doesn't work. The X button does not close the VI front panel window nor the diagram window. Control-Q does not cause LabVIEW to quit. I have to kill the process in Task Manager.) It is the same story with just a plaing 3D picture indicator. Also, the solarsystem.vi example does not work either. The problems start as soon as I open the solarsystem.vi. After killing LV with Task Manager and relaunching LV10, I do not get the LV message about a previous crash.
The problem I am talking about is for LabVIEW 2010 with the f2 patch running in Win7. I am actually running it using VMware Fusion 3.1.3 on a 2009 Mac Pro running Lion. The Mac drivers are all updated. Since it is VMware Fusion machine, the video driver on the Windows side is part of the VMware Tools installation, which is up to date.
After searching the forums, I've tried all the other potential solutions I could find: 1) repaired LV2010 using add/remove programs and 2) tried using the compatibilty mode settings to turn off Aero.
Interestingly, 3D graphs work fine on the Mac side for LV2010 for Mac.
Even more insterestingly, 3D graphs work fine on Win7 for LV 8.5, which I still have installed. The fact that it works fine for LV 8.5 would seem to indicate that Lion did not introduce the problem and that the video driver is working fine.
Solved!
Go to Solution.

Yep, it's the same virtual machine. I set it up almost 2 years ago and it has been extremely stable. Both LabVIEW 8.5 and 2010 have been perfectly happy on it. It's a great way to do LabVIEW on Win7. I didn't notice any changes at all to the VM when I upgraded from Snow Leopard to Lion. I installed LabVIEW 2010 before upgrading to Lion, but I didn't have occasion to work with 3D controls before the upgrade to Lion so I don't know if it would have worked on Snow Leopard. The Mac versions of both LabVIEW 8.5 and LabVIEW 2010 also work great on the both Snow Leopard and Lion.
I happen to have an XP virtual machine too, but I haven't installed LabVIEW there. Let me know if that would be a worthwhile test.
You might check with Marc Page--unless he has already upgraded again I think he has a similar machine to mine.
The video card is the original stock:
NVIDIA GeForce GT 120:
Chipset Model: NVIDIA GeForce GT 120
Type: GPU
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Total): 512 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0640
Revision ID: 0x00a1
ROM Revision: 3386
Displays:
Cinema HD Display:
Resolution: 2560 x 1600
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Display Connector:
Status: No Display Connected

Similar Messages

Facing memory error during shifting from 3d stem graph to 3d surface graph in labview 2010

hello all,
earlier I was using 3D Stem graph in labview 2010. Now we want to move to Surface plot for same data.when i am trying surface graph it shows memory error.
I have 10240 data.
I was using vector method in stem graph so now for Surface graph i have thought that i have to make matrics of 10240x10240 and its diagonal elements should be my Z co0ordiants.
plz help me out here.
thanks & regards,

hello mikeporter,
thanks for reply.I am attaching my Vi. It has some error also.plz look into it.
X and Y are my co-ordinates pairs.I will be having values for these and have to update for same.
Attachments:
Untitled 2_surface.vi ‏184 KB

Some emails from a particular sender causing Outlook 2010 to hang, task manager shows memory use spikes

Posting this to the Exchange forum because I'm hoping there's a server-side solution.
SOME emails received from an external sender (gmail.com address, not sure the mail client) are causing Outlook 2010 to hang when trying to open the email. Outlook becomes non-responsive when viewing the email through the preview pane or by double-clicking
the email. If I open Task Manager I see that the outlook.exe process memory use starts increasing very quickly. As far as I know the only resolution is to end the task and re-open Outlook (and avoid that email).
I've found several excellent threads on these same symptoms, but there seems to be a variety of causes. I've tried a bunch of things so far:
- Tried opening from another system on our network running Outlook 2010, same issue.
- Tried opening from OWA, opens fine.
- Tried exporting the email to a PST, then opening from a completely different system outside of our network, but still running Outlook 2010, same issue.
- Tried exporting the email to a PST then opening from a completely different system outside of our network, running Outlook 2013, email opens fine.
- Tried setting Outlook to open all emails as PLAIN TEXT, opens fine.
Systems are running the latest Outlook 2010 SP and patches, and running a variety of OS's. Only common denominator seems to be Outlook 2010.
I was hoping to find a way to convert incoming emails from this sender to open as Plain Text using a Hub Transport rule, but cannot find a way to do it.
Unfortunately I have no control over the sender, so don't know what could be triggering the problem.
Can anyone advise on a possible solution? Any way to someone convert emails from a particular sender to Plain Text automatically?

Either you inform the sender to configure in sender's outlook to send only to you in plain text please check this
http://office.microsoft.com/en-001/outlook-help/change-the-message-format-to-html-rich-text-or-plain-text-HA101992313.aspx
Or
Call a macro in your outlook example below. Please check
this for details
Dim msg As MailItem
For Each msg In myNS.GetDefaultFolder(olFolderInbox).Items
If msg.Unread = True And _
msg.SenderName = "Linda Cooper" Then
Item.BodyFormat = olFormatPlain
Else
' Message doesn't meet criteria.
End If
Thanks,
MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Error 404 causes Labview 2010 to crash but only occasionally

Hello,
I am requesting help to solve a problem with LabVIEW 2010 crashing. I am new to this company and the last Labview developer left without providing
background on this problem. Labview crashes after running project VIs. Labview closes without warning or error messages. The project acquires data from pressure transducers, dP transducers, thermocouples, IEPE, load cells, and voltages through NI real-time system and has digital I/O. NI hardware includes PXI-1050 with modules 6221, 6280, 6224, 6220 and NI PXI-1052, SCXI-1306, SCXI-1112, SCXI-1520, and SCXI-1102. I've reviewed the labview program and the software relies heavily on shared variables, references, and local variables but I cannot find anything that stands out as a problem in the software .
The program crashed again today after running for only 1/2 hour and was not recording data. No error message occurred before the crash and the only error after restarting LabVIEW was the standard message that LabVIEW did not close properly. I went to the Event Viewer and at the time of the crash I received the following information:
Event ID = 3299
Source = LabVIEW
Log = Application
Level = Error
LabVIEW Information: Error 404 "Not found" for "/national instruments/ real-time execution trace toolkit/ 2.0/ trace receiveport", file "Crogram files (x86)/ national instruments /shared/ ni webserver/ www/ national instruments/ real-time execution trace toolkit/ 2.0/ trace receiveport": Can't access URL
According to Event Viewer, this error 3299 occurred 15 times in the last 3 days. LabVIEW crashed today at 10:19 am at the same time this error 3299 occurred but LabVIEW did not crash the other times this error occurred in the last 3 days. I believe this error is related to the crash but does not usually cause the crash. It appears to me from reading the error message that the error is the result of occasional lose of communication with the real-time system (Can't find URL). Any suggestions how to resolve this would be greatly appreciated.
Bill

1. Have you had this code working before on this or another machine?
2. Which operating system and version of LabVIEW are you running? (This can be found in Control Panel >> All Control Panel Items >> System)
3. Which National Instruments Drivers are you using? (This can be found in the measurement an automation explorer under the software tab [a screenshot would be good])
I would look into removing afsetup.exe which is a data collection tool provided by Microsoft which could a) not be installed correctly and/or b) trying to pull data from LabVIEW. I think this may help you out, as even though your programs aren't explicitly calling it, the service is running in the background.
Secondly, I would look into stopping the NI Web Server application that could be polling a web page that's not needed.

Bug in Formula node under LabVIEW 2010

appendix is my test project.
there is a test.vi in the project. The test.vi contains only a case structure with 5 SAME subdiagrams. Each subdiagram contains a formula mode. The formula code does some calculation with an 2d array of double.
If i run the test.vi under LabVIEW 2010(or SP1), it may cause LabVIEW 2010 corrupt occasionally. If I build application form the test.vi, and run the application ,the application will definitely corrupt.
if I delete one subdiagram of the case structure , the test.vi and the application both run well.
however, the same project works well under LabVIEW 2009.
so is it a bug with LabVIEW 2010?
Attachments:
Test.zip ‏7 KB

'corrupt' means the program exit unexpectedly without any warning or error message. it just disappeared and you can't find it in the 'process' tab of windows task manager after that.
If LabVIEW corrupted, once i reopened it, there may be a error message dialog pop-uped before the LabVIEW interface appeared. The dialog said something wrong with 'undo.cpp'. I zipped the failure long to the appendix. I can't find any other error or warning message from LabVIEW or Windows ( I checked the Windows Event Viewer).
If the built exe corrupted, There isn't any message for LabVIEW or Windows neither.
I tested the project on my own laptop with Windows XP(SP3) Chinese Version and NI PXI-8810 with Windows XP(SP3) English Version which is my target machine.
Appendix also contain a exe build in my laptop. If I run the exe file, once I click the run button , it will corrupt. I wonder if it works the same on your computer.
Thanks for your concern.
Attachments:
lvlog2011-05-13-23-23-35.zip ‏150 KB

Loading my VI in LabVIEW 8.2.1 causes LabVIEW to hang.

Loading my VI in LabVIEW 8.2.1 causes LabVIEW to hang. I have an older version that sometimes loads, but it causes LabVIEW to hang many of the times as well. I think the older version of my VI only hangs when you try to scroll around by clicking in the scroll bar area instead of clicking the scroll arrow. I am not getting any error messages. I have to close LabVIEW using the task manager. I've tried this on multiple computers with the exact same results. The VI has sensitive information, so I would rather not post the VI publicly. If you have the capability of debugging a hung LabVIEW .VI, then please send me your email information.
Thanks,
Matt

Hi Matt,
nice to hear that trick helped. Usually LV informs you about any "insane objects" before saving, in this case you should perform this procedure immediatly... When the vi "kills" LV while loading it's too late.
To rate messages you should click on those "kudos" buttons right to the message. Once should be fine, but it's Christmas time and nice to give away presents Maybe you're too new to the forum and this option isn't enabled yet?
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

LabVIEW 2010 SP1 may not cleanly shut down

Occasionally LabVIEW 2010 SP1 (32-bit, running on Windows 7) will appear to "hang" when the "Getting Started" window is closed. The window disappears but the shortcut icon still appears in the Windows toolbar in the bottom of the screen. Right-clicking and selecting "Close Program" does not work and Windows seems to think any VIs that have been recently closed are still open. The program is still in the list in Task Manager and it can successfully be shut down all the way from there.
This is more of an annoyance than an operational issue (I think) - is there something I am doing (or failing to do) that causes this problem?
Thanks in advance.

Hello Unplugnow,
Deleting the .ini file will not cause any issues in terms of being able to reload Labview it will simply restore the default settings for Labview which will insure that there were be no data corruption issues. I have tried this procedure on my side with no issue although I would recommend copying the .ini file to another directory in case you need to recover this information at a later time.
To another note, does this issue arise when you are opening a particular VI, or does it occur when you are simply opening and closing Labview?
Best,
Blayne Kettlewell

LabVIEW 2010 crashes when changing representation of TypeDef

Hello NI,
I have to report a bug
which causes LV 2010 to crash with error in "datamgr.cpp", line 2720.
This crash is reproduceable.I use LabVIEw 2010, 32 bit on Windows 7.
To cause this crash you have to perform the
following steps (I attached a sample VI to reproduce these steps.):
Place a ring control on the FP, change
representation to I32
On the BD, create a property node “Strings
And Values[]”
The datatype of this property is Array of
Cluster with 2 Elems, “String” & “Value”, where “Value” is of type I32
Create a control of this property,
surprisingly the type of Value is “extended”
On the FP, select the cluster inside the
array, click “Customize Control…” from Edit- menu
In the Control- Editor change the DataType
of Value to I32, then exit the Control Editor without saving the control,
but replacing the original cluster
LabVIEW 2010 will crash with the error
message stated above
The problem is to change the
representation of the cluster element, where the cluster is part of a typedef. A
solution is to forbid to call the “Customize”- editor directly from the FP (not
nice) or to forbid to replace the orginal control, instead force the user to
save the altered control to a .ctl (nicer).
This shows a general problem with TypeDefs,
where the array of a not-typedefed cluster is typedefed. This was discussed
earlier with the cursor list of waveform graphs (couldn’t find it anymore, but
read it in this forum) where this problem also can occur. So this is an appeal
to National Instruments to change the TypeDef to the clusters and make arrays
of them.
And, after all, for me it is
unexpected behaviour that a constant / control / indicator, created from a
property (or any terminal / node I can find on the BD) has another datatype
than the original terminal or node.
Greets, Dave
Picture 1: Type of property node
Picture 2: Type of created control
Picture 3: Error message
Greets, Dave
Attachments:
Ring TypeDef Problem.vi ‏66 KB

Hi All,
I am also facing the same bug from the long time which causes loss of data unexpected.Please solve this bug and tell me any way to solve this.I am using Control Type Def in my project.
Thanks
Yogeshwar
Attachments:
error.jpg ‏19 KB

Building App Gives Error 6 about 50 - 80 - 99% of the time. Windows7, LabVIEW 2010 SP1

Hi
First off here is a link to a discussion of the problem. http://forums.ni.com/t5/LabVIEW/Error-6-occurred-when-building-an-Executable-in-Labview-2009/m-p/997...
I have tried all the suggestions on this link with no luck.
Background: have been using LabVIEW 2010 without problems since Sept, then I started getting the error 6 with the following message.
" Error 6 occurred at Delete in AB_Engine_Delete_Internal_Files.vi->AB_EXE.lvclass:Build.vi
->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller "
This started on one project and is now occurring on another project. Sometimes it builds 50% of the time, other times I can't get it to build at all. I have upgraded to SP1, no change.
Here are some things I have tried.
Moved build directory to c:\a
Renamed project, moved project right under c:\
Disabled Google , disabled Win indexing, disabled Win7 user acct. Control, run LabVIEW as Admit all the time, win explorer closed
mass compiling, closing the project, closing LabVIEW, re-booting
Unistalled LabVIEW 2010 SP1 and re-install, twice.
I believe I rebuilt my project in a new project.
I moved my projects to a WinXP system laptop I have, and they never get Error 6 ! Short term fix, but I have to use Win7. So I hope this means it is not my code.
The funny thing is that this is totally random. The unfunny thing is having to explain to a client I can't get my code to compile during a frustrating 95% of the time failure episode, yikes!
Any help and suggestions would be welcome.
BTW, the next step is to totally uninstall LabVIEW with a 'special' procedure and piece of code sent to me. Don't want to, but am really at wits end. Also waiting to hear back from my service ticket, but am desperate to have parallel solutions to try.
Thanks
Mark Ramsdale

Thanks for the clarify.
I also meant to post this link. It has a lot of info, this is the link I tried most if not all of the suggestions for.
http://forums.ni.com/t5/LabVIEW/Get-Error-6-about-50-of-time-when-building-Application/td-p/1242634
By the way, I was told that uninstalling LabVIEW will not resolve the issue, dodged a time killer :-)
It seems the error is caused by Win7 and file reserving. Waiting to hear back on that. Have an SR.
Again, any suggestions welcomed, maybe some Win7 ideas from those who know more about it.
mr
Mark Ramsdale

LabView 2010 Application Builder for EXE Always Included files are not Included

In LabVIEW 2010 F2, When I am using the Application Builder to build an EXE file, I have listed 10 or so files to Be "Always Included". But when I Explore the directory where the EXE was built, those "Always Included" files are not there or in any subdirectory under the EXE file.
This frequently makes my EXE file not work properly because important files are missing. I have to spend extra debugging time to find out the the cause of my problem is missing files that the Application Builder should have transferred "Always".
Why did the Application Builder, when building an EXE target, not include the files that should be "Always Included"?
Why does the Application Builder ignore these files specifications?

Dennis Knutson wrote:
The build does include files you select. Post an example project with a small VI and some separate files where this does not happen.
No, it does not appear that all of the files that I listed in the "Always Include" list are copied during the Build process to the Build directory or any subdirectory under that.
The Build Source Files.jpg file shows most of the list of the files that should be "Always Included". Notice the .VI and .ctl files that are listed
The Build Directory.jpg file shows the file in the Build directory that were built.
The Data Directory.jpg file shows the data directory under the Build directory and may include some of the files listed in the "Always Include", but not all of them.
The other subdirectories under the Build directory were created by me and do not include any files that were copied during the Build process.
So not ALL of the files that were included in the "Always Include" list were copied into the Build directory area as expected. ALL of the files that are listed as "Always Include" should be copied, if they exist. Those files existed when then were selected for the List and they existed at the time of the Build.
I can not include an example project that demonstrates this. I am prevented from doing so by the terms of an NDA. You are going to have to take my word that this event is real and happens the same way every time. This information should be sufficient for someone to investigate why do not ALL of the files listed in the "Always Include" list are copied into the Build directory area regardless of the file type or contents.
Attachments:
Build Source Files.jpg ‏151 KB
Build Directory.jpg ‏125 KB
Data Directory.jpg ‏131 KB

LabView (8.2) hangs when using I/O operations with traditional NI-DAQ 7.4.4 after aborting LabView program

Hello!
We have the following problem:
LabView (8.2) hangs when using I/O operations with traditional NI-DAQ 7.4.4 after aborting LabView program
We freshly installed LabView 8.2 (2006) and NI-DAQ 7.4.4 on a PC running Windows XP (Service Pack 3). We built a larger vi that remotely controls a traditional NI-DAQ card (AT-AO-10) on a second PC via NI-VISA 5.0.3. We were successfully running this program until a power failure caused the first computer to crash. After this crash we were unable to start the program again: LabView freezes while loading the vi. LabView itself can be started but freezes when adding I/O operations from the NI-DAQ palette to a block diagram.
We have tried to re-install NI-DAQ 7.4.4, but it did not help. We then re-installed all NI software, but still no improvement. In the end we decided to reinstall ALL software, first Windows XP, then LabView and finally NI-DAQ 7.4.4. This worked. However, after a few days of running the program we had to abort LabView via Windows Task manager and afterward we again experienced the same problem as before: LabView freezes when loading the program.
Obviously, we cannot afford to reinstall Windows every time. Are there any known Windows XP / NI-DAQ issues that might cause the freezing of LabView? We would be very grateful for any idea.
Best regards,
Matthias

Hello Sprice,
Browse the shipping examples according to “Directory Structure” and then select
DAQ to find the Traditional DAQ examples.
There a lot of examples that are written for counters (Counter >>
daq-stc.llb >> Count Edges (DAQ-STC).vi).
What kind of signals are your photons creating? Are they TTL compatible at a certain
frequency? You don’t care about overwriting
your buffer?
Respectfully,
Rob F
Test Engineer
Condition Measurements
National Instruments

Labview Program will hang between 33% and 50% of the time.

I have a problem with a Labview program I made. I have two programs that do the same thing. One is in flat sequence form and the other is in state machine form.
As explained in the link below, I would like to make use of a microcontroller to make wiring connections for automating a measurement process. A separate current source and volt meter will be used.
https://forums.ni.com/t5/LabVIEW/Sequence-a-good-idea/td-p/2601333
I have since made some simple test programs which I have attached. The problem is when executing, the labview program will hang, but not every time the program is execute.
For example: Hall 1.2.vi will work properly twice with the third time it is executed it will hang. If you abort and try again, it will again run twice with no problems with the third hanging. This one is in flat sequence format (was in a flat sequence, but merged the windows because I thought that was the cause). From what I can tell, the program will hang when calling Keithley 6517 Single Read.vi. Both connected Keithley devices are connected to the computer via GPIB at 16 and 27. The way I verified if it was this vi causing it or contributing to it was that I removed it and the program never hung. I find it very strange that it will hang exactly on the third attempt every time.
Hall 1.3 simple.vi will work the first time and hang the second time. So it works 50% of the time. This one is in State Machine format. This one will hang at the case titled "Measure 1" which contains the Keithley 6517 Single Read.vi.
I've used the highlight execution button and watched the program run. Oddly, it doesn't hang when using this button. So I tried adding delays/wait in different places to no avail.
What could be causing this? As a side note, I say the program hangs for two reason. The main one is the program doesn't finish running so the run arrow is still black. The second thing is that if you notice at the end of the labview program, I have a block there that turns the current source off which doesn't happen when it hangs. I have to manually turn it off and then hit the abort program button to stop labview.
Solved!
Go to Solution.
Attachments:
Hall 1.2.vi ‏42 KB
Hall 1.3 simple.vi ‏81 KB

altenbach wrote:
SaintsFan wrote:
Also, I've tried placing wait/delays at various places with no improvement of the problem. My next thought is to just remove all the vi calls and have everything in one program.
How did you place the waits?
Why would placing everything in one program fix the problem. That makes no sense! What is your reasoning?
In the case of hall1.3, I placed a wait in the Measurement cases and CS On cases and there was no affect. In the hall 1.2 when the blocks were broken up similar to the state machine cases where each sequence window was identical to the cases, I placed a wait or delay in each window with no effect on the hanging.
My reasoning for placing everything in one program is the same as my reasoning for figuring delays would help, since the time of execution would be altered. If the execution time is faster and if the timing is the problem then I figured that the problem would happen more frequently or even every time.
Somehow I get the feeling this is not the case. The reason being the interval in which it succeeds or hangs is constant. I believe somewhere, a value is getting set. The 6517 Read vi runs fine if I run this vi by itself no matter how many or how fast I run it. Also, the same goes for both 1.2 and 1.3 if I remove the 6517 read vi they run fine no matter how fast or how many times I run them.
Somehow after the current source is set to operate and triggers labview will hang on a set interval when calling 6517 read vi.
Separately they work, together there is a problem. I tried placing a delay between these two by connecting the error out of the trigger vi to the error in of the delay block and the error out of the delay block to the error in terminal of the 6517 config block. I've also tried delays between other blocks connected the same way. From what I understand, a called vi can't execute until all inputs are present. Is this the correct way to wire the delays?

LabVIEW 2010 SP1: "Controls" pop-up palette "Select a control..." bug?

I'm using LabVIEW 2010 SP1 (32-bit) and I noticed today that I cannot place my custom controls on a VI's front panel when I use the "Select a Control..." option on the "Controls" pop-up palette. I'm wondering if anyone else is having this same problem?
Steps to reproduce the problem:
1) Create a custom control, or download/save the attached custom control "Machine State.ctl" (< a strictly-typed enum control).
2) Open a VI (new or existing).
2.1) If the "Controls" palette is visible (pinned open), close it.
3) Right-click with the mouse on the VI's front panel window to display the "Controls" pop-up palette.
Note: DO NOT use the "Controls" option in the "View" menu here.
Note: DO NOT pin open the Controls pop-up palette at this point.
See my comments below in the "Notes" section.
4) "Controls" palette > "Select a Control..." option
5) Using the "Select the Control to Open" dialog, browse to, select and open the custom control file (e.g., "Machine State.ctl").
At this point the on-screen cursor should show the outline of an instance of the custom control I just opened, but for me that doesn't happen; all I see is the "+" crosshair cursor, and left-clicking with the mouse on the front panel does not place an instance of the custom control on the front panel.
Notes:
* In step 3) above, if I open the VI's "View" menu and select the "Controls" option, or if I pop-up the "Controls" palette and pin the palette to keep it open, I can successfully use the "Select a Control..." option to browse to, select, open, and place an instance of my custom control on the VI's front panel. The failure only occurs when I use the "Select a Control..." option on the pop-up (unpinned) version of the Controls palette.
* I can successfully drag-and-drop an instance of a custom control onto a VI's front panel from a Windows Explorer window, or from the LabVIEW project explorer window.
* The host computer is running Windows 7 Enterprise x64 w/ SP1.
Jim
Attachments:
MachineState.ctl ‏5 KB

Just now I tried creating and using controls on five different computers, each running Windows 7 Enterprise x64 w/ SP1.
On three of the systems the problem did not occur; I was able to place a user-defined control on the front panel using the "Select a control..." option on the controls palette.
On two of the systems the problem still occurs. Upon further investigation, however, I learned that the hard drives in these two systems were cloned from a "master" hard drive image the IT department created. So I'm guessing there's some bad mojo on the master hard drive image, and that's what's caused this problem to show up on these two systems (and others).
So for now, I'm just going to put up with having to use the old "drag-and-drop" method for placing user-defined controls on the VIs. Thanks for your feedback and assistance with this.
Jim

Having Trouble Copy and Pasteing Local Variable in LabVIEW 2010

I am Having Trouble Copy and Pasteing Local Variable in LabVIEW 2010 in s subVI.
I have a VI that has a Local Variable called "Node Addr". I can select it OK, and it appears to Copy OK, But when I go to paste it, nothing appears. It doesn't matter if I use Cntrl-C Cntrl-V or the Copy and Paste from the Edit menu, I get the same results. I tried many times and got the same results. I made sure that I had click a paste location. I can insert the Local Variable if I use the Data Communication panel.
On one of the Paste, I got an error in the error list that said that a Local Variable was not connected to anything. When I clicked on the error, it took me to an insible item in the lower right corner of the block diagram that had nothing but a select box around it. I couldn't select the invisible item, but I could delete it.
Why does the copy and paste of this local variable not work?
Why does the paste cause the insertion of an invisible item?

dbaechtel wrote:
My VI is fairly complicated. In several places in the VI, I am either reading or writing to this variable which is an numeric Indicator on the Front Panel. Using local variables seems to be the best way to handle this situation rather that using wiring all over the VI. Since the VI is mainly a State Machine and there are only 2 Writes to the local variable, I am not afraid of race conditions in this case. NO!! While you may think that using Locals is your solution to wiring, it is not! The fact that you are writing and reading, most likely from several places, will most definitely contribute to a race condition. Depending on your implemetation, you should ALWAYS use wires. The wires are the variable. If you are using a loop (While, For), then using shift registers are appropriate means for routing values so that they are used by other sections of the code, later. One thing you must respect with LabVIEW is the dataflow. That's where Locals often fail.
I am not copying the Local Variable from one VI to another.
I am not copying the Local Variable from one VI to another.
The Data Communication panel is one of the panels that shows up in the Functions pop up list when editing the Block Diagram. It is the panel that includes the Local Variable function.
I don't know if the invisible item that was inserted in my block diagram was hidden or not. All I know is that the Errors List said that it was a Local Variable and that it was not connected to anything. I couldn't select it to get more information. All I could do was delete it.
You did not address my questions about why the Copy and Paste does not work properly for my Local Variable. Maybe it's a sign from the Software Gods not to use them LOL!..
So if I understand correctly, you are trying to copy & paste the Local Variable from within the same VI. How large is your block diagram? Did you try right-click on the variable and select "Find > Local Variables"? If it's a block diagram larger than 1 single screen (which it shouldn't), then it is possible that the Local is hiding beyond the screen. You should find it as I described earlier.
See my comments in red above.

Deleting broken wires crashes Labview 2010

Hi
I am down to earth after
enjoying all the nice features of LV 2010.
I randomly encounter
hour-glass hang-up when I try to delete broken wires. This is really
unpredictable as far as I have watched. I t happens if click on a broken with
the mouse or when I select a couple of those. It does not happen, if I use
ctrl-b.
When you try to delete it,
the hour glass comes up and the window is no longer refreshed.
I use the task-manger to
kill LV after
that a wild hard disk action starts, whoever initiates that ??
After LV-restart I usually
can recover a lot, but this make RAEL work almost impossible.
I a running an English LV
2010f2 on a German WinXP professional.
And Please, please patch
this as soon as possible.
Gabi
7.1 -- 2013
CLA

Hi Gabi,
I'm glad to hear that you are enjoying LabVIEW 2010! Can i ask what is the specifiation of the computer you are using it on?
This is because it might be that your computer doesn't have enough memory for this program.
Also there is a patch for LabVIEW 2010, in this link.
Hope this helps!
John McLaughlin
Insides Sales Engineer Team Leader
National Instruments UK & Ireland

3D graphs cause LabVIEW 2010 to hang

Similar Messages

Maybe you are looking for