Hi juanfer23,
Could you use a Property Loader Step instead?
You will find an example here:
C:\Users\Public\Documents\National Instruments\TestStand 2017 (32-bit)\Examples\Built-In Step Types\Property Loader Step Type
Unfortunately, I have not found anything related with the error you have faced.
Let me know if the Property Loader Step works for you.
Have a nice Wednesday!
Hello all,
I am trying to programmatically enable a button on my user interface when the Post Batch sub sequence has finished executing from the Batch Model.seq.
Originally I thought of adding a custom UI message and then programmatically enabling the button when that custom UI message is sent however I would rather not add this extra dependency.
Is there any way of checking if the Post Batch sub sequence has finished using the already supplied UI messages from TestStand?
Any suggestions would be most appreciated.
This is being added in TestStand 2017 SP1, which will release in the next few weeks. You'll be able to use the standard ‘//’ prefix to denote a comment, which will be ignored by property loader.
-Trent
Thanks, looks like I'll have to plan on upgrading then!
Adam
For now you can still use comments outside of the <PropertyGroup> tag, but i see how that's not ideal for requirements tracking.
Hi
I would like to find out how I could implement some buttons within my sequence. I am taking a measurement, if that measurement fails I want the user to be prompted to either 'continue through the sequence' or 'repeat the step' or 'terminate the sequence'.
I have set up my 'if statement' and the three button options 'continue', 'repeat' and terminate', now I need some help to discover how to execute the buttons to do what is mentioned above.
Thanks
Howdy Curt,
I'd take a look at the documentation below for how to alter the report file path with expressions.
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019RwESAU&l=en-US
Hi Jackwat,
Thanks for reaching out. Could you give a little bit more context to your problem?
1) Did you update from Windows 7 to Windows 10?
2) Are you getting any error code or crash error message?
3) What version of TestStand and what versions are your drivers?
Thanks, hopefully this can give more insight onto your situation and what you are experiencing.
Hello,
Why are you trying to disable the sequence analyzer programatically? You can have the analyzer disabled and simply manually analyze by clicking the analyze option.
Best,
Ben
I have custom User Interface instead of TS interface.
Hi again,
I think I understand your situation.
It is true what you say, that overriding a callback from the process model affects all test sequences using that said process model. Therefore, if you were to edit a callback from the process model you must also edit the corresponding model callbacks in all the test sequences already existing.
In your situation you can either edit the callback in the process model, which inevitably requires you to correct the corresponding model callbacks in your affected test sequences; or you can edit the model callbacks in your test sequences directly. The work load is similar. However, the best option depends whether or not this new feature of the callback will be the new default. If you plan to have this as a new default behavior for future test sequences, you should make the edit in the process model. But if this behavior is test sequence specific I suggest you edit the model callbacks for the relevant test sequences only.
Generally, if one would like to edit/customize the process model itself, this is best done before one even starts developing any test sequences. Otherwise one could eventually end up in a situation similar to yours, where if one decides to change the process model in the middle of the development process, all the existing test sequences have to be edited manually.
Note, if you ever plan to make a custom process model, add and work with a copy of the pre-existing ones (sequential, batch, parallel) instead of overwriting them. This is to avoid the risk of needing to reinstall TestStand in case something goes wrong.
Best regards,
// Marcus Bengths
Hi,
I think a possible approach would be to use a model callback. This KnowledgeBase article includes some useful steps to get you started:
Programmatically Abort Execution upon Step Failure
Best regards,
// Marcus Bengths
Hi Marcus
The article is useful for terminating on each failure. Please see attached, I want to implement these button for one step in my sequence and they should execute depending on what the user selects.
Thanks
Hi run321,
is this still actual topic? I see it was added some time ago.
Let us know, therefore we will try to help 
Regards,
Hi,
In the list of available pre-defined UI messages I found UIMsg_ModelState_TestingComplete. It is sent when the MainSequence returns control to the process model. In case of a Batch Model, I interpret it to be sent after every test socket is finished, i.e. when the postBatch callback executes.
I suggest you give it a try.
See UIMessageCodes Enumeration for more details.
Cheers!
//Marcus Bengths
Hi Exle,
Do you still experience challenge with logging additional values and creating your own schema?
Did you have a chance to see this tutorial, instead of the one you were linking in your post?
http://www.ni.com/tutorial/14595/en/
Hope this helps!
Regards,
Hi Patrik,
thanks for your message. No the topic is not really an actual one any more.
After a lot of discussions we decided to use separate Testsand instances rather than the parallel model.
There was still a lot to do (to change) to enshure that
- with the wrapper the HW Adress is needed only once (for the whole sequence of tests)
- without the wrapper the HW Adress GUI starts in each single test
- with the wrapper if a test is interrupted there is a retry
- every single Test is a new Execution with it's own report
....
So thanks for your offer
Best regards
Matthias
Hi Matthias,
I believe you would be able to achieve your results with parallel process model as well, however as you wrote in the title - if it's about reducing maintenance effor, this could be a better way.
Thanks for reply and good luck with implementing every feature in your test sequences.
In case of any hesitation, feel free to reach this beautiful NI community
Regards,
Hi Bilalm,
I might not be understanding this correctly, but it sounds like you just want to programmatically know which button the operator selected? If so, then Step.Result.ButtonHit will have a numeric value representing the button selected by the operator. Set a local variable to this value, and use the local value in your IF/ELSEIF/ELSE statement.
I hope this helps.
-Jack
Object: I want to update custom controls on the parallel UUT Dialog from a LabVIEW module.
Overview: I have a simple TestStand sequence using the Parallel Process Model, and modified the UUT Information Dialog in CVI to graph the values of the UUT during the test. I have successfully added custom controls and can even modify the values of the custom control calling my custom function in the modelsupport2.dll with the C/C++ module.
I have validated that the same values are being passed to my LabVIEW VI and my call to the modelsupport2.dll. I am assuming that it has to do something with TestStand loading the modelsupport2.dll into memory and therefore it works calling the dll from TestStand but not LabVIEW.
The custom function currently takes only 2 parameters (int panelId, int testSocketIndex), and I am calling the same dll and function.
Question: How to I call the modelsupport2.dll within LabVIEW to update the the UUT Information Dialog?
Thanks in advance
Matthew
