Error -209836

[zyash95]

Hey everyone, I am currently encountering an issue while attempting to read a voltage input signal through my cRIO 9048 system using LabVIEW version 2023 Q3. The voltage input is sourced from a Coriolis mass flow meter and is connected to an NI 9923 module in slot 2 of the cRIO. Upon attempting to implement the VI created for this purpose, I am encountering Error -209836. (Which is "The devices in your task cannot be synchronized. This may be because there are no available synchronization mechanisms between the devices.
Some synchronization paths are not available in interactive tools like the DAQ Assistant. To determine whether synchronization between these devices is possible, try deploying and executing your task in your application environment.)

Despite also trying to utilize an example VI provided in the LabVIEW documentation, I am still encountering the same error.

I have diligently followed the guidance provided in the NI documentation, ensuring that all drivers are installed correctly. However, the error persists.

One aspect worth noting is that the NI 9923 module in use is a Real-Time Resource module, rather than a Real-Time Scan module. Could this difference in module type potentially be contributing to the synchronization error?

Additionally, there is a known bug in LabVIEW 2023 Q3 that restricts the use of the DAQ Assistant through Express VI. Could this bug be related to the issue I am encountering with DAQmx, and if so, how?

I kindly request assistance in diagnosing and resolving this synchronization error. If further information about my system configuration is needed to facilitate troubleshooting, please do not hesitate to ask.

[ZYOng]

NI-9923 is the terminal block. You need to provide the actual model of the module inserted into slot 2.

You also mentioned using DAQ Assistant but you are attaching images related to Activation and DAQmx examples.

You need to provide your actual code that returns error -209836 for us to understand better.

[Bob_Schor]

Also, do provide complete VIs as either .vi files or as LabVIEW snippets, something we can open in LabVIEW, see all the code (not just a tiny piece that might not include the bug you are looking to fix), allow us to edit the code, even try to run it and figure out the problem.  You should also know that many long-time LabVIEW users who frequent these Forums are not using the "latest version", so you should probably "Save for Previous Version" and specify LabVIEW 2019 or 2021 (which most of us "long-timers" have available).

Bob Schor

[zyash95]

I apologize for the confusion. I have attached the correct picture of 'my VI' that I used for my application, along with the LabVIEW file for it. Additionally, I have included a screenshot (named '3') of my Project Tree, showing the NI module inserted in slot 2, which is the NI 9202.

To provide more context regarding the issue I encountered with DAQ Assistant:

Initially, I attempted to use DAQ Assistant (from Express VI) to read the voltage input signals, but encountered an error, as depicted in the screenshot named 'Error with DAQ assistant'. The steps I followed to set up the DAQ Assistant are outlined as follows:

1. Step 1 for setting up DAQ Assistant - navigating to acquire signals.
2. Step 2 for setting up DAQ Assistant - selecting Analog input as voltage.
3. Step 3 for setting up DAQ Assistant - choosing the physical channel Mod2-ai1.
4. Step 4 for setting up DAQ Assistant - changing the acquisition mode to continuous samples and observing the output in graph mode (showing 2 V input).
5. Step 5 for setting up DAQ Assistant - encountering an error after pressing 'OK' on the previous window.

(All Screenshots are attached in zip file with the name 'Steps for setting up DAQ assistant')

The solution suggested on the NI website is to install LabVIEW 2021. However, considering the inconvenience of uninstalling everything related to LabVIEW 2023 (the current version on my PC) and then installing everything related to LabVIEW 2021, I decided to try using DAQmx instead of DAQ Assistant.

Now, while using DAQmx, I'm encountering error -209836, as mentioned in my previous post.

I'm seeking assistance with resolving the error I'm facing using DAQmx (-209836).

As I'm relatively new to this field, I appreciate any guidance and suggestions. Thank you for your support and time.

[ZYOng]

I would recommend ditching DAQ Assistant.

Are you seeing error -209836 when using "My VI for voltage input measurement version 19.vi"?

[zyash95]

Yes, I have stopped using DAQ Assistant and now I am using DAQmx. The Error -209836 is faced while using DAQmx.

Yes I am using "My VI for voltage input measurement version 19.vi".

[GerdW]

Hi zyash,

---

@zyash95 wrote:

Yes I am using "My VI for voltage input measurement version 19.vi".

---

• When using "Continuous Samples" with a samle rate higher than ~100S/s then you should set a fixed amount of samples to read at DAQmxRead. I recommend to read 500 samples per iteration for your samplerate of 5kS/s.
• Delete the wait function inside your loop. It is not required AS SOON AS you set a fixed amount of samples to read!
• Don't stop and delete your task in parallel! Use DATAFLOW to stop first, then delete…

[ZYOng]

---

@zyash95 wrote:

Yes, I have stopped using DAQ Assistant and now I am using DAQmx. The Error -209836 is faced while using DAQmx.

Yes I am using "My VI for voltage input measurement version 19.vi".

---

Try these.

Error -209836 at DAQmx Timing: The Devices in Your Task Cannot Be Synchronized

Error -209836 in DAQmx Start Task on TSN-Enabled cRIO or cDAQ

[zyash95]

I want to express my gratitude to both of you for your prompt responses. Your assistance means a lot to me.

Despite implementing both of your suggestions, I'm still encountering the same issue. I've included screenshots of my updated VI for your review, along with the file itself. Kindly take a look.

To address this problem, I've taken the step of reinstalling LabVIEW, changing it to version 2021. However, as depicted in the screenshots, my VI continues to produce the same error. Additionally, I attempted to utilize the example VI provided in the LabVIEW documentation, only to encounter the same error.

I've reached out to NI support for assistance, but unfortunately, they haven't been able to offer much help.

Your continued support and guidance in resolving this issue means a lot to me. Thank you for your time.