Measurement Studio for .NET Languages

cancel
Showing results for 
Search instead for 
Did you mean: 

PCI-6111 not responding to reference triggers

Solved!
Go to solution
Using the .NET (C#) DAQmx dirvers I am not getting a reference trigger when using a PCI-6111. I get the triggers fine with a PCI-6115 and PC-MIO-16. I was under the impression that the API was not device specific, so I am a bit surprised by the behaviour.
 
I previously ran into an issue with a few particular 6111s, and had to modify the code to get around that. I am assuming that the previous problem has been solved. Here is what I am doing:
 

foreach (int channelIndex in m_ActiveChannelList)

{

string channelName = string.Empty;

// Set this to -1 to let the NI driver decide which terminal configuration to use

int useDefaultTerminalConfig = -1;

// Get the name of the current channel

channelName = BASE_CHANNEL_NAME + channelIndex;

// Create the channel

m_DAQmxTask.AIChannels.CreateVoltageChannel(m_Device.AIPhysicalChannels[channelIndex], channelName, (

AITerminalConfiguration)useDefaultTerminalConfig,

-10.0, 10.0,

AIVoltageUnits.Volts);

}

 

foreach (AIChannel curChannel in m_DAQmxTask.AIChannels)

{

curChannel.DataTransferMechanism =

AIDataTransferMechanism.Interrupts;

}

// Setup the sample clock

m_DAQmxTask.Timing.ConfigureSampleClock(

string.Empty, m_ClockFrequency, SampleClockActiveEdge.Rising,

SampleQuantityMode.FiniteSamples, m_NScans);

// Setup the reference trigger

m_DAQmxTask.Triggers.ReferenceTrigger.ConfigureDigitalEdgeTrigger(

"PFI1", DigitalEdgeReferenceTriggerEdge.Rising, m_PreTriggersScans);

// Set the time out

m_DAQmxTask.Stream.Timeout = (m_Timeout * 1000) - 500;

0 Kudos
Message 1 of 3
(3,962 Views)
Hello All,

Tyzack has contacted National Instruments directly for Technical Support. I will post a resolution to this issue when we determine one, but I encourage users with any insight to post any ideas they may have.

Matt Anderson

Hardware Services Marketing Manager
National Instruments
0 Kudos
Message 2 of 3
(3,925 Views)
Solution
Accepted by topic author Tyzack
This appears to have been related to a faulty board.
0 Kudos
Message 3 of 3
(3,823 Views)