Hello Frank,
As I am using VS2010 & targetting .NET framework 4.0, I took the 9.2.3.
NI-DAQmx Device Driver 9.2.3f1
NI-DAQmx ADE Support 9.2.3
NI-DAQmx MAX Configuration 9.2.3
Open up the solution and take a look at TestProject2 project.
Configure the const, which are pretty self describing:
DIO\DO.cs
private readonly string CONST_OUT_LINE_ADDRESS = "Dev4/Line32";
DIO.DI.cs
private readonly string CONST_IN_LINE_ADDRESS = "Dev5/Line0";
In that case, my DO card is a NI6514. I set the output line to use to be Dev4/Line32.
My
DI card is a NI6518. I set the input line to be Line0. Both are linked
together and it works fine using Measurement Automation Explorer.
Go
to UnitTest1.cs, TestMethod1(). Right click on TestMethod1 name and
select Run test. You should get the following error message :
Error TestMethod1 TestProject2 The agent process was stopped while the test was running.
If you run it in debug mode (CTRL + R,T), it NEVER step into the DigitalChangeDetection event. It even stop running after the call to Sleep without any particular message. (Debugger gets detached)
The
event should be fired after myDO.Write() has been called. I putted
breakpoint in : DIO\DI\myTask_DigitalChangeDetection. It never get
fired. That's the problem.
OTHERWISE, in the same solution, take a look at WindowsFormsApplication2 project.
It's the same exact code, only put in a different project type.
Configure the const, which are pretty self describing:
Form1.cs
private readonly string CONST_OUT_LINE_ADDRESS = "Dev4/Line32";
DI.cs
private readonly string CONST_IN_LINE_ADDRESS = "Dev5/Line0";
In that case, my DO card is a NI6514. I set the output line to use to be Dev4/Line32.
My
DI card is a NI6518. I set the input line to be Line0. Both are linked
together and it works fine using Measurement Automation Explorer.
If
you run the application, click START IN (which start the DI task) and
then click Start OUT (which start the DO task and write a change to
trigger DI DigitalChangeDetection event).
This works fine.
They
are both made from the sample applications provided by NI, which work
fine. They only difference is that one is being used in a UNIT TEST
project, the other on a regular Windows form project.
All my other
unit tests works fine, using Analog Input, Output and even DigitalInput
and Output when using a software timer to check for change. The ONLY
problem is when using DigitalChangeDetection.
Let me know if you need more explanation. I'm guessing it has to do with some background thread running on the driver side.
