NI VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Custom control with OPC: which licence ?

Solved!
Go to solution

Hi !

We've developed a custom control which allows mapping VS channels onto OPC tags.

So from the workspace you can perform the links and push data to an OPC server.

 

In that conditions, which OPC licence should I use when I distribute this custom control to customers ?

Due to the nature of the workspace / code executed (llb, vi, no compiled code), is OPC deployement licence enough ? Or does it require the dev licence version ?

 

Thanks !

CLA, CTA

View Cyril Gambini's profile on LinkedIn
0 Kudos
Message 1 of 6
(1,485 Views)

At a high level, what VIs/methods are you using to update the OPC server tags? Is it an I/O Server? Data sockets? Really any licensing that you might need depends on the functionality and VIs that we're using. 

0 Kudos
Message 2 of 6
(1,446 Views)

I'm using the OPC UA toolkit stand alone (no DSC).

Tags are exposed into a Kepware OPC server.

CLA, CTA

View Cyril Gambini's profile on LinkedIn
0 Kudos
Message 3 of 6
(1,444 Views)
Solution
Accepted by topic author CyGa

To close the loop on this question, deployment license will be required for use of the VeriStand custom device that uses the LabVIEW OPC UA Toolkit.  I have created an article on this for documentation:  https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000001Dd7BSAS&l=en-US

Clemens | Technical Support Engineer | National Instruments
Message 4 of 6
(1,417 Views)

Hi Clemens,

 

Thank you for the answer.

Just to be clear, my development is NOT a custom device but a custom CONTROL (running on Windows PCs, in the Workspace).

Your information about the license is still valid in that case ?

CLA, CTA

View Cyril Gambini's profile on LinkedIn
0 Kudos
Message 5 of 6
(1,414 Views)
Solution
Accepted by topic author CyGa

For those who are interested, I got an answer from NI support.

The custom controls are 'built' as a source distribution and executed by the workspace in the LV Run-Time engine.

Therefore, even in that case, only the OPC Deployment licence is necessary.

 

Original messsage from NI:

The deployment license is still valid in this case, because you are using OPC UA Toolkit as a source distribution and it should be running in the LabVIEW run-time engine.

CLA, CTA

View Cyril Gambini's profile on LinkedIn
Message 6 of 6
(1,393 Views)