Skip to content

Waveform timestamps do not have enough precision for high AI Convert Clock rates #941

Description

@bkeryan

Bug Report

Waveform timestamps are returned from the DAQmx C API in .NET-style 100ns ticks, which is not high enough precision for high AI Convert Clock rates.

Repro or Code Sample

Add print(f"{time_offset:f}") to the updated voltage_acq_int_clk_plot_wfm.py from #940 and acquire Dev1/ai0:3 with a sample rate of 250e3.

Expected Behavior

Each channel has a unique time offset.

Current Behavior

Each channel has a time offset of 0.0.

0.000000
0.000000
0.000000
0.000000

Possible Solution

Fix internal bug AB#3229757

Context

Updating shipping example to plot multiple channels correctly

Your Environment

  • Operating system and version: Windows 11
  • NI-DAQmx version: 2026 Q2 dev build
  • nidaqmx-python version: 1.5.0 dev build
  • Python version: 3.11.7

AB#3782148

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions