How to force TestStand to ignore LabVIEW errors

Hi,
usually where there is an error in the LabVIEW code module TestStand stops and gives a pouup message .
Is there any way to force TestStand to ignore LabVIEW errors and contiouse testing?
Thanks

You can also work more globally - go to the Configure menu item and select Station Options.
At the bottom of the execution tab, there's a section for what to do on Run-time errors. -> Show dialog, Cleanup, Ignore or Abort.
Whilst not specific to steps configured to use the LabVIEW adapter (assuming you're mixing some programming languages) that at least get you continuing on to the next step without the dialog.
If you need to assess if it's specifically LabVIEW modules causing the error, then you need to use the Station, Process Model or Sequence File callback for On run-time error, and the step gets passed as a parameter. That would allow you to work out if the step was LabVIEW specifically and then make a decision as to what to do next.
Hope that helps.

Similar Messages

Firefox pops up an error message on certain pages, all other browsers work fine, how can I make firefox ignore the "error" [e2219] css init error: ReferenceError: g is not defined

Basically I want to replace the Ajax Control Toolkit Slider in favor of the Component One Studio for iPhone Slider for better mobile/desktop consistency (the ajax slider doesn't work well with iPhone). I created a simple page that works on every browser and platform (iPhone, Android, Mac, Windows) except Firefox, which fails on every platform. I have already tried disabling all plugins (safe mode) and clearing cache, I have also tried this with different versions of Firefox on different platforms. I posted this error on the Component One forum but since this only occurs with Firefox I believe this is a Firefox issue.
I searched for this error on the forums and Google but didn’t get any results:
''[e2219] css init error: ReferenceError: g is not defined''
The console has this message:
''[12:05:26.954] uncaught exception: [Exception... "prompt aborted by user" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: resource:///components/nsPrompter.js :: openTabPrompt :: line 462" data: no]''
You can see the error by visiting http://www.componentone.com/i/
Visit the same URL with IE, Chrome or Safari and there is no error. If I click [OK] the page loads normally enough for me. Is there some JavaScript or CSS line I can put in the page to make Firefox ignore the error? If so that would be great because even if there is a fix put into Firefox itself there will be those millions of users out there that will not upgrade.

A good place to ask advice about web development is at the MozillaZine "Web Development/Standards Evangelism" forum.
*http://forums.mozillazine.org/viewforum.php?f=25
The helpers at that forum are more knowledgeable about web development issues.<br>
You need to register at the MozillaZine forum site in order to post at that forum.

How to terminate TestStand Application after a LabView error.

We've just started launching TestStand from a command line, and when it (TS) stops sequence execution due to a LabView error, the command window doesn't know its status. So, I have a two part question:
1) Is there a way to COMPLETELY STOP the TestStand application when a LabView error is encountered? (I have been able to get the error popup to stop, but TestStand is still active and the command line is still sitting there thinking everything is fine).
2) Assuming that there is a solution to #1, is there also a way to get LV or TS to report the error to an external command prompt or batch file?
Thanks,
   - Paul Iovanna
Solved!
Go to Solution.

Hi Manooch,
We've managed to get the TestStand sequence to stop when we want it to (by using the /quit option in the command line), but now we can't seem to get Reports to generate.
Specifically what we are doing is including a particular test sequence in a fully automated Build/Test/Report system. After an automated build of our product completes, we have tools and command files that load all appropriate code into the various components of our system, and then we lauch a TestStand sequence that exercises much of the newly imaged system. Since we are running from the command line - and that command line is being monitored by other processes within our Build/Test/Report system, we need to have TestStand stop AND exit, or else the command line just hangs.
So, we really need two things to happen:
1) Get TestStand to stop execution AND exit - and we seem to have this working.
2) Report the results from the test sequence:
   - We have no problem doing this when the Sequnce Editor is launched directly, and the sequence is started from its GUI.
   - However, when we use the command line to launch the sequence via your "TestExec.exe" - there's no report! All of the Report Options settings are the same as for the Sequnce Editor GUI.
So, at a minimum, we need to get the usual report to be generated and saved when we launch from the command line - and the preferred option would be to have any error codes from TestStand (or LabView, since the test sequence uses only LV steps) reported directly to the stdout, in this case the command line.
Hopefully that explains our setup and requirements a little better - and thanks in advance for the assistance.
FYI - TestStand version 4.1.1 running on Windows XP.

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

How do I fix my VI when error -1074000000 and -213 "Init ignored" comes up and what does it mean?

When I run Test Main 002.vi in debugging mode, this error continues to pop up. I am finding and recording the voltages for a Keithley 2700 multimeter. I have Test Main 002.vi call on Read Volt.vi and this VI calls on Configure Volt Task.vi. I got most of the functions used by the latter two programs from the Keithley 27XX driver. Everything there seems to work fine. All the example codes given by the Keithley 27XX software run just fine and give good values. When I look at everything in debugging mode, there seems to be a value that appears for voltage but then the error pops up. No error is given anywhere else. Could anyone let me know where my error in the programs is and how to fix it? Thanks.
Attachments:
Test Main 002.vi ‏129 KB
Read Volt.vi ‏27 KB
Configure Volt Task.vi ‏28 KB

