TestStand 3.1 Run Selected Steps generates Visa error -1073807346?

When using Run Selected Step in TestStand 3.1 to interactively execute previous steps in a sequence a Visa error (-1073807346 The given session or object reference is invalid.) is generated even though the selected step has previously executed with no errors.
Some history:
The sequence in question was developed with TestStand 2.0 and LabView 6.1 and does not exhibit the above mentioned issue. The error began after migration to TestStand 3.1 and LabView 7.1. The sequence executes without errors in all other conditions.

Hi,
When your sequence halts, does that mean it's closed the visa sessions and if so when running the selected steps are you running the setup with the open visa sessions or are you just reusing the sessions stored in the Station Globals (I assuming when you said globals you were referring to Station Globals).
Regards
Ray Farmer
Regards
Ray Farmer

Similar Messages

Error -17300 is generated when running selected step

Error -17300 is generated when running selected step (with ot without process model).
Using TestStand 2.0.1f1
See BMP file for error dialog.
I was trying out the example in the Resource Library - TestStand | Process Models | Running Selected Steps via Execution Entry Point -Test UUTs or Single Pass
(link http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3E2B756A4E034080020E74861&p_node=DZ52222&p_source=external ). This example is a 1.0.1 example but the web page does say that it should work in 2.0.x
I followed the readme file to use from "Execute" menu:
I have attached the resulant SequentialModel.seq file.
The modifications to the SequentialModel.seq file appears to wo
rk, but when I tried to run 'Run Selected Steps Using' menu item. I got the error message -17300 displayed. (see ErrorScr.bmp attached). The only way to close the execution was to launch Task manager and 'End Task'.
I have attached a small demo sequencefile.
To try example:
Move the SequentialModel.seq to 'C:\TestStand\Components\User\Models\TestStandModels'.
Launch TestStand Sequence Editor and open 'Debug Example1.seq'.
This is how to generate error condition-
1. Run the sequence file from menu Item Execute | Single Pass. You should get a full run with test result, it fails but that doesn't matter.
2. Select Steps 1 and 3 in Main of MainSequence. Run Selected Steps using Single Pass. Again sequence executes correctly.
3. Now run the same selected steps using the new menu item Execute | Selected Test(s). Again the sequence executes again.
4. With Steps 1 and 3 still selected. Run Selected Steps using Single Pass (as in 2 above). This time the error -17300 will be gener
ated.
I also tried running the sequence first doing step 1 (as above), then step 3, then repeating step 1 and this was ok. So the problem appears to be in interactive only.
Any clues as to whats going on and how to resolve it.
Regards
Ray Farmer
Regards
Ray Farmer
Attachments:
SequentialModel.seq ‏174 KB
Debug_Example1.seq ‏19 KB
ErrorScr.bmp ‏915 KB

Hi,
TestStand 2.0.1f1
Attached is a SequentialModel.seq that will run selected steps in a new execution using the process model. (It started life based on the inital
demo example)
When either Test UUT's or Single Pass is selected a check is made to determine if there is an initial selection.
If there isn't then the normal Test UUT's or Single Pass sequence is run.
If there is then a new sequence file is created with a new MainSequence. The selected steps are cloned and inserted to the new MainSequence. Also
the Setup and Cleanup groups are also cloned. Likewise the FileGlobal Defaults are copied to the FileGlobals of the new Sequencefile and also the
Locals.
Any Sequences contained in the SequenceFile are cloned to the new sequencefile (except the MainSequence, SequenceFileLoad and SequenceFileUnLoad).
In addition, as the Steps are cloned any break point are also set in the new sequence file.
The new sequence file is executed in a new execution using the process model entry point with the break on first step controlled from the menu
option.
One thing I am assuming is that there is only one element in the RunState.InitialSelection.SelectedSequences array.
Question: Under what circumstances will there be more than one selected sequence?
I had one problem, I tried my SequentialModel.seq with the demo auto.seq. This contains the SequenceFileLoad and SequenceFileUnload.
When I run this demo with a few steps selected, it run ok but when I closed the results window the UnloadFile callback was executed.
I found an option that can be set with the Engine.ReleaseSequenceFileEx which should have stopped the UnloadFile callback from running. But it
made no difference.
I then came across SequenceFile.UnloadCallbackEnabled() and using this function it did disable the Unload callback and this worked.
Question: So, Why didn't setting the Option in the Engine.ReleaseSequenceFileEx work?
Limitation using this SequentialModel.seq,
1) Any precondition to a step's execution based on the result of an early steps are not check when cloning the selected steps. Therefore this has
to be done manually when making the selection.
2) All Sequences in the SequenceFile are cloned to the new sequencfile. (May not be a problem when SequenceFile contains only a few sequences.)
3) The selections are limited to the MainSequence. If steps are selected in a Subsequence then these would be copied to a new MainSequence and
this would be run. Providing this doesn't require any parameters passed from the original caller then this should still run. The problem will
arise if parameters are required.
4) This is not really a limitation - If a full run of the SequenceFile using Test UUT's or Single Pass is required then the user must ensure no
steps are selected.
What I whould like to happen is the ability to make a selection in SubSequence calls either one or two levels down from the MainSequence. The new
execution setup would contain those steps in the MainSequence that are required to call those selected steps in the lower levels.
Would welcome any comments on my SequentialModel.seq attached and answers to my questions.
Regards
Ray Farmer
Regards
Ray Farmer
Attachments:
SequentialModel.seq ‏233 KB

