09-25-2025 08:47 AM
Hi,
Curious if anyone has come across this error when configuring a cDAQ in Labview DCAF. When I go to run my "Host Main.vi" that comes standard in the project, I get a code -200277, which causes my UI to freeze up and not read any of my current inputs into the modules. The modules work fine in NI MAX, seems like the DAQmx module is not liking something in the configuration of the .pcfg file. I can't seem to find anything on this error code which might be due to DCAF no longer being supported.
Thanks.
Solved! Go to Solution.
09-25-2025 09:51 AM
I know no details about the "DCAF" framework nor what a .pcfg file might look like. But that error code is a little familiar, so here are some thoughts FWIW.
I don't think that error comes up much (if at all) when doing pretty vanilla DAQ tasks and letting DAQmx do the grunt work of buffer management. I'm only familiar with seeing it in cases where one is explicitly manipulating DAQmx Read properties such as "Offset" and "RelativeTo".
When these are changed manually, it's possible to make requests that are invalid, thus leading to the -200277 error. To save myself some typing, here's a thread where I've already described such things in more detail.
-Kevin P
09-26-2025 09:42 AM
How is the DAQ module configured in your DCAF project?
For Kevin, the pcfg file is just a configuration file loaded by DCAF that defines the execution of the DCAF engine. Somewhere in that configuration there's information that tells the DCAF framework to load the DAQ plugin and tells it how all channels/tasks should be configured.
09-26-2025 10:47 AM
Thank you Kevin. I might avoid the framework if it keeps happening. Without the framework I read analog inputs fine just using the daqmx read palette. Seems to only happen with my analog input cards. Reason for the framework is there are already established DAQ programs with it where I work, so they want to somewhat standardize it. But for some pretty basic reads, it seems overkill I think.
09-26-2025 10:52 AM
Attached are some screen captures of my configuration. If I remove all analog input cards and configure a boolean switch to toggle a digital out, my chassis works. Once I introduce the analog cards and configure them for sensors, the chassis never responds to anything. Just seems to display all default values for analog inputs and gives that error code.
09-26-2025 11:44 AM
It's likely overkill for simple DAQ readings. For the other DAQ programs where this is working do you know if they're also using the 9185/9189 or are they using other chassis/devices?
The configuration looks good so I wouldn't be surprised if this was an issue with the plugin itself.
09-26-2025 11:50 AM
Something in addition to my previous response. I was playing around with the DAQmx Module Data Rate parameter and initially had it around 10 Hz. Switched it to around 25K Hz and the error doesn't show up and my cards read fine but now the user interface is displaying at a much faster rate. Previous programs were set to around 10Hz, so unsure of the difference again.
09-26-2025 11:53 AM
It was the same model chassis. We tend to just stick with the ethernet cDAQ models. Another difference is previous programs were built on 22 version of labview and I've got 25 running on mine. It seems to like the 25K data rate, just way too fast for what I need now.
09-26-2025 12:03 PM
I haven't used DCAF in a while so you'll have to help me with where you set that data rate. I found the configuration section and after the DAQmx task is created and all the channels are added, this is how the read is configured.
When the module does the actual read it takes the AI task (this has all AI channels) and does a N-Channel 1-Sample read so it's trying to just read the latest sample that was acquired. If it doesn't work at 10Hz, there might be an issue if it does the read and then tries to do another read before any new data comes in.
09-26-2025 12:10 PM
It's located in the same daqmx module, just the last tab. Should one alter the module files to change the most recent input? Or best to avoid making changes to the plugin?