Loading vi's with operator interface

When I load a sequence file with my operator interface, I always get a message that the vi is already in memory. When I close LV in taskmanager and the load the sequence again, the error is gone too. Is this a configuration problem? Because my other system don't have this problem.
Solved!
Go to Solution.
Attachments:
File_load.png ‏111 KB
load-error.png ‏128 KB

Great!
Thanks for letting me know.
If you would encounter any other issues or have some questions, then don't hesitate to let us know.
Kind Regards,
Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
CLD, CTA
If someone helped you, let them know. Mark as solved and/or give a kudo.

Similar Messages

How to load external DLLs with C++ interface in TestStand?

Hi,
Can you please let me know how would I load external DLLs with C++ interface in TestStand?
Regards.

TestStand 3.x can only call static class C++ methods. TestStand cannot call methods on a C++ object because TestStand does not know how to enstantiate the C++ object. In TestStand 3.x, there is a online help topic called "Exporting Class Methods and Functions in Visual Studio .NET".
Scott Richardson
National Instruments

Launch TS sequence with operator interface

create shortcut for launching a TS sequence with operator inteface.
Right now, with Windows98,
1. I doubleclick the test stand Labview Operator interface on the windows desktop.
2. Click on File menu
3. click /Select the sequence (at the bottom of File menu to launch the sequence in the Operator Interface.
How do I create a shortcut to do these three steps?
Double-click an icon on the desktop, launch the Operator interface and the sequence.

Hi,
I guess what you want to do is launch the OI and load a test sequence from the command line.
Unfortunately you cannot do this with the LabVIEW Operator Interface as labview apps does not except the command line parameters.
Regards
Ray Farmer
Regards
Ray Farmer

Error Loading a VI of a sequence in operator interface (Error Code -18002)

I am deploying a teststand sequence using LabVIEW adapter. After deploying, while running this sequence in operator interface in the deployment computer, I get an error saying that a particular step could not be loaded. This step calls a DIO initialization VI which basically uses DIO Port Config.vi from Traditional DAQ 7.4.4 version. Please see the attached image.
Software Versions Used: Teststand 4.0.1f1, LabVIEW 8.5, Traditional DAQ 7.4.4, Simple OI shipped with Teststand, windows XP
From couple of links from www.ni.com, I did following actions in my development computer:
1. Compile All the VI in LV 8.5 using Mass Compile including Traditional DAQ LLBs, simple operator interface etc.
2. Check if any VI or step is not broken.
After getting the error, I tried opening the same sequence in sequence editor in deployment computer (I am also including sequence editor with the deployment utility), I checked DIO Initialization step. I see the warning in step indicating that the VI is either broken or one of its sub is not located. I tried using Reload VI Prototype, it asks for LVDAQ.dll which is also bundled in my deployment files. After specifying this dll, I can run this sequence without errors but after I exit from sequence editor, it does not save the changes and I get the same error in Operator interface as well in sequence editor after re launching. Also I dont want to reload VI prototype as I dont expect some to do this change after deploying the testsequence.
Kindly help.
Thanks in advance.
Nirmal
Attachments:
Auto_Cal_18002 Error11.JPG ‏25 KB

I found solution for this. While creating the workspace for my sequence and other files, I used to include all the files including the LabVIEW VIs. Doing this, DIO Config VI seemed getting confused while searching for LVDAQ.DLL in the deployment computer.
I tried only including the test sequence and letting the teststand deployment utility select the VIs from the specified directory resolved this issue. I observed that in this case, all the sub vi and the support dlls gets placed in the support and data folder respectively. This resolved the issue.
Regards,
Nirmal

Problems to show IVI driver, properts loader when using operator interface

I am using the Operator Interface (programmed in CVI, with asynchronous timer) in folder OP1 in attached zip file. This operator interface puts not the error message of IVI driver, properts loader etc... on the screen (messages like in attached picture error.jpg in attached zip file). Because of stability problems I am using this operator interface but I need these error message.
A Other Operator interface is OP2 in attached zip file. This operator interface puts the error message of IVI driver, properts loader ... on the screen (messages like in attached picture error.jpg in attached zip file).
Now I want to have this functionality with OP1 becaus of stability reasons I have to use OP1.
How can I implement this in OP1? I tried and searched a lot of time but I have not found a method to implement this.
can anyone help me?
thank you
regards Samuel
Attachments:
OP.zip ‏3405 KB

Hi Sam,
if you open the userinterface which comes with Teststand - the simple one - you should be able to find the difference. You can find it here:
C:\Programme\National Instruments\TestStand 4.1\UserInterfaces\Simple\CVI
I hope this helps.
Greetings, RMathews

Programatically Loading Several Sequences Using LV Simple Operator Interface

I am playing around with the supplied LV(2009) Simple Operator Interface for running TestStand (4.2) and hoping that someone can point me in the right direction.  I know this may be too generic for a concise solution, but hopefully I can get some suggestions on the best approach for this. Here is a short description of what I am trying to accomplish.
I am testing 2 unique UUTs on a single test fixture that is controlled by a PCI-7831R DAQ. Each UUT will have a unique serial number and report generated. Therefore, I am using 2 unique sequence files created using TestStand. Basically, I want to be able to read in a barcode on the test fixture and have the operator interface load the 2 unique sequence files based on information contained in the barcode. The operator will then hit a button to start the sequence file executions.  I want the first sequence file to run and test the first UUT. Once the first sequence file is finished, I want the second sequence file to load and run on the second UUT.
I can use the simple operator interface to load both sequence files. I then have to select the combo box to select which one I want to run. This works fine, however, I am trying to automate this so that the operator doesn't have to open the files and continually use the combo box to select sequence files.
Any ideas or suggestions would be greatly appreciated.

I have figured out a solution (for my initial application at least) of programmatically loading the sequence files. When the operator interface first starts, there is a prompt where the user will scan a barcode that is loaded on the front of the fixture. For all of our product lines, we will have a unique format for the fixture barcode. Included in this barcode is a product specific software ID number. I create a folder with the same software ID number and store the sequence files there. I then parse the barcode and open all *.seq files in that folder. I have this working correctly now.
Once the sequence files are opened, the user must scan each UUT ID barcode before installing them on the fixture. The intent is to have both UUTs installed on the fixture at the same time so they can be tested serially.  If, however, they do not scan one of the UUTs, it will not be tested. Basically this is due to the fact that they may want to run only a single board. Once all of the UUT barcode scanning has been completed, I have another button that will execute the sequence files using the 'Single Pass' execution entry point. I agree that the 'Single Pass' and 'Test UUTs' points should be hidden from the user. Once the execute test(s) button is pressed, it will check each UUT barcode to make sure that it is valid. If both UUT's have valid barcodes, it will run the first UUT and then the second using the 2 sequence files that were previously loaded, otherwise, it will run only one or the other. The UUT(s) will then be removed and the process starts over again from the UUT ID barcode scanning. They will not have to scan the fixture barcode again since the correct sequence files have already been loaded.
Currently I have the UUT/Sequence File associations hard-coded in the UI. I will need to put my thinking cap on so that as we increase the product lines (several are already in the pipeline) we can use the same UI without any modifications. Scalability is King!

Can Not execute a TS Sequence File with VIs that are already being compile in my Custom TS Operator Interface

I have build a custom TS Operator Interface (Executable) with some custom VI(s)(GOOP VIs). I want to be able to call the same custom VI(s) from Teststand Sequences. When i try ti launch the sequence from my TS OI i got an error message, because LabVIEW Run Time find the same VI(s) from two different location : the OI and the sequence.
I would like to know, that is the best approach to resolve this problem.
For the moment i got two solutions :
(1) dynamically calling the VI(s) in the OI (executable)
(2)Changing the name of the VIs in the TS sequence.
I would like to know if it exist an another solution ?
thank you
derek

For the moment the VI�s that are shared between the sequencefile�s and the operator interface, are used as code module in the sequencefile�s (not as sub vi in the code module).
On the target system I will got my custom operator interface (which is build from the Testexec.llb + my goop VI�s). My goop VI�s are statically link to my operator interface.
(I will say that my executable are on the C drive : C:\Testexec.exe)
My sequencefile�s and the differents VI�s of each step is deploy with the TestStand deployment wizard. A library with all the vi�s call by the sequencefiles are group in SupportVIs.llb. (the sequencefiles and the VI�s library are on the C drive too)
For exemple I will say that I got a foo.vi (goop
method) which is build in the operator interface testexec.exe. The same foo.vi is call (as code module) by a step of one of my sequencefile�s.
When I try to launch the sequence with the operator interface, The LabVIEW Run Time inform me that he can�t load step "foo" of sequence �MainSequence� because he find 2 VI�s with the same name in 2 different location (C:\Testexec.exe\foo.vi) and (C:\SupportVIs.llb\foo.vi.
If you got a sample example, i will be glad to see it.
Thank you Ray for your help.
Derek

Send UI meassages from teststand sequence to Simple CVI Operator Interface with Asynchronous Timer

Hello,
Is it possible and how is it possible to send UI meassages from a teststand sequence to the Simple CVI Operator Interface with Asynchronous Timer which could be downloaded from NI Hompage. I use this problems because it is more stable than the standard OIs
regards samuel

This post could help:
http://forums.ni.com/ni/board/message?board.id=330&message.id=7567
Regards.

I just loaded the 8.1 operating system on my iPad. It has been sitting for about 4 hours with the black screen and white apple with the bar underneath. What should I do?

I am having trouble after loading the 8.1 operating system on my ipad.
My iPad is model A1397 EMC 2424
MEID ********
Serial DL******JHH
64GB
I started loading 8.1 about 5 hours ago and it is still sitting with the black screen with the progress bar underneath. It shows that it is almost done loading - just has a tiny bit of the progress bar left.
<Edited by Host>

I Don't know if this will work for anyone else but just FYI - after loading 8.1 on my iPad it froze for several hours on the black screen with white Apple and progress bar underneath. It would not do anything. I thought I was doomed. I accidentay left it sitting overnight without plugging it Back into the charger. I meant to but got sidetracked and thought it was plugged in. During the night the battery was totally drained so this morning my iPad was dead. I plugged it into the charger and after a few minutes the battery icon came up showing it was charging. I gave it about 30 minutes and then turned it on and the new operating system came up. It looks like it might be ok now. I can't say I recommend this, but it worked for me.

Sequence file path programmed in operator interface

Hello,
I do not want to load the sequence file with the button OPEN_FILE etc.. for example how it is done in th Simple Operator Interface. I want to programm the path and the sequence file name in the Operator Interface. How can I do this that the correct file will be loaded
regards
samuel

I try to explain what you have to do without an example, because it is realy simple, and so we have no version dependency ;-)
I used the "simple operator interface" installed with TestStand (..\National Instruments\TestStand 3.x\Operator\Interfaces\NI\Simple\LabVIEW\TestExec.llb\Simple OI - Top-Level.vi). I added the method mentioned above in front of the Event-Structure (See attached picture) and added a path-constant, to define which Sequence should be loaded automatically.
Try this out. It works fine on my machine (LabVIEW 8.2.1, TestStand 3.5, but should be independent of Versions as long as you have TestStand 3 and LabVIEW 7 at least).
Hope this helps!
André
Message Edited by Andre_Saller on 04-25-2007 11:34 AM
Attachments:
Autoload.jpg ‏167 KB

Customize NI Operator Interface!?

Hi
Im using Labview 8.5 Base and TestStand 4.0 Development System!
Now I want to deploy my teststand sequences to an other PC! I Want to use the Operator Interface from NI "C:\Program Files\National Instruments\TestStand 4.0\UserInterfaces\NI\Full-Featured\LabVIEW"! In this Operator Interface you can press "CTRL+F5" to execute the sequence! How is it possible to change the Keyboard-Command for execution to "F5"? I searched the "Load Top-Level VI.vi" for something like that but I didn't find anything!
I hope someone can help me!

Hi,
There are defined in an ini file in the \componenets\NI\language folder. I cannot remember the actual name of the file but you will see the obvious one when you look that folder.
You dont modify this file but put the Section key and the key with its new values in the CustomStrings.ini file in the User\language folder.
You dont need to add everything thats in the default file only the items that you want to change.
When TestStand launches it will use the values in the CustomStrings.ini instead of the default ini file.
Regards
Ray Farmer
Regards
Ray Farmer

How to force SequenceFileUnload callback to run from within operator interface

I need to force SequenceFileUnload callback to run from within operator interface arbitrary, with possibility to control execution flow.
I.e. discarding object handle of execution object, which has client sequence file, which has SequenceFileUnload callback, causes it(SequenceFileUnload callback) to run. Unfortunately, after discarding execution object handle, it can be used to control execution flow(pausing, aborting, terminating).

Thanks for the clarification. Here are the answers to your 3 questions:
1) You can programmatically run any sequence (including callbacks) by using the TestStand API Engine.NewExecution() method.
2) The Execution API object has several control methods for breaking, aborting, terminating, restarting, etc... All you need to do is obtain a reference to the Execution you want to perform one of these actions on and call the appropriate method on the reference. If you start the SequenceFileUnload callback with the Engine.NewExecution method, this returns a reference to the Execution object that you can call these methods on. If you don't use the NewExecution method, you can do a check in your UIMsg event handler for the StartExecution UIMsg event
for an execution starting that is running the SequenceFileUnload callback, and simply manipulate the Execution reference the UIMsg contains as you see fit.
3) To disable the SequenceFileUnload callback for a sequence file that is currently loaded. You can set the SequenceFile API object property "UnloadCallbackEnabled" to FALSE, and the callback will not execute for that file when it is unloaded unless you go back and reset the property to true before unloading. Note this property is reset each time you load the file.
For more information on the TestStand API objects, methods, and properties discussed in this post, refer to the TestStand Programmer Help accessed through the Sequence Editor's Help >> TestStand Programmer Help menu selection.
Jason F.
Applications Engineer
National Instruments
www.ni.com/ask

