Fix overlapping controls in error cluster (LabVIEW 2013)

In LabVIEW 2013, the "Error In.ctl" and "Error Out.ctl" have overlapping controls. If you run the VI Analyzer, you get an error from this arrangement. That shouldn't happen in something that's built-in.

Has an answer been determined for this?
I am getting this error for a few objects, but the error is not consistent and there doesn't seem to be alot of information on it.
See the attached images.
The Standard "error out" cluster is reporting 2 overlapping errors,
Status indicator
code indicator.
My "BioSig Control" is reporting 3 overlapping errors,
Bump/Offset F3
Yoke Connection Control
Programmer Connection
My question, are these really errors? or is this a defect in the analyzer and these indicators pose no threat to VI performance?
-Regards
eximo
UofL Bioengineering M.S.
Neuronetrix
"I had rather be right than be president" -Henry Clay
Attachments:
Overlapping control error labview.PNG ‏56 KB
Overlapping control error labview error output.PNG ‏5 KB

Similar Messages

Internal error or labview crash in 7.1ver thread.cpp(2842) whats reasons and how to fix it

Hi
Everybody ,
I am working with pci-6723 and labview 7.1 yesterday when iwas testing , the programme was running , suddenly the power has gone , since i have not connected my system to UPS system got shutdown , and when i booted pc its higlighted this error , now to what extent this problem affects to my software, and how to fix it.
"Internal error or labview crash in 7.1ver thread.cpp(2842) whats reasons and how to fix it"
Thanks in advance
Rajesh

Hello Rajesh,
Do you get this error frequently or you got it only once after the power shutdown? Are you making a call to a DLL in multithreaded environment? Try mass compiling the VI by going to Tools->Advanced->Mass Compile. Also please follow the suggestions provided in this knowledge base entry regarding thread.cpp and see if that will fix the problem:
http://digital.ni.com/public.nsf/websearch/01B186B5CEB1D07786256747000F4319?OpenDocument
If you continue to have this error, is there any way you can send me a pared-down example demonstrating what your program does, so I can at least investigate to see if I can narrow down the cause of the thread.cpp failure?
Thanks and good luck!
Shakhina P.
National Instruments

Labview 2013 (32 bit vs 64 bit)

Hi,
I have subVI to read the current from the Keithley 2400.
1. When I run it under Labview 2013 (64 bit) is no error
2. When I run it under Labveiw 2013 (32 bit) is ERROR
Error Code ID = -201 - Invalid while in local
Error Code ID = -420 - Queary Terminated
How can I fix this subVI to run under Labview 2013 (32 bit) ?
Thanks
Khanh

Hi,
Error at GPIB Read:
Output of the GPIB Write is OK but output of the GPIB Read is error. But the same subVI, if I run by Labview 2013 (64 bit) no error, unfortunatly the rest of the program (other instruments communication) are running with Labview 2013 (32 bit). That's why I would like to fix this to run under Labview 2013 (32 bit).
Please help. Thanks

LabVIEW new "Silver" error cluster and TestStand

I have some new VI's that use the new "Silver" style error controls and indicators. I started calling the VI's from TestStand and noticed that the new VI's were not auto populating the TestStand error to the VI's error out. Not sure how this mechanism works but it doesn't work with the default "Silver" controls. I think it is name based case sensitive and I just have to rename the "Error Out" cluster to be lower case "error out".

Paul -
Can you confirm that the problem you're describing is that because the name of the Silver error cluster is "Error Out", when you configure a LabVIEW step to call a VI that has the Silver error cluster wired to the connect pane, TestStand does not automatically assign Step.Result.Error to that parameter? If so, we have reproduced this behavior and yes, you are correct that it is due to case sensitivity. We have taken note of this in order to fix the problem in a future version of TestStand.
I also just wanted to confirm that the problem is not that the error information is not correctly passed from LabVIEW to TestStand, when you assign Step.Result.Error to a Silver error cluster parameter.
Please let me know.
Manooch H.
National Instruments

Labview 2013 error 1304

