The call of the TestStand of LabView modules

Similar Questions

• a problem with one of the files in the TestStand\AdapterSupport\LabVIEW directory

  When looking at the module a LabVIEW VI called for TestStand, I get the following message:

  A problem with one of the files in the TestStand\AdapterSupport\LabVIEW directory.  Please reinstall or repair.

  I made the mistake of cleaning C: in my computer.  Clean the C:\National Instruments downloads

  Why would someone put bits of applications or modules, etc. in such a directory?

  I'm not too crazy about restoring 11FR in this folder.  It's just crazy!

  If anyone has encountered this before?  No "easy"? outside re - install TS...

  Side note: I do not touch anything in the \Program files. National Instruments\TestStand\AdapterSupport\LabVIEW

  What version of LabVIEW and TestStand do you use?

  In 2012, TestStand, this directory is mapped to:

  C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 2012\AdapterSupport\LabVIEW

  Have you tried mass compiling the screws in this folder?

  I had to create a new 'TestStand - default values XX.llb"file, where XX is the last version of LabVIEW you use, but I have not seen this message before.

  Good luck

  PH

• I am using IVI step switch in TestStand 4.1.1 and also try to call the Actions of LabVIEW using IVI

  I use IVI pass the stages and steps of IVI DMM TestStand 4.1.1 and then I have an Action step that IVI spend IVI DMM and features.  The problem I have is that if I run the VI in LabVIEW bear only functions without any error, if I run of TestStand without all previous calls to switch IVI or IVI DMM it works also, but if I run the sequence with a step of IVI teststand pass first I get the following error:

  Initialize IviSwtch with Options.vi
  The primary error: unknown status code (Hex 0xBFFA4001)

  «"" "String of full appeal:»»"»
  Initialize IviSwtch with Options.vi

  -1074118655; User-defined error code.

  I remember there used to be a problem with the steps of the IVI and IVI running LabVIEW, does anyone know if this problem has been corrected?

  Other ideas would be appreciated.

  Hello Kevin,

  It is a question of trying to open more than one session to a particular device of IVI.

  Here is a knowledge base on the issue. I found this knowledge base by searching '1074118655' or 'TestStand IVI Action no' to ni.com.

  Please let me know if you have any other questions.

• How to avoid the launch of Labview when called by Teststand VI

  Hi, friends.

  I am a student of teststand. I wrote a few screws by Labview. Now, I want to invoke in teststand environment. But when I run the sequence. LabVIEW automatically launches. How to avoid the launch of Labview when I run the sequence?

  Thank you.

  I'm not sure that I follow what you're saying...  But it seems that when the VI is called, the LabVIEW Development software is started and you want to avoid this.

  If you create an executable file or a dll and that any call within TestStand, she should not call the development environment.  You must have the LabVIEW runtime engine installed on the target computer.

  For several years I used TestStand with LV, if my memory does not have to be precise.  I think that the above worked for me.  However, it seems that I remember something to have the LV code in debug mode, causing to open development environment... but it's a distant memory.    You do not use breakpoints where the LV VI is called, are you?

  R