TestStand Error only when using Operator Interface

My testStand sequence runs correctly when I run it from the seqEditor, but when I run it from our Operator Interface (modified version of the simpleOI example), I get the following error,
"Error Message: Parameter 'Input Files': System Level Exception. [Error Code: -17502]
Input Files is a parameter of the LabView vi being called, and is an array of strings. The VI executes correctly even when called fromthe OI, but when it returns to TestStand (when called from the OI) the error occurs.
Thanks for any info and help on this. Also any info on why the simpleOI would cause an error would be appreciated too.

Hi Ray,
Here are some answers to your questions.
This VI that error's, is it part of the simpleOI or part of the Sequence File being run by the simpleOI?
---- The VI is part of a sequence file that is called by the OI.
If it is in a Sequence File, does this run in the default OI?
---- No, it's part of a new set of test sequences for our equipment.
What does the simpleIO do with the data contained in Input Files?
---- The data is just passed to another VI to load our input vectors.
What version's of TestStand and LabVIEW are you running.
---- I believe it's LV 8.5.1 and TestStand 4.0
What sort of modification have you done to the simpleOI example?
---- I think we only added our new sequences, a Operator info popup, and a few more buttons (Pass/Fail light, Change Op Info). And we removed some unused code to make it more simple.
Thanks again for your help.
Billy

