Activex server excel example in LV 8.0

Does anybody know how to get the following ActiveX Server example working for LV 8?
labview\examples\comm\freqresp.xls
The menu items appear to have been moved. The equivalent (VI Server) options under Tools-->Options don't appear to work.
Has anybody managed to get the Ctrl+M and Ctrl+L in the spreadsheet to generate calls to the VI?
Thanks.

Hi battler,
The VI itself can run on its own. There is a Visual Basic script that you can look at to see how the Frequency Response VI is called from Excel. Within Excel go to the Developers tab and click on Macros. Then select LoadData and press Edit to look at the script.
There is some additional information here and here.

Similar Messages

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

Bug Appeal: LV6 activeX with Excel; Error -2147319784

At Thu, 16 Nov 2000 14:55:00
"Dominic Lavoie" wrote:
<-2147319784 Old format or invalid type library.
Dominic and others
This is an old bug in LabVIEW that I have been fighting
with for several years. The problem (as I have seen it) is that
LabVIEW for some reason on some PC's suddenly becomes unable to read
from the (NT-) registry that Excel is installed as an
available ActiveX component on the machine. In my case the
Excel8.olb file.
Under earlier verion of LabVIEW no error messages
was generated, but you could see the problem when entering
the list over ActiveX classes, Type library. Suddenly the Excel
would be gone from this list, and it will not come back no matter
how you try to install, reinstall or reconfigure the Excel (or Office)
system. (And the Regsvr32 program does not handle OLB files.)
The only way I have heard to fix it, is to reformat the
harddisk and install the OS and everything fresh. But you might
see the problem coming back again.
There might be a possibility that this bug is not NI's, but one
in the OS. When I use other programs to View/Edit the registry,
these programs have no problems of detecting the Excel library.
So I believe it is a LabVIEW bug !
When working with Excel and ActiveX with this problem
meant that you had to manually browse to the OLB file each time you
would want to work with it, or you would sometimes get messed up
the wires and VI's working against the Excel library.
Now, under LabVIEW 6i, this situation creates the error message
-2147319784, and the problem suddenly seems much bigger.
I have reported this bug two month ago to NI, together with some
other people that has seen the same problem. So far NI has not
been able to locate the problem in detail or done anything with it,
as far as I have been informed.
This has been a very frustrating experience for me, because there are
many other features under 6i that I would like to use right away.
But since I am working a lot with Excel as a data format from LabVIEW,
I cannot proceed with 6i before they have broken this bug.
So now I would like the LabVIEW community to help me push NI
a little in their effort to debug this one.
All questions of course assuming that you have installed Excel
on your PC.
Could as many as possible out there check out if,
when testing the ActiveX/Excel examples;
A) under 6i; do you get the Error -2147319784 ? (YES or NO)
B) under 5.1.1 or earlier; can you run the example Write Table to XL.vi ?
(YES or NO)
C) if B=NO, can you locate the Excel library in the ActiveX class list ?
(YES or NO)
D) Where in the world are you located (country) ?
(Some has speculated that this bug might be connected to a problem
with different OS versions in different parts of the world.)
E) What version of Excel are you using ?
F) What OS are you running ?
If you can't do both A and B/C, send me the one you can.
Please report your results directly to me.
DO NOT REPLY TO THIS LIST. I will send a
summary after a couple of weeks, to let you know
the results. And also if NI seems to make any progress here.
best regards
Martin Plassen

