MEASUREMENT LOGGING SOFTWARE: BUILD A TRUSTWORTHY TEST RECORD
Editable planning/verification record — Yenra
Updated: October 2, 2026
Article: https://yenra.com/virtual-instrumentation-measurement-logging-software/

Purpose: Define channels, units, timestamps, calibration context, missing-data flags, and export checks so a saved run can be interpreted and reproduced.
Intended reader: Test engineers and technicians setting up PC-based data acquisition

HOW TO USE
Save a working copy. Enter the actual specification, units, assumptions and evidence references in each field. Preserve original observations and record changes. Have the responsible reviewer resolve missing or conflicting requirements before release. Examples below are fictional teaching inputs, not process settings or acceptance standards.

RECORD
1. Test ID, purpose, part revision and acceptance document:
   ____________________________________________________________

2. Channel name, physical input, sensor model/serial, units and range:
   ____________________________________________________________

3. Calibration reference, scaling equation and configuration revision:
   ____________________________________________________________

4. Hardware clock source, actual sample rate in samples/s/channel, trigger and synchronization:
   ____________________________________________________________

5. Timestamp meaning, time zone, start time and sample-index convention:
   ____________________________________________________________

6. Read-block size, buffer configuration, file format and rollover rules:
   ____________________________________________________________

7. Expected and observed samples per channel; gap indices and error events:
   ____________________________________________________________

8. Raw files, configuration export, checksums and read-back results:
   ____________________________________________________________

9. Derived result, analysis version, exclusions and reviewer:
   ____________________________________________________________


WORKED EXAMPLE AND LIMITS
FICTIONAL: A finite acquisition at 100 samples/s/channel for a 60 s acquisition window expects 6,000 samples per channel. With zero-based indices 0 through 5,999, a jump from 2,999 to 3,100 omits 100 samples (3,000 through 3,099), representing 1 s of missing scheduled samples. A channel with only this gap has 5,900 samples. Preserve the gap; do not silently interpolate it for acceptance analysis.

REVIEW
Prepared by / date: ____________________
Reviewed by / date: ____________________
Open issues, responsible owner, due date: ____________________
Approved next action and evidence: ____________________

SOURCE CONTEXT
These primary references support the linked article. Use exact applicable product, contract, and document versions for operational work.
NI documents TDMS file, group and channel properties
https://www.ni.com/en/support/documentation/supplemental/07/tdms-file-format-internal-structure.html
NI's DAQmx timing documentation
https://www.ni.com/en/support/documentation/supplemental/06/learn-10-functions-in-ni-daqmx-and-handle-80-percent-of-your-dat.html

Return to the guide: https://yenra.com/virtual-instrumentation-measurement-logging-software/