PCI 6602 signal no periodic

bonjour,
je voudrais simuler un signal non périodique et synchrone sur une seul des sorties de compteur de la PCI-6602.
Cependant j arrive a simuler mon signal mais j utilise deux compteurs :
pour cela j ai utilisé un des sous VI de multiple pulse train c est a dire "configure and arm counters phase(NI-TIO)(with phase delayed)"
mais j ai enlevé le sous vi "counters start triggers "
j'ai voulu synchronisé mon signal via un generateur externe dont j ai definie les parametres dans le diagramme de mon vi (numero de PFI).Puis j'ai décomposer mon signal en 2(voir attached files).Une fois que je suis arrivé a visionné mes signaux sur l'oscilloscope,
j ai relier mes 2 signaux a une "porte ou" à 2 entrées.
soit S la sortie de la porte l
ogique on obtient donc:
S = compteurs 0 ou compteur 1
merci""
Attachments:
chronogramme_des_signaux.doc ‏22 KB

With this setting, the edges of the internal 20MHz timebase of the PCI-6602 are counted !
Change Edge Source to /Dev1/PFI39 (--> CTR 0 source --> signal A of the encoder with your wiring) and try again.
See page 3-7 of the user manual for the PFI numbers.
Some examples ship with LabVIEW.
Message Edité par JB le 03-13-2008 08:44 AM

Similar Messages

Multi counter PCI 6602 daqmx semi period measurement

Hi All, Currently I am working on 20 PWM input channels. I have some problem on my labview code. Would some one give some advice on my vi? I crated labview code for 2 channels for now. I am doing semi period measurement. I want to measure the frequency and duty cycle of the PWM signals. But when I run it, it has error. Please give some advice where I did wrong on my vi. thanks Johnny
Solved!
Go to Solution.
Attachments:
Multi PWM Reading.vi ‏118 KB
erorr message.doc ‏91 KB