• With the help of dynamically called screw in TestStand deployment

  I write code to interface with a & Rohde Schwarz ZNB Network Analyzer.  I use LabVIEW 8.2 and TestStand 3.5.  For reference the ZNB driver is available here: R & S of ZNB Driver.  I use a slightly older version of the driver, some before they needed to LabVIEW 2009.  I am writing all the code on a development machine that has the full version of TestStand/LabVIEW and it works on another machine that has the TestStand deployment license.

  This driver is dynamically linked to some things he needs.  I am able to operate with simple LabVIEW EXEs but not in TestStand deployments.  The following excerpt comes from their documentation, explaining a little about how the driver works and how to use in LabVIEW EXEs.

  3.4.2 How to generate executables or libraries in LabVIEW driver kernel drivers instrument based on attributes is dynamically bound to any VI performed during execution. This can be recognized by the LabVIEW application builder. The LabVIEW application builder follows all the static dependencies and include them in the package distributed at the generation of an executable file.

  To create an executable in LabVIEW, please manually add all the screws in the \PREFIX \_utility\callbacks folder to the LabVIEW project. In the case of project based please add private to your project folder. With this reference manual, the driver core is included in the compilation and the driver core is accessible during execution.

  I can't get this to work in TestStand deployments at all.  I can't even connect to the device since the VI Init has these issues.  I get the same error for all the various attempts that I made.  The same error is that when you add manually the screws for the LabVIEW EXE.

  Error-1073807346

  Property in Rohde & Schwarz Vector Analyzer.lvlib:rsidr_core_session_fgv.vi-> network node

  Rohde & Schwarz Vector Network Analyzer.lvlib:rsidr_core_check_error.vi->

  Rohde & Schwarz Vector Network Analyzer.lvlib:rsidr_core_attribute_write_int.vi->

  Rohde & Schwarz Vector Network Analyzer.lvlib:rsidr_core_attribute.vi:3->

  Rohde & Schwarz Vector Network Analyzer.lvlib:rsvna.vi:2->

  Example 1 setting of the Instrument 24Default .vi:1->

  Rohde & Schwarz Vector Network Analyzer.lvlib-> efault Instrument Setup.vi

  Rohde & Schwarz Vector Network Analyzer.lvlib:Reset.vi->

  Rohde & Schwarz Vector Network Analyzer.lvlib:Initialize.vi->

  Connection of ZNB testing.VI

  VISA: (Hex 0xBFFF000E) the given reference of session or the object is not valid.

  So far, I tried the following, all solutions producing this same error.  I struggled with this and turned off for awhile then maybe there are other solutions attempts I forget.

  (1) it looked like a lot of the report to go to the private folder were finished in SupportVIs.  I manually pasted the rest there, too.

  (2) I added all driver files on my workspace and included in the files with the rest of my deployed screws.

  (3) I added all driver files on my workspace and said pilot TestStand to deploy them to the original location in Program Files.

  Someone at - it ideas?  R & S didn't even know what was TestStand, so that they could not help me.

  I was finally able to solve this problem on mine, the other day.  I brought the Network Analyzer to my office and did a lot of tests in this way.  Eventually, I discovered that I needed to include the folder private pilot deployment, what I was doing in one of previous attempts.  It turns out that you must also maintain the original of this file directory structure when you include it, otherwise dynamic calls are not looking in the right place.  Once it worked on my PC, I got it on the machine test and worked as well.

• How to configure controls/indicators of Labview so the TestStand will automatically import the

  Hello

  I am fairly new to Labview and TestStand.

  I created a simple GUI of Labview with controls and indicators. When I add the labview module to TestStand it doesn't matter these controls/indicators.

  What should I do to get TestStand to import these controls/indicators.

  Thank you best regards &,.

  Aly.

  Is this just a VI LabVIEW implemented as a step of TestStand? If yes associate you controls and indicators to the connector pane in the upper-right corner of the LabVIEW vi? (index right click the icon and select Show the connector pane)

  What is a LabVIEW to Interface to operator TestStand implimentation? If if look at the examples in file for Simple Interface operator of LabVIEW TestStand.

