Saving choise of enum to TestStand

Similar Questions

• DAQmx tasks name variable

  Can someone explain why use a variable LabVIEWIOControl to keep the name of the task of DAQmx, Labview causes the sequence editor to become extremely slow. The vi attached does nothing more to open a chan (output on a pxi-6723) and its closure via the parameter of OPERATION enum (see teststand sequence).

  To simulate the problem, right click on the Action step and select "define the module." Once the tab "module" is open, click back and forth between Action 1 and 2 of the Action (1,2,1,2, 1.etc). You should see some delay, pulling up info from module of step up 2-1.

  My 'real' application works well, but a step of editing may take 10 seconds to get the info from the module. Note: This is the type of variable only what causes this problem that I have used cluster, string, enums, tables ect in the past without problems.

  I have attached a seq teststand advocating the vi.

  Görz

  There is a slowdown in TestStand, known while choosing a 8.6 VI, which has control of e/s on the side of the connector.

  See the following link for more details and a fix - http://digital.ni.com/public.nsf/allkb/1E3C0A420D28B60E862574C8004D9062

  Concerning

  Anand jegou

  National Instruments

• TestStand deployment error - error: unable to locate all the screws saved subVIs because it lacks a Subvi

  Hello

  I am a systems and software engineer based in Vancouver. I developed a test system automated using 2013 LabVIEW and TestStand 2013 with custom operator interface.
  I encountered problem 'lack screw' which is kind of weird because I went to analyze the sequence for the TestStand Deployment Utility and TestStand sequence editor > files broadcast tab.
  But when I tried to build the installer and reach the point ' called distribution screw, it always throws an error saying "an error occurred trying to read the error of the screw, possible because the screws are not saved in the latest version of LabVIEW. Do you want to save any changes now? ". I tried both (that is to say Yes and no) for this option, but it has not solved the problem.

  This is part of the original error message displayed in the TestStand deployment utility:
  " ***************************
  Then the treatment live...
  Error: Cannot locate all the subVIs screws saved because a Subvi is missing or the VI is not registered in the last version of LabVIEW.
  The chain of calls to missing screws:
  1 - ATE_AccelerometerTest.vi
  2 - CreateAndMergeErrors.vi (missing)
  3 - LogControl_CheckForErrorSendUpdates.vi (missing)"

  All screw missing come from userlib.

  Actions performed:
  -File of sequence analyzed by using the TestStand Deployment Utility and TestStand sequence editor
  -Checked "search directories" include all the necessary files/dependencies.
  -Mass to compile the directory of the missing screws
  -Added all the necessary files and folders in the workspace file.

  The result is always the same function according to the actions performed.

  Debugging last I did earlier, is that I tried to find the sequence and steps missing screws as shown above (for example ATE_AccelerometerTest.vi)
  and I discovered that the measure appears to be an empty action step. This would be possible even if it has already passed the analysis?

  Other considerations include:

  I'm using sp1 2013 LabVIEW and TestStand 2013. We tried the building three 3 computers and we only managed once to a freshly installed comptuer.

  Hoping to hear from you soon.

  Kind regards

  Michael Panganiban
  Engineering systems and software
  www.Synovus.ca
  [email protected]

  Hi all

  We were able to solve the problem. First of all to note is that the release notes in 2013 TestStand is obsolete and we confirmed engineer OR Austin TestStand 2013 works very well with LabVIEW 2013 SP1.

  Second, we played option deployment TestStand that solved the problem. Attached are the pictures.

  We have activated just the 'delete unused Components VI'. It could be one of the libraries (lvlib) we have included in the compilation, but we've not thought of it again because we have checked that all the screws are working. It could also be something else that I think is very hard to find from information. However, if someone had the same problem, this could be useful.

  Again, we return to using 2013 TestStand and LabVIEW 2013 SP1.

  I appreciate all comments and feedbacks. Otherwise, you can close this request for assistance.

  Thank you.

  Kind regards

  Michael Panganiban

  Engineering systems and software