Note: Due to heavy load, the latest workflow operation has been queued. It will attempt to resume at a later time

Dear all,
sorry for opening another thread on this.
I think I have a performance issue with workflows attached to document sets in SharePoint. And I say “I think” because people keep telling me that this is the way it just is.
The user creates a new document set, which triggers a workflow in which the user has to confirm/review/approve a series of tasks. The time it takes from clicking the OK button on those task form to the workflow status moving to the next step is about 4 seconds.
And visiting that status page within those 4 seconds brings up the infamous “Note: Due to heavy load, the latest workflow operation has been queued. It will attempt to resume at a later time.” message.
Hitting Refresh in the browser after those 4 seconds will make the new workflow status appear and the red text go away.
Is that normal? Is that the performance that everyone else is seeing as well?
I struggle to see why simply moving a workflow from one task to another should take that on a machine that isn’t doing anything else at the time.
(1)
I have a standalone (non-clustered) SharePoint box, 4 CPUs, 8 GB of memory, more than half of that available, acting as application server and wfe; only the database is on different box.
(2)
The CPU only goes up to 18 or 19%, so CPU does not seem to be the bottleneck. Half the RAM is also still free.
(3)
The workflow is designed with Nintex, and has about 9 flexi and review tasks – the last 2 of them in a loop iterating over typically 3 or 4 items.
(4)
Looking at the logs it looks like the processing in Nintex only takes about 1 second – I don’t know where the other 3 seconds are going.
(5)
There is nothing obvious in the logs.
(6)
We’ve looked at all the “theoretical” improvements around throttling and batch sizes etc. – none of them appeared make any difference. And the workflow is so small that it looks like my tasks gets executed straight away. The problem appears
to be that the execution takes too long(?) and therefore has not finished by the time the page get redrawn.
(7)
I am running perfmon and I can e.g. see one(!) workflow being loaded into memory – as expected as I am the only user.
(8)
I am seeing a total of 3(?) SQL queries being executed(?). I get the Bytes Sent/sec spiking at 25K, and Bytes received at 18K. But is this good or bad or a bottleneck?
Where do I take it from here?
I have been told that “[…] most customers have no issue with this as they are used to the way SP operates and it can be slow at times.” Is it really that bad?
If it is worth watching more performance counters then I’d need to know what to compare them to.
Is there something else I am missing?
Thanks
Martin