In LabVIEW OI the Run Selected Step Using Test UUTs does not work

TestStand LabVIEW Operator Interface (old style) - TestStand Version 2.0.1 & 3.0
The Interactive option was enabled for the Process Model Entry Point - Test UUTs in the SequentialModel.seq.
When selective steps were selected to run within the LV OI using the menu item 'Run Selected Step Using - Test UUTs' it was found not to work.
The reason for it not working was because the main event string was "Run Selected Step 0" but this isn't available in the case statement. Changing the "Run Selected Step 1".."Run Selected Step 9999" to "Run Selected Step 0".. didn't produced the desired result. Instead of the selected steps running using the entry point Test UUTs, the steps ran without the process model.
The Case Statement string was retored back to "Run Selected Step 1".
The changes that are required to make the "Run Selected Step 1".."Run Selected Step 9999" work with either of the Entry Points are as follow.
In the VI TestStand - Create Entry Point Menus for Interactive Exec.vi
Insert an Increment from the iteration terminal of the FOR loop. This ensures the Message Queue string generated is in the range 1 - 9999 not 0 - 9999.
In the TestStand - Sequence Display.vi
For the Main Message Event "Run Selected Steps", "Run Selected Step 1".."Run Selected Step 9999"
In the case "1, Default", decrement the input 'Entry Point Index' to the VI TestStand - Start Interactive Entry Point Execution.vi. This ensures the Entry Point Index starts from the value 0.
Now when the selected steps are run using a Pocess Model Entry Point, they run correctly.
This problem only appears to affect the LabVIEW Operator Interface and only the old style. The new style that comes with TestStand 3.0 runs correctly.
There is one other problem. When an Operator is logged in to TestStand, the Entry Point - 'Single Pass' is disabled. But this is not reflected to the menu item 'Run Selected Step Using'. Both 'Test UUTs' and 'Single Pass' are available to the operator.
The reason for this is because in the VI 'TestStand - Create Entry Point Menus for Interactive Exec.vi' the sub menu item is enabled as a result from the property Sequence.AllowInteractiveExecutionOfEntryPoint. This is not enough to disable the 'Single Pass'. The Engine.CurrentUserHasPrivilege needs to be checked as well. Which means modications to the VI 'TestStand - Create Entry Point Menus for Interactive Exec.vi'.
Hope is maybe of help to anyone that may need to use this option.
Regards
Ray Farmer
Regards
Ray Farmer
Attachments:
In_Labview_OI_-_Run_Selected_Steps_Using_Test_UUTs_doesnt_work.txt ‏3 KB

Thanks Ray for the "heads-up". )
I am about to implement a vi which calls TestStand functions. This vi will allow to select tests and permits test re-entry (loops) if the user has supervisor privileges.
I will consider what you recommend in this string.
I will also provide feedback on this thread if I discover anything .... let's say "unusual"..
On another note, I am using TestStand 3.0 I have not observed any problems when running selected steps or run selected steps using single pass. I have also within TestStand set privileges for certain Operators to do the same. They have not reported any problems.
Thanks,
JLV

Display Step.Result.ReportText direct in the LabView OI after using "Run selected Steps"