Hi
I have the latest version of Labview 2012 on my computer. It has been running well now for over 6 months. I now wish to update that with Labview 2013
First question do you have to remove Labview 2012 and two modules first before you install Labview 2013?
Problem 1. Within a few minutes into the installation process l obtain error 1304. When reviewing the file location reported in the error popup, the file states its a Labview 2013 template. I do not how that occurred but l have installed the last critical updates for Labview 2013 including the NI 488 driver updates for Labview 2012
Problem 2. If you ignore error a second error box pops up with no code.
A month ago l contacted our local NI support but they could not help. I have been away for a month and now l was hoping to have the bug fixed. But it still occurs. I could not find anyone who has had this error in the search for errors. The closest was error 1303
So at the moment l cannot install Labview 2013.
Has anyone had this problem. The word file illustrates the pop up messages.
Regards
Wetland
Attachments:
Labview 2013 installation error.docx ‏60 KB

Hi
Thank you for your response. I am downloading Labview 2013 onto my own home computer using the supplied DVD. I have full administrative privileges.
When l get Labview working at home l then download it at work. I cannot afford to have Labview not operating at work.
Last night l received a critical update for Labview 2013 patch f2. The update program seems to think l now have Labview 2013 installed. If l get no solutions to the problem l will install the patch just to see if that will fix the problem.
At the moment it seems that no one else is having the same problem since you are the first to respond. Thank you for your information
Regards
Wetland

LabVIEW 2013: An error occured trying to load the assembly

Hey all,
I'm trying to load a .NET 4.5 dll into LabVIEW 2013.
When I place any of the .NET VIs and try to select the one I'm after it says "An error occured trying to load the assembly" and won't let me load it.
I also tried importing the dll, but that gave errors too.
It's defintely a .NET 4.5 dll as the .NET reflector gives me
[assembly: ComVisible(false)] [assembly: TargetFramework(".NETFramework,Version=v4.5", FrameworkDisplayName=".NET Framework 4.5")] [assembly: SecurityRules(SecurityRuleSet.Level1)] [assembly: SecurityPermission(SecurityAction.RequestMinimum, SkipVerification=true)]
To try and get around the import issue, I added the following to my LabVIEW.exe.config file
<?xml version ="1.0"?>
<configuration>
<runtime>
<loadFromRemoteSources enabled="true" />
</runtime>
</configuration>
but it made no difference.
Any suggestions? All the things I've read so far are for 2010.
Solved!
Go to Solution.

Hornless.Rhino wrote:
Wart wrote:
I had the same issue a while back. Unfortunately mine magically resolved itself, but I made a post with what I'd been reading and got a reply with another suggested link. It sounds like you've gone down the same road, but I figure every little bit helps:
http://forums.ni.com/t5/LabVIEW/Error-Loading-NET-Assembly-in-2013/m-p/2521098
Thanks.
Hopefully mine will resolve itself too. LV2013 is meant to support the newer stuff without me having to mess about.
We shall see...
So far no dice.
It's really bizarre. It works with sample c# code in visual studio (see link below), but for some reason LabVIEW doesn't like the dll (tried both LV 2012 and 2013).
Sample code (not mine) is available at http://elbruno.com/2013/12/01/kinectone-hello-world-with-kinectsdk-v2-body-count/

Problems with Labivew 2013 / 14 install - Ni Variable Engine error and Labview does not close, processes do not stop when I run Vis.

Hi All,
I am hoping at all my problems are relateded to a problem I am experancing, when I look into my windows 7 (64bit) event viewer near every time I boot up I get an error regarding the NI Variable Engine which reads.
The description for Event ID 0 from source NI Variable Engine cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
C:\Program Files (x86)\National Instruments\Shared\Tagger\ni_tagger_plugin_mxs.dll: Failure to load plugin: Unexpected Error: Unable to get the Interface from the plug-in.
and a second which is the same apart fomr the last line
Unable to load the MXS configuration plugIn: Failed to get MAX Configuration interface for Tagger: 0x80040318
I have tried uninstalling all labview things and I have tried repairing all labivew programs. Along with this I got this error when I installed Labview 2013 so I thougth why not try 2014 and I still get the same problems. I also shoudl point out I use bot 32 bit and 64 bit versions of labivew. I have installed labview on many machines before but never encountered this problem. That being said this was a new clean windows install.
Along with thiese errors labview heardly ever shuts down properly when I close the program it just freezes and needs forshed shut down.
Apart form this I noticed that when I run any of my Vis which I have never had problems with in the past and I stop the program somtiems processes keep using CPU such as "lktsrv.exe"
I really need to get this sorted out because its morstly the crushing and processes not stopping which is rather annoying.
I shoudl also say that these problems are both in the 32bit and 64 bit versions of labview not difference. and no difference if its 2013 or 2014
Cheers