• deployment error: unable to locate all the subVIs screws saved because a Subvi is missing or the VI is not registered in the last version of LabVIEW.

  Hello world

  I want to deploy my project Teststand and got a strange error when creating the image.

  For many additional files with the suffix as .tso, alias, lvlpb, exe, dll... deployment tool launches the error message "unable to locate all the subVIs screws saved because a Subvi is missing or the VI is not registered in the last version of LabVIEW.» (see also the attached picture).

  If I exclude the files of my distribution or set them to "include without treatment or dependencies of elements of" the generation works fine.

  After the error, I checked the Temp folder. The temporary project LV is not yet created.

  I used the deplyoment-installation in the same way within a fromer project and had no problems like that...

  I use Win7 / LV2013 SP1 & Teststand 2013 f1 (5.1.240).

  Could someone help or support? Thank you!

  Finally, I tried the construction with LV2015 & TS2014 - no problems... Everything works fine...

• TestStand can not find that all exported DLL functions

  Hi all

  My problem is the following:

  I have a DLL that I compile with Visual Studio with 40 functions. When I want to use this DLL in teststand, there are two missing functions. If I check with the dependency walker, the 2 missing function in teststand tool are well implemented.

  The missing function prototype:

  struct HModemBoardOpaqueType * mbCreateModemBoard (void)

  Good function prototype:

  enum UbtDllErrorCode mbDisconnectFromModemboard(struct HModemBoardOpaqueType *)

  Is that possible that teststand does not structure opaque type correctly?

  If I export my function type C (with extern C) no function is missing from the test bench

  Thank you

  What version of TestStand do you use? Older versions of TestStand only supported zero, digital and Boolean data types for the return values of the adapter of the dll. More recent versions of TestStand are now supported pointer/handle as well. New versions of TestStand I expect you can use such a prototype with the handle/pointer data type. However, if you want to convert this struct to an equivalent TestStand custom data type, you need to make a parameter instead of a return value, as the card does not support the conversion of struct for return values.

  Basically returning a struct pointer this way (as return value) is dangerous in C/C++, because it is not possible to know who owns the memory. The type of pointer/handle allows you to do anyway, but it must be properly to maintain life of memory return you at a lower level (i.e. maybe with an exported function that uses the pointer who knows how free it).

  Hope this helps,

  -Doug

• Record class in binary with TypeDef Enum object

  I'm curious to know if this is expected behavior. I'm trying to save a class object to a binary file. In the private class data, I have an enum of the def type. If the type def change once the data has been written to disk, the data back out restores the default value of the enum.

  I have worked under the assumption that "Labview automatically creates algorithms to change data from the old format to the new format when you change your private data" (cited directly in the section on storage of objects of the class on the disk in the oriented object programming in labview course). It doesn't seem to be valid in this case. I've attached an example that illustrates. To reproduce:

  1. run "Write Binary.vi" and a binary file will be saved with the value enum Val3.

  2. make run 'read Binary.vi. ' The results should be Val3 as expected.

  3. open "TypeDefEnum.ctl" and remove Val2 from the list of enum.

  4. make sink "read Binary.vi". The result will now be Val1, Val3 not.

  EDIT:

  Should have added, I'm on Windows7, 64-bit, sp1 Labview 2012

  It turns out this is a known issue and it has been documented in CAR 48516.

• How to pass an enum testbed

  Is it possible to pass an enum in of TestStand? Otherwise I'll have to do a string and don't compare on my case, but it would be useful as I could?

  The compiler said

  Accessibility inconsistent error 1: type of parameter 'ChamberClass.Chamber.ChamberName' is less accessible than method ' ChamberClass.Chamber.Initialise (NationalInstruments.TestStand.Interop.API.SequenceContext, ChamberClass.Chamber.ChamberName, int, out bool, out int, String)

  The enum (highlighting) is declared in my class, and so I could understand why he loves her but just on the off chance that there is a solution...?

  Fixed! No need to answer:-once more, it wasn't a question of test bench: it's because my enum is private...

