ProMetrics Compute Metrics for Display.vi

[mrbean]

We've developed a wrapper/tool here that uses the ProMetrics Compute Metrics for Display.vi (available from C:\Program Files\National Instruments\LabVIEW 8.2\project in the file prometrics.llb) and applies different weightings to the various output (i.e.Nodes / Diagrams / Controls / Indicators - NDCI).  However, we want to create an EXE version of this tool and we're running into some problems since the library/VI behind the metrics code is locked. First, from a legal/license standpoint, can we use this VI within an EXE in this manner when we intend (ultimately) to make this product available to a number of groups within our organization (not to the public).  Second, if this is allowed, what licensing\legal issues must we address?

[DuffmanSays]

Hello mrbean,

To answer your question, yes you are able to include any VIs from this library in your executable without special considerations for licensing. This tool is included with LabVIEW and as such can be distributed under the standard licensing agreement. You will most likely want to examine the NI Software License Agreement (primarily section 12) to be sure that your distribution follows these licensing requirements. I hope this was the information you were looking for. Please post back if we can offer any additional assistance. Thanks!

Mike D.
National Instruments
Applications Engineer

[mrbean]

Now that we've addressed the legal issues, we have a technical issue we can't seem to resolve.  When running our code within LabVIEW, everything seems to work fine.  It's when we create an EXE (using a labview project) that things go south.  We've attached an example that mimics what we're trying to do.  In general, though, it seems that under LV, the prometrics tool knows how to find the VIs resident in memory, and can therefore perform the metrics calculations.  When built/run as an exe, however, it seems the prometrics tool (within our app) loses its knowledge of the loaded (in memory) VIs, and thus captures no metrics.  Can anyone offer an explanation of how this tool works, related to the memory access and what we can do to help it find the files involved in the metrics collection.

[Darren]

The ProMetrics Compute Metrics for Display.vi includes functionality that is not supported in the LabVIEW Run-time Engine.  Thus, you will not be able to use this VI in a built EXE.

-D

[mrbean]

Can you be more specific (i.e. includes functionality that is not supported in the LabVIEW Run-time Engine) ?  And, more importantly, can you offer any suggestions/solutions?

[Darren]

Certain LabVIEW functionality that is available in the development environment is not included in the LabVIEW Run-Time Engine (i.e., not available when using a built EXE or DLL).  For example, if you read the LabVIEW Help for various VI Server methods and properties, one of the rows in the information table in the Help for most properties/methods is "Available in Run-Time Engine".  In your case, the ProMetrics tools use some private VI Server functionality (which is why the VI is password-protected), and this VI Server functionality is not supported in the Run-Time Engine.

There is no workaround for this issue at this time.  You can file a suggestion at the Product Suggestion Center that the ProMetrics functionality should be supported in the LabVIEW Run-time Engine, and we will evaluate this suggestion as a feature for a future LabVIEW release.

-D