Hi GajanS,
Thanks for your reply sorry I havetn noticed anybody had replied as I stopped hoping for any responce before then.
I have attached a screenshot of the four processes that seems to be giving me a problem.
I have actually managed to find the program causing labivew to crash was in fact my antivirus software which I have now removed and have no more problems with labview crashing on shutdown.
After removing it I tried the repair feature again for all my labview programs but sadly the one persistant problem remaining is still the four processes using around 13% processor each. I have found out this happens sometime after booting up regardless of if I run labivew or not. So it does not directly seem related to the running of any labview applications but rather a bug in the labview software.
the processes are:
lktsrv.exe
tagsrv.exe
nidmsrv.exe
lkads.exe
as shown in the task manager.
I would relaly help if I can get this sorted out.
Cheers
Attachments:
Screenshot 2015-03-24 21.50.00.png ‏12 KB

How to remove error 59 which occurred while using Send Email Using Smtp Client .VI in Labview 2013.

Hi,I am trying to run Send Email Using Smtp Client .VI in Labview 2013 examples ,but it gives error 59.Please can anyone suggest how to remove the error.The printscreen is attached below.
Solved!
Go to Solution.
Attachments:
error.docx ‏310 KB

Thanks for the help,but i have set the parameters right but still it does not work for me.Please suggest me reasons and how to correct them.
Attachments:
error.docx ‏270 KB

Pass error cluster from labview dll to teststand

Hello,
I just want to pass an error cluster from a dll compiled in LV7.1 to TestStand 3.1. I never receive the contents of the LV error cluster in TS. I compiled my function with standard calling convention option, this should work. In my VI I generate only an error and pass to error output.
LV Settings:
TS settings:
regards
MB

MB,
please follow the info in this KB:
http://digital.ni.com/public.nsf/allkb/22BF02003B4588808625717F003ECD67?OpenDocument
Please note that using "By Value" will never return any values to TestStand!
You cannot use the default error-container in TestStand to receive data from the LV error cluster if you compile the VI into a LV DLL.
So either you choose to follow the KB or you split up the error cluster in your LV VIs to return error.occurred (boolean), error.code (numeric i32) and error.msg (LV String) .
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Running Datasocket in labview 2013 open labview runtime engine 7.0

Hello All,
I am trying to communicate with a COGNEX camera using Labview 2013. I am using Datasocket to read tags from cognex OPC server.
but when I open labview and run the code for the first time. An installer will automatically pop up trying to install labview runtime engine 7.0.
When i cancel the installation datasocket throws an error. Again if i run second time, datasocket works fine and communicate with cognex camera using OPC.
This problem comes everytime I open labview and run the datasocket. I cancel the installer. second time onwards when i run the code everything works fine.
This is actually annoying and i doubt how things will work when i make an executable.
Need help.
Is this due to datasocket version installed... how to resolve this.

Hi phil,
That is interesting that you were unable to find the offending key that the installation is having trouble with. Do you have Administrator privileges on your computer? You may even want to try to log in as the actual Administrator itself to make sure that you have access to all of the proper registry keys. Also, I was going to say that I do think you're right with Windows XP not having the Scanreg/fix function, but there are several free programs that you can download as registry checkers. You may want to try one of those to see if you can find the key and give it the proper permission.
As far as the other part of your question, the Run-Time Engines are very important for LabVIEW to be able to run, but the 7.1.1 Run-Time Engine should not be affecting a LabVIEW 8.2 installation as it will use the 8.2 Run-Time Engine. One thing that you can do is go into your Control Panel under Add or Remove Programs>>National Instruments Software and you can try and repair/modify your Run-Time Engine there. If you already have the 7.1.1 Run-Time Engine on your computer, this is where it will show up so you can make any changes you want. Also, if you go to www.ni.com and click on "Drivers and Updates" on the right, you will be able to find the Run-Time Engine there that you will need, but I would definitely try using a downloadable registry checker first before attempting to change any of the software that is currently on your computer. As stated in the Knowledgebase article, this is actually an error from Windows saying that the registry key does not have the proper permission settings, so I am reluctant to say that downloading the new Run-Time Engine from our website will help much. Please try some of these suggestions out and let me know how they work out for you. Thanks!
Regards
Noah R
Applications Engineering
National Instruments

