TestStand 2014

Similar Questions

• Disable the TestStand 2014 report batch

  Hello

  I'm trying to disable batch report generation in the model batch of TestStand 2014. I found this thread back in 2005, but it seems that things have changed a bit since then with the addition of the Plugins model in new versions of TestStand. I always want to the individual report for each shot to test but I would like to disable the additional orders summary report. Anyone know the best way to achieve this?

  I seem to have jumped with success the guests to collect the serial number of the lot.

  I think I got it.

  There are 3 steps.

  1 - one, that we discussed.

  2. read report any controller model plugin - end

  3 - determine the path of the Batch report file in Plugin - Start Batch model

  Hope this helps,

• TestStand 2014 freezes when I select a path from the project during an Action LabVIEW using LabVIEW TERM 2014

  In the company that I work, we have a solution that uses the two TestStand 2014 and 2014 LabVIEW.

  We work with the development version of the two, but we are deploying our automation using TestStand and Labview Runtime engine 2014.

  We tried to deploy a new station, but during the analysis of our project, the User Interface for Teststand (version Deploy) froze.

  I tried several things and decided to install a full version of TestStand 2014 and 2014 LabVIEW to try to debug the problem.

  What I've discovered is that when I create a new sequence in TestStand, add a VI Action and try to load the path to the project, the TestStand freezes if I use the adapter Runtime.

  If I go to the LabVIEW development system adapter in TestStand, it works. However, I need to use the Runtime since it's free while the LabVIEW Development is paid.

  We already use our solution in other places, and this is the first time, it never happened. The only post I found online that had something to do with this issue is this.

  If I remove the path of the project and call the VI himself, as "dvu", said in his second post, it works.

  However, it is something not good to do in our automation together, since we have several calls from LabVIEW.

  Any ideas on how to do this only works with 2014 DURATION and 2014 Runtime LabVIEW TestStand?

  Thank you!

  Thanks a lot Stop_Luke_and_Listen, but the guy where the deployment was made called the support NEITHER and they couldn't find the problem, so they formatted the PC.

  Now it works very well, so I won't be able to generate the report. It would have been a great idea.

  Thank you!

  SOLUTION: Format the PC and reinstall.

• API dll windows 10 teststand 2014 SP1

  Hello

  I'm looking for a solution to my problem a few hours ago, but I found nothing. I'm working on Teststand 2014 SP1 32 bit with a windows 10.

  I did a sequence on the same version of teststand on a windows 7, but I now have a windows 10. I opened my sequence (which worked fine on W7) on W10, but when I am executing it I got the following message.

  http://PUU.sh/pizsw/deabdd594d.PNG

  I tried to install the SDK W10 and some versions of Visual studio, but did not work. On my 64-bit version, I got another message that seems normal cause he says TS is unable to open my 32-bit dll.

  I think I forgot to install something but I don't know what, if soemone found a solution to this problem must be large to share =)

  Best regards

  Guillaume

  It would be wise for you to recompile DLL - 07_modbus.dll to work on Windows 10.  It looks like all of its dependencies are specific to W7.

  Kind regards

• No icons shown in the sequence editor (Teststand 2014 Windows SP1 + 10)

  Hello

  I have the problem in the followig:

  After installation of Teststand 2014 SP1 on a computer Windows 10 empty, no icons are shown for the steps in the sequence editor. In addition, the breakpoints do not appear by clicking on the left side of the stage. Icons, which uses Teststand are in C:\Program NIUninstaller Instruments\TestStand directory 2014\Components\Icons, nothing is missing.

  Everyone knows the same problem?

  See you soon,.

  Roman

  

  Hey guys, so I finally found the solution to my problem: change the Format of the region of English (Europe) to English (United States). Thanks to Scott for an idea!

  I'm really curious to know what kind of bugs are hiding there, where Windows 10 meeting OR software

• Call Testexe with TestStand 2014 command line

  We are modernizing our Testsuites to TestStand 2014.

  When I want to run a movie with Testexe from an external batch file using the entry Point 'Test DUT' I get the error (see attachment file)

  'Test DUT' entry point does not exist.

  Invalid or out of range value. Code error-17300

  The content of the external batch is:

  On the echo
  'C:\Projects\TestStand\UserInterfaces\Full-Featured\CVI\win32\TestExec.exe' /runEntryPoint 'Test DUT' "C:\Projects\FrameworkFkt\TestProg\B1_SequenceFiles\E4_FRAMEWORK_SHORT.seq".
  pause
  ECH off

  With TestStand 2013, that it worked well. Does anyone know a solution to this problem. And the 'Test DUT' Entry Point exists.

  In addition, I would like to unload all the sequences wenn, I close the Testexe. Is there an easy way to do this, without changing the Code-Source-Testexe?

  Thank you very much for the help.

  Regards, Paul

  When a UI is closed all the sequence files are already closed. It is a standard cleaning part when the process is stopped. What exactly is the problem you see? Is it just that you don't want to reopen the next time that the user interface is launched? If so, it's just a setting in the ApplicationMgr of the ApplicationMgr.ReloadSequenceFilesOnStart user interface object. You can set this property in any programming language designer allows you to create your user interface, or programmatically set before calling Start() on the ApplicationMgr.

  Hope this helps,

  -Doug