• How can I get the TestStand splash screen to not show up when I call the results treatment Utility offline?

  So I call the Offline processing Utility (ORPU) a not executable call results in a plugin to perform a personalised treatment in another configuration.  Everything works fine, including having run reduced (mostly hidden) by using the option/tray.  When he called, the TestStand splash screen appears (certainly is not a show-stopper but it's confusing from the point of view of the user).

  Is it possible that I can get this start screen to not appear when calling the ORPU?  I noticed in the help, mention is made of the use of the callback file, and I wonder if someone has successfully used this to avoid the dialog box or other behaviors.  I would like more info on how it works, but it doesn't seem to be a vast detail on this in the help, and I'm not also find me useful examples.

  The source of the Offline utility treatment results is included with TestStand and can be changed.

  The ORPU source is located under "Components\Models\TestStandModels\Offline utility treatment results"

  From the source, you can see that there is no flag that allows you to hide the splash screen (except for / I leave, but that it will also close the ORPU!); However, you can easily change the ORPU so it does not show the start screen by removing the following lines in \Components\Models\TestStandModels\Offline Results Processing Utility\OfflineResultsProcessingUtility\MainForm.cs

  If (! data.) Quit smoking)
  splashScreenForm = new SplashScreen (mEngine, false);

  Regarding the flags without papers, there are not really many flags undocumented in the ORPU (even once, you can see them in the source), and undocumented flags have very specific use cases (open files from shell and NEITHER internal regression tests).

  A (non-official) complete list of indicators ORPU from 2014 TS:

  /?
  Shows help

  / tray
  Starts the ORPU in the status bar

  / exit-when-done
  Exits when all files are made

  / I'm leaving
  Leave immediately

  /process - files - Missing - Data
  Treats the files even if they lack of data

  / which-process-files-Missing-Data
  Do not process files that are missing data, show only a mistake (it is the default behavior).

  / Process-All-Profiles
  Start all profiles

  / Process-No.-Profiles
  Don't start any profile

  / Process-Profiles
  Treat the profiles specified in the following arguments

  / process-files
  Add the files specified for the specified profile

  / log - level

  Sets the logging level for the newspaper ORPU, all of the messages above, the specified log level is saved.

  /ShellOpen
  It is an internal indicator, it is used to treat applications for the shell (for example, after a double click on a tsr in Windows Explorer). Do not use this indicator.

  / non-interactive
  It is an internal indicator used for the test. Do not use this indicator.

  Please note that NEITHER does not support appellant flags undocumented and that NEITHER is not guaranteeing backward compatibility of these flags undocumented and they could change at any time, without warning.

  For a more detailed explanation of the working of each option, refer to the Arguments of the command line Utility using TestStand treatment results offline.

  Hope this helps,

  Francisco

• The execution of the sequence TestStand in LabVIEW via TS - API: execution different times for the same sequence

  Hello - the members of the Forum.

  I have a problem about the execution of a TestStand sequence into LabVIEW. I created a VI that offers the possibility to choose a sequence TestStand-file and then executes the sequence using the TestStand API. The implementation is based on an example in C++-Application found the following link:

  http://forums.NI.com/T5/NI-TestStand/unreleased-references-using-engine-API-in-C/m-p/2927314#M46034

  The app works pretty solid where the VI is executed the first time. The VI treats the sequence chosen in an acceptable time.

  But where execution is started again, the sequence takes approx. 30 sec more than in the first case.

  So far I have not found a solution and hope someones got a clue about this problem...

  I use 2013 LabVIEW and TestStand 2013.

  I enclose my own VI, a sequence of the specimen with a small sample of VI, so you can reproduce the problem.

  Kind regards

  TobiKi

  
  

• Call the function in LabView from a DLL, and then access the global variable of DLL

  I've created a DLL in LabWindows with a function and structure.  I want to call the function from LabView and then access the overall structure.  I am able to call the function in the DLL with a "call library function node" and has access to the return value, but I can't understand how to access the overall structure.  The structure is declared in the header DLL with __declspec (dllimport) struct parameters file.

  Is it possible to access this structure without using the library of network variables?

  My guess is that you need two bytes of padding after "in_out" and another to two bytes of padding after "anin."  The reason being that ints are 4 bytes, and most of them C compilers will align on 4-byte boundaries.  The struct will naturally start to such a limit (in fact, in Windows, it will probably start to an 8 byte boundary).  If you then count bytes in your structure, you are 70 byte after "in_out."  70 is not divisible by 4, so you need 2 bytes more to reach the next 4 byte boundary.  You can also you could reorganize your struct so that "anin" follows "in_out" and this is probably the best option if it won't cause you other problems.

  Unlike most C compilers, LabVIEW compressed structures as closely as possible, without filling.  I don't know enough about the history of LabVIEW and internal parts to explain the reasons and to do this performance penalty, but, as choice of LabVIEW "endianness", it is probably a remnant of the first versions of LabVIEW that were running on the Mac.

  If for some reason you want to force your C struct to match package LabVIEW, you can use the #pragma pack (x) directive, but I wouldn't recommend that here because you can control the C and LabVIEW.

  EDIT: in the cases where it was not clear, add padding to your cluster of LabVIEW, insert appropriate size or items at the place desired in the cluster.

