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

Similar Messages

Error Cluster Source and Explanation differ

I have a routine that unbundles the error cluster and is supposed to append the 'source' string to some status information that had occurred before that point. I ran some tests and found that the "Source" string differs (provides less information) than what is displayed in the Explanation field of the ErrorOut Cluster. How do I access the more verbose 'Explanation'?

Hi Mr Bean!
The errors are staded in several .txt files in the National Instrument library on your harddrive, search for *errors.txt and you will find a lot of them.
You can even state your own errors if you Select Tools»Advanced»Edit Error Codes in LV.
I created a simple VI there i use the Error Code Database.vi from the Error.llb to get the description for a specific error code.
Regards
/Thomas
Attachments:
Error_Code.vi ‏22 KB

Vi works in LabVIEW, but not when executed by TestStand.

Hi everybody. I'm using LabVIEW 8 with the Sound and Vibration
Toolkit, and TestStand2. I am planning on using TestStand to
execute a series of performance tests on an audio processing
board. When run independently, the vi (which I have attached
here) runs correctly, and returns a value for the parameter being
tested. In this case it is SNR.
However, when executed by TestStand, the vi seems to run correctly, but
returns a value of "NaN". This causes TestStand to fail the test.
Does anybody know what is going on here? I've checked FAQs and
help files, etc... Why would the vi work on its own but not in
TestStand?
Thanks.
Brett Gildersleeve
Attachments:
SingleChannelSNR.vi ‏173 KB
Test Sequence.seq ‏15 KB

Hi Ray, Thanks for the reply.
Basically, when I run the VI on its own, I see the SNR value appearing
both in the SNR indicator and in the Test Data Out cluster under
Numeric Measurement. The rest of the indicators are empty
(string, report text, status, code, source). My waveform graph
shows an FFT of the signal.
However, when running the exact same VI through TestStand, I get NaN as
the output. The FFT of the signal is NOT displayed in the
waveform graph... strange. No errors are received.
In order to make it easier to debug, I replaced all of the analysis functions
with functions included in LabVIEW 8. Now everybody should be
able to run it. I do a simple THD test this time around. With the VI running
on its own, I get a value of 1.8 as the THD and the Numeric Measurement of Test Data
Out. However, whenever running the test with TestStand, I get a
value of NaN.
Same problem.
Any suggestions?
By the way, what exactly do you mean by "wiring
up the Error cluster and feed in to the Error Out."? I'd
like to try it out, but I'm not sure exactly what you mean. I
already have the Error out cluster wired up, I think.
Message Edited by TheSleeve on 05-22-2006 12:12 PM
Attachments:
SingleChannelTHD.vi ‏159 KB
Test Sequence2.seq ‏15 KB

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

Adding existing SQL Server 2012 to a New SQL 2012 Cluster

We currently have a SQL 20012 Server setup and running on our domain. We would like to switch this to a clustered environment. Is it possible to setup the new SQL 2012 Cluster and add the existing SQL 2012 server as a node in the cluster
without losing any functionality. All servers will be built with same drive letter.

We currently have a SQL 20012 Server setup and running on our domain. We would like to switch this to a clustered environment. Is it possible to setup the new SQL 2012 Cluster and add the existing SQL 2012 server as a node in the
cluster without losing any functionality. All servers will be built with same drive letter.
No its not possible to convert standalone installation to cluster.Moreover first you need to configure Windows cluster then backup all SQL server databases logins jobs packages and install fresh instance of SQL Server in cluster aware mode
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

NI 5660 Driver DLL Errors when using Teststand 2010 and LabVIEW Run-Time Engine 2010

This problem seems similar to the post "Resource not found error in executable on development machine." but I didn't want to repost under that thread because I only happened upon it by chance and none of my searches brought me there... so I made a more descriptive Subject.
I am working on a system that uses a PXI Chassis with a NI 5600 Downconverter and a NI 5620 high speed digitizer, among other PXI Cards.
I inherited working code written in LabVIEW 2010, running with the LabVIEW Run-Time Engine 2010. The code was using a custom executive and my task was to rewrite the test using TestStand 2010. I reused the majority of the old code. The old code used NI-5660 to control the 5600 and 5620. When I run my sequence using the LV Development System and TestStand, it runs without any issues. When I change the adapter over to LabVIEW Run-Time Engine 2010, all of my NI5660 VIs become broken due to DLL issues. It warns that the nipxi5600u.dll was not initialized correctly. Many of the errors are associated with the NI Tuner and NI Scope. After this LabVIEW will crash randomly, and the seqeunce will not work in TestStand even when back with the LV Development Adapter. The only way to recover after this is to restart the computer - TestStand automatically reverts back to the development system, the VIs are no longer broken and the sequence works again.
I have all of my VIs associated with a project. After reading a little bit about DLLs and TestStand, I found all of the DLLs in the dependencies section of my project and added them to my TestStand workspace. I also used Dependency Walker to track down the problems with the nipxi5600u.dll, the 2 DLL files that it said were not found already existed in the same folder as the original DLL (C:\Windows\System32). I have also performed a Mass Compile to make sure everything was running in LV 2010. If I skip the steps involving the 5660, my entire sequence runs fine.
The previous code was running with the LabVIEW Run-Time Engine without any issues. Is there just a step I am missing? Has anyone seen anything like this before? I can send screenshots of errors to provide more detail if necessary.