LabVIEW 2013 SP1 Compile Worker Fails

Hello,
after receiving the new DVDs with LabVIEW 2013 SP1 and successfull installation, I wanted to compile my FPGA.vi.
The Compile Worker does not start an I get the attached error Message. The additional Download of Xilinx Compilation tools 14.4 from the NI Website does not help.
When I choose the FPGA Compilation Tools via the Start menu, the Compile Worker does not start. When I try to start the FPGACompileServerConfiguration an Error occurs (see picture).
At the Moment I hav not Idea what to do. Perhaps someone can help.
What does I have to do to convert my system back to the Version 2013?
Attachments:
FehlermeldungCompileWorker.jpg ‏41 KB
ErrorwhenstartingFPGACompileServerConfiguration.jpg ‏15 KB

dfschunk,
Thanks for your post. We are aware of an issue with the compile tools installed from the 2014 developer suite (2013 sp1) where the compile worker is installed with missing dependencies. We are taking immediate action to push out a fix for this and you will receive a notification through NI update service when the fix is available.
In the meantime, our recommendation is to downgrade to the 2013 installation of the Xilinx tools. No fixes were made between 2013 and 2013 sp1 in the compile worker or in the Xilinx tools so no worries there.
Go to Control Panel >> Programs and Features and select National Instruments Software.
This will launch a window where you have the option to select various NI software products and modify/repair/remove them.
Select NI LabVIEW FPGA Xilinx 14.4 Tools and select Remove.
After the software has been un-installed, go to the NI LabVIEW 2013 FPGA Module Xilinx Tools 14.4 donwloads page and install this version of the tools (released with 2013) or you may install the tools from your original LabVIEW 2013 developer suite disks.
Please post back or call support if you have any problems with this process, we want to make sure you are up and running until we push out a fix.
Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

Error cluster constant appears different in two locations on a block diagram

I am a newbie to LabVIEW. I have taken Core 1 & 2 and Machine Vision and I have not com across this before.
The image on the right is obviously an Error cluster constant used in the block diagram to create an Error cluster and wire it to an error out terminal. As far as I can tell the image on the left is about the same thing, but why does it look different? The different appearance causes raises a concern that there is a difference in behavior that I do not understand. LabVIEW help suggets that both are Error constants. When I create a new error constant, it always ends up appearing like the right image above. I have not been able to create someting looking like the image on the left.
Could someone please confirm what the image on the left is on a blck diagram?
Thanks,
Bill
Solved!
Go to Solution.

The image on the left is an error cluster control. It has a front panel presence and can be set either via the front panel or through a property node or local variable. The image on the right is an error cluster constant. It is a static value.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Feedback nodes in Error cluster

Some time back I
had posted a VI called Simple StateMachine template. Based on the
comments from fellow members I have redone it and am attaching it
herewith. ( LV7.1 + Win_XP Professional )
If you just open it and check the block diagram, you will notice that
LV has introduced a feedback node in the error cluster looping between
DAQMx function Write Digital Output and Read Analog input. I am not
sure why LV does this even though the two functions have no common
reference or relevance between them.
You can also try this : Just remove the data lines to the two Digital
Out functions, and also the error cluster with Feedback node . Rewire
the Error cluster but this time without the feedback node. And now if
you try to connect the Digital Out data lines, you will find that the
Data lines are drawn with feed back nodes !!
I am sure LV is trying to tell me something - only that I don't understand what it is. Can some one elaborate on this ?
Thanks
Raghunathan
Message Edited by Raghunathan on 07-04-2005 08:29 PM
Raghunathan
LV2012 to Automate Hydraulic Test rigs.
Attachments:
PRP_Main.vi ‏288 KB