I took the (full-featured) LabView OI and modified it to my needs.
Now the problem:
I only have sequences with LabView Action Steps. Those Steps (VIs) all have a Cluster Output "Test Data"
Now i would like to display one element of that Output Cluster (Step.Result.ReportText) direct on the OI after using "run selected steps"
It would be ok, when the Result would display after every step (also in UUT/Single Pass) but most important, after Run Selected Steps.
How can i connect the Output of the step with an element on the LabView OI?
(sorry for my bad english)

RNiklaus wrote:
I took the (full-featured) LabView OI and modified it to my needs.
Now the problem:
I only have sequences with LabView Action Steps. Those Steps (VIs) all have a Cluster Output "Test Data"
Now i would like to display one element of that Output Cluster (Step.Result.ReportText) direct on the OI after using "run selected steps"
It would be ok, when the Result would display after every step (also in UUT/Single Pass) but most important, after Run Selected Steps.
How can i connect the Output of the step with an element on the LabView OI?
(sorry for my bad english)
Is the "Run Selected Steps Using Single Pass" feature not sufficient for your use case? That feature will run the selected steps along with result processing to generate a report for those steps.
-Doug

Which case in LV Oper. Intf. will do "Run Selected Steps using single pass" for me?

I added a button to simulate "Run Selected Steps", but I really want a button that will "Run Selected Steps Using Single Pass". Which case in the Complex Labview Operator Interface does this for me? What I really want is the report to be generated which happens when I use "Run Selected Steps Using Single Pass" but no report when I select "Run Selected Steps".
Thanks!

I figured out how to make this work. Instead of calling the Sequence File View Manager ConnectCommand method using the Run Selected Steps button and the CommandKind_RunSelectedSteps command kind, you use the CommandKind_RunSelectedStepsUsingEntryPoints_Set command kind. The tricky part is that before you can use the ConnectCommand method with the CommandKind_RunSelectedStepsUsingEntryPoints_Set command kind, you have to create a set of new commands. Do this by first invoking the Application Manager method NewCommands. This method returns an empty set of commands. You must then add a new command to that set. Do this by invoking the InsertKind method on the empty set of commands using CommandKind_RunEntryPointOnSelectedSteps for cmdKind, Sequence File View Manager for managerControl, -1 for insertBefore, and empty strings for currentMenuName and allMenuNames parameters. Once you have made these calls, then you can call the Sequence File View Manager ConnectCommand method using the CommandKind_RunSelectedStepsUsingEntryPoints_Set command kind.
The previous instructions work just the same for the Loop On Selected Steps button. Just substitute the CommandKind_RunEntryPointOnSelectedSteps and CommandKind_RunSelectedStepsUsingEntryPoints_Set command kind constants with CommandKind_LoopEntryPointOnSelectedSteps and CommandKind_LoopOnSelectedStepsUsingEntryPoints_Set command kinds (and of course use the Loop On Selected Steps button reference instead of the Run on Selected Steps button reference when invoking the ConnectCommand method).
There is one mystery with this solution that I haven't figured out yet, besides the fact that it is so laborious and non-intuitive to me (but at least it works). Nowhere in any of the calls detailed above did I ever see a parameter to specify which execution entry point to use. I am using the default sequential model entry points Test UUTs and Single Pass. Typically you specify which entry point you want to use (such as when invoking the ConnectCommand method) in the form of an index to a set of entry points where the Test UUTs entry point corresponds to a set index of 0 and Single Pass corresponds to a set index of 1. How did the previous calls determine which entry point to use when I didn't specify anywhere which one to use? Do this just work because you can only run or loop on selected steps using no process model or the Single Pass entry point?

While run "Program - Run Financial Statement Generator" occurs errors? why

while running "Program - Run Financial Statement Generator" occurs errors?
Program - Publish FSG Report
output:
The concurrent request ID of your FSG request is 309112.
The concurrent request ID of your XML Report Publisher request is 309113.
hawk_BS_IFRS PC by month (PL) (Financial Statement Generator)
can output good format xml
but
Program - Run Financial Statement Generator
the phase: Completed and
the status: Error
anybody can give me some sugguestion?

hello, I have known why.
because my xml publisher's version is 5.6.1. it's not afford it .
you can refer to metalink.
and it's not problem in 5.6

When trying to test my serial port instrument I receive Visa error 1073807346, which means that they is not enough information for Visa to access or resource does not exist.

The error I am getting is on Visa open.

