NI-DAQmx Integration for Java

Use NI‑DAQmx from Java without writing JNI

NI has never shipped a Java API for NI-DAQmx. The driver exposes C, .NET, Python, and LabVIEW APIs — but not Java. If your test or measurement stack runs on the JVM, the usual workarounds are to hand-write JNI bindings against the C driver or run a separate Python service and stream readings across a process boundary. Both work. Both become the part of the project nobody wants to own.

JNBridgePro takes the third path: call NI’s NationalInstruments.DAQmx .NET API directly from your Java application with JNBridgePro-generated proxies. Discover devices, configure DAQ tasks, and acquire measurements — no custom JNI wrappers, no separate service layer.

View the Java demo guide See the full source →

Complete working example with step-by-step setup. Runs against an NI simulated DAQ device — no physical hardware required.

AnalogInDemo.java FROM THE WORKING DEMO
1// The NI-DAQmx .NET API, called directly from Java
2DaqSystem daq = DaqSystem.Get_Local();
3Task task = new Task();
4task.Get_AIChannels().CreateVoltageChannel(
5 daq.Get_Devices()[0] + "/ai0:3", "",
6 AITerminalConfiguration.Differential,
7 -10.0, 10.0, AIVoltageUnits.Volts);
8task.Get_Timing().ConfigureSampleClock("", 1000.0,
9 SampleClockActiveEdge.Rising,
10 SampleQuantityMode.FiniteSamples, 100);
11task.Start();
12double[][] data = new AnalogMultiChannelReader(
13 task.Get_Stream()).ReadMultiSample(100);
Runs against an NI simulated device
CONSOLE OUTPUT
Found device: Dev1 (NI simulated DAQ) Configuring 4 AI voltage channels… done Acquiring 100 samples @ 1000 Hz… done Ch 0: -0.2294 0.0558 1.4633 1.3437 … Ch 3: 0.6313 2.6854 0.3211 3.8001 … Done.
YOUR JAVA APPAnalogInDemo.java
BRIDGEJNBridgePro proxies
NI .NET ASSEMBLYNationalInstruments.DAQmx.dll

How It Works

Java-to-NI integration in 3 steps

JNBridgePro generates Java proxies for the NI-DAQmx .NET API. Your Java application calls the proxies naturally, and JNBridgePro handles communication with the underlying .NET classes and the NI-DAQmx driver.

Architecture at a glance

Your Java World
Java application Your existing code calls the proxies
JAR Generated proxy JAR Java proxies for NI‑DAQmx classes
The Bridge
JNBridgePro runtime Bridges calls between Java and .NET
The NI / .NET World
.NET NI-DAQmx .NET API NationalInstruments.DAQmx
NI-DAQmx driver Talks to the DAQ hardware
DAQ hardware Real device or NI simulated device

Your code never leaves Java — no JNI, no System.loadLibrary, no service layer to deploy.

The Process

1

Generate Java proxies

Point JNBridgePro at the NationalInstruments.DAQmx assembly. It analyzes the API and generates strongly typed Java proxy classes for the public types your application needs.

2

Add to your Java project

Add the generated proxy JAR and the JNBridgePro runtime to your application. Import the proxy packages like any other Java library.

3

Call NI-DAQmx from Java

Instantiate and use NI-DAQmx objects from Java. JNBridgePro invokes the corresponding .NET objects while the NI-DAQmx driver handles communication with the device.

No JNI. No service layer. Just Java.

Work with the full NI-DAQmx .NET object model directly from Java, with far less code to write, test, and maintain.

View the demo guide →

Use the Real NI .NET API

Leverage NationalInstruments.DAQmx classes directly from Java through generated proxies.

No JNI. No Service Layer.

Avoid the cost and complexity of handwritten JNI wrappers or maintaining a separate integration service.

Complete DAQ Workflows

Discover devices, configure tasks, acquire data, and process results entirely from Java.

Test Without Hardware

Use NI-DAQmx simulated devices to develop and validate your application before connecting real hardware.

Trusted by engineering teams worldwide

Boeing Bank of America IBM Swiss Re Progress