01-19-2022 05:16 PM
We saw something similar with a cDAQ-9185. This was caused by only having NI DAQmx Runtime installed. We added DAQmx Runtime with Configuration support and that solved the issue.