I found couple of knowledge base (KB) entries that talk about Visa error 1073807346. The best way to find knowledge bases (KB) is to goto ni.com >> Support >> Advanced Search (option 3) >> type in the keywords in the box "1073807346", you will get them.
Also refer, http://www.ni.com/support/labview/visa/default.htm. Hope this helps.

Visa error 1073807346

I?m new on LabView and create an application that uses a power meter, everything works fine during 127 tests but after this I get the following error message :
- Error ? 1073807346 Occurred at VISA Write in ?
- Error Query VI -> ???.
Posible reasons:
VISA: ( Hex 0xBFFF000E ) the given session object reference is invalid.
Why is that the system works fine during 127 iterations ?
Is there any buffer or something that maybe is getting overload ?
I hope somebody can help me.

Hello,
The open VISA is not exactly in a loop, because it?s in a VI that opens twice on each test but when is open then the VISA session open only is called once and the loop is for the measure, because the meter is accessed X number of times but the VISA session is closed only after all the measures have been made I think this works as you mentioned, then is not really inside the loop, I couldn't send you the Spy capture file the system indicates an error, the file is about 1.2 Mb for one run, I only capture one because the systems run very slowly when the NI Spy is running then it will take a lot of time and a very large file to reach the 127 tests, I think the file is big because the meter it?s not the only instrument
that I?m accessing, I?m using a generator and a power supply during the same test.
Let me know if there is another way to send you the file.
BCU

How can I run a step only if TestStand not is terminated?

I want to run a step I Cleanup only if TestStand not is terminated. Is there a variable I can read who tell this?

Jan Inge -
I did not know whar version of TS you are using so I created the sequence using TS 2.0.
In the example a save the state to the numeric result of a numeric limit step and the step determines that execution is normal if the state is 1, so the step passes, otherwise it fails. The precondition of the next steps use the pass/fail status of the first step. This way you do not need a local variable.
Scott Richardson (NI)
Scott Richardson
National Instruments
Attachments:
CleanupStepNotRunDuringTermination.seq ‏30 KB

How to run selected sequences/steps after the great-grandparent, the grandparent and the parent sequence ?

Hi,
I developped a sequence file with many levels of interlinked subsequences, and I want to be able to run selected subsequences/steps after the great-grandparent, the grandparent and the parent sequence.
Anyone know the best method to do this ?

Indeed, there was an little error in the sequence file. You can find the corrected file in attachment.
Run the selected step "Grandparent 2" doesn't do what I require because this run all sequences under "Grandparent 2", while I want to run "Parent 2.2" and "Child 2.2.2" under "Grandparent 2".
Attachments:
sample.seq ‏10 KB

Loop on selected steps using entry point set in LabVIEW OI

Hello All,
I have an Operator Interface where the operator has the ability to select particular steps and loop on selected steps as required.
Everything works as intended but the customer would like to supress the default Loop configuration pop-up box.
The loop parameters needs to set programmatically (not by the user). I figured out how to build the interactive arguments but not sure how to pass this.
Any ideas / suggestions would be greatly appreciated.
Thanks in advance.
regards,
SS
Solved!
Go to Solution.

Hi,
My name is Mark and I'm an Applications Engineer at National Instruments.
I have looked at your issue and it seems that you are on the right track here. Your code snippet seems to generate valid data and in order to avoid the "Loop on Selected Steps" dialog you simply need to feed the "BuildInteractiveArgs" output from your example to the "interactiveArgsVal" input on an invoke node with a method named "Loop on Selected Steps" (see picture below). Once this has been done, TestStand will receive all the data needed and the pop-up box will not be shown.
Hope this helps.
I will look forward to your reply.
Mark N
Applications Engineer
National Instruments UK & Ireland

Unable to load LabVIEW VI into TestStand using LV Run Time only

I'm unable to load some of my VIs into TestStand from LabVIEW. I am using:
TestStand 4.2.1
LabVIEW 2010
I have the appropriate patches installed for both TestStand and LabVIEW, and I still get the error.
Attached is a message that I get when I hover over the "!" to explain my error. The VI has the "Simple Error Handler.vi" as part of the build, and when I eliminate this VI from my VI, TestStand then loads correctly.
Thanks,
Eric
Solved!
Go to Solution.
Attachments:
TestStand_LoadError_Hover.png ‏16 KB