You have an impossible loop in your code (Run it with execution highlighting to verify):
Dig8-15 relies on data from the case structure.
analog input 0-7 provides data into the big case structure
This means that Dig8-15 cannot execute until the case has executed, but the case must wait for data from analog out. LabVIEW is smart enough to insert a feeback node such that AI0-7 gets the error from the previous interation. This is NOT a desirable situration.
Without the feedback node, yuor code is broken. AI0-7 cannnot run because it must wait for DO8-15 to execute. DO8-15 cannot execute because it must wait for AI0-7.
You should:
Uncheck the diagram option "Auto insert feedback nodes in cycles" to make sure to get broken wires so it is easier to find the problem.
FIx your dataflow. Please make sure your wires flow left-to-right, it make errors like this less likely. You need to wire the error clusters in the order the subVIS execute.
I hope this is clear enough, but please ask is you continue to have problems. Good luck!
Message Edited by altenbach on 07-04-2005 07:18 PM
LabVIEW Champion . Do more with less code and in less time .

Event 7024, Service Control Manager Error %%16842771

Am running Windows Server 2008 R2 OS. I received a Service Control Manager error, event ID 7024 with an error code of
%%16842771 when trying to stop the PlanetPress Suite Messenger 7 service. Does anyone know what this error code of
%%16842771 means and/or how to fix it? Is there somewhere that I can look up these codes? Here are the details:
System
Provider
[ Name]
Service Control Manager
[ Guid]
{555908d1-a6d7-4695-8e1e-26931d2012f4}
[ EventSourceName]
Service Control Manager
EventID
7024
[ Qualifiers]
49152
Version
0
Level
2
Task
0
Opcode
0
Keywords
0x8080000000000000
TimeCreated
[ SystemTime]
2013-12-03T16:40:51.395984800Z
EventRecordID
33920
Correlation
Execution
[ ProcessID]
512
[ ThreadID]
11744
Channel
System
Computer
AXE1PPS02P.axe.anixter.com
Security
EventData
param1
PlanetPress Suite Messenger 7
param2
%%16842771
Thanks,
Laurie

The error code may be linked to application (PlanetPress Suite Messenger 7).
So seek help from application vendor once.
Regards, Ravikumar P

Slow LabView 2013

Hi
I have Labview 2013 Professional Dev Sys SP1 ver 13.0.1f2 (32-Bit) and it is slow when I develop any aplication.
For example, if I have a tab control and I change to another tab, it takes about 2 seconds to change tab after I click it.
If i wire a new line, it takes 2 seconds to appear that line in block diagram, and so on.
I have a new computer Dell Optiplex 7010, i7 Processor 3.40Ghz, 64-Bit, 4Gb RAM, WIndows 7 enterprice SP1
If i run Windows task manager it shows 17% CPU usage and 2.14 GB Memory.
If I run for example, excel 2013 it does not seems slow.
Do you have any suggestions ?
Regards
Solved!
Go to Solution.

EDGAR_PLATRONICS wrote:
Hi Yamaeda:
I am not sure about mass compile. You mean rewrite code ? Or create exe file and test?
A this moment I have checked with only one Vi but it is very large. Many sub VIs and code.
Actually it worked correctly in labview 8.5 but i converted to LV 2013.
I will research about transparent borders overlapping.
Hi Altenbach:
17% is overall. 3 cores are high % than others.
The problem is at edit mode and also when I run program.
Yes I have many front panel indicators, but I do not think they have tons of data but I will double check.
When I open my VI in labview it shows 118 MB memory when running and 124MB at edit mode
By the way, last week when by mistake I moved a part of code to some centimeters below, block diagram was frozen and was been updated to new position but line by line until complete full screen. I took about 5 minutes to work normally.
I am using 2 monitors in my PC. One to display LV panel and one for LV code.
I meant Tools -> Advanced -> Mass compile and recompile your upgraded code. In the same manner a ctrl+run array will force recompile your program. It can help. Else you're down to e.g. using VI analyzer tool to find the culprit, it might be some VI that's corrupted and needs to be moved to a new VI.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

Fix overlapping controls in error cluster (LabVIEW 2013)

Similar Messages

Maybe you are looking for