Try the Enum() expession function - it's mentinoed in the help topic you linked.
Hope this helps!
Trent
Try the Enum() expession function - it's mentinoed in the help topic you linked.
Hope this helps!
Trent
You can attach the CVI debugger (Run»Attach to Process) to Seqedit.exe or your operator interface.
Hope this helps!
Trent
Hello pwaszkewitz,
The property appears to be updated on the step, specifically <Step Type>.Substeps.<SubStep>.TS.SData.Call.Parms[x].Type. Can you verify that the substep actually works? If it does, this might just be a cosmetic issue.
To workaround this by specifying the parameter to be an Object and type is ActiveX Automation IDispatch Pointer or ActiveX Automation IUnknown Pointer?
I'd like to be able to set the bounds on my TS array of containers from Labview. I've done it before from CVI on a numeric array using TS_PropertySetDimensions.
I'm passing in SeqContext from TS and I'm using the AsPropertyObject Invoke Node to get a reference. This allows me to use a PropertyObject to set the values but I can't figure out how to set the bounds.
I see a SetNumElements Method but it doesn't have a lookup string to select the array.
I could probably initialize it then use the insert if missing property but I'd just prefer to set it to the size I already know.
Hi,
What we recommend to obtain the test time of a step or group of steps during an execution is the following: http://digital.ni.com/public.nsf/allkb/52933BCB633C8F28862576F0006BB959.
Please let us know if this is what you are looking for.
Hi Trent
thanks for your reply. I found that and still couldn't figure out what it wanted or how to make it work.
Locals.myFavoriteColor==Enum(Enum.Color,Enums.Color.light blue) still gives an unexpected token.
Locals.myFavoriteColor==Enum(Enum.Color,"Enums.Color.light blue") - could not find type ".
To me the whole point of the enum is to be able to type Enums. {Prompt for defined enum names...} . {prompt for value string}
So for the color example how to get it to work?
I'd recommend method 2 from that link, done within PreBatch and PostBatch callbacks you add to your sequence. Stored the time in a fileglobal instead of a local so that both callbacks can share the value.
Pictures...
use the get property object to get the reference to the array and then use the setnumelements on that?
The Enum() method is expecting a string for the first input as well, try:
Locals.myFavoriteColor=Enum("Color","light blue")
or
Locals.myFavoriteColor=Enum("Color",3)
I understand what you mean about the auto complete issue, and there is actually already a CAR (612847) in place improve the auto complete usability for enums.
Hope this helps!
Trent
Hello Community,
Using Teststand 2014 32bit
Using Labview 2015 SP1 32bit
I am trying to distinguish between multiple virtualbenches on different test stations. I made a VI that will select the present virtualbench connected to the computer (see attachment). The VI works great and I am able to give the present virtualbench a command, in my case a voltage from the power supply. However, I run into an error when trying to use my VI in Teststand (see attachment).
I inserted an action step in Teststand and called my VI. After receiving the error, I debugged my issue to the 3 system configuration VIs (Initialize Session, Find Hardware, and Close). Also, my code works fine when I use the Labview Adapter Configuration in Development System, but not in Run-Time Engine. However, the teststations only have Labview Run-Time Engine. How can I go about getting my VI to work in Teststand while having the Labview adapter set to Run-Time Engine?
Thanks a lot for your help Trent, at least I can progress now....
I tried Locals.myFavoriteColor == Enum(Enums.Color,"Dark Blue") Error is expected type String Found type (Enum) Color.
Locals.myFavoriteColor == Enum("Enums.Color","Dark Blue") also fails as cannot find type Enums.Color.....
Lets say its not that intutive and misses the point of autocomplete alltogether. Autocomplete is currently miss-leading users down the wrong path as well. I look forward to the CAR being completed.
How are you deploying these VI's to the test stations? Are you using TestStand Deployment utility, or just copying them over? TSDU can usually detect the kind of errors that will cause this.
Also, since all three of those VI's are nisyscfg, I would also make sure that you have the same version installed on the test stations. It installs automatically with several NI installers, or you can download it from Drivers and Updates.
Hope this helps!
Trent
Hello Trent,
It seems can't enter into the breakpoint set in activex project.
what I do are below steps:
1. in cvi,attach the seqedit process.
2. build and run activeX project in cvi.
3. run seq in teststand
attached my code,pls change the file extention from .doc to .rar.
When I try to run a step created with the StepType showing the empty types where TS:: PropertyObject should be, it fails with the following error:
Error message: -17313: Object interface of argument expression 'Step.HdvpInterface.ControlOutputs' is incompatible with parameter. Expected , found TS:ropertyObject
I can however edit the interface of the step after insertion, change the empty types to TS:: PropertyObject and then execute the step correctly.
So I think it is not cosmetic, it actually does not work (or I am missing some trick), but with an Edit substep that fills in the missing types etc. it should work.
Thanks
Peter
Peter,
reading your reply, i think the easiest short term solution would be to add an OnNewStep substep module which automatically fills in that paramenter type entry. Using this, you can provide a working custom step type immediatly and do not require any rework of the DLL.
Hi,
I'm trying to create sequences that will open my company control software and read and write to the control software. I'm fairly new to TestStand and I can't figure out how to get started with this task.
For example, I would like TestStand to change modes of the software, input data and retreive data from the software, etc. How would I go about doing this?
Thanks, Jon
Jon,
what control software are you talking about? SAP?
TestStand most likely cannot directly interact with that software. I recommend you to really dig into TestStand and learn how to implement custom step types (for something like property loader) and custom report plugins (writing test results back to the 'control software').
Hi Norbert,
No, the control software is not SAP. It's basically a GUI for a NI I/O controller programmed in labview. What would custom step types and custom report plugins do?
Thanks,
Jon
If the 'control application' is custom implemented, i hope you have information about the API.
If so, you can create modules which use the API to communicate with that software and call these from TS.
Custom step type is useful to provide general (company standardized) functionality for sequence developers.
Custom report plugin is used to write test results to a proprietary format like custom file formats (e.g. Excel) or conrol external applications for passing data.