• Why my TestStand deployment installation appear under my Windows will not start menu of my target machine?

  Why my TestStand deployment installation appear under my Windows will not start menu of my target machine?

  I managed to install the deployments of work to the target machines. However, I expected to see the classified facility "My TestStand system" in my Start menu, but it is not. Am I misunderstanding something here?

  Also, if I do another target second deployment to the station as "My TestStand system B", all LabVIEW files in my previous installation for "My system TestStand" disappear from the directory (c:\Program Files\My TestStand system) target.

  I use TestStand Professional 4.2.1 on Windows XP and LabVIEW 2009 development station.

  Thank you Paul,.

  That solved my second problem and inspired me to look deeper for the response to my first problem. The answer lies in the tab 'distributed file","Installer properties' box 'create a program item:

  

  Wouldn't be nice if it is automatically checked by default for main sequence files? Wouldn't also nice if "Upgrade Code" was regenerated automatically by default whenever we have saved the file *.tsd under another name?

  Thanks again,

  Eugene

• Run another module after the generation of the report before TestStand ends the execution

  In my application after that TestStand generates and saves the report, I would like to initiate a stage to send a flag informing that the test is complete and the report is saved. How do I get there? The report is saved at the end of execution of TestStand.

  I don't want to On-the-fly reports because I don't like the information during execution. On-the-fly reporting, also saves the report at the end. I would like to save the file and then sent indicator. It is fine if the results of the stage to send the flag are not saved in the report.

  Hi Sumit,

  You can change the sequentialmodel.seq itself as indicated in the document that you referred. (process template customization).

  After reminder Post USE in the "TestUUTs" sequence that you can add your custom steps that will search the report exists and that the flag.

  The path to the report file will be in the local variable as shown below. (full runtime).

  "Locals.ModelPluginConfiguration.Plugins [0]." PluginSpecific.RuntimeVariables.PerSocket [0]. Path. "

  Generally, please copy the model of process changed in the equivalent public folder with a new name.

  User can select this new process model in the menu set up--> stationoptions--> model tab.

  Your new process model must be detected automatically if you copied into the right directory public and restarted TestStand.

  I hope this helps.

  Ravi

• 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

• TestStand said modified prototype

  When starting my TestStand complains that the prototype of a VI changed the main sequence. The file has been opened and saved inadvertently, but comparison tools shows some differences between the archived version and the working version. This vi is affected dozens if not hundreds of times, then it will be a major undertaking to stop at each place TS complains and reload the prototype.

  Why think TS that the prototype has changed? Is there an easier way to solve this problem?

  Thank you

  JVH

  Bug 4.2 and 4.2.1. Use "tools > update VI calls" as a workaround.

• path of the TestStand 4.2 file report "SpecifyByExpression" does not work

  I noticed that there is a problem in specific terms that has been fixed in 4.2.1

  Is not this problem.

  This is a problem when I select 'Specify report File Path by Expression' specify the expression to use, and then TestStand uses settings appropriate to the option "specific directory.

  I rechecked and it is quite reproducible.

  The phrase is: "\\Reports\\_ [] [] [] .xml'"

  But each time, the report file is generated by using the specific directory setting.

  Is there a solution for this?

  Thanks for any help.

  BTW, the "New Message" page on your site does not work in Opera 10.01 - I can not enter line breaks after the current line in the editor no HTML - line breaks go in front of the current line instead.

  I don't feel well in software TODAY. Entering the path expression of the report in HTML file is not my favorite activity!

  Nick-

  I'm a little confused as to what you mean. You have configured ReportOptions to specify the report by Expression file path? If so, the Locals.ReportOptions.DirectoryType property contains the string "SpecifyByExpression"? The directory 'C:\Documents and Settings\Temp\TestStand\Reports administrator' is where TestStand stores reports where the report should be saved on disk in the directory the Client's sequence file, but the file of the Client's sequence has not yet recorded on the disc.

  I followed the Locals.ReportOptions.DirectoryType and the Locals.ReportFilePath of the process template properties to check if they contain the appropriate strings.

  Determine the path of file report Expression is default SequentialModel.seq, where the expression is evaluated and the Locals.ReportFilePath property is set. You should check to see if this step is actually performed during your run and if the Locals.ReportFilePath property is on the right channel:

  

  

  I hope this helps.