• TestStand 2014 Version selector "Program Error"

  I upgraded to TestStand 2014 from 2013. I suspect that I deleted TestStand 2013 by using the uninstall program NOR but had not chosen 2014 TestStand using the version selector.

  When I try and run the selector version as an administrator, I get an error "unable to determine the current Version of TestStand. The Version selector then begins with the "Version Active current = n/a" and launch sequence buttons are grayed out.

  The select Version section all seem OK with 32 and 64 bit paths showing correctly and the projection of "2014 (14.0)" in the Teststand installed drop-down. When I click on 'Get active', I get a dialog box error which is entitled 'Attention' and says "program error".

  Is there a way to fix this? I installed 2014-64 bit and then reinstalled the 2014-32 bit version but still the same.

  I am on Win 8.0 and Avast antivirus and firewall (which I checked and logs do not show that it is not blocking anything related to this).

  I could just try and install the 2013-32 bit version and see if I can make some versions then and uninstall 2013 thereafter. This sounds like a good idea?

  Thank you very much: David

  I did a deactivation of 1 hour of Avast and used the repair option. This made me the Teststand service installed and everything is working again now.

  Thanks much for the tips

• Need to frontend.dll for 64 bit TestStand 2014

  Hi all

  I get an error during indexing, I think I changed something in the directory then it asks x64\frontend.dll file that I could not find anywhere.

  I found frontend.dll for 32 bit, but not for 64 bit.

  I also tried to uninstall teststand 2014 and install it again. Same problem, I directed to

  Need Suggestions

  Thank you

  You might have a custom version of FrontEndCallbacks.seq in your public directory? If so, it is perhaps where it isn't finding the 64-bit version. You should be able to copy from the installation location to C:\Program NIUninstaller Instruments\TestStand 2014\Components\Callbacks\FrontEnd as far as your custom version is in your public directory. Or remove your custom so FrontEndCallbacks.seq you do not use it.

  Hope this helps,

  -Doug

• Failure TestStand 2014 operator Interface examples

  I tried to run a number of examples that illustrate the operator TestStand 2014 (32 bit) functionality of the interface, such as handling user interface Messages.  When I load and run the .NET solution interface operator beneath the example file I get the following error:

  System.Runtime.InteropServices.COMException was unhandled
  HResult =-2147221164
  Message = recovery of the class factory COM for component with CLSID {B2794EF6-C0B6-11D0-939C-0020AF68E893} failed due to the following error: 80040154 class not registered (Exception from HRESULT: 0 x 80040154 (REGDB_E_CLASSNOTREG)).
  Source = NationalInstruments.TestStand.Utility
  ErrorCode =-2147221164
  StackTrace:
  at NationalInstruments.TestStand.Utility.LaunchTestStandApplicationInNewDomain.LaunchHelper (point of entry MainEntryPointDelegate, MainEntryPointDelegateWithArgs entryPointWithArgs, String [] args)
  at NationalInstruments.TestStand.Utility.LaunchTestStandApplicationInNewDomain.Launch (point of entry MainEntryPointDelegateWithArgs, String [] args)
  at TestExec.MainForm.Main (String [] args) in c:\Users\Public\Documents\National Instruments\TestStand 2014 (32-bit) \Examples\Modifying User Interfaces\Handling UI Messages\DotNet\MainForm.cs:line 284
  InnerException:

  I tried restarting the PC and also reinstall TestStand 2014 but still not the same error.  I can, however, run the sequence editor and run sequences that without errors.

  I am that running on a Windows 7 64-bit installation and execution of the interface Visual Studio 2012 runtime solution.  Any ideas on what else to try?

  Kind regards

  David

  Hi David,

  Sorry to hear you're having trouble to get examples of the user interface to work.  A few questions to get a better idea of what is happening:

  1. If you have TestStand 32-bit installed only, ensure that the platform selected for the solution of the example is x 86, and then rebuild the solution.

  2. the example of the simple User Interface gives the same error?  ("\UserInterfaces\Full-Featured\CSharp\TestExec.sln")

  3. If you run the version selector TestStand and select this option to activate TestStand 2014 (even if it is already active), do you get any errors?  The example gives the same error after this step?

  4. If you have Visual Studio 2010 installed, please test this version as well because it's the version in that the examples have been developed.

• TestStand 2014 cleaning after the failure of a step

  Hi all

  I am new to TestStand, so I have a simple question that could boring you but I cannt find the solution.

  In my main sequence, I say 50 steps. If a step has not the next step to executete (by deafult).

  What can I do to stop the execution of the following steps if a step fails. I wish that the sequencer will cleanup directly then call the next step in the main sequence.

  All mere suspicion is appreciated.

  Axel

  Hello

  You can define the sequence of cleaning goto on the failure of the setting sequence:

  Configure > Station Options > immediately Goto cleanup sequence if an error occurs

  

  Also, make sure that the steps fail sequence on a step failed, by setting up:

  Parameters of the step > step sequence of Causes of failure

  

  I hope this helps.