I have tried some more things and still can't get it to work. I have added the VIs mentioned in the Notes On Creating Modulation Executables KB both to the TestStand workspace and the LabVIEW project holding all of my VIs. This did not change the results.
When I try to run my sequence, The first error I get is shown in Error 1445.bmp. This happens when I try to use the NI 5660 initialize.vi. If I click ignore, the next error I see is shown in Error -20551.bmp. When I try to open the VI to look at it, I get the 2 DLL errors shown in Error loading nipxi5600u.bmp and Error loading nidaq32.bmp. When I close TestStand, I get the error LabVIEW Fatal Error.bmp.
Attachments:
Error1445.JPG ‏164 KB
Error -20551.JPG ‏174 KB
Error loading nipxi5600u.JPG ‏9 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.

I am trying to have some LabVIEW code called in a New thread exit when the testStand sequence terminates

I have a Sequence that launches a sequence in a New Thread that happens to launch some LabVIEW code. The problem is when the LabVIEW code finishes, it will not close even when the TestStand sequence terminates. Is there a way to tell this LabVIEW code to Exit, I've tried the Quit LabVIEW function, but that causes a C++ RunTime Error. The LabVIEW code does end though, and it is set in the VI properties to:
Checked - Show Front Panel When Called
Checked - Close Afterwardds if originally closed
The sequence call that the LabVIEW code is launched from has the following options:
- New Thread
Unchecked - Automatically wait for the thread to complete at the end of the current sequence
Unchecked - Initially Suspended
Unchecked - Use single threaded apartment
Any clues on this would be appreciated.

Hi ADL,
Everything should close correctly if you check the checkbox "Automatically wait for the thread to complete at the end of the current sequence" in the thread settings.
With it unchecked, I am seeing the behavior you are.
Gavin Fox
Systems Software
National Instruments

Pass an error cluster in and out of a C/C++ dll?

Hi all,
I'd like to know if it is possible to pass a LabVIEW error cluster to a C/C++ function from a dll. This would greatly help error handling in the different VIs.
I am able to access and modify the first two members of the error cluster; the error status and the error code, which are, respectively, boolean and integer. But I cannot modify the string. LabVIEW crashes completely doing so.
I first define a structure in C++ like this:
const int N = 512;
#pragma pack(push,1)
typedef struct lvcluster {
bool status;
int code;
char source[N];
} lvcluster;
#pragma pack(pop)
Then, I define a function that will access the members status, code and source:
int TestCluster(lvcluster *err)
err->code = 1;
err->status = false;
sprintf(err->source, 'Test');
I then use LabVIEW's "Call Library Function" to call this dll's function. I have set the parameter "err" to "Adapt to Type" and "Handles by Value". Trying to write characters to the source array crashes LabVIEW.
Is this possible at all? How should it be done?
Thanks!

Thanks all for the comments.
I've been looking at extcode.h where I saw the defeninition of a LStrHandle. It seems to be a pointer to pointer to "character array":
typedef struct {
int cnt; /* number of bytes that follow */
unsigned char str[1]; /* cnt bytes */
} LStr, *LStrPtr, **LStrHandle;
The "character array" is different than a C character array, see http://www.ni.com/white-paper/4877/en/#toc4
The first 4 bytes contain a signed 32 bit integer representing the number of characters. There is no NULL-termination character.
So the error structure should be something like this (modulo the size of boolean, thanks rolfk):
const int N = 512;
#pragma pack(push,1)
typedef struct lvcluster {
bool status;
int32 code;
LStrHandle source;
} lvcluster;
#pragma pack(pop)
From there, I was able to access a LabVIEW string from C. But I am unable to modify any of it. I might be able to change the characters from an alreay allocated string, but resizing or even creating a new string crashes LabVIEW. As reported by others, manipulating these strings would require linking against labview's library to access the string manipulation functions, but this is not possible as the library must be independant of LabVIEW.
The only last possible way I can think of is to allocate a new cluster inside the DLL. Then I might be able to change the string in it, and hopefully LabVIEW would pick it up. I don't know how LabVIEW manages its memory; would it garbage collect the input cluster that is not used anymore?
Thanks for all the feedback.