"[email protected]" wrote in message
news:[email protected]...
> Martin, I'm not sure how to reply directly to you. (I can't find your
> email address or anything.) I may be experiencing a very similar
> problem. I am trying to generate Excel reports using LabVIEW 6.0
> under a Windows 2000 OS. Under Win95 in LabVIEW 4 I had no problem
> but I recently updated. Now I can't even open Excel using the NI
> distributed LabVIEW 6i Excel toolkits from ni.com. When I execute the
> Open Excel vi I get a Windows error message, "Labview.exe has
> generated errors and will be closed by windows. An error log is being
> created." Could this be the same problem dominic was having under WIN
> NT?
dmbillings
It seems NI has been so kind as to remove the fix on this problem
from their Knowledgebase. Well, I dug up some old e-mails on the subject,
and here's one you should look through. According to NI this problem
should have been fixed under LV 6, so I really hope this is not what you are
facing...
Martin
Good news for all of you,
we have a bug-fix that seems to do the trick.
Here's the recipe , with my words:
Do You have the bug ?
You can confirm that the bug is there, by opening a new file in LabVIEW,
in the diagram, insert an Automation Open.VI, right-click on it,
Select ActiveX class, Browse, and check the Type Library list.
You should not see the Microsoft Excel5 and 8 library in the list,
if the bug is there.
As I have suspected for a long time, the whole bug was related to
how LabVIEW read the registry at startup to locate all ActiveX
components on the machine.
Here's the fix to try out;
1. Open the RegEdit program
2. Under HKEY_CLASSES_ROOT locate the TypeLib
3. Locate the Excel-key
On my machine this is {00020813-0000-0000-C000-000000000046}
(You will find it on top part, I think, not necessary to browse long
down.)
4. There are two base keys there, named "1.0" and "1.2".
Under the "1.0"-key, right-click and create new key, name it "0"
(zero).
5. Under the new "0"-key, create a new key kalled "win32".
6. Under the "1.0"-"9"-"win32" key you will find the link to the
Excel5-library on the machine, copy this link into the key you created
under pt 5.)
On my machine this is "C:\Program Files\Microsoft
Office\Office\XL5EN32.OLB".
That's all. Exit RegEdit.
Afterwards, check again that the Microsoft Excel5 and 8 libraries
is on the LabVIEW list mentioned above. After restarting LabVIEW of
course. It is not necessary to restart the PC.
Attached you wil find two gifs showing how this should look
in RegEdit before and after the described operation.
Good luck
PS: hacking around is the registry are do be done with
caution. The wrong actions here could have large consequences.
The two attached pictures should help you out,
but if you feel uncomfortable by working with the registry,
try to hook on to some hacker around that has been there before.
As I understand it, this is the reason that NI asked me also not to
give this info directly to the List-server. So please don't do it
you either. I plan to put the word out about the fix, not with these
details, but with a reference to the NI Knowledgebase that soon will
have this info.
You are welcome to send me a conformation that you see the
fix is working, or worst case, not.
Martin

How to implement an ActiveX server in LabVIEW

My task is to implement an ActiveX server in LabVIEW 8.0 that will be called from a data management software (DXE).
The LV server will take care of data acquisition and control.
I have been looking for tutorials and example code at the NI developer zone and elsewhere without any progress. Information is either to general or code is to old (LV 5.1) to give any help.
Please, show me to a good example of an ActiveX server in LV 8 properly commented or with attached explanations.
Alternatively, suggest any tutorial, short course or books with practical instructions.
Specific information is most welcome.
I suppose that it is possible to write a ActiveX client in LabVIEW to verify the functions of the ActiveX server ?

