NI-HSDIO Returns Error -1074115594 During Multi-Record Acquisition

Updated Sep 28, 2026

Reported In

Hardware

  • PXIe-6547
  • PXIe-6544
  • PXIe-6545
  • PXIe-6548
  • PXIe-6556
  • PXIe-6555

Driver

  • NI-HSDIO

Issue Details

I am performing a multi-record acquisition using an NI-HSDIO device at a high trigger rate.
 
The acquisition consistently stops after approximately 100000 records and returns the following error:

 
The behavior is reproducible and occurs when acquiring a large number of records at high retrigger rates.

Solution

NI-HSDIO devices use a dedicated timestamp buffer when performing multi-record acquisitions. In multi-record mode, a timestamp is automatically generated for each acquired record and stored separately from the onboard sample memory. Timestamp generation cannot be disabled.
 
At high retrigger rates, timestamps may be generated faster than they can be transferred from the device. When the timestamp buffer capacity is exceeded, NI-HSDIO returns the error.
 
To avoid this limitation:
  1. Configure the acquisition as a single continuous record instead of a multi-record acquisition.
  2. Acquire the total number of required samples within the continuous record.
  3. Fetch the contiguous sample stream using the appropriate NI-HSDIO fetch function.
  4. Export or store the continuous acquisition and use external analysis software to separate individual packets or bursts based on known sample counts or timing information.
This approach eliminates dependency on the per-record timestamp buffer used by multi-record acquisitions.

Additional Information

Multi-record acquisitions on NI-HSDIO devices use a dedicated timestamp buffer that is separate from onboard sample memory. Applications that acquire large numbers of records at high retrigger rates can reach the timestamp-buffer limit before reaching the available sample-memory capacity.
 
Because a timestamp is generated for every record in multi-record mode, the maximum achievable record count may be limited by timestamp-buffer capacity rather than onboard memory capacity.