• TestStand 2014 F1 Patch removes the report itself after execution of finishing

  Hi all

  today I installed the patch 2014f1 TestStand and after that, I recognized that TestStand removes my reports of ATML5 by itself after execution of finishing.

  I'm active On-The-Fly Reporting and store reports in different places for each sequence. This place, I determine in the PREUUT callback.

  During execution, I see that the report is generated exactly at the specified location, but if the execution is complete they will be removed immediately. I don't know why?

  Do I have to remove the f1patch? Someone at - it the same problems?

  I will be happy if someone has a suggestion what to do.

  Thank you very much!

  Hello

  I created a sample file to show the effect (see attachment). I think I found the problem and it's my fault.

  I have seen that it is me who deletes files (SetReportPath.vi). Before you begin the statement I want to erase the reports directory.

  When I work with my custom GUI LabVIEW (uses parts of the SimpleUserGUI-example of TestStand, singlePass-execution) everything works fine. The SetReportPath.vi removes the old reports and after the execution of this new report remains in this directory. PreUUT-reminder, therefore, seems to be executed only once. The same thing happens if I use TestStand SequenceEditor for the execution of the sequences and use there "SinglePass.

  When you use the SequenceEditor TestStand to perform sequences in Mode TestUUT the new report is deleted after that first Test USE ended and I click on stop in the USE Information-dolls. I think the PreUUT callback is called here and SetReportPath.vi deletes my report. This seems logical.

  With this routine I'm working now for two months and I noticed that the "deletion" just after the installation of the Patch TestStand2014f1. So I think that there are some changes by calling PreUUT-reminder, but I'm not sure. Maybe you can check this.

  Thank you!

• TestStand result processing

  Hello community,

  Using 32-bit Teststand 2014

  Is there a way to switch treatment result for the database enabled checkbox control programmatically in Teststand?

  Hi MechUnit,

  You can switch different report plugins programmatically by using the DatabaseOptions and ReportOptions reminders as described in this knowledge base Article.

  This does not affect the sequence running, it does not change what the result of processing dialog box appear or affect other sequences.

• TestStand table average

  Hello community,

  Using 32-bit Teststand 2014

  I have a one-dimensional array with a size ten (Array [10]). I want to be able to take an average of this table in Teststand. Using an expression of the statement, I am able to do digital = ((Array [0] + tableau [1] +...)) Array [10]) / 10), but this is tedious. Especially, if I have a table for more than a decade.

  In Teststand, is there a mathematical operation or another way to get the middle range?

  I don't think it's possible in a single expression.  Consider the attached example that does it in a single step.

  Hope this helps,

• ProcessHandle in 64-Bit TestStand

  Hello

  in the 32-Bit-TestStand sequences (4.1), I get 64-Bit-TestStand (2014) steps to "Call the executable" error

  "- 17308: ownership of process step manage rental must be an expression that returns an object reference."  "Invalid expression: Step.ProcessHandle.

  Now, the Step.ProcessHandle exists as a property of the step. The documentation says that an independent appeal of the number of bits should use the expression

  RunState.Engine.Is64Bit? Step.ProcessHandle64: Step.ProcessHandle

  However, Step.ProcessHandle64 does not exist as a property. Is it okay to use Step.ProcessHandlePtr? Would this work in sequences used in 32 - bit and 64-bit or the conditional expression above is necessary (with ProcessHandlePtr instead of the ProcessHandle64 non-existing)?

  Concerning

  Peter

  Hello Peter,.

  Thank you for your message.

  Yes, your proposal is good:

  Step.ProcessHandle is only supported on 32-bit Teststand. To use your secuences to a Teststand 32-Bit to a 64-Teststand, you must use Step.ProcessHandlePtr. 
  

  I hope I could help you.

  Christian

• The deployment of TestStand-19049 utility error

  I'm running an error when you try to create a new deployment of TestStand (process model, UI, etc.).  Specifically, I want to install the user interface and to transform the model in an absolute path, and that's where I'm running into the issue.  When I install to program files, the work of deployment without problem, however, I have run into issues trying to find files in things like property charger and other.

  To reproduce the problem:

  On the Installation Options tab, ' default Installation Base Directory: ' the absolute path value.  And the default installation directory is basically what whether (I tried my desired just C:\ directory and all the rest, but does not seem to make a difference)

  During construction, the status tab to build indicates the number of error-19049 with the message 'Destination not taken in charge under the current number of bits' and the message ' Base Directory default Installation: using the destination following WOW64 Directory System.

  I use TestStand 2014 32 bit with Labview 2015 32 bit on a 64-bit OS to Windows 7.  I can't change the number of bits of the TS or LV due to the dll I'm referencing that cannot be changed.

  Can anyone help?

  Seth_K salvation,

  It is a known bug that has been fixed in SP1 of TestStand from 2014; See ID 529404 number in the list of correction of a Bug in SP1 2014:

  http://www.NI.com/product-documentation/52845/en/

  The only known outside the upgrade to SP1 2014 TestStand solution is to use a relative destination instead of the absolute. If the upgrade to SP1 2014 TestStand isn't an option, let me know and we can look into other options.