Hi,
Before considering an additional hardware try to change following configurations for workflow:
Increase Throttle Size
Increase Batch Size
Time Out
Workflow Timer Interval
AutoCleanUpDays
Increase Throttle Size
The Workflow throttle setting controls how many Workflows can be processing at any one time on the entire server farm. By increasing the throttle it will allow the number of Workflows execution or can be initiated at a time.
Use below PowerShell command to get the current Throttle Size:
Get-SPFarmConfig | Select WorkflowPostponeThreshold
Use below PowerShell command to set new Throttle Size:
Set-SPFarmConfig -WorkflowPostponeThreshold 100
Increase Batch Size
This is the size that determines number of events processed for a single Workflow instance. Default value is 100, but it can be range from 1 to any number.
Use below PowerShell command to get the current Batch Size:
Get-SPFarmConfig | Select WorkflowBatchSize
Use below PowerShell command to set new Batch Size:
Set-SPFarmConfig -WorkflowBatchSize 200
Time Out
This decides the time out of the Workflow event. The default value is 5 and can be any integer. The time is in minute.
Use below STSADM command to get the current Time Out value:
stsadm -o getproperty -pn workflow-eventdelivery-timeout
Use below STSADM command to get the current Time Out value:
stsadm -o setproperty -pn workflow-eventdelivery-timeout -pv “15″
Workflow Timer Interval
This setting is applicable at Web Application level and not the farm level. The workflow timer interval specifies how often the workflow SPTimer job fires to process pending workflow tasks. This interval also represents the granularity of delay timers within
your workflow. If a timer is set to delay for one minute, but the interval timer fires only every five minutes, the workflow delays for five minutes, not one minute.
Use below STSADM command to get the current Workflow Timer Interval value:
stsadm -o getproperty -pn job-workflow -url <Web Application Url>
Use below STSADM command to get the current Workflow Timer Interval value:
stsadm -o setproperty -pn job-workflow -pv “Every 10 minutes between 0 and 30″ -url <Web Application Url>
Here is the url for reference :
http://praveenkasireddy.wordpress.com/2013/06/14/workflow-due-to-heavy-load-the-latest-workflow-operation-has-been-queued-it-will-attempt-to-resume-at-a-later-time/