Yes, I did mean highlight execution. It was not able to work when it was run normally. I did fix the problem though. The problem is that the boolean attached to Initiate.vi (given as a function from the instrument drivers) that drove the "continuous initiation" was set to true and it needed to be set to false. After I did this, I was able to get to program to work just fine. I have been able to run it for several hours now without any hiccups.
Another option I found was to be able to unbundle the error cluster attached to the Read Volt.vi in my Test Main 002.vi under the acquire case and force the boolean to be false such that it would ignore the error. It was not the best way to do it but it was a work around.
Thanks.

How do I ignore 10920 error

I am using Labview with a MultiIO DAQCard-AI-16E-4. I am using both counters. I get a 10920 error... and my data aquisition stops. I want to ignore this error and continue aquiring data.
I can easily replicate this error by removing the input wire to the GATE and then connecting it again while running(simulate an intermittennt short).
How do I ignore this error and continue aquiring?
I can replicat

Use General Error Handler.vi (Functions palette --> Time & Dialog). It allows to cancel an error by setting exception action, exception code and exception source. Read the online help for more information.

How to send a path from labview to teststand.

Hi!
I have a DLL that I have developed in LabView and as a input parameter I have a path to a file
but if I in the LabViewCode uses String to recieve the path from TestStand and the path includes \T
these just disapperes.
ex:
I send "C:\test.vi" to LabView from Teststand
If I check the Path recieved in LabView i get "C: est.vi"
Instead if I in LabView uses Path to recieve data from TestStand I get an error in Teststand.
How should I do?
/Andreas

Labview strings use the backslash "\" as a special character. \t is a tab, \n is a newline, \r is carriage return, and so on. To send a real backslash use two of them, like \\. So your path string should be "C:\\test.vi".
- tbob
Inventor of the WORM Global

How to disable drive upon LabView error

I'm running a closed loop PD position controller in Labview 8.5 and NI PCI-6259 M series card and BNC-2120. I'm sending an analog voltage signal (+/- 10) to a Copley Xenus amplifier (current command) as well as a +5v signal to enable the amplifier. The controller uses position for feedback. When labview errors out, the daq card stays in its current state (and keeps sending the 5v enable signal). For safety reasons, how can I configure my system so that this signal stops being sent out, and the amp is disabled?
Maciek