• How can I get the LabView return standard splash screen after installation of the evaluation of Robotics module?

  I installed the Labview Robotics module for evaluation, but when I start now Labview I meet the following start screen:

  

  How to bring back the Labview standard splash screen?

  Terje,

  When LabVIEW Robotics is installed, it replaces the file LabVIEW get a window on the way.  You can return to the standard window began to to repairing the installation of LabVIEW:

  1. Go to add/remove programs from the control panel.
  2. National Instruments -click and select Change/Remove.
  3. Choosing to fix LabVIEW.
  4. Insert the LabVIEW Setup disk if you have an or navigate to the network location that you used to install LabVIEW.
  5. After you have repaired LabVIEW, you should be able to restart with the default value getting started window restored.

• How to avoid the launch of Labview VI when he invokes in Teststand environment?

  Hi, friends.

  I am a student of teststand. I wrote a few screws by Labview. Now, I want to invoke in teststand environment.

  But when I run the sequence. LabVIEW automatically launches.

  How to avoid the launch of Labview when I run the sequence?

  Thank you.

  LabVIEW programs require a runtime engine. Under the TestStand configuration drop-down, select adapters. You can change the LabVIEW adapter to select the runtime rather than the development system.

  This should prevent the main screen of LabVIEW to appear, but you will not be able to change your LabVIEW VIs while they run of TestStand using the runtime engine.

• Store the Teststand ActiveX reference in the LV shift register

  It is posted here

  I'm trying to store the references TestStand ActiveX in a shift register not initialized a VI.  In my case, the references are passed into the TestStand VI (not created from in VI).  If I call the same VI to the next step (same sequence and execution of the previous step), since the shift register ActiveX references are not valid.

  The VI remains reserved to run during these two stages and is not unloaded from memory, so the shift register data should remain intact (in fact, the numerical values of the references are actually kept).  LabVIEW is still trying to close any ActiveX reference, even if they were not created from the VI?  Is there a way around this problem?  Or I'm just something wrong?

  

  jsiegel-

  In general, when the code is passed a COM reference and code is to keep the reference to a global or shift register, even after his return from the call, the code must add a reference to the object so that the object server knows that the object must be destroyed not. It is also the responsibility of the code that fits on the reference in the world or a register shift to release the reference to the object when it is no longer necessary.  LabVIEW is not different from any other language.

  So, here are more details. TestStand application LabVIEW for run the VI, TestStand after the reference as a parameter to the method of the server to run the LabVIEW VI. COM creates a proxy for reference and give the reference of proxy for the code module. Your VI then stores the value of the proxy reference in the global or the shift register. When your VI ends and returns to TestStand, COM releases the proxy reference, the value in the global or the shift register is no longer valid.

  Basically, you need to add or duplicate the reference to the object passed in LabVIEW by calling the VariantToData function. Pass the existing reference, set the input type to the same type of the reference, and the result will be the reference in doubles. You can assign the double reference to worldwide or register.

  Normally you must well to release the reference later by reading the value of the global or shift register, explicitly calling the function close reference with which to reference, and then assign A Refnum Constant stepped up to the global level or shift register to nullity. In the case of a module of code, I believe that when TestStand unloads the VI, LabVIEW frees the reference correctly. If this isn't the case, you will get a debug message to unpublished during the TestStand stop object if you have this option enabled.