Hi marconi,
This error that you are getting is a buffer overflow error and is likely due to the value that you used as an input to "number of samples" on the DAQmx Read VI. You had it set to 4 but depending on how fast the PWM that you are reading is, you may be acquiring values to the onboard buffer much faster than you are retrieving them with the DAQmx Read VI. Then when you call the DAQmx Read VI, which reads relative to a read pointer the data that you are expecting to read from the buffer has already been overwritten. One way to get around this is to increase the number of samples to read each time you call the DAQmx Read VI. I tried out your VI and got it to work with a slight modification to the start trigger (using PFI0 instead of the 20MHz timebase) and added a loop condition to stop from getting a buffer underflow error as well. Take a look and see if this helps out. Also, why are you triggering off the 20MHz timebase? is there a particular reason? This is essentially like using no start trigger since you should get the first rising edge of that almost immediately after the DAQmx Start VI is called. I am just curious, since using this start trigger did not actually work for me (though I didn't look into why).
Chris W
Attachments:
Multi PWM Reading.vi ‏51 KB

NI PCI-6602: semi-period measurement stops unexpectedly or returns wrong values

Hi,
Using an NI PCI-6602 card we try to measure the semi-periods of a digital signal.
In "continuous sampling mode", 10 samples are collected in the buffer and then are read
out.
Up to 6 counters on this card are sampling the same signal in our testing configuration.
Here we found these issues:
1. Failure
In principle, the measurement runs correctly, but one or more counters sporadically may
suffer a complete failure. I.e. these counters don't provide samples anymore.
Only after stopping and restarting the assigned task, a failed counter works again.
Apparently, a counter failure is most likely to happen when
    - the sampled signal "changes", i.e. when the pulse width of the signal changes,
    - or when the computer load is high, e.g. when opening a window of another application.
Every counter occasionally failed, but the issue was found very often at counter 1 of
the PCI-6602 card, if we used counters 0 through 5 in parallel.
Using another PCI-6602 card, the failures happened preferably on counters labeled "near"
number 5.
2. Wrong values
Occasionally the "interpretation" of the sampled values changes, i.e. the length of the
"high level" period is returned, where the "low level" period length should be given, and
vice versa.
This is our task configuration:
Configuration done with MAX:
Signal input range:    2 usec - 2 sec
Custom Scaling:        None
Sample mode:        continuous
Buffer size:        10 Samples
In addition these calls are made:
ret = DAQmxSetDigEdgeArmStartTrigSrc( task->mHandle, <use the same terminal as is used for
the signal to be measured>);
ret = DAQmxSetArmStartTrigType( task->mHandle, DAQmx_Val_DigEdge);
ret = DAQmxSetDigEdgeArmStartTrigEdge( task->mHandle, DAQmx_Val_Rising);
ret = DAQmxSetCISemiPeriodStartingEdge( task->mHandle, <the channel>, DAQmx_Val_Falling);
Best regards
Manfred

Hi Manfred7,
did you already test this behaviour with a simple example from us?
Just go through the example database and try the examples there.
These examples should work.
If it works, there is a problem with your programm.
If it won't work, please tell me more about your software:
- Version
- DAQmx Version ,...
best regards
Dippi

PCI-6602 comment generer un signal non peridodique

"bonjour,
je voudrais simuler un signal non périodique et synchrone sur une seul des sorties de compteur de la PCI-6602.
Cependant j arrive a simuler mon signal mais j utilise deux compteurs :
pour cela j ai utilisé un des sous VI de multiple pulse train c est a dire "configure and arm counters phase(NI-TIO)(with phase delayed)"
mais j ai enlevé le sous vi "counters start triggers "
j'ai voulu synchronisé mon signal via un generateur externe dont j ai definie les parametres dans le diagramme de mon vi (numero de PFI).Puis j'ai décomposer mon signal en 2(voir attached files).Une fois que je suis arrivé a visionné mes signaux sur l'oscilloscope,
j ai relier mes 2 signaux a une "porte ou" à 2 entrées.
soit S
la sortie de la porte logique on obtient donc:
S = compteurs 0 ou compteur 1
merci"
Attachments:
chronogramme_des_signaux.doc ‏22 KB

Je ne parle plus le francais. Il y a 20 ans depuis je l'etudie. Je pense que je peux vous aider, mais seulement en englais.
S'il vous plait, trouvez quelqu'un qui peut lire l'englais et expliquer mon reponse ici:
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=50650000000800000059CD0000&UCATEGORY_0=_32_%24_12_&UCATEGORY_S=0
Bon chance!

Frequency divide by N doesn't work on Counter-Timer PCI-6602

Hello everybody,
I tried to do something basic ( ?) with this Counter-Timer 6602 Board, and it doesn’t work.
So I hope some people with more experience than me could understand what happens here.
1) What I need:
I need to generate 4 synchonised clocks, whose periods will be multiple of 1 ms.
2) What I have:
LabVIEW 7.0 and a PCI-6602 Counter-Timer Board in a DELL PC running under XP pro.
The PCI-6602 Counter-Timer Board has 8 counter timers named CTR 0, CTR 1, ... CTR7.
3) What I have already done, and that worked:
- Generate a 1 kHz “Master Clock” signal from CTR 4, configured by “Continuous Pulse Generator Config.vi” (found in “Data Acquisition, Counters...).
- configure CTR 0 and CTR 1 to work as frequency dividers, by use of “Down Counter or Divider Config.vi”.
- Apply the output signal of CTR 4 (OUT ) to the SOURCE inputs of CTR 0 and CTR 1 by means of physical wiring in the SCB-68 connection box.
When I do this, I get two nice secondary clock signals on my oscilloscope screen, ( with periods = 3 ms, or 5 ms or whatever multiples of 1 ms I choose) from CTR 0 and CTR 1 outputs , very clean and perfectly in phase with the 1 kHz Master Clock.
So far, so good...
But I still need 2 more secondary clocks...
One would say: “No problem, do the same trick with two other counters...” Well, not so simple, it seems...
4) What I tried to do, and that didn’t work:
When I try to do the same frequency division with any of the remaining counters, (CTR2 to CTR7), the program stops and I get an error “ –10020 : Time base not valid “.
I can’t figure out what happens here: I thought any counter could be configured to work as a frequency divider, but it seems not to be so, and I am stuck here.
Has anyone an idea about how to fix this type of problem?
Attached file: hor_div02New.vi
Attachments:
hor_div02New.vi ‏123 KB