The program crashed. I shut off the amp. The actuator shaft, which is positioned vertically, dropped to its lowest position due to gravity (it's a linear actuator). The daq card kept pumping out a high force command, due to the large position error created by the disturbance, as well as the 5v enable signal. Upon turning the amp back on, the PD controller saw a large difference between desired and actual position, and the actuator shaft shot up forcefully, creating a very dangerous situation. In the program, I have a case structure which won't enable the amp. unless the difference between desired and actual position is small enough. But the amp stays enabled when labview crashes.
m

How to read and write data from Excel to TestStand without using LabVIEW VIs

Hi,
How can I read in columns of data from Excel into a TestStand array and write columns of data to Excel from TestStand without using LabVIEW VIs?
I don't think the Property Loader custom step type in TestStand will work because the data I would like to read in from Excel is in a column that is thousands of rows long and the data has to be in the proper format to use the Property Loader to load in an array from Excel.
Thanks for your help.

That example does not use LabVIEW and it does about 40% of what you need to do by calling Excel through ActiveX. If you don't know how to use Excel through ActiveX then you'll need to brush up on that.
http://www.microsoft.com/en-us/download/details.aspx?id=16250
http://support.microsoft.com/kb/141759
http://support.microsoft.com/kb/302084
CTA, CLA, MTFBWY

How can I force TestStand to create multiple instance of an activex server instead of share the same reference?

Hi, All:
     I am trying to migrate a application coded by VC++ to TestStand+CVI. This application opens multiple serial com ports and send commands to test targets, and get responses from these targets. The VC++ application creates multiple thread, and every thread create an activeX server instance which is responsible for opening serial port,sending test commands ,and getting response. It works fine as every thread has itsown activeX instance, so data and commands can be handled in the right serial port successfully.
     Yet when I works on TestStand, I got problems. I choose parallel model as the process model. I create a activeX object reference with AxtiveX/COM Adapter, and store the reference in a sequence local varialbe. If there is only 1 testsocket, It is OK. But if there are multiple test sockets, and communication between the application and test targets will be directly to the last test target. I try to popup a message within a execution to indicate the value of the activeX object reference, and all of them are identical. But this is not the behavior I want.
    So, is it possible to force TestStand to create independent instances of an activeX server? How can I make it work?
Thanks

Thanks for your comment, Dan.
      Yet I do get problems as none of us know how to program an activeX server so that it can be forced to be a single-instance or multiple-instance.
As I mentioned earlier, there is existing application which is written by VC++ can create multiple instances of this activeX server, all I have to do is to create multiple threads, and initiate an instance of this server to contrl multiple test targets.
     My colleague said he creates the server with VC++ ATL, and cofigure it to be dual-interface and STA. And in the VC++ application side(client side), I use smart-pointer in threads to create an instance of the server:
IMySerialServer pIMySerialServer;
  HRESULT hr = pIMySerialServer.CreateInstance("UUTCmd.MySerialServer");
  if(FAILED(hr))
   AfxMessageBox("Fail to create instance.");
And then I got multple instances of the activeX server. Every thread can have itsown com port, can send/receive commands indepently. I have no idea how can I make it work on TestStand. Would you show me some reference documents or sample codes?
Thank you
Cipher

How to change Enumerator programmatically in LabVIEW called in Teststand

How to change Enumerator programmatically in LabVIEW called in Teststand ?
I know that Enumerator cannot be changed programmatically since the data type itself different from other controls like Ring and Combo box.
My application involves in Property loader which will load the list of names to Enumerator during Initialization. And the same shall be used by operator to select in further steps for testing. I tried with Ring and combo box but it doesn't works because its not giving dropdown option in TestStand Steps to select the name.
I need a drop down and also programmatically changing the value of the same variable. I had gone through all forum solutions regarding Enum, but I couldn't get any work around for this.
Please suggest me a solution or best work around to do this.
Thanks,
Vijay
L&T Limited
Certified LabVIEW Developer
India.

Can you provide an example of how a ring control/combo box does not work? This should be the way to do what you want unless I am misunderstanding exactly what you want to do. In theory you could have a dynamic enumerator type, but there are lots of hoops to jump through using VI server and scripting and it is not worth the effort. Aesthetically, you can make the ring control and enumerated data type look exactly the same. I would be using a ring control.
Please post an example of how it does not work.

How to ignore SSL errors

When setting up email via secure smtp and imap there is an error because of self signed cert and i am unable to complete the setup process. I know that
the ssl cert is invalid and ready to deal with it better than leave plain text connection. How to ignore ssl errors and continue with email setup?

Hello akamit,
If I understand your question correctly, I think there is no ready solution for this situation. You could have a look at https://bugzilla.mozilla.org/show_bug.cgi?id=874346 - the discussion there may help you to understand the problem in more detail.
Kind regards.

Teststand deployment with LabView VI gives error code 1035

Using Teststand 3.0 deployment tool. My test sequence uses LabView 7.0 VIs. When I build, error code 1035 is output after several minutes along with the message :-
Error Code:1035
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. Labview error:
Invoke Node in Teststand - Diost Chg and Save VIs-> TestSTand - Dist Build LLB Image ->TestStand - Build VI
Distribution.vi->TestSTand - Build VI Distribution AX Wrapper.vi-> TestStand - Build VI DIstribution AX Wrapper.vi.ProxyCaller
++++++++++++++++++++++++
I tried a LabVIEW mass compile of my VI directory and it reported no errors.
I have tried this website for an explaination of this error but there appears to be nothing. System is Windows N
T4 SP6.

Jon, you mentioned this problem got solved in TestStand 3.1. Right we are using TS 3.0 and have that problem caused by LabView's own locked VI's (not to mention LabView VIs with the "/" character in the filename, i had to save those under a different name) . Is there any documention about this problem being fixed in 3.1? This would help me explain the need for the upgrade to the powers that be.
Thanks,
Fernando Marquez
Project Engineer
CSI
Jon Bowers wrote:
There can be a problem in Teststand 3 when deploying with the "Lock vi Diagrams" option checked when your sequence contains vi's that already have locked diagrams. Un-checking this option or removing the vi's which have locked diagrams should allow you to build successfully. This has been fixed in Teststand 3.1.
Jon Bowers
Applications Engineer
NIUK

How to Ignore Insert Errors in LKM.

Hi,
I would Like to know how to Ignore insert errors in Oracle Data Integrator (Something like flat file mechanism, where the errors are located into .bad and .error files). If My Step 'insert new records' thrown an error regarding to Wrong Data, Constraint, etc. I would like to redirect the records with error to another location without affect the performance.
is this possible throws Interface configuration or something like that?
Thanks in advance.

Thanks for your reply. there is 'deprecation warnings' under Project Properties--> Compiler. These errors are not deprecation errors.
The below code doesn't help either.
<jsp-config>
<jsp-property-group>
<url-pattern>*.jsp</url-pattern>
<el-ignored>false</el-ignored>
</jsp-property-group>
</jsp-config>

How to ignore MP560 error code B200

I have got error code B200 on my MP560 last week. I tried every methods which I found on internet, such as unplug, reset, deep clean the printhead, etc. But it doesn't work. I think I have to give up to recover the print function. I plan to buy a new printer but I'd like to use this MP560 just as a scanner. Is there any way to ignore the error code so I can use it as a scanner?
Thanks a lot to anybody who can help me.

Hi griea,
To try and resolve the issue, please remove the power cord from the back of the printer and leave it out for at least 10 minutes, then plug it back in and turn it back on. If the error persists, the printer will require servicing to resolve the issue.
Please drop us a line by clicking on the Contact Us link to start the process!

How to force TestStand to ignore LabVIEW errors

Similar Messages

Maybe you are looking for