• Retrieve the names of the measures of the stage using LabVIEW

  How retrieve you the names of the measures a digital multiple of the step using LabVIEW?

  I have built a vi to be called TestStand and will pass the "ThisContext', but the vi is not complie.  That's how far I got.  The vi is attached.  The error message is:

  "The method selected in the invoke node is invalid or no method has been chosen.  Click on the invoke node and select a method. »

  My vi is an attempt to write the code of

  Normal
  0

  fake
  fake
  fake

  MicrosoftInternetExplorer4

  / * Style definitions * /.
  table. MsoNormalTable
  {mso-style-name: "Table Normal";}
  MSO-knew-rowband-size: 0;
  MSO-knew-colband-size: 0;
  MSO-style - noshow:yes;
  "mso-style-parent:" ";" "
  MSO-padding-alt: 0 to 5.4pt 0 to 5.4pt;
  MSO-para-margin: 0;
  MSO-para-margin-bottom: .0001pt;
  MSO-pagination: widow-orphan;
  do-size: 10.0pt;
  do-family: "Times New Roman";
  MSO-ansi-language: #0400;
  mso-fareast-language: #0400;
  mso-bidi-language: #0400 ;}

  message.ID = 10653 in LabVIEW.  More precisely:

  Normal
  0

  fake
  fake
  fake

  MicrosoftInternetExplorer4

  / * Style definitions * /.
  table. MsoNormalTable
  {mso-style-name: "Table Normal";}
  MSO-knew-rowband-size: 0;
  MSO-knew-colband-size: 0;
  MSO-style - noshow:yes;
  "mso-style-parent:" ";" "
  MSO-padding-alt: 0 to 5.4pt 0 to 5.4pt;
  MSO-para-margin: 0;
  MSO-para-margin-bottom: .0001pt;
  MSO-pagination: widow-orphan;
  do-size: 10.0pt;
  do-family: "Times New Roman";
  MSO-ansi-language: #0400;
  mso-fareast-language: #0400;
  mso-bidi-language: #0400 ;}

  Dim MyStep ACE [step]
  Dim MyMeasurement As PropertyObject

  MyStep =
  seqContext.AsPropertyObject.GetPropertyObject ("Step", 0)
  MyMeasurement =
  MyStep.AsPropertyObject.GetPropertyObject ("Result.Measurement [0]", 0 ")

  MsgBox (MyMeasurement.Name)

  Can someone help me complete the vi?

  Thank you

  Thank you very much.

  A small change to the vi required.

• How to save stationglobals the disk in Labview

  Hi, can anyone suggest me how to save the values of stationglobal the disk when my vi is running? I update the stationglobal property set API TS call in my vi. But when I left the TestStand and open again the old values of stationglobal are still there and not news. What should I do to update the values of stationglobal? If anyone has any sample vi please provide me.

  Thanks in advance,

  Nadie

  Try this. You don't mention the version of LabVIEW, you use so I recorded to 8.0.

• Looking for advice on navigation in the TestStand API.

  I use TestStand for a few months now (self-taught using a LV architect with experience of the TS) and I think I will do certain things programmatically at run time and finished watching the massive array of properties/methods, etc. and ask yourself who are the properties/methods that will allow me to do what I have in mind.  Is there something fundamental missing in learning to understand which path to take to get down to the specific class and property/method interests me?

  For example, at the moment I am trigger some additional operations on the process model in addition to running the main client generated when you enter Test DUT. I would like to be able to programmatically from within TS itself, or more probably of LabVIEW or hide these tabs when running... I guess it's possible.  I know that executions can be set initially hidden but a search for 20 minutes of the API not immediately revealed magical items to let me do this programmatically.

  Hey, smoke,

  The ApplicationMgr TestStand is located within the TestStand UI control server. To access the Application Manager, you first need to action a step ActiveX (because it is an ActiveX control) and RunState.Engine.GetInteralOption (InternalOption_ApplicationManager), you get a Manager Application object.

  Example:

  "Select the Module tab then under Automation server" NI TestStand XXXX UI controls (Ver X.X)

  The object reference"RunState.Engine.GetInteralOption (InternalOption_ApplicationManager)

  Class object' ApplicationMgr (IApplicationMgr)

  Get the property executions

  Which returns an object reference and class performances, thus, create a variable(Local,FileGlobal,etc) of object reference to use to retrieve the properties of the Application Manager.

  Also note that to get the individual properties of your Application Manager object you won't be ActiveX measures for the properties you want.

  I hope this helps.