This fixed my issue as well. Thank you for posting this. I have repaired LabVIEW 2010 sp1, LabVIEW FPGA, LabVIEW RT, DAQmx, and VISA 5.0. These are not small programs to do repairs on. Even after doing all of these repairs I still had issues with just labview coming up.
Just by clicking on my lv shortcut to run the labview.exe I would get a loading screen for gws_int.vi This was before opening any projects or VI's. Labview was having many issues. Once the loading vi screen went away the standard labview 2010 startup page was present. But this page was dysfunctional. For example if you clicked tools and then options it would just totally crash LabVIEW, no error message or warning.
Many people are suggesting to mass compile to fix this, but that is not an option. If you went to tools>advance>mass compile the same loading vi screen would come up (pic A), but then the mass compile program would have a broken arrow (pic b) I included a image to show people this.
The error list will always pop up, but there are no errors.
I called NI tech support and they suggested that I repair all of my programs starting with the largest programs first. During the repairs I found this forum. I have over 30 different NI modules installed on this machine, I would have been at this for the next two days.
Thank you very much for this.
A good question is why didn't the repairs of these large programs find this, and would any repair of any module have fixed this?
Attachments:
b.png ‏116 KB
a.png ‏46 KB

Windows 7 is Error reporting when running a program generated with in Labview LV 7.1!

Dear Labviewer's
Once back in the yaers I'd generated a program with - Labview 7.1.
Now I'm informed that the version LV 7.1 is not supported by Windows 7.
Now when i try to run the Program generated by Labview 7.1. in windows 7 , I get communication error by the serial port.
Is there somehow somthing I can do to get this work. Is there any Runtime engines From NI for Windows 7.?
Please Feed back if anyone got info for help.
4 Stars ...
HFZ
Solved!
Go to Solution.

Have you installed a newer version of the NI-VISA runtime engine that will work with Windows 7?
The most recent on the NI website appears to be version 5.0.3.
http://joule.ni.com/nidu/cds/view/p/id/2257/lang/en

Teststand 4.0 IVI-DMM Step error

I have Teststand 3.5 and 4.0 installed on a computer and a NI-4060 in a PXI chassis. When I try running a sequence that has an IVI-DMM step in it in 3.5 everything runs fine. When I try the same sequence opened in 4.0 it gives me the following attached error (both attachments are the same error one is just scrolled down so you can see the whole thing.) I have tried adding a simple IVI step from scratch in teststand 4.0 and I get the same error.
Any ideas?
Brian
Attachments:
untitled1.JPG ‏107 KB
untitled2.JPG ‏106 KB

Ok, I used the version selector, went back to 3.5, and ran the sequence and it ran fine like I expected. When I switch back to 4.0 and ran it it worked (first time in a dozen tries.) So I switched back to 3.5 ran it and then ran it 4.0 again and it failed. I attached a spy capture from 3.5, 4.0 worked, and 4.0 didnt work.
Brian
Attachments:
DMMConfig_TS40_Capture_Didnt_Work.spy ‏1 KB
DMMConfig_TS35_Capture.spy ‏11 KB
DMMConfig_TS40_Capture_Worked.spy ‏12 KB

Select query generating redo

Hi
I am trying to run a select query in a database which has performance problems and I get the following stats
recursive calls     47
db block gets     0
consistent gets     36909
physical reads     203
redo size     205164
bytes sent via SQL*Net to client     1873
bytes received via SQL*Net from client     1716
SQL*Net roundtrips to/from client     4
sorts (memory)     2
sorts (disk)     0
I get a lot of consistent gets and redo size compare to the same query run on a good performing db(results below). Why should a select query generate a lot of redo? Can some one suggest me where should I be looking at to resolve this issue?
Thanks
recursive calls     47
db block gets     0
consistent gets     3470
physical reads     0
redo size     0
bytes sent via SQL*Net to client     1885
bytes received via SQL*Net from client     1725
SQL*Net roundtrips to/from client     5
sorts (memory)     2
sorts (disk)     0
Edited by: APV on Nov 18, 2008 1:08 PM

Queries can also generate redo if auditing is enabled. If you don't have auditing enabled and you find that a SELECT statement with no FOR UPDATE clause sometimes generates redo entries, you might be witnessing a case of delayed block cleanout

TestStand 3.1 Run Selected Steps generates Visa error -1073807346?

Similar Messages

Maybe you are looking for