• TestStand on Windows 2K 3 x 64 deployment issues

  Holil:

  I hope that there can someone advise me.

  I recently tried to build an application TS to deploy on a server running WIndows Server 2003 x 64, and I ran into some difficulties.  On my development system, (32-bit Windows XP pro), I built a deployment TS Installer.  I transferred to the destination machine.  Installation failed... He says that many files were missing from different CAB files.  I tried again... the second time I had more luck... the installation seems to take.  Using the License Manager, I turned on my setup using my development license (my deployment license has not yet arrived).  I tried to run my application and I get an exception that seems to indicate that the ActiveX DLL are not saved:

  Unhandled exception: System.Runtime.InteropServices.COMException (0 x 80040154): C
  Lass did not registered (Exception from HRESULT: 0 x 80040154 (REGDB_E_CLASSNOTREG))
  at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance (Guid & clsid, Obj
  ECT punkOuter, Int32 context, Guid & iid)

  I tried to register these manually to help

  regsvr32 "D:\Program NIUninstaller Instruments\TestStand 4.1\API\DotNet\Assemblies\CurrentVersion\NationalInstruments.TestStand.Interop.UI.AxControls.dll"

  but he complains that this DLL has no DllRegisterServer entry point.  (Is this the wrong DLL to register?)

  I tried to uninstall my deployment and installation the teststand full... and the SeqEdit seems to work fine.  (He must have registered the DLLs required, no?)  My app, however, still does not. I try to install Visual Studio to see if I can rebuild the application on this system with better results.

  I missed an important step?

  Thank you!

  Tom MacLean

  I think the problem was I have to target the solution for a x 86 platform... not any platform.  If I have other problems with this particular application, I was able to recreate the example Simple OI in a new project with the same exception that I had with mine, and change the target platform does the job.

• TestStand Simple OI does not close properly

  Hello.

  We need to build a test system that runs TestStand 4.2 and code modules are created with LabVIEW 9.0. The SW is running on a PC with Windows XP.

  We currently use TestStand Simple (LabVIEW version) User Interface to run the tests, and with the Interface of the operator we have a problem.

  If we use the file TestExec.exe provided with the installation of TestStand, everything works fine. But we need to make some modifications to OI and if we open the project file, and then recompile the IO, then the IO does not properly close. It seems the execution testengine stop and stop the VI, but the window doesn't go away until move us the mouse.

  When I open the LabVIEW project file informs me that the project was saved last version 7.1.1 and we now run 9.0.

  Can someone tell me what is now the window on the screen until there is activity on the mouse?

  I found a solution.

  But I'm still a little bit frustrated because I have no idea why it works...

  Anyway, if I open the vi for the OI Simple properties, go to execution and change the enforcement system preferred UI Standard, then the problem goes away.

• What TestStand prevent you to do if you don't have administrator rights on your computer?

  Hello

  I need to know what TestStand will not allow me to do if I don't have admin rights on my computer?

  Dusty,.

  There are very detailed information on the TestStand users in the TestStandReferenceManual for TestStand 4.0. I would like to begin in Chapter 7 "user management".  In addition, if you are not the administrator of the windows account, you will not be able to write to the registry, and you will be limited to specific locations on the machine. You will not be able to use the version switch, and depending on your user account settings, you can or perhaps not being able to write to program files. If you do not have this ability, you will not be able to write to the directory of TestStand CFG. The CFG directory is where your settings are saved, so if you change something in your options of station and then close, you get an error message and must reset the settings when you reopen the sequence editor. This problem has been fixed in TestStand 4.1 because they left the CFG program files directory and is documented in the TestStand 4.1 release notes.