How to Add New Parameter in Cluster with LabVIEW Executable Program?

   In this VI，it can write the parameter in Cluster to the database (Access 2003).it run well.
   But When I add another parameter in Cluster,such as EE,I have to modify this Cluster. And at the same time,I have to modiy the database (I should add a column of EE).if this vi build to exe, how can I achieve it?Can LabVIEW have any way to increase new parameter EE in Cluster and in Database in executable program?
   Would you give me some advice?Thank you
Attachments:
Add ParaMeter In Cluster 20130206.zip ‏105 KB
Cluster.JPG ‏9 KB

It's rather unclear what you try to do here. In your first post you talk IMHO about the high level Datatbase Toolkit functions that take a cluster and translate it automagically into the appropriate SQL Query/Update.
Your second question seems to be about the user interface of your application.
Proper application design would mean to separate the user interface aspect from the actual database query in some ways. I definitely wouldn't use the same cluster for both. Also if you simply hide a control on the frontpanel (possible also in an executable) it still is present logically and if you end up using the high level database toolkit functions with that cluster it will result into a query or update of the database with all the data in the cluster, also the hidden ones.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

What are the current versions of Labview and Teststand

Hello,
i am currently downlading the current versions of teststand and labview for evaluation.
In the Teststand-link i saw that it is called "Teststand 2012".
1. But there was no version-information in the Labview-Download. Is this also version 2012?
2. Are both things 32-bit-software?
3. After i installed the evaluation-downloads - can they be activated with a key or do i have to install it again when the CDs arrive in my office?
Thanks for help
Solved!
Go to Solution.

OnlyOne wrote:
Thx for the links.
I am using Windows-7-64bit - should i prefer then also Labview 64? (The NI-download-Links only provides 32bit for download)
Will there be any problems converting my existing Labview 8.5-Vis to the new Labview2012?
Thank you
You can have both the 32-bit and 64-bit installed. Just remember your target when you build an exe. 64-bit compiled programs can only run on 64-bit machines.
You should have no problem upgrading your code from 8.5.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

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

System Default Cluster and New Cluster

Hi gurus
I am seeing a stange thing with our system. I created a new Cluster and associated it with the server host name.
It is now giving me a different login page than usual and doesnot allow "enterprise" ID to login
When I change the context back to System Default Cluster, I get regular login page and I am able to login as enterprise ID.
I am seeing that System Default Cluster has "Cluster Members" = full hostname.
Is this normal?
Point is we are able to create a new cluster now to associate it with our new context.
Thanks
JS

We loaded master data, and also created Directory configuration, and then associated the new cluster first to Directory config and then to the context. It was not giving an error anymore.
Hope this helps. It was all trial and error as everyone here are new to this product.
Thanks
JS

Some error in cluster alertlog but the cluster and database is normal used.

hi.everybody
i used RAC+ASM,RAC have two nodes and ASM have 3 group(+DATA,+CRS,+FRA),database is 11gR2,ASM used ASMlib,not raw.
When i start cluster or auto start after reboot the OS,in the cluster alertlog have some error as follow:
ERROR: failed to establish dependency between database rac and diskgroup resource ora.DATA.dg
[ohasd(7964)]CRS-2302:Cannot get GPnP profile. Error CLSGPNP_NO_DAEMON (GPNPD daemon is not running).
I do not know what cause these error but the cluster and database can start normal and use normal.
I do not know whether these errors will affect the service.
thanks everybody！

anyon has the same question?

HT4972 i cant update my iphone 3gs to a more newer ios? it says here error! and the phone flashes some connect to itunes.. an if i connct nothing happens.. help me.. the ipgone wont open . and work pls help me thank you!

i cant update my iphone 3gs to a more newer ios? it says here error! and the phone flashes some connect to itunes.. an if i connct nothing happens.. help me.. the ipgone wont open . and work pls help me thank you!

Hello AlexCornejo,
Thanks for using Apple Support Communities.
The screen you're seeing on your iPhone indicates it is in recovery mode. Now since the device is not appearing in iTunes on your PC, first follow the steps in this article:
iOS: Device not recognized in iTunes for Windows
http://support.apple.com/kb/TS1538
After following those steps, you should be able to restore your iPhone.
Take care,
Alex H.

LabVIEW new "Silver" error cluster and TestStand

Similar Messages

Maybe you are looking for