Brad Keryan
Brad Keryan
When you call add_di_chan or add_do_chan with name_to_assign_to_lines!="" and line_grouping==CHAN_FOR_ALL_LINES, two things happen: - The channel collection passes name_to_assign_to_lines to the DAQmx C API, which honors the user's requested channel...
The task subobject types (AIChannel, Timing, etc.) are defined in internal modules contained in the private `nidaqmx._task_modules` package. When users write helper functions that accept channel objects or other task...
`DAQmxWaitForValidTimestamp` returns the timestamp: https://www.ni.com/docs/en-US/bundle/ni-daqmx-c-api-ref/page/daqmxcfunc/daqmxwaitforvalidtimestamp.html So does `Task.WaitForValidTimestamp` in .NET: https://www.ni.com/docs/en-US/bundle/ni-daqmx-net-framework-40-api-ref/page/ninetdaqmxfx40ref/html/m_nationalinstruments_daqmx_task_waitforvalidtimestamp.htm And so do the interpreter classes: https://github.com/ni/nidaqmx-python/blob/master/generated/nidaqmx/_library_interpreter.py#L5831 But `Task.wait_for_valid_timestamp` does not return anything: https://github.com/ni/nidaqmx-python/blob/master/generated/nidaqmx/task/_task.py#L1035 Cc: @DeborahOoi96
Task.read doesn't slice the array for multi-channel power reads. Test case (from `tests/component/test_task_read_ai.py`, under development): ```python def test___power_multi_channel_finite___read_too_many_sample___returns_valid_2d_channels_samples_truncated( pwr_multi_channel_task: nidaqmx.Task, ) -> None: samples_to_acquire = 5 pwr_multi_channel_task.timing.cfg_samp_clk_timing(rate=1000.0, sample_mode=AcquisitionType.FINITE, samps_per_chan=samples_to_acquire) num_channels...
When `DAQmxReadAnalogF64` with `DAQmx_Val_GroupByChannel` returns fewer samples than requested, it squashes the valid samples together at the beginning of the buffer. The way that `nidaqmx.Task.read` handles short reads doesn't take...
For normal AI channels, leaving samples_to_read unset reduces the dimensions of the resulting list: - Single channel task: - task.read() -> scalar - task.read(1) -> 1D list by sample -...
In the DAQmx LV and C APIs, the raw read/write functions support all channel types including DIO and counters. However, the nidaqmx-python raw read/write methods (`task.in_stream.read` and `task.out_stream.write`) query AI/AO-specific...
Many of this package's docstrings incorrectly conflate `Optional[T]` with default arguments. `typing.Optional[T]` means "either a `T` or a `None`", which is orthogonal to whether the parameter has a default argument...
It would be nice if the docs for methods/properties that use `datetime`, `hightime`, and NumPy types had hyperlinks. We can enable this with the [intersphinx](https://www.sphinx-doc.org/en/master/usage/extensions/intersphinx.html) plugin. See https://github.com/ni/measurementlink-python/pull/430 for an...
- [ ] This contribution adheres to [CONTRIBUTING.md](https://github.com/ni/nidaqmx-python/blob/master/CONTRIBUTING.md). TODO: Check the above box with an 'x' indicating you've read and followed [CONTRIBUTING.md](https://github.com/ni/nidaqmx-python/blob/master/CONTRIBUTING.md). ### What does this Pull Request accomplish? This...