Programmatically Insert ActiveX/COM Step Using LabVIEW

Hi,
I would like to be able to create sequences like the one attached, using LabVIEW.
This sequence has only 2 steps, a LabVIEW VI call, and an ActiveX/COM Adapter Call.
I have been able to do this using an adaptation of the code here: https://decibel.ni.com/content/docs/DOC-36337
However, I am struggling to add the ActiveX/COM step.
Any help would be gratefully received.
Thanks,
Dan
CLD
Solved!
Go to Solution.
Attachments:
Valve Control - Test 1.seq ‏6 KB

Obviously there is a way if you look for it
Since you have an existing object of the "Step" class you can also get a "Module" object for it. Afterwards you have to specify that this is an ActiveX module. If you do not know that - probably you need to get it from the "Adapter" object somehow... Our case is simplier, so you just cast it to the ActiveX module and ... set some properties like ServerId, ActiveXReferenceExpr and so on.
I have attached an example for you. Interesting thing is the ServerId - I have just read this chain from the TS for similar step and reused it here so don't ask me how to obtain it automatically
You still have to fill your "Properties" like "file" - but I will graciously leave this job for you =
Best Regards,
CLA, CTD, CLED @ Test & Measurements Solutions Poland
Attachments:
ActiveX Step_2.vi ‏24 KB

Similar Messages

Programmatically modify ActiveX/COM-step module settings

Would like to modify programmatically ActiveX/COM-step module settings (Automation Server, Object reference, Object class, method/property, parameters-list).
Can't find this in context. How this can be modified?
Thanks!
Solved!
Go to Solution.

Hey bestware,
You need to get a reference to the step: RunState.Sequence.Main["MyActiveXStep"]
Then you can use that to convert to the ActiveX module: RunState.Sequence.Main["MyActiveXStep"].Module.AsActiveXModule
Once you have that you can do whatever you'd like with it. You can read in the help more about this. Search for ActiveXModule.
You sould see all sorts of properties: MemberType, MemberName, ServerID, ActiveXReferenceExpr. If you read about them they are refering to the different things you want to set. For instance the ActiveXReferenceExpr is where you store the Object Reference. The MemberType is Call Method (1), Get Property(2), Set Property(4) or Don't Call(-1), etc...
So to change the step to be a Get Property step I would do this:
RunState.Sequence.Main["MyActiveXStep"].Module.AsActiveXModule.MemberType = 2
To store an Object Reference to Locals.MyObj I would do this:
RunState.Sequence.Main["MyActiveXStep"].Module.AsActiveXModule.ActiveXReferenceExpr = "Locals.MyObj"
Hope this gets you pointed in the right direction.
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Create Teststand 3.5 SequenceCall Step use Labview 8.2

Dear ALL:
I want use Labview 8.2 to create a sequence Call Step,and I know I must get the SequenceCall Module first.In Teststand 3.5 I can use NI Teststand Adapter API 3.5(Ver 1.0) to get the SequenceCall Module,But In Labview 8.2 I can not access to NI Teststand Adapter API 3.5(Ver 1.0),Because when I Select NI Teststand Adapter API 3.5(Ver 1.0) in "select object from Type Library"(See 1.bmp),It the same as the NI Teststand API 3.5(Ver 1.0),and I can not find SequenceCall Module.
I think this is the compatible probelm with labview 8.2 and teststand 3.5. When I use Labview 7.1, I can normally select NI Teststand Adapter API 3.5(Ver 1.0).
Attachments:
11.jpg ‏34 KB

yiweihua2002,
You didn't say if you were using LabVIEW 8.2 or 8.2.1, so I'm not sure if this truely reproduces your behavior.
However, I just ran LabVIEW 8.2.1 and selected the adapter API, and I was able to see all of the items.
There are a few things I'd like you to try:
1) Run the TestStand Version Selector and make version 3.5 active. Even if it is already the active version, this will re-register all of the TestStand components to make sure they are properly working
2) Restart LabVIEW (if you haven't already)
Josh W.
Certified TestStand Architect
Formerly blue
Attachments:
adapter.gif ‏18 KB

No longer able to insert ActiveX controls or use existing ActiveX controls in Word documents

Using Word 2010 32bit on Windows 7.1 64bit OS.
I have a document with several ActiveX controls that I use as a template to generate new documents. This morning I installed the monthly roll-out of Windows/MS Office updates and then rebooted. After rebooting, when I opened my Word document,
I could not use the controls.
As far as I can tell, the controls are not disabled in security but are actually not recognized. If I go into Developer Mode and open the Properties from the context menu on one of the ActiveX controls, the Properties dialog opens but shows properties
for the main document and not for the control. If I try to drop a new ActiveX control in a blank document, I get the following message from Microsoft Word: "The program used to create this object is Forms. That program is either not installed
on your computer or it is not responding. To edit this object, install Forms or ensure that any dialog boxes in Forms are closed." I have not been able to find any information on a program called "Forms". Is this some component
of Word that has been corrupted?
I don't think there is any problem with the actual document because I can still open and use it on another machine running Word 2010 (where the latest updates have not been installed).

Among the monthly updates for March 2015 is a series of updates that should correct the problem. Use Windows Update to get them.
The relevant updates are:
Word 2007: http://support.microsoft.com/KB/2956109
Excel 2007: http://support.microsoft.com/KB/2956103
PowerPoint 2007: http://support.microsoft.com/KB/2899580
Word 2010: http://support.microsoft.com/KB/2956139
Excel 2010: http://support.microsoft.com/KB/2956142
PowerPoint 2010: http://support.microsoft.com/KB/2920812
Office 2013: http://support.microsoft.com/kb/2920754
Word 2013: http://support.microsoft.com/KB/2956163
PowerPoint 2013: http://support.microsoft.com/kb/2965206
Regards, Hans Vogelaar (http://www.eileenslounge.com)

Insert SubSequence Call Step using TS API

We are creating a LabVIEW application that generates TestStand Test Sequences, using the TS API. I am attempting to write a SubVI that creates a TestStand Sub Sequence Call step. The problem I am having is that although I can create the SubSequence call without problem I cannot seem to find a way of specifying the arguments for the parameters to pass to the sub sequence that is called by the SubSequence call step.
We are using TS 3.1 and LV 7.1
Has anyone got any ideas?
Regards
Steve

Hi Steve,
I have done this with C# take a look to this code
static bool DoSequenceCallStep( XmlNode nodeStep, Step step, SequenceFile seqFile, Engine engine)
XmlAttributeCollection attrColl;
attrColl = nodeStep.Attributes;
XmlAttribute attrID = (XmlAttribute)attrColl.GetNamedItem("ID");
XmlAttribute attrName = (XmlAttribute)attrColl.GetNamedItem("Name");
XmlAttribute attrMin = (XmlAttribute)attrColl.GetNamedItem("Min");
XmlAttribute attrSoll = (XmlAttribute)attrColl.GetNamedItem("Soll");
XmlAttribute attrMax = (XmlAttribute)attrColl.GetNamedItem("Max");
XmlAttribute attrDoReport = (XmlAttribute)attrColl.GetNamedItem("DoReport");
XmlAttribute attrSeqName = (XmlAttribute)attrColl.GetNamedItem("SeqName");
String strSeqName = attrSeqName.Value;
Sequence sequence;
// sequenz neu erstellen falls sie noch nicht existiert
if (!seqFile.SequenceNameExists(strSeqName))
sequence = engine.NewSequence();
sequence.Name = attrSeqName.Value;
PropertyObject pObj = sequence.Parameters;
pObj.NewSubProperty("dblMin", PropertyValueTypes.PropValType_Number, false, "", 0);
pObj.NewSubProperty("dblSoll", PropertyValueTypes.PropValType_Number, false, "", 0);
pObj.NewSubProperty("dblMax", PropertyValueTypes.PropValType_Number, false, "", 0);
seqFile.InsertSequence(sequence);
else
sequence = seqFile.GetSequenceByName(strSeqName);
SequenceCallModule objModule = (SequenceCallModule)step.Module;
objModule.UseCurrentFile = true;
objModule.SequenceName = strSeqName;
objModule.UseSequenceParameterPrototype = false;
objModule.LoadParametersFromSequence(sequence);
SequenceCallParameters Parameters = objModule.Parameters;
SequenceCallParameter Parameter;
String strValueExpr;
Parameter = Parameters[0];
if (attrMin.Value.Length == 0)
Parameter.UseDefaultValue = true;
else
strValueExpr = attrMin.Value.Replace(",", ".");
Parameter.ValueExpr = strValueExpr;
Parameter = Parameters[1];
if (attrSoll.Value.Length == 0)
Parameter.UseDefaultValue = true;
else
strValueExpr = attrSoll.Value.Replace(",", ".");
Parameter.ValueExpr = strValueExpr;
Parameter = Parameters[2];
if (attrMax.Value.Length == 0)
Parameter.UseDefaultValue = true;
else
strValueExpr = attrMax.Value.Replace(",", ".");
Parameter.ValueExpr = strValueExpr;
// Do Report
bool bDoReport = true;
if (attrDoReport.Value.Length != 0)
String strHelp = attrDoReport.Value;
if(strHelp.CompareTo("0") == 0)
bDoReport = false;
else
bDoReport = true;
step.RecordResult = bDoReport;
// SeqName
step.Name = attrName.Value;
return true;
Do not care about the XML stuff from the i get the values !
I think this code snipped could be useful your you because the procedure in LV is the same
Greetings from the lake of Constance, Germany
Juergen

CAN I WRITE "COM CLIENT" USING LABVIEW?

I am trying to trnsfer data from Texas Instrument's Code composer to other software packages which in my case is Labview. In TI's tutorial it is mentioned that this can be done by writting "COM Client". Please suggest.
Regards,

There may be other easier ways too. If you can create DLLs with this Code Composer, you can access those from LabVIEW. That's the easiest way. You can also build CINs (Code Interface Nodes), though I would suggest not going this way, as it is much more tedious than just calling a DLL.
J.R. Allen

Step Type ActiveX/COM

Hi!
I want to know what is exactly ActiveX/COM step Type. I don't know what kind of program produce this type of step.
Thanks
Capblans

Hi,
You would use these step type to interface to the methods and properties of an activex/com object.
Tpyically you would use this step type to interface with the TestStand API methods and properties. Also code generated using Visual Basic.
There is a couple of articles (application notes) here that maybe helpful.
Within the TestStand\examples folders and on the NI website are examples using the ActiveX/COM adapter
Regards
Ray Farmer
Regards
Ray Farmer

Creating TestStand GOTO step programatically using LabView. Problems.

Hi
I am trying to programatically create and configure a TestStand GOTO step, using LabView. I can create the step fine, but I cannot work out how to specify the GOTO Destination.
Has anybodt got any ideas?
Regards
Steve
There are 10 types of people in the world that understand binary, those that do and those that don't.

Managed to solve this one myself by setting the CustomActionExpr to 'True' and the CustomTrueActionTargetByExpr to the name of the step I wanted to jump to.
Steve
Message Edited by SercoSteve on 01-24-2006 02:13 AM
There are 10 types of people in the world that understand binary, those that do and those that don't.

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

Problems using Labview as ActiveX Server

Hello,
       I have been having difficulty using Labview as an AcvtiveX server. I have reviewed all the postings on this subject and most are either pre Labview 8.2 and thus do not account for the changes made between 8.2 and 8.5 which broke the Activex server functions. I have looked at the recommendations for changing the to code to export (exported vi's in a DLL or Source distribution) and have tried these with no success. The closest example I have found was posted here http://forums.ni.com/ni/board/message?board.id=170&thread.id=283417 the example code they posted does ont work for me and still generates and error 3005.
      What i need is simple. I want to turn my applicaiton into a Vi server.. Expose a vi that acceses elements in the Vi server.. (controls, queues, Globals etc) that are in the Vi server context. I would then like to build a vi .. or dll that calls the 'exposed' vi in the vi server to pass data to or from the vi server. The V test.zip example file in the above indicated post is a pretty good example of this .. it just does not seem to work when i build it in 8.5. Are there any GOOD and 'current' examples of using labview as the ActiveX server (Compiled) and calling exposed vis from an external application Labivew, Visual Basic.. etc?? I am only interested in cases where Labview is the Sever. or both client and server.
       I have used a tool "ActiveXplorer" to examine the registered "exe" when the viserver is run. It always shows that there is no Type Library associated and the object is not creatable. There is a .tlb created by the project build however, where as the previous version 8.2.1 of Labview did not build that correctly. I have also tried this on 8.6 with similar error 3005 generated. sooooo what am i missing?
      Thanks
       Louis Ashford

Mike,
       Thank you for your response to my question. The problem is that the example you site does not use the Labview vi as the Server. Excel is actually the vi server and the automation open is using and excel automation object. I am sure that Excel creates proper automation objects .. Labview however does not seem to. So while this example shows how labview can function as a client it is not an example of a compiled Labview Sever being accessed by a 'laview vi'. Possibly I am not looking at the vi that you are thinking of.
       The examples i am aware of:
                   "ActiveX Event Callback for Excel.vi... (Excel is server not Labview vi)
                    "ActiveX Event Callback for IE.vi (same Labview vi is client)
                    "Write Table to XL.vi" ( again excel is the server)
                    "3D Graph Properties - Torus.vi" (accesses an activex Control 'not' and Activex EXE)
                    "3D Lorenz Attractor Draw at Compeltion using 3D Curve.vi (Uses an activex control not activex Exe server)
                    "3D Parametric Surface - Ribbon.vi (Uses an activex control not activex Exe server)
                    "3D Surface Example - Fluctuating Sine Wave.vi (Uses an activex control not activex Exe server)
                    "Excel Macro Example.vi (Uses excel as automation server..not Labview)
                    "FamilyTree.vi (uses MSComctlLib.ITreeView object not Labview as server)
                    "SlideShow.vi" (uses PowerPoint._Application not Laview as server)
      Most of the posts I have seen are for versions prior to Labview version 8.2 (where the ActiveX server was broken) I have seen only a few posts that actually address the issue i am talking about. however thus far no real solution has been offered. I get the same results when compiling and testing this with 8.6.. as well. So have you tried this Mike? Possibly i am missing something very simple..
      The example i did find and gave the link to is a pretty simple one. This does not work on my machine at all. You can select the automation server that is registered with windows after running the server one time and this then breaks the client vi.. I have found by reselecting the GetViReference property node in the Client vi that it will the 'fix' the client vi as far as labview is concerened and it no longer shows and error. Now when you run the Client vi it will infact find the vi server and will launch it ok. However. The open automation object then hangs.. for quite some time then returns the error
"Error -2146959355 occurred at Server execution failed
in Client_reader.vi" Obviously the automation Exe (server) was seen because it was opened yet it did not return a valid reference so the subsequent property nodes in the client.vi will fail. Something is wrong with Labviews opening of or creating of automation objects..
          Thanks,,
                Louis Ashford

Creating LabVIEW module adapter TestStand Steps using the API without loading module prototype???

Is it possible to programatically create a TestStand step (using the API), that calls a LabVIEW module, without loading the prototype of the module to get a reference to the Module Parameters.
I want to specify a VI Pathname, but I dont want to use that pathname to load the prototype. I want to programatically specify the name, type, representation etc. of each of the controls and indicators.
My reason for attempting this is that I only want the VIs called by the steps to exist on the target hardware not on the numerous development machines running my application.
Any thoughts greatly appreciated.
Steve
https://decibel.ni.com/content/blogs/DailyCLAD

Hi Steve,
Unfortunatly it is not possible to do what you want within Test Stand but I am not sure why it is necessary, I think I am understanding your application incorrectly. The only time you will need to load the prototype is if you are creating the step but if you are creating the step you will need the VI that the step calls so that VI will need to be present on the system. If you are not calling the step then you shouldn't need to load the VI prototype. If this is how you program funtions it may be a problem with your architecture but if not please could you correct my misunderstanding so that I can go about finding a suitable solution.
Regards,
Tom
Applications Engineer
National Instruments UK & Ireland

Reading Tables in MS WORD using LabView & ActiveX

I would like to be able to read tables contained in an MS WORD document using LabView and ActiveX. (I've been successful in doing this with Excel files. ( I am not using the report generation toolkit.) After searching numerous posts with similar questions about LV & ActiveX I've not found any solution to my specific app. In LabView I'm successful doing an "Automation Open", followed by a Property Node, to an Invoke Node ("Documents" Open) and then a Property Node with "TABLES" selected. That's where I get stuck. Now that I have a reference (?) to "Tables" I can't seem to figure out what I need to connect and follow that with in order to now read the Tables in my document. I guess that's due to my lack of understanding as to what exactly this "Table" property node output actually is. Can someone tell me what this reference output is referring to and how I can get to the Tables within the document from it? I've tried connecting both a property node and invoke node to no avail. Can someone point me in the right direction?
Thanks. Ed

Dear Ed,
Figuring out "what I need to connect and follow that with" relates to the organization of the MS Word Object Model. Please refer to the Word Object Model Reference MSDN >> MSDN Library >> Office Development >> 2007 Microsoft Office System >> Word 2007 >> Word 2007 Developer Reference >> Word Object Model Reference. You can think of the Object Model as a software hierarchy. You must start at the top of the hierarchy and work your way down to the item of interest. You must descend the hierarchy one level at a time; you cannot skip levels.
At each level of the hierarchy, you have access to the methods and properties of that "level".
Click on the Tables Collection link from the Word Object Model Reference page. Notice how Tables is at the top of the hierarchy. When you have a LabVIEW reference to a Tables object (technically speaking a collection), you then have access to the methods and properties supported by this "level". Click on the Tables Object Members link. Here you will see that the Tables collection supports two methods, Add and Item, and also supports five properties, Application, Count, Creator, NestingLevel, and Parent.
Notice how Mike gets the Count property of the Tables object. He then uses the Item method to return a reference to an individual table. The key thing to take away from this is how Mike uses the Item output node to gain access to the methods and properties of the Table object (not the Tables collection). Mike has descended the hierarchy from Tables to Table. He descends the hierarchy again with the Cell method and Range property of the Table and Cell object respectively. Lastly, the Text property of the Range object, "Returns or sets the text in the specified range or selection."
Effective LabVIEW programming with this type of ActiveX control requires a fair understanding of how Microsoft organized its software libraries. The Object Model Reference is a good place to start visualizing how these libraries are organized. Thank you for using the forums Ed, and thanks for your post, Mike.

I am using the NI application note "Calling IVI-COM drivers from LabVIEW" I created an Automation Open and an Invoke Node, after wiring

the 2, the AN asked to right click the Invoke Node(this is step9) and choose initialize. However there is no intialize option on the pop up menu. Anything am I doing wrong? I am using Labview6 and I did add the "enableCustomInterface=True" in the INI-fileThank you for your help.
T Tall

the 2, the AN asked to right click the Invoke Node(this is step9) and choose initialize. However there is no intialize option on the pop up menu. Anything am I doing wrong? I am using Labview6 and I did add the "enableCustomInterface=True" in the INI-fileT Tall,
What's the number of the application note "Calling IVI-COM drivers from LabVIEW"? I'm unable to find what you're looking at.
Thanks,
--Bankim

Using labview global in test stand sequence steps

If I have to pass data between different steps ( only labview vis) within same Main sequence, is it right using LabVIEW globals, rather than TestStand globals?
in one step, I will be writing data to the Global.
In a later step, I will be reading the global to access that data.
Example sequence:
I am more comfortable with using Labview globals than Teststand variables. Labview is the only adapter in my sequence.

If it is just within one sequence, then I would use the TestStand variables. The reason is because you are limiting your possible reuse of those VIs by using the global. If you pass in the value, you have a better chance of being able to reuse the VI.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Retrive the names of step measurements using LabVIEW

How do you retrieve the names of a multiple numeric step's measurements using LabVIEW?
I've constructed a vi to call from TestStand, and will pass it "ThisContext", but the vi doesn't complie. That's how far I got. The vi is attached. The error message is:
"The method selected in the invoke node is invalid or no method has been selected. Right-click the invoke node and select a method."
My vi is an attempt to write the code from
message.id=10653 in LabVIEW. Specifically:
Dim MyStep As [Step]
Dim MyMeasurement As PropertyObject
MyStep =
seqContext.AsPropertyObject.GetPropertyObject("Step", 0)
MyMeasurement =
MyStep.AsPropertyObject.GetPropertyObject("Result.Measurement[0]", 0)
MsgBox(MyMeasurement.Name)
Can someone help me finish the vi?
Thanks
Solved!
Go to Solution.
Attachments:
Dev-GetMeasurementName.vi ‏8 KB

You missed the the AsPropertyObject in "MyMeasurement =
MyStep.AsPropertyObject.GetPropertyObject("Result.Measurement[0]", 0)". Checked out the attached.
I cleaned up your code. Make sure you're closing every reference you get from TestStand or it'll yell at you when you shut the engine down.
Attachments:
Dev-GetMeasurementName.vi ‏12 KB

Programmatically Insert ActiveX/COM Step Using LabVIEW

Similar Messages

Maybe you are looking for