Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

NI-DAQmx DAQ Devices

by K-Dense-AIversion 0.1.2i★ 32 (Stars for the whole repo)iRuns on your computerRepository ↗
Registry nameio.github.K-Dense-AI/labmcp-ni-daqmx

How to install

What it does

MCP server for National Instruments DAQ devices (NI-DAQmx).

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness7/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score7/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install NI-DAQmx DAQ Devices. Follow https://mcp.popnx.com/i/k-dense-ai-labmcp-ni-daqmx.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server NI-DAQmx DAQ Devices for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "labmcp-ni-daqmx": { "command": "uvx", "args": [ "labmcp-ni-daqmx" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the NI-DAQmx DAQ Devices tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "labmcp-ni-daqmx": {
          "command": "uvx",
          "args": [
            "labmcp-ni-daqmx"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use NI-DAQmx DAQ Devices and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using NI-DAQmx DAQ Devices or shows a NI-DAQmx DAQ Devices tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • LABMCP_ADDRESS Instrument address, e.g. serial:///dev/ttyUSB0 or tcp://192.168.1.50:5025
  • LABMCP_SIMULATE Set to 1 to use the built-in simulator (no hardware)
  • LABMCP_READ_ONLY Set to 1 to disable all state-changing tools
  • LABMCP_LIMITS Safety limit overrides, e.g. max_temperature_c=80

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect NI-DAQmx DAQ Devices yet

NI-DAQmx DAQ Devices runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect NI-DAQmx DAQ Devices

  • Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Python (uv) on your computer first (one time)
  • Install Python (uv) on your computer first (one time)
  • Install Python (uv) on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server NI-DAQmx DAQ Devices for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user labmcp-ni-daqmx -- uvx labmcp-ni-daqmx 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the NI-DAQmx DAQ Devices tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user labmcp-ni-daqmx -- uvx labmcp-ni-daqmx
  4. Type /mcp in Claude Code

    You should see NI-DAQmx DAQ Devices listed as connected

  5. Try it

    Use NI-DAQmx DAQ Devices and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using NI-DAQmx DAQ Devices or shows a NI-DAQmx DAQ Devices tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • LABMCP_ADDRESS Instrument address, e.g. serial:///dev/ttyUSB0 or tcp://192.168.1.50:5025
  • LABMCP_SIMULATE Set to 1 to use the built-in simulator (no hardware)
  • LABMCP_READ_ONLY Set to 1 to disable all state-changing tools
  • LABMCP_LIMITS Safety limit overrides, e.g. max_temperature_c=80

Descriptions are as written by the maker.

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server NI-DAQmx DAQ Devices for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "labmcp-ni-daqmx": { "command": "uvx", "args": [ "labmcp-ni-daqmx" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the NI-DAQmx DAQ Devices tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use NI-DAQmx DAQ Devices and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using NI-DAQmx DAQ Devices or shows a NI-DAQmx DAQ Devices tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • LABMCP_ADDRESS Instrument address, e.g. serial:///dev/ttyUSB0 or tcp://192.168.1.50:5025
  • LABMCP_SIMULATE Set to 1 to use the built-in simulator (no hardware)
  • LABMCP_READ_ONLY Set to 1 to disable all state-changing tools
  • LABMCP_LIMITS Safety limit overrides, e.g. max_temperature_c=80

Descriptions are as written by the maker.

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server NI-DAQmx DAQ Devices for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "labmcp-ni-daqmx": { "type": "stdio", "command": "uvx", "args": [ "labmcp-ni-daqmx" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the NI-DAQmx DAQ Devices tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use NI-DAQmx DAQ Devices and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using NI-DAQmx DAQ Devices or shows a NI-DAQmx DAQ Devices tool in the answer, you are connected

4 optional setting(s) (works without them)

The command above works without these. Add them only if you want to change something, following the maker’s description.

  • LABMCP_ADDRESS Instrument address, e.g. serial:///dev/ttyUSB0 or tcp://192.168.1.50:5025
  • LABMCP_SIMULATE Set to 1 to use the built-in simulator (no hardware)
  • LABMCP_READ_ONLY Set to 1 to disable all state-changing tools
  • LABMCP_LIMITS Safety limit overrides, e.g. max_temperature_c=80

Descriptions are as written by the maker.

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use NI-DAQmx DAQ Devices💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user labmcp-ni-daqmx -- uvx labmcp-ni-daqmx

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "labmcp-ni-daqmx": {
      "command": "uvx",
      "args": [
        "labmcp-ni-daqmx"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "labmcp-ni-daqmx": {
      "command": "uvx",
      "args": [
        "labmcp-ni-daqmx"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "labmcp-ni-daqmx": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "labmcp-ni-daqmx"
      ]
    }
  }
}

Values you fill in

  • LABMCP_ADDRESS env
    Instrument address, e.g. serial:///dev/ttyUSB0 or tcp://192.168.1.50:5025
  • LABMCP_SIMULATE env
    Set to 1 to use the built-in simulator (no hardware)
  • LABMCP_READ_ONLY env
    Set to 1 to disable all state-changing tools
  • LABMCP_LIMITS env
    Safety limit overrides, e.g. max_temperature_c=80

Descriptions are as written by the maker.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

GitHub starsi
32 (Stars for the whole repo)
This repo holds several MCP listings; its stars count once in rankings
Downloads per weeki
35/wk
Licencei
Apache-2.0
Connection
Runs on your computer
Latest versioni
0.1.2
Categoryi
Other
Published to registryi
Sep 27, 2026
Code last changedi
Sep 27, 2026
Maker
K-Dense-AI
Packages
pypi: labmcp-ni-daqmx
Website
github.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account K-Dense-AI, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 months ago

  • ✓ Pass

    Has a licence

    Uses Apache-2.0

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for labmcp-ni-daqmx@0.1.2

Checks only this package version, not every dependency · checked Nov 16, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/k-dense-ai-labmcp-ni-daqmx.svg)](https://mcp.popnx.com/en/servers/k-dense-ai-labmcp-ni-daqmx)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 0% of the other 20653 servers in this category
  • Published to the registry more recently than 45% of the other 20653 servers in this category
  • Basic checks equal to or better than 99% of the other 20653 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is NI-DAQmx DAQ Devices safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 2 months ago, and the latest version (0.1.2) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
NI-DAQmx DAQ Devices
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseApache-2.0AGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

NI-DAQmx DAQ Devices — MCP Server

Let an AI agent acquire voltages and thermocouple temperatures, read digital lines and (with your permission) set analog and digital outputs on National Instruments DAQ hardware through the official NI-DAQmx driver and its Python API.

Packagelabmcp-ni-daqmx
InstrumentsNI-DAQmx devices: USB-6001/6002/6003, USB-6008/6009, USB-6211/6212/6218, USB/PCIe M and X Series (62xx/63xx), CompactDAQ C Series modules (e.g. NI 9201, 9211, 9263, 9401), NI MAX simulated devices
InterfacesUSB, PCI/PCIe, PXI, Ethernet (cDAQ chassis)
ProtocolNI-DAQmx via the nidaqmx Python API (API docs, source, NI-DAQmx driver)
Status🧪 simulated: tested against a simulated nidaqmx backend, not yet verified on hardware. Report a hardware test

Try it without hardware

uvx labmcp-ni-daqmx --simulate --check

The built-in simulator is a USB-6341-like X Series device Dev1: a 1 V / 50 Hz sine on ai0, a 2.5 V sensor on ai1, ao0/ao1 looped back to ai2/ai3, a ~37 °C thermocouple on ai4, and an external "interlock" holding port1/line0 high. It reproduces NI-DAQmx behaviour such as error codes (e.g. -200170 channel does not exist, -200576 no built-in CJC) and the shapes task.read() returns.

Testing the real NI-DAQmx path without hardware: in NI MAX (Windows) choose *Devices and Interfaces → Create New… → Simulated NI-DAQmx Device*, then run the server *without* --simulate against that device, e.g. --address SimDev1. NI MAX simulated devices return synthetic data, and get_connection_info reports ni_max_simulated_device: True. On Linux, simulated-device support is limited (NI's configuration tools can import a configuration file that defines one, with mixed results); use --simulate there.

Connect your instrument

  1. Install NI-DAQmx (Windows or Linux; macOS is not supported by NI-DAQmx) from ni.com. The nidaqmx Python package is installed with this server; python -m nidaqmx installdriver can also install the driver.
  2. Find the device name in NI MAX (*Devices and Interfaces*) or with nilsdev on Linux, e.g. Dev1 or cDAQ1Mod1. Close NI MAX test panels before connecting.
  3. Test the connection:
   uvx labmcp-ni-daqmx --check                    # works if exactly one device is present

uvx labmcp-ni-daqmx --address Dev1 --check

   `--address` is the NI-DAQmx device name. It is optional when exactly one device exists.

Add to your MCP client

Claude Code

claude mcp add ni-daq -- uvx labmcp-ni-daqmx --address Dev1

Claude Desktop / Cursor / Windsurf (claude_desktop_config.json, .cursor/mcp.json, …)

{

"mcpServers": { "ni-daq": { "command": "uvx", "args": ["labmcp-ni-daqmx", "--address", "Dev1"] } } }

Add --read-only to allow acquisitions but block the output tools (set_outputs_safe stays available). Add --option safe_do_lines=port0/line0:3 to make set_outputs_safe always drive those lines low. For other clients, generate the snippet with uvx labmcp config ni-daqmx --address Dev1 --client vscode (also cursor, codex, claude-code).

Tools

ToolKindDescription
get_command_log👁 readReturn the most recent raw commands sent to / replies received from the instrument (newest last). Useful for debugging and for recording what was done.
get_connection_info👁 readReport which instrument is connected (identity, address, simulated or real), whether the server is read-only, and the active safety limits. Call this first.
get_device_info👁 readDescribe the connected device: analog input/output channels, digital lines, supported voltage ranges, maximum sample rates, and the outputs this server has set. Call this before choosing channels, ranges and rates.
list_devices👁 readList every NI-DAQmx device the driver can see (product type, serial number, channels, whether it is an NI MAX simulated device) and which one this server is connected to.
read_analog👁 readMeasure voltage on one or more analog inputs: a single on-demand reading, or a finite hardware-timed acquisition of samples per channel at rate_hz. Returns per-channel statistics and a downsampled waveform; optionally saves all data to CSV.
read_digital_lines👁 readRead the logic level of digital lines.
read_thermocouple👁 readMeasure temperature (°C) with thermocouples (types B, E, J, K, N, R, S, T) on a thermocouple-capable device, e.g. an NI 9211/9212/9213/9214 module or USB-TC01.
reconnect🛑 safetyClose and re-open the connection to the instrument (e.g. after it was power cycled or a cable was re-plugged).
set_outputs_safe🛑 safetyPut the device's outputs in a safe state: every analog output to 0 V (or the bottom of its range if 0 V is not in it) and, by default, every digital line this server drove - plus the safe_do_lines option lines - driven low. Use when finished or if anything looks wrong.
write_analog⚠️ hazardSet an analog output to a DC voltage (static, software-timed). The output keeps this value after the call on most NI devices, until changed or set_outputs_safe is called.
write_digital_lines⚠️ hazardDrive digital output lines high or low. The lines keep their level after the call until changed or set_outputs_safe is called.

get_connection_info, get_command_log and reconnect are built into every LabMCP server. The command log records every task the server ran (channels, ranges, rates, values written).

Safety limits

LimitDefaultMeaning
max_ao_voltage_v5 VLargest \voltage\an agent may put on an analog output
max_samples100 000Most samples per channel in one acquisition
max_rate_hz100 000 HzHighest sample clock rate per channel
max_acquisition_s60 sLongest finite acquisition (samples / rate)

Override at launch, e.g. --limit max_ao_voltage_v=10 --limit max_acquisition_s=300. Limits are checked before anything is sent. The device's own AO range is also enforced (e.g. USB-6008/6009 outputs 0-5 V only), as are its maximum sample rates.

Example prompts

  • "List the NI devices and tell me which inputs Dev1 has and their voltage ranges."
  • "Acquire ai0 and ai1 differentially at 10 kHz for 0.5 s on the ±1 V range and give me the RMS noise of each; save the data to ~/daq/noise.csv."
  • "Read the type K thermocouples on cDAQ1Mod1/ai0:3 once a second for 30 seconds using the built-in CJC and report the average of each."
  • "Set ao0 to 2.0 V, confirm it on the ai2 loopback, then set it back to 0."
  • "Is the interlock on port1/line0 closed? Then switch port0/line2 high to open the valve."
  • "We're done: put every output in a safe state."

Notes

  • Every tool call is one short DAQmx task (create channels, configure timing, read or write, close), as in NI's examples, so the server never holds the device reserved between calls. Another program using the device at the same time causes a clear "resource reserved" error (-50103). Output and digital-line tasks are serialised separately from acquisitions, so set_outputs_safe (and write_analog) never wait for a running acquisition to finish: NI-DAQmx runs an analog-input task and AO/DIO tasks on the same device side by side.
  • Acquisitions are capped at 600 s per tool call even if max_acquisition_s is raised. The returned waveform is downsampled by keeping each block's minimum and maximum, so short spikes are not lost. save_path must be a new .csv file: it is checked before acquiring, and an existing file is never overwritten.
  • Outputs hold their value after the task closes on most NI devices, which is what the output tools rely on. Some devices have configurable idle/power-up output behaviour; check your device if it resets outputs.
  • Reading a digital line can change it. A DAQmx digital-input task configures the line as an input. The server therefore reports lines it is driving from their last commanded level instead of reading them, and documents the risk for lines driven by other software.
  • Terminal configuration matters. default lets NI-DAQmx choose (often differential where supported). A wrong choice gives offsets or noise rather than an error.
  • Thermocouples use add_ai_thrmcpl_chan with built-in or constant cold-junction compensation. A CJC *channel* (SCANNABLE_CHANNEL) is not offered in this version because its correct use depends on the device.
  • Rates: multiplexed devices share ai_max_multi_channel_rate_hz across channels, and NI-DAQmx coerces the sample clock to a rate the timebase can produce. The actual rate is returned in sample_rate_hz.
  • NI-DAQmx warnings (e.g. about coerced values) are returned in each acquisition's warnings list.

Hardware verification

ModelNI-DAQmx versionInterfaceVerified byDate
*none yet: be the first*