From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Deploy and use shared library in VeriStand for many VCD

Solved!
Go to solution

Hi everybody,

 

I'm using LabVIEW 2011 SP1 and VeriStand 2011 SP1.

 

We developped many Custom devices that are using shared code (C++ code and LabVIEW).

For the moment, there is a copy of the C++ shared dll in each custom device.

The problem is when we are modifying the C++ dll and we forget to copy the new one in each custom devices, the oldest one could be used by each custom devices.

What we would like to do is to have only one dll shared in a specific folder.

 

My questions are how can we deploy this dll in a specific shared folder in VeriStand ?

Is there a specific folder that we can use to do this ?

Is there a way to deploy it using Measurement and Automation Explorer ?

 

If someone has an idea, you're welcome !

 

Best Regards,

CFOE

0 Kudos
Message 1 of 4
(5,879 Views)

You can set this property on any of your custom device nodes with the information about the DLL and where you want it deployed to on the RT target.

Jarrod S.
National Instruments
0 Kudos
Message 2 of 4
(5,877 Views)

Jarrod,

 

We already did this.

To be more precise, what we want to do is to install our dll maybe like a driver before deploying a Veristand project.

This dll should be used by many custom devices.

 

For the moment, the dll is in every Custom devices. We don't know which one is loaded when the project is deployed.

What we saw is when the are two different versions of the dll because of a human error, the latest one is not loaded.

 

To avoid such problems, we would like to have only one release of the dll.

All the custom devices, we created, are not necessarily started together that's why it should be deployed before the custom devices.

 

What we imagine is that a custom device called core (for example) should be created with the dll. The custom device should be always deployed in order to let the other custom devices access to the dll.

It could be done but it's not really smart.
If there is no other possibility, we will do this.

 

We explore an other way that is to create for example a driver that could be installed using MAX.

It could be a pre requisite before using Veristand with our custom devices.

We don't know if it's possible to create custom driver for MAX, that's why we ask it here.

 

Is there a way to deploy a dll (using MAX for example and to do it automatically) and what is the best folder to store such files.

 

Thanks !

Best Regards

CFOE

0 Kudos
Message 3 of 4
(5,869 Views)
Solution
Accepted by cfoe

You might want to post that question in another forum as I dont think it has anything directly to do with NI VeriStand.

Stephen B
0 Kudos
Message 4 of 4
(5,832 Views)