03-07-2012 03:45 AM
Hello,
i try to generate finite samples with pci-6602,
I use CO Pulse Ticks + Implicit options
External pulses is 1PPS 1ms impulses from GPS trimble receiver
if i set number of pulses = 1, then i got pulse length = (High ticks -1)
if i set number of pulses >=2 and low ticks>=3, then i got pulse length = (High ticks)
if i set number of pulses >=2 and low ticks=2, then i got last puls width = (High ticks -1) and all other pulses with length = (High ticks)
With single pulse generation pulse width is (High ticks -1)
Are there any option to configure the same impulse width for any number of pulses for a finite train (N pulses)
screens in attach
Solved! Go to Solution.
03-07-2012 05:18 AM
03-07-2012 05:37 AM
I use labview 8.5 with daq-mx release June-2008
03-07-2012 01:54 PM
Do you have a system where you can try the program with a newer version of DAQmx? Dunno if it'll help, but it's the only thing I can think to try.
Can anyone from NI comment on whether this is a known issue or whether the behavior may be DAQmx-version dependent?
-Kevin P
03-07-2012 02:50 PM
03-08-2012 09:37 AM
hey AlexanderRyabov,
I'm interested in trying this out on my system with daqmx 9.4 on it to see if I get the same error. I don't have a 6602 (but might be able to find one if needed); however, I have an x-series and an m-series DAQ card in my computer right now. Thanks for attaching the screencaptures. This extremely helps. Is there any way you can attach the code or a more complete diagram of it? I'd like to run exactly what you're running to test it. I don't see indicators for the waveform charts you have at the bottom in your code.
Additionally, I'm not entirely sure if this is a bug that's been fixed in daqmx since the 8.0 version was a really long time ago. For now it looks like your coding is correct, so I think if you have an option to upgrade, I'd definitely check it out. One of the things you should note though is the daqmx/labview compatibility guide. it looks like you can get up to daqmx version 9.3 with LabVIEW 8.5.
03-08-2012 09:53 AM
03-09-2012 02:10 PM
Hey Alexander,
Posting that program could be helpful. Can you give us some more information or a summary of your overall application?
03-11-2012 03:52 AM
Hello all,
thanks for replies!
Let me describe my program.
The required program functionality:
generating pulse train of a given length and intervals
Pulse duration will be given from a range of 2 - 1000 seconds,
the intervals between pulses of 2 - 1000 seconds with 1 second step
pulses will be used for triggering other counter
an attachment program generates a pulse train of specified length and intervals from 1PPS timebase
the problem is:
If i set high ticks = 3, low ticks = 3, number of pulses = 2
i got 2 pulses with 3 seconds duration and 3 seconds pause between them
If i set high ticks = 3, low ticks = 3, number of pulses = 1
i got 1 puls with 2 seconds duration
I need to configure program to generate pulses the same duration for any number of pulses
I use digital oscilloscope (pci-6123) for pulse monitoring (in attach)
Connection diagram:
1PPS connected to AI-0 of PCI-6123 (oscilloscope) and PFI-31 of PCI-6602 (terminals 34 and 68, terminal block SCB-68)
PFI-28 of PCI-6602 (terminals 32 and 42) connected to AI-1 of PCI-6123 (oscilloscope)
Generating pulse train:
Channel parameters: Dev4/ctr2
Source of ticks: Dev4/PFI31
System devices:
pci-6123 "dev1"
enet-9215 "enet-1416895" (unplugged)
pci-6221 "dev2"
usb-6210 "dev3" (unplugged)
pci-6602 "dev4"
system:
NI-DAQmx 8.8
labview 8.5
03-12-2012 03:50 PM
Hey AlexanderRyabov,
Thanks for that additional information. It helps a whole lot in identifying what the problem actually is. I've been looking through it over here, and it doesn't look like any of the coding would be wrong. The number of high ticks does specify how many ticks the pulse would be high and low for how many ticks the pulse is low. I find it odd that you're getting other behavior than this.
I took a look at the original screencaps that you sent, and looking at the one called Finite Pulse 3 seems to be the one with the problem. Is this consistant every time you run it? If not, I wonder if it's somehow missing one of the ticks in there.
I did some digging on this end and found some similar bugs and issues related to these older versions of daqmx. I'm wondering if what you're seeing is something like those ones. Do you have access to test this on a machine with some more up-to-date software? I've been trying to find a 6602 to do some testing on this end, but haven't found anything. Please let us know.