karolik,
I'm just adding a followup in English. As Marc L. mentioned, the particular vi named "Down Counter or Divider Config" isn't compatible with the 6602. While the 6602 does have the ability to generate 4 synchronized clocks, a different syntax is needed. Here's how I'd do it:
Traditional NI-DAQ
1. Configure a continuous pulsetrain on CTR 4. Route its output to, say, RTSI 4. Don't start it yet.
2. Configure CTR 0,1,2,3 for continuous pulsetrains using RTSI 4 as their "timebase source." Start them.
3. Start the CTR 4 pulsetrain.
4. Now CTR's 0-3 should generate separate clocks with synchronized phasing.
DAQmx
1. Configure a continuous pulsetrain on CTR 4. Don't start it yet.
2. Configure CTR 0,1,2,3 for continuous pulsetrains using "Ticks" for units. Use a DAQmx property node (probably Channel property node, but am not 100% sure and don't have a LV PC handy to check) to specify that the "ctr4 internal output" should be used as the timebase. Start them.
3. Start the CTR 4 pulsetrain.
4. Now CTR's 0-3 should generate separate clocks with synchronized phasing.
-Kevin P.

Alternative to PCI-6023E + PCI-6602

Hello,
I am already using a system to acquire 16 analog inputs data (at 50Hz) and 100Hz PWM signals (counters) and to send 100Hz PWM signals to external devices. Because it deals with 12 concurrent counters I bought 2 x PCI-6602 counter boards on top of a PCI-6023E for the 16 analog inputs (through a SC2345 box). This works all well.
I now have to build a simplified and portable solution that has to run on a laptop. I was thinking about a DAQ-6036E or DAQ-6024E (or even DAQ-6062E) and keep a SC2345 but do not know if I will get the same functionalities particularly for the PWM counting (in and out). I have to be able to count the high edge of the square signal at 100Hz while acquiring my analog inputs; also be able to generate those 100Hz signals. Will I be able to connect my counter in and counter out (one of each) to the SC2345 to do that?
Thanks for your comments,
Christophe

Hello Christ0phe,
Looking at your current specifications and hardware, the best suitable solution for a portable appication with >2 counters would be the Compact RIO Platform.
As this is an FPGA based platform, you can implement (theoretically) as much counters for PWM generation and reading as you want.
As you are an existing DAQ user, you will not be able to reuse your existing code. The cRIO platform uses the NI-RIO driver which is using some different program logic than the NI-DAQmx driver.
Why is the Compact RIO platform the best solution?
Well, the cRIO chassis can be powered by a simply DC power supply. Depending which chassis this is between 9 and 30 VDC.
The cRIO platform also has a dedicated controller inside which will run your LabVIEW code. The PWM logic itself can run on the FPGA integrated in the cRIO chassis.
So, the laptop will not be use for any calculation, only for monitoring and control of your application.
If you want to stay with the NI DAQ plaform I see two other portable solutions:
The first one is to make the swtich to the PXI platform.
There is a small chassis (PXI-1033) which has an integrated MXI-interface. Using MXI technology, you can control a PXI chassis from another PC, including a laptop (using ExpressCard, not PCMCIA).
For the PXI platform you can use identical or similar DAQ boards as you have now, reusing your existing LabVIEW code.
Drawback of the PXI-1033 is that it can only be powered by 230VAC, you will have to provide a DC-to 230VAC converter yourself to be able to use it in the field.
For your information. It's becoming harder and harder to find laptops with PCMCIA slots, ExpressCard is the successor available on most new laptops.
But please have a look at following article concerning laptop compatibility: http://zone.ni.com/devzone/cda/tut/p/id/5035
A last solution is to use the cDAQ plaform.
Again a fully portable DAQ solution, but as it uses the same technology as the 'normal' DAQ boards, it only has 2 counters on board.
As your PWM speeds are quite slow, it may although be possible to use this platform for multiple PWM signal generation and reading. All will depend on the desired PWM accuracy (resolution) and if they all share the same signal period.
It is possible to use the 2 on-board counters as a known sample clock to generate and read the PWM pulses using correlated DIO.
Correlated DIO means that your digital input and output signals are hardware clocked (synchronized with other available clock source). On the cDAQ platform, your I/O modules must be placed in slot 1-4 of the cDAQ chassis to be able to use correlated DIO. Possible I/O modules are in the C-series 940x range.
Drawback: all your calculations have to be done on the fly in LabVIEW. You will need to write code to generate an array
of digital waveform data, then output it using hardware timed DIO
synchronized to generate counter clock. For the readout of the PWM signal, you will have to count (within the LV application) the number of tick (of pulses) of the sample clock during which the PWM signal was 'high' and calculate based on the known timing information the PWM on-time, period (and if needed duty cycle).
More info about cDAQ and Correlated DIO:
NI-DAQmx: Correlated Digital I/O with NI CompactDAQ and LabVIEW
Can I Use Different Sample Clocks for Correlated DI and DO?
Some examples exist:
CompactDAQ - Generating More Than 2 Pulse Trains
NI-DAQmx: Digital Channel Pulse Width Modulation (PWM)
This info should already help you make a selection.
But please contact you local National Instruments office if you need more information.
Best regards,
Best regards,
Joeri
National Instruments
Applications Engineering
http://www.ni.com/ask
Make our forums great:
If you like the answer, don't forget to "Kudos!".
"Accept the Solution" if your question is answered!

Conceptual problem in using a PCI-6602?

Hi, All You Wild and Crazy NI/LabVIEW Types --
I have a problem that's been close to sending me off the deep end for more than a month now, and I think that I'm so enmeshed in it that I can't see the forest for the trees anymore. I'd like to apologize in advance for the length of this post, but there are some details that might or might not be important, and I'd rather make the mistake of giving you too much information than not enough.
We do impact-cratering experiments, using a gun to launch (usually) spherical projectiles at a variety of targets. One of our big efforts is to measure the velocities at which material is ejected from growing craters. We do that with a line-generating laser, oriented so the "sheet" of laser light is perpendicular to the target's surface and through the impact point; we strobe the laser at a programmed rate (with our PCI-6259 board) and take a time exposure of the scene with a Nikon D100 DSLR. When target material -- usually grains of sand -- is ejected, the laser illuminates a "slice" through the curtain of ejecta, illuminating a small portion of the fragments numerous times in their trajectories. Since we know the scale of the photograph and its orientation relative to the laser's illumination, and we also know the rate at which the laser is flashing, we can easily calculate the velocities of the illuminated particles. I'm attaching a picture (file 4044, cropped.jpg) of an example taken with an older camera to give you an idea. In the picture, the laser's illuminating the scene from the right of the frame and the projectile flew into the picture from the top of the frame, traveling along the left-hand edge. The brightest portion is the flash from the impact, and the rest of the parabolic trajectories are the grains of sand in flight. The target bucket, full of coarse sand, is the elliptical looking cylinder at the bottom of the picture. It's roughly 28 cm in outside diameter, if you'd like a scale.
As you might imagine, with our projectiles moving anywhere between 0.7 and 3 km/s, sequencing everything is pretty important. We're using (or trying to use) LabVIEW to do all of the sequencing, instrument control, and data storage. Things are going pretty well so far, except for what I'll describe in more detail below. A couple more things, though, first. It's important that we measure the projectile's speed in each shot, as that controls impact energy and momentum, which are critical to know in a given experiment. We do that with simple laser-photodetector pairs (which we normally call "velocity stations") arranged along the projectile's trajectory. As the projectile passes between a laser and its detector, its shadow is detected and a TTL pulse is sent to our PCI-6602 board. Depending on the experiment, we use three or four such laser-dector pairs. They use counters 0, 1, 2, and 3. We know the distances between the laser stations and, once we get the times between detections, it's s simple matter to calculate the projectile's velocity.
We also use LabVIEW to fire the gun, and we do that because opening the camera's shutter has to be synchronized with the firing pulse, which currently is sent via P1.1 on the 6259. Here's the problem: when we test the laser-detector arrays in a "standalone" mode (that is, without any other tasks or operations being done with LabVIEW), they work infallibly. It's when we try to use LabVIEW to fire the gun that we get either very erratic results from the velocity stations/6602 or no results at all.
I've tried a range of things, from starting the two-edge measurement task before the firing signal is sent, to trying to force things with a timed sequence, to doing things with brute force via a seuqence structure. When I try to start the two-edge measurement task first, though, the firing signal isn't sent until the counters time out. This of course, wrecks the experiment, because all of the timing is then messed up. The VI that I've attached (Version 1.vi) is a HIGHLY simplified version of the initial attempt I made at doing this, with all sorts of background stuff removed just so I can cut to the chase. (Only one two-edge measurement task is shown, for instance.) I think that the VI is pretty self-explanatory (and embarrassingly primitive), so it probably doesn't need much in the way of explanation. Counter 7 and PFI 0 on the 6602 are used to accept the signal from the firing button and trigger the event structure, which contains the two-edge separation and gun-firing tasks. (In reality, I use a separate VI to have three to four concurrent two-edge separation tasks running concurrently, one for each velocity station.) I start the two-edge separation tasks first so the detectors and counters are ready for the projectile. It's not necessary here, but I kept the 500 ms wait frame in this example because that's why the sequence structure exists -- to allow the shutter of the Nikon to open completely before the gun fires. After those 500 ms, the firing signal is sent to the circuit that actually fires the gun.
What happens in this configuration is that the second frame of the sequence structure doesn't execute until the 5-s timeout transpires in the two-edge separation task. I've also tried this using a line on the 6602 to fire the gun instead of P0.1 on the 6259, but that ends up with the same result. (Both counters are used on the 6259 to strobe the main illumination laser, so they're unavailable, if you're wondering. In any case, we need four counters for the four velocity stations.)
FINALLY, my question: What am I doing wrong, here? If I put the two-edge separation tasks in the same frame of the sequence structure as the firing task, the gun fires when it's supposed to, but we get no velocity measurements. I've also tried to force the timing with another version of a sequence structure; I'm attaching another very simplified version below as Fire and speed example.vi.
After you recover from your violent fits of laughter, I'd really appreciate hearing what you might recommend. (And no, surrender isn't an option.)
Thanks for taking all of your valuable time to read this huge post -- I really appreciate it!
Mark
Attachments:
4044, cropped.jpg ‏197 KB
Version 1.vi ‏35 KB
Fire and speed example.vi ‏30 KB

I agree with all 3 of Kevin's points. His first suggestion will probably fix your problem (see below). The 2nd and 3rd suggestion would improve efficiency and responsiveness, but #2 might not be possible since independently triggering four outputs in hardware would require the use of 4 counters (on the 6602 anyway) which might be busy doing other tasks in your application (although if you don't need the stations to trigger independently then you could implement this with a single counter).
I think I have an explanation of the problematic behavior you are seeing based off of the following bits of information from your post:
1. Running the small example code by itself works flawlessly, but adding other simultaneous functionality fails. You mentioned you are doing this on 4 stations, so I'm assuming 4 counter input tasks running in parallel.
2. The behavior you are seeing is that the 2nd sequence does not execute until after the read times out (note that the sequence is supposed to be executing in parallel with the read).
It sounds like the problem is coming from a combination of calling into DAQmx Read before data is available (this consumes one of the threads that LabVIEW has allocated to your application until DAQmx Read finishes executing) along with the fact that LabVIEW allocates 4 threads per execution system per priority by default. Since all of your threads (from what I can tell) are executing on the same priority, the 4 reads you are calling will block anything else from executing until they have completed. By then it's too late and the firing of your gun happens after the counter task has already timed out.
You *may* increase the number of threads allocated to your application by using a VI that is included with LabVIEW (vi.lib\Utility\sysinfo.llb\threadconfig.vi) and this would also probably remedy the behavior you are seeing. However, rather than throwing more threads at this application I think the better solution would be to change the sequencing of your tasks like Kevin suggested ("create and start the 2-edge task before entering the sequence structure, and defer the 2-edge *reading* until *after* firing the DO")--in doing this you would now expect to see data immediately upon calling DAQmx Read and you avoid the situation where Read is blocking indefinitely and consuming an application thread. You could take this a step further by checking the Available Samples per Channel property (or using the DAQmx EveryNSamplesAcquiredIntoBuffer event) to ensure that data is actually available before calling Read.
Best Regards,
John Passiak

How to generate a pulse on x number of events PCI-6602

I am running LabVIEW 5.1 full development with a PCI-6602 counter board.
I would like to generate an output pulse after counting x number of input pulses. I would also like to reset the counter with an external signal.
My application is I am trying to generate a second index pulse for an encoder.
I would like to count the pulses from encoder phase A and generate an output pulse on x number of counts. Then I would like to reset the counter using the encoder’s index pulse. This way I can change the phase of the “generated” index pulse with respect to the “real” index pulse by x number of counts (degrees) and maintain that regardless of encoder rpm.
Thanks
Brian

Brian,
There actually is a way to do what you want, but it gets a little complicated. I don't have LV on this machine so I'll have to just describe the idea. First a summary: the counter will repeatedly countdown to 0. Each time it reaches 0, it will generate a brief pulse which will in turn hw-reset the counter value to N. Then it will countdown to 0 again, etc. The same brief pulse could also be wired to a different encoder-measuring counter to create a "delayed" reset to 0 (or some other #).
1. Configure your counter for "position measurement" instead of "simple event counting". Set the encoder type to, um, I forget the name -- something like "two pulse encoder." It's the setting that will increment with every SOURCE edge and decrement with every AUX edge. Wire your encoder channel A to the counter's default AUX input (in position encoder mode, you must use the default input pins). Hard wire from the default SOURCE input to GND. Now every encoder edge will decrement the count, and nothing wlil ever increment it.
2. Configure the counter to use z-indexing. Set the z-index reload value to be N-1, where N is the # of encoder counts by which to delay the encoder's real z-index pulse. Set the z-index reload phase appropriately, probably to A low B low. Wire the real z-index pulse to the counter's GATE input.
3. Configure the counter to "pulse on terminal count" -- you do this using 'Counter Set Attribute.vi'. So N encoder edges after the real z-index pulse, you'll generate a pseudo-z-index with this counter.
4. You can wire this pseudo-z-index to the GATE input of the encoder-measuring counter. Now the encoder's z-index pulse is delayed by an amount you can program.
5. Note: this method requires the motion to be uni-directional.
Good luck!
-Kevin P.

Count digital events on a Counter with pci-6602 with callback on CVI

Hi,
I'm using a PCI-6602 card with CVI 8.5 and I need to trig on event.
On every pulse I received, I need to do some actions like increasing a counter, send a message on Rs232 etc.. I don't want to do any loop checking that the counter value has changed. I would like to use a callback to execute this code only on the edge or counter value event.
My problem is that I don't know which function can do this. Is there any way to get an event on a pci-6602?
Thanks
James
Solved!
Go to Solution.

Hello.
It's completely possible to create a callback that will allow you to do what you want when a edge will occur on an external signal you define.
To do this, you can for exemple create a counting edges task that will use one of the 6602 counters,and the set your external signal to be the source of your sample clock.You'll then be able to register a callback with the function DAQmxRegisterSignalEvent, and your callback will be called each time an edge will occur on your specified sample clock source.
Here's 2 links that explain the events in DAQmx and how to handle them in CVI. The example ReadDigChan-ChangeDetectionEvent.pr that ships with DAQmx examples (Hardware Input and Output<<DAQmx<<Digital measurements) can be very useful to understand how to do. This example creates a signal event callback to detect change detection for digital inputs.
Regards.

Continuous pulse train generation on my PCI 6602 takes up too much of my system resources.

I am using a PCI 6602 to generate a clock signal that is to synchronize pattern generation on two PCI 6534's. I have done this by generating a pulse train at a user defined frequency on the PCI 6602. My problem is when I generate this pulse train, the program uses all of the computer's CPU, and slows the rest of the processes down. Just to let you know, I have isolated this program to ensure it is the only thing running, and it still has the same result. The CPU usage soars to 100%(and remains constant) and the memory consumption increases (and remains constant) as well. Also, if it helps at all, the CPU consumption is completely independent of the frequency that is being gene
rated, but the memory usage increases a little with an increase in frequency. Does anyone have any insite as to how to fix this, for I have noticed that all of the posted examples like this behave in the same manner.
Thanks,
Dave

Russell,
Thanks for the reply. Just about five minutes ago I came to the realization that the card itself was not causing this to happen. When I took a closer look, I found that my C program and all of the example programs were using the NIDAQWaitForKey() function to enable countinuous generation. So what was happening was that function was constantly polling the CPU to find a key to be pressed. So lets just say I found a way around this problem, and so everything is well. There are a handfull of things that i need to work on now, but at least I know my clock generation program is correct and I can stop banging my head against a wall trying to solve a problem that does not exist and for which there is no solution.
Thanks Again,
Dave

Connect NI PCI-6602 with NI PCI-6503

Hello,
I want to connect a NI PCI-6602 Counter/Timer with the NI PCI-6503 DIO-Card. The problem is the varying number of pins. (6602->68 pins; 6503 -> 50 pins). Is there a possibility to connect both? Maybe a complete adapter?
regards Thomas

Thomas,
You are correct both cards have male connectors. You could still use the 68M-50F connector if you use a 68-68 cable. Or if you had a 68F-50M then you would need a 50 pin cable. I have found another option, the R6850-D1 Cable(part number 777419-01) . This is a digital cable that was made to use our 68 pin digital devices with 50 pin breakout boxes. It ties the ground lines together and you also loose access to PFI 37,the up/down pin for counter 0, and you loose the +5V line. I think you may want to check the pin mappings to make sure that you really want to connect these 2 boards directly together. When using a 50 pin conversion with the 6602 you will get the following pin mapping:
Pin Number (1-50) 6602 Signal Name
1 PFI_25
2 PFI_28
3 PFI_27
4 PFI_24
5 PFI_30
6 PFI_31
7 PFI_26
8 PFI_29
9 PFI_21
10 PFI_23
11 PFI_19
12 PFI_17
13 PFI_18
14 PFI_16
15 PFI_22
16 PFI_20
17 GND
18 PFI_34
19 GND
20 PFI_35
21 GND
22 PFI_33
23 GND
24 PFI_32
25 GND
26 GND
27 PFI_38
28 GND
29 Reserved
30 GND
31 PFI_36
32 GND
33 PFI_39
34 GND
35 PFI_4
36 PFI_6
37 PFI_0
38 PFI_2
39 PFI_1
40 PFI_3
41 PFI_7
42 PFI_5
43 PFI_13
44 PFI_10
45 PFI_15
46 PFI_14
47 PFI_8
48 PFI_11
49 PFI_12
50 PFI_9
You will loose half of the cards functionality since half the pins (even numbered pins) will be connected to ground on the 6503. It would be easy for you to short lines to ground this way. It would probably be better if you get a breakout box for each card (SCB-50 and SCB-68) and then connect only the lines you want to share between the cards. So in answer to your question, yes you CAN connect then directly together, but do so with caution, and I do not feel this direct connection is the best solution for y
ou.
Hope this helps.
Kevin R

How do I synchronize a pulse output to a sine wave input on a pci-6602 card?

I have a sine wave from a function generator as the input on the source of a counter. Input frequencies vary from 2-60 kHz. I want to produce a pulse train at a different frequency (10 Hz), but in phase with the sine wave. I have only been using Labview 5.1 for a short time. I am using the PCI-6602 card with a SCB-68 connecting block.

Hello;
Unfortunately, you can't connect a analog sinewave to the counter source. Counters only work with digital TTL signal type. To accomplish that task, you will need a MIO board working in sync with the 6602 you already have.
Regards
Filipe A.
Applications Engineer
National Instruments

Error -200141 when doing buffered events with DAQmx and PCI-6602

When doing buffered events with DAQmx and PCI-6602 I get error 200141 - Data was overwritten before it could be read by the system.
This error is generated ONLY with random inputs >200/sec.
My setup is :
DAQmxCreateCIVCountEdges(taskhandle,"Dev1/ctr3"....
DAQmxCG+FGSampClkTiming(taskhandle,"/Dev1/FPI35",...
DAQmxSetCICountEgdesChan(taskhandlem,"", "/Dev1/80MHZTimeBase")
DAQmxSetChanAttribute(taskhandlw,",",DAQmx_CI_DataXferMech,DAQmx_Val_DMA,0);
Can somebody help ?

i'm getting the same Error-200141, while reading semiperiods. (Meas_Buffered semiperiod continous)
while loop ex.rate seems to be pulsewidth*no.Samples to read. in my case PW=60ms
Input buffer size measured with Property node= 10000
why this error happens?? i cant use any mode other than implicit timing for semi-period measurement right??
more info: all the ai channels are used ~ 16 differencial.
i found one solution which is _ reinitializing the whole task if an error occur. is this the right way??
Kudos always welcome for helpful posts
Attachments:
Counter_1_Meas Buffered Semi-Period-Continuous_main_lv09.vi ‏34 KB
SemiPeriod_Reconnect Counter on Error.vi ‏35 KB

Pci 6602 external clock

Hello I'm a little bit a newb concerning the PCI-6602, and I need somenones help. I have a APD which delivers signals I want to count while an external gate is high. My code so far (this is just pseudo code since I have a wrapper in python): I have connected the signal I want to count to the PFI39 and the Gate to Gate - ctr7
DAQmxCreateTask('', task)
DAQmxCreateCIPulseWidthChan( task, "/dev1/ctr7", '', 0, MaxCounts*DutyCycle/f, DAQmx_Val_Ticks, DAQmx_Val_Rising)
DAQmxSetCIPulseWidthTerm( task, "/dev1/ctr7", "" )
DAQmxSetCICtrTimebaseSrc( task, "/dev1/ctr7", "/Dev1/PFI39" ) )
DAQmxSetCIDupCountPrevent(task, "/dev1/ctr7", True )
DAQmxSetReadRelativeTo(task DAQmx_Val_CurrReadPos) )
DAQmxCfgImplicitTiming( task, DAQmx_Val_FiniteSamps, 1000)
DAQmxSetReadOffset(task, 0)
DAQmxSetReadOverWrite(task, DAQmx_Val_DoNotOverwriteUnreadSamps)
DAQmxStartTask(task)
DAQmxReadCounterU32(task
, 1000
, 0.008
, 285099872
, 1000
, ctypes.byref(self._CINread), None)
DAQmxStopTask(task)
this is not actual code, this is just copied from a python file - thus not C Synthax, but the functions should be ok.
If I set the Gate to low however I still get counts, although the Gate is low. Can anyone help me? Did I connect the gate / src to the correct pins?

The behavior you describe doesn't make sense to me. Having configured implicit timing, you would only expect a single sample every time the gate signal goes from high to low. Each buffered sample would indicate the number of source ticks that occurred between sequential rising and falling edges of the gate signal. Is this the behavior that you intended? If the gate is just staying low one would expect the read call to timeout since no new samples would be available.
Does DAQmxSetCIPulseWidthTerm( task, "/dev1/ctr7", "" ) not return an error? On my simulated 6602 as well as my real PCIe-6351 I get error -200254 indicating that an empty string is not a valid terminal (although I know for a fact that this does work for counter output terminals, I don't think it makes much sense for the input terminal on a pulse width task). In any case, you should just specify the PFI line to which you have connected your gate signal.
Best Regards,
John Passiak

Connect PCI-6602 to relay

Hello,
I am absolutely new to Labview and the PCI-6602 card. What I would like to do is to use Labview to control a relay through the PCI-6602 DAQ card. I am of course using the CB-68LP connector block to make the hardware connection.
Since I want to control a relay with a 0-5V TTL signal to open and close, I guess I am supposed to send a digital signal to the DIO lines on the PCI-6602. However, could someone explain to me if there is an example VI that can do this?
Moreover, what are the pin numbers on the CB-68LP connector block where the actual digital signal will come from? This is not clear from the manual. I would first like to measure it on a voltmeter before connecting an actual relay to it.
Eventually, there will be three relays connected and each of them will in turn be controlling a solenoid valve. In some cases, two of the relays should open at the same time while the third one is closed. At other times, only one relay will open.
I appreciate your feedback in advance.
thank you.

Hi,
I have attached a modified version of the example which only outputs on one line. Notice the change at DAQmx Read.vi. The output will remain high if you stop the program.
Please clarify if you have further questions.
Pelle S
District Sales Manager
National Instruments Sweden
Attachments:
Write Dig Chan1line.vi ‏28 KB

PCI 6602 signal no periodic

Similar Messages

Maybe you are looking for