Due to heavy load, the latest workflow operation has been queued. It will attempt to resume at a later time.

I have SharePoint 2010 Enterprise running SP1. Configuration is one SharePoint server in the farm and a SQL 2008 R2 database for the backend. Our user environment is 80 users with very little load on the SharePoint server. I have the workflow timer
set to 1 minute.
I have a SPD workflow that starts manually on a form library. Whenever I publish a new version of the workflow, the next time I start the workflow it takes the full minute to finish. If I click on the workflow status before it finishes, I see the message
"Due to heavy load, the latest workflow operation has been queued. It will
attempt to resume at a later time.". After the minute completes the workflow finishes.
Here's the weird thing, the next time I start the workflow, it runs in a couple of seconds - almost instantly. I've tried up to 15 times after the inital publishing and everything seems to work fine on initiation.
Well, that would be fine for me, however, I intermintantly get this heavy load message during task processes that are running inside the workflow. It's probably less than 5% of the time. It's really frustrating though so I appreciate some help. I'm look
online and haven't found anything that describes my situation.
Thank you in advance!

Hi,
Before considering an additional hardware try to change following configurations for workflow:
Increase Throttle Size
Increase Batch Size
Time Out
Workflow Timer Interval
AutoCleanUpDays
Increase Throttle Size
The Workflow throttle setting controls how many Workflows can be processing at any one time on the entire server farm. By increasing the throttle it will allow the number of Workflows execution or can be initiated at a time.
Use below PowerShell command to get the current Throttle Size:
Get-SPFarmConfig |
Select WorkflowPostponeThreshold
Use below PowerShell command to set new Throttle Size:
Set-SPFarmConfig -WorkflowPostponeThreshold
100
Increase Batch Size
This is the size that determines number of events processed for a single Workflow instance. Default value is 100, but it can be range from 1 to any number.
Use below PowerShell command to get the current Batch Size:
Get-SPFarmConfig |
Select WorkflowBatchSize
Use below PowerShell command to set new Batch Size:
Set-SPFarmConfig -WorkflowBatchSize
200
Time Out
This decides the time out of the Workflow event. The default value is 5 and can be any integer. The time is in minute.
Use below STSADM command to get the current Time Out value:
stsadm -o getproperty -pn workflow-eventdelivery-timeout
Use below STSADM command to get the current Time Out value:
stsadm -o setproperty -pn workflow-eventdelivery-timeout -pv “15″
Workflow Timer Interval
This setting is applicable at Web Application level and not the farm level. The workflow timer interval specifies how often the workflow SPTimer job fires to process pending workflow tasks. This interval also represents the granularity of delay timers within
your workflow. If a timer is set to delay for one minute, but the interval timer fires only every five minutes, the workflow delays for five minutes, not one minute.
Use below STSADM command to get the current Workflow Timer Interval value:
stsadm -o getproperty -pn job-workflow -url <Web Application Url>
Use below STSADM command to get the current Workflow Timer Interval value:
stsadm -o setproperty -pn job-workflow -pv “Every 10 minutes between 0 and 30″ -url <Web Application Url>
Here is the url for reference :
http://praveenkasireddy.wordpress.com/2013/06/14/workflow-due-to-heavy-load-the-latest-workflow-operation-has-been-queued-it-will-attempt-to-resume-at-a-later-time/

Loading vi's with operator interface

Similar Messages

Maybe you are looking for