rolfk wrote:
skalis wrote:
Thank You. Good to know that I am on the right track.
However,
Your sentence "If You look at the several shipping examples..." make me
little concerned. I am not able to find any example of a LV ActiveX
server in my LV 8.0 installation. I would be very grateful of You can
send me any.
Basically you can not create your own
Active X server with your own object hierarchy and methods in LabVIEW.
LabVIEW however can export a predefined Active X server interface that
is just another access method to its internal VI server interface.
With this interface you can determine what VIs are available to
control, load specific VIs from disk if you know their path and,
execute those VIs and passing parameters to it and receiving outputs.
So if your software allows you to script the Active X access to an
Active X server in some ways such as VBA or similar you should be fine.
If your software expects a specific Active X interface you have to
implement in the server application, you are out of luck with LabVIEW,
without using an external component such as an extra Active X server
DLL that translates between the expected interface and the exported
LabIVEW interface. But this last method is quite likely not worth the
hassle.
Rolf Kalbermatter
While I did follow the link mentioned above and found the Interop.LabVIEW.dll that is included in the C# project for the purpose of calling VIs from C#, I am frustrated that these methods are 'buried' in a .dll that you have to go and find on the NI web site, and are not ActiveX methods that are available in an ActiveX Object that is installed when you install LV 8.20 PDS.
Rolf, I don't know that you will get this email, but are you refering to the methods inside of the Interop.LabVIEW.dll in what you are saying above, and if so, how did you become aware of this .dll?
Is anyone aware of any documentation for these ActiveX methods?
Thanks,
Wes
Wes Ramm, Cyth UK
CLD, CPLI

ActiveX Server Method Problem

LabView men help me!
I have a problem with using ActiveX Server Method object.Run(async) with
async = TRUE in MS Visual C++ program.
I want to call ActiveX Server and continue program execution.
I call this metod in program block.
COleVariant No_Wait;
No_Wait.boolVal = TRUE;
pVI->Run(No_Wait);
After this operator I can not return from VI, until VI does not close, inspite
of parameter async = TRUE.
I ask your send me example how to use this metod and wait for you recomendations.
Gregory.

I think I have exactly the example program both of you are looking for. Take a look and post to let us know if you have any questions. Thanks!
Best Regards,
Chris C
Applications Engineering
National Instruments
Chris Cilino
National Instruments
LabVIEW Product Marketing Manager
Certified LabVIEW Architect
Attachments:
Calling_LabVIEW_from_C++_Using_ActiveX.zip ‏4972 KB

Calling LabView ActiveX Server from TCL?

Does anyone have experience calling a LabView ActiveX server vi from
TCL? I created a simple VI with one control (labeled "A") and one
indicator (labeled "B") and a +1 adder between them. I can load and
open the VI from TCL:
package require tcom
set lv [::tcom::ref createobject "LabView.Application"]
set viPath "D:\\National Instruments\\LabView\\Activity\\a.vi"
set vi [$lv GetVIReference $viPath]
$vi FPWinOpen True
But when I try to send in data:
$vi -namedarg Call A 1
I get the error message "unknown parameter A".
I have also attempted to duplicate the "ActiveX Server" example
from the LabView help file, calling "Frequency Response.vi". This
approach encounters the same error message:
% package require t
com
3.0
% set lv [::tcom::ref createobject "LabView.Application"]
::tcom::handle0x013202F4
% set viPath "D:\\National
Instruments\\LabView\\examples\\apps\\freqresp.llb\\frequency
Response.vi"
D:\National Instruments\LabView\examples\apps\freqresp.llb\frequency
Response.vi
% set vi [$lv GetVIReference $viPath]
::tcom::handle0x01335AE8
% $vi FPWinOpen True
% $vi -namedarg Call Amplitude 10
unknown parameter Amplitude
If anyone can point me in the right direction, or give me an
example of how to do this I would greatly appreciate it.
TIA.
Leslie

In article ,
Leslie Brooks wrote:
>"Bruce Hartweg" wrote in message
>news:...
>> "Chin Huang" wrote in message
>news:[email protected]...
>> >
>> > I don't use LabView, but from the Visual Basic example I saw, it seems
>> > the Call method takes two arguments. The first is an array of parameter
>> > names and the second is an array of parameter values. Try to send in
>> > data with the Tcl command
>> >
>> > $vi Call [list A] [list 1]
>>
>> I'm unable to help the original question (don't know LAbView or VB stuff) but
>> just want to point out that [list A] is equal to A and [list 1] is the
>same as 1.
>>
>> Bruce
>
> I know what is supposed to be passed to the 'Call' method. Doing
>this:
>
>set inst [::tcom::info interface $vi]
>$inst methods
>
> produces (among other things):
>
>{1015 VOID Call {{{in out} {VARIANT *} paramNames} {{in out} {VARIANT
>*} paramVals}}}
>
> So the 'Call' method is expecting two parameters, both pointers
>to variants. TCOM appears to be passing the correct parameter type
>because the TCOM documentation says that a TCL List maps to a
>one-dimensional array of VT_VARIANT. However, the results are
>INvariant (bad pun intended):
>
>% $vi -namedarg Call Amplitude 10
>unknown parameter Amplitude
>% $vi -namedarg Call [list Amplitude] [list 10]
>unknown parameter Amplitude
>% $vi -namedarg Call [list Amplitude] [list [::tcom::na]]
>unknown parameter Amplitude
>% set i 5
>5
>% $vi -namedarg Call [list Amplitude] {incr i}
>unknown parameter Amplitude
>% $vi -namedarg Call [list Amplitude] [list [incr i]]
>unknown parameter Amplitude
>% $vi -namedarg Call Amplitude [incr i]
>unknown parameter Amplitude
>
> Who can help me with this? Who is the LabView Guru?
Try invoking the Call method without the -namedarg option. The
-namedarg option doesn't work the way you seem to think it works. The
-namedarg option provides a way to specify arguments named from the
method's parameter specification. For example, you discovered that the
Call method take two parameters named "paramNames" and "paramVals".
Tcom returns the error "unknown parameter Amplitude" because "Amplitude"
doesn't match either parameter name.

Is it possible to querry all of the Virtual Instruments in a VI using the ActiveX Server Virtual Instrument Class?

Is it possible to querry all of the Virtual Instruments that exist in the Front panel of a VI using the ActiveX Server Virtual Instrument Class? I can't seem to find a method or property that returns all the Instruments I may want to control from another application.
I wish not to have to reference to the VI to figure the ControlName by looking at the VI FrontPanel.
But rather have a prop that exposes the strings of all the Instruments.
Example:
allinstr=ObjectVIInstrument.VIControlNames
Object.SetControlValue(AllInstr(1),value)
Thanks.
-Abe

Abe,
There is a VI method called "Get All Control Values" that returns an array of {name,typedesc,flatstrvalue} but this method is not exposed to ActiveX interface, most probably because type descriptors and flattened strings are data format internal to LabVIEW.
However you can make a subVI that inputs the target VI name and returns the name of all controls on the Panel invoking the internal method. Then you call this VI via ActiveX to retrieve the list of Front Panel controls of the target VI.
LabVIEW, C'est LabVIEW

Teststand 4.1.1 PAWS Run-Time System ActiveX Server

Hello,
I downloaded Teststand 4.1.1 for evaluation. However, when I tried to run the example called "Manual Intervention Example.seq" or "ParameterPassingExample.seq" shows an error.
Both sequences indicates "PAWS Run-Time System ActiveX Server not installed."
Error: Error executing substep 'Execute TPS'.
An error occurred calling 'ExecuteTPS' in 'IExecuteTPS' of 'NI ATLAS StepType 1.0'
The TPS Server could not be created. A possible cause is that the PAWS Run-Time System ActiveX Server is not installed. Check your TYX PAWS installation and try again. [Error Code: -2147221164, User-defined error code.]
Where do I get that installation from?
Why wasn't it installed when I install the evaluation for Teststand 4.1.1?

Hi,
Try here:
http://www.tyx.com/index.html
regards
Ray Farmer
Regards
Ray Farmer

Does Labview's ActiveX server throw any events?

I'm trying to use Labview as an ActiveX automation server. It works so far, but I can't figure out a good way to get data back from the VI without polling it. Does Labview throw any ActiveX events that I could catch or is there some other way to receive data? Polling is a rather poor solution, so I figure there must be a better way.

qx3n42j,
I ran the List ActiveX Events shipping example on LabVIEW 6.1 and it returned that there are no events. I also searched through the documentation and found no reference to LabVIEW ActiveX events.
You could implement a DLL that throws an event and call that from your LabVIEW VI.
Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

Turning a LabVIEW built DLL into an ActiveX server

Does anyone have a list of the steps you must go thru
to convert a LabVIEW generated DLL into an ActiveX server. Do the functions become methods?

Hi James,
we have a library we deploy in three ways: as a LabVIEW library, as a DLL and as Active-X server.
In the build file for the DLL we have made each "function to call" a top level VI.
In the Active-X server each "function to call" is a dynamic VI. We created a new top level VI which will run when the server is started and stops after his window is hidden. In LV 6.x you need the winutil library to hide the window. If you close the window (through FP.Open set to FALSE) the server will stop. The window size is set to 1x1 in the VI Properties to minimize flickering on the screen during start of the Active-X server. You must check the "Enable Active-X Server" box on the "Application Settings" page in the app builder. In your client application yo
u open a reference to the server and then you can open a reference to the VI. You set/read the controls and run the VI. There is sample code for Visual Basic on the NI web site. I have also sample code for Visual C++ single and multi threaded clients.
If you are interested in the examples contact me at [email protected] and I will ask my customer to allow me to send it to you.
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

ActiveX server output strings

I'm working on creating an ActiveX server executable with a number of interfaces. Each interface includes at least a couple methods that need to provide string output. The canonical prototype for such a method would simply accept a pointer to char for the output parameter:
HRESULT method1(char *outputString);
The ActiveX server editor dialog for method entries provides options for both input and output strings. If I specify outputString as an "output string", the prototype that's generated is:
HRESULT method1(char **outputString);
If I specify that it is an "input string", I get the desired prototype in the generated server code, but the corresponding controller code method specifies this parameter as "const char *", meaning that it can only be read, not written; so this isn't workable.
If I specify that is an "output char", I also get the desired prototype, but in this situation, the generated code only copies 1 character into the output string; so this isn't workable either.
So I've tried using the prototype produced for "output string" (see above). My server implementation for this method refers to *outputString, e.g.,
strcpy(*outputString, "Hello");
to populate the output parameter. On the client side, I pass in the address of a pointer-to-char that points to a string, e.g., &op where:
char output[1024];
char *op = output;
Each time I invoke this corresponding client-side operation, the server crashes; *outputString in the strcpy function call evaluates to NULL. I'm sure I must have something wrong with my approach here. Is there a preferred approach for handling output strings in an ActiveX server?
Many thanks in advance!

I don't know if this is helpful at all, but there is an example that uses output strings, SimpleEXE.cws. It may be beneficial to see how it is handled there. The method in question is the Add method in the IString interface.
Steven

Labview activex server registration incomplete.

I made an ActiveX server using LabVIEW. The server should communicate with Excel. During installation of the server I register the server: "Server.exe /RegServer". When I try to call the server from Excel/VBA, it responds with "Run-time error '429': ActiveX component can't create object". The server is only recognized by Excel after I have started and stopped the server once.
When investigating the registry, it appears that the difference between registering with /RegServer and just starting and stopping the server are the following registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ServerName.Application
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ServerName.Application.6
To my opinion the /RegServer commandline option does not do the whole job.
Also /UnRegServer does not remove the above mentioned registry keys.
Is this a bug or just normal behaviour?
Has it been solved in newer LabVIEW versions (I use 6.0.2)?

Hi,
I've tried to call a with LabVIEW 7.1.1 created activeX server. This works without any errors. I've attached my code.
As for the register keys, this seems to be the default behaviour of ActiveX, each server has a key without version number e.g.
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ServerName.Application
And one or more with a version number:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ServerName.Application.6
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\ServerName.Application.7 Kind regards,
Karsten
Applications Engineer
National InstrumentsMessage Edited by KvZ on 07-27-2005 02:37 PM
Attachments:
ActiveX Server.zip ‏45 KB

What's the difference between the 2 activex server interface types

Hi,
i have a problem with a LabView ActiveX-Server i wrote. This is a little test application with 2 ActiveX-Servers and a VC++ Application. The first server opens the serial resource and sends it as variant to VC. VC sends the variant then back to the second server where i want to communicate with a serial device. When i access the second server through the LabView.Application interface everything is fine. But when i'm trying to access the exe directly with [VI-Name].vi (i think this is called run interface) i get an error that my resource for the serial interface is not correct.
Want is the difference between the two interface types and how can i solve the problem?
Thanks

The path of a main VI changes after it is compiled into executable. For example, the original VI is at
c:\temp\test\main.vi,
after building it into executable (say the executable directory is exe), the path to main.vi then changes to
c:\temp\test\exe\main.exe\main.vi
Sometimes in order to correctly reference some relative information, the "main.exe" need to be removed from the path. If you are accessing main.vi at development time, then the correct path should be the longer one during runtime.
-Joe

How Do I set up a LabView ActiveX server?

Are there any documenation or sample program which is about how to setup a LabView ActiveX server? my C++ program will dynamically call VI and then pass the integer to Labview program via ActiveX and then perform some control of digital oscillscope. Do anyone help me? thanks for help so much......It is in hurry......please help..............
CowCow

From the NI knowledge base...
Problem: How do I enable LabVIEW as an ActiveX Server?
Solution: Under Edit >> Preferences >> Server: Configuration, select ActiveX as a protocol and enable all server resources. Under Edit >> Preferences >> Server: Exported VIs, list the name of all VIs that can be accessed remotely. You can include the full path to the VI, or just list its name. Wildcard characters are valid. You can explicitly deny access to certain VIs by clicking the Deny Access button. Note that changes to the Server will not take effect until LabVIEW is relaunched.

How can I force TestStand to create multiple instance of an activex server instead of share the same reference?

Hi, All:
     I am trying to migrate a application coded by VC++ to TestStand+CVI. This application opens multiple serial com ports and send commands to test targets, and get responses from these targets. The VC++ application creates multiple thread, and every thread create an activeX server instance which is responsible for opening serial port,sending test commands ,and getting response. It works fine as every thread has itsown activeX instance, so data and commands can be handled in the right serial port successfully.
     Yet when I works on TestStand, I got problems. I choose parallel model as the process model. I create a activeX object reference with AxtiveX/COM Adapter, and store the reference in a sequence local varialbe. If there is only 1 testsocket, It is OK. But if there are multiple test sockets, and communication between the application and test targets will be directly to the last test target. I try to popup a message within a execution to indicate the value of the activeX object reference, and all of them are identical. But this is not the behavior I want.
    So, is it possible to force TestStand to create independent instances of an activeX server? How can I make it work?
Thanks

Thanks for your comment, Dan.
      Yet I do get problems as none of us know how to program an activeX server so that it can be forced to be a single-instance or multiple-instance.
As I mentioned earlier, there is existing application which is written by VC++ can create multiple instances of this activeX server, all I have to do is to create multiple threads, and initiate an instance of this server to contrl multiple test targets.
     My colleague said he creates the server with VC++ ATL, and cofigure it to be dual-interface and STA. And in the VC++ application side(client side), I use smart-pointer in threads to create an instance of the server:
IMySerialServer pIMySerialServer;
  HRESULT hr = pIMySerialServer.CreateInstance("UUTCmd.MySerialServer");
  if(FAILED(hr))
   AfxMessageBox("Fail to create instance.");
And then I got multple instances of the activeX server. Every thread can have itsown com port, can send/receive commands indepently. I have no idea how can I make it work on TestStand. Would you show me some reference documents or sample codes?
Thank you
Cipher

Activex server excel example in LV 8.0

Similar Messages

Maybe you are looking for