LabVIEW gets a ready-made VI library: one VI per function, each with error in/error out, saved in LabVIEW 2026 (64-bit) and packaged as a VI Package for VI Package Manager. Underneath are Call Library Function nodes on a stable C ABI, so in another LabVIEW version you wire the nodes yourself from the supplied header and instructions, and a VI you wire today keeps working.
Configuring the Node
Point the node at the shared library, set the calling convention to C (not stdcall), and match the bitness of your LabVIEW installation — a 32-bit LabVIEW needs the 32-bit library. Both are supplied. Byte arrays are passed as Array Data Pointer, and anything returning variable-length data follows the two-call convention: ask for the size, allocate, ask again.
Why This Fits Test and Measurement Especially Well
A LabVIEW application is usually inseparable from a physical setup: a test cell, a rig, an instrument rack. That machine frequently has no internet connection and never will, which makes online activation the wrong tool and a dongle the obvious one. It also means the licence can move with the rig when the rig moves.
Gate on your calibration constants, limit tables or instrument coefficients rather than on a Boolean wire — a Boolean is one diagram edit away from being replaced with a True constant, and unlike compiled code, a VI is editable by whoever has it.
Shipping the Native Library with a LabVIEW Application
The VI library calls keynub_licdongle_flat.dll through Call Library Function Nodes; the flat API exists for exactly this caller: integer handles, caller-allocated buffers, no callbacks and no structures. In a clone of the SDK the VIs find the DLL in natives/win-x64/; deployed elsewhere, put it next to the VIs or on PATH, since LabVIEW looks in the calling VI’s folder when the stored path does not resolve.
For a built application or a run-time-engine deployment, include the DLL in the build so that it lands beside the executable, in the bitness of your LabVIEW rather than of the operating system. The VIs are saved in LabVIEW 2026, 64-bit; the import header licd_labview.h lets the Import Shared Library wizard regenerate them for another version.
Questions LabVIEW Developers Ask
Which LabVIEW Versions Does the Binding Support?
The ready-made VIs are saved in LabVIEW 2026, 64-bit, on Windows. For an older version, the Import Shared Library wizard generates the VIs from the shipped header in a few minutes.
Can a LabVIEW Executable or a Test System Be Protected with a Hardware Dongle?
Yes. A test or measurement application ships with instrument parameters, calibration data and limits; sealing those with the dongle and decrypting them at start protects the application without a single boolean to patch.
Does a LabVIEW License Check Need an Internet Connection?
No. Verification is a local exchange between your program and the dongle over USB: the SDK checks the dongle’s certificate chain to KeyNub’s root and runs a live challenge-response. There is no activation server and no account, so the check works on air-gapped machines.
Can Several Dongles Be Connected at Once?
Yes. The SDK enumerates every attached dongle with its serial number and device path, and you open one by serial; with no serial given, the first dongle found is used.
What Are the Hardware Counters For?
Counting things that must not be reset: activations, runs, consumed units, exports. The dongle’s monotonic counters only go up, reading one needs a session and incrementing one needs the write role.
Can a License Written from LabVIEW Be Read by a Program in Another Language?
Yes. Every binding drives the same core library and the same dongle, and records and sealed data are language-neutral bytes. Your issuing tool can be written in one language and your product in another.
Code
VI library: bindings/labview/keynub_licdongle. Wiring instructions and flows: labview/README.md. Binding source: bindings/labview. Both are Apache-2.0, in the public SDK repository; the prebuilt native libraries are in the repository’s natives/ folder, one per platform.
All supported languages · All industries · Buy a KeyNub · Ask us something
