PCIe-6320 sees no encoder

Similar Questions

• Pulse train generation question-PCIe-6320

  Hi all...

  IM using PCIe-6320 series daq x to generate trains of pulses. I went through the examples found in the labview to generate digital impulses. Provided vi runs without error, but I could not find any pulse output in my PIN ctr0. Is there a specific connection to check the output?

  Hello..

  I had a problem with the interface cable, I found this later.thanks.now I havesolved.

• No count output / pulse pulse does in a meter of pcie-6320

  Hi all

  IM using pcie-6320 in my application to generate impulses using the counter i/o.Even when I try to generate/counting pulses using MAX, I coundnt find no exit, im watching the e/s using a CRO. My camera works very well and tested hardware DAQ Diagnostic Utility tool in this tool also spent the meter test. IM completely stuck here, if anyone has come across such a problem please help me.

  Hello.. I solved the problem. In fact, it was found that the cable between junction box and data acquisition is not properly inserted. In any case thanks for your contributions

• Replace PCI-6220 PCIe-6320?

  New to the forum, so bear with me if I'm in the wrong place.

  I have a system with a card PCI-6220, and I am considering the upgrade of the computer used. If I decide to do, then I would like to upgrade the jury as well. According to the information of product of NOR, the PCI-6220 can be replaced by PCIe-6320. I am concerned by the mapping of the e/s on the same map if and I was wondering if anyone else has had experience with this. I need to know if I should change the LabView code to accommodate the new Board of Directors, or if a replacement that will work only.

  Thank you!

  WisDave wrote:

  Since the list of pins of the two boards are the same, you expect that there is problems with the interaction with the SC-2345?

  Not at all.  NEITHER tends to keep things mostly the same between boards so that they can reuse the connection blocks.

• Question on the NI PCIe-6320 cash events

  Hello, all:

  I use 6320 for counting digital proofs. I use a tampon gated method of counting. At the end of each inventory period, I read everything in the buffer of events to get their timestamps. However, there is a problem with this method. When the number of events exceeds 1 million (?), all buffered of lost events and I can't read anything. My guess is that this is due to the size of the buffer or counting clock reversal. (?)  There are basically two ways to overcome this problem. We're to do several reading and the other events is prescale events. Anything know how to perform a count prescale? For example, I can just count the timing of each event in the fifth.

  My method of counting is seen in the attached vi.

  Thank you.

  Since your actual code is different from what has been published, I can only take a few guesses for why you can't count impulses more than (about)? 1 million.

  1. If your code real don't wire DAQmx Timing.vi a value of 'number of samples', so a primary task which is told that she acquires 100 MHz uses a default buffer size of 1 million samples.  You can create a larger buffer by wiring in a greater value.  You can also loop on your reader calls to help prevent a buffer overrun.

  2 Theres a limit to the rate, you can stream data from the system RAM card.  The X-series is good better than most of his predecessors in this respect for the measures in the base.  (See this thread and the related links.)  But it won't always manage frequencies of efficient sampling of 100 MHz for any significant duration.

  3. Another option I've seen used is County binning.  This method works a little inside-out your method by letting external impulses increment the counter that this indictment is sampled at a constant sampling rate.

  4. I could not yet make any real life playing with a card X-series, but I think that there is also a precise frequency measurement mode for sampling at a constant rate.  This mode may be useful for you as well.

  -Kevin P

• need help to get started with 6320

  I got a PCIe-6320 recently and I did not use it for purposes of counting. I entered the TTL signals to pin 37 and I try to see some numbers counter County 0 but I still get nothing. The Board of data acquisition has been successfully installed.  But I can't read any number of counter. I run example screws as County Digital Events.vi and Clk.vi of digital counting events-buffer-continues-Ext. I don't connect only a signal to the SCB-68 box: the signal pin37 and the Earth to Terminal 4. What other tests should I do to figure out the problem?

  Thank you.

  Lixin

  problem solved.

• 6320 slow ADC read

  Hello

  I use a PCIe-6320, I'm voting of the ADC, in a very simple while loop.  The time per iteration of the while loop is about 9 milliseconds. While the time interation of the while loop without reading the DAC is 10 microseconds. That's the difference.  Any thoughts, I try to ask about 4 kHz which I think would not be a problem.  BTW, I read only one channel.

  Kind regards

  Mike

  Software, let me give harware timed to try.  Thank you.  It seems so strange that just do a simple reading would take so long.

• Quadrature encoder frequency division dotNet VB Net c#

  Hello

  After a long search on this forum, I decided to start this thread for dotNet developer.

  I have a PCI-6602 with an encoder in quadrature (A, B, Z). The frequency of the pulses is average (10 kHz).

  I'm only using the channels A and B.

  The function I need to implement is to output all N pulses forward. N is a natural number and ranging from 1 to say 100.

  I have no constraints on the output. I may be a little switch or a generation of impulses.

  What features I'll call in MeasurementStudio.Net to implement this?

  How many counters should I use?

  On the registry, my guess is that I have to preload a value in the registry.

  Then when countdown counter reaches 0 this in turn does 2 things:

  • reload its set value meter
  • triggers the generation of output (TerminalCount)

  Thanks for any help you can provide

  Guy nOTEs for EITHER:

  ---------------------------------

  Moreover, in samples of NOR, squaring does work all the way.  I NLE sample "CountDigEvents" with CountDirection the 'Externally controlled' value, backward motion is never displayed. This is because the meter is read as a UInt32.

  Hi anthony75fr,

  Although there is no support for A, B and Z entries, the behavior you're looking for is essentially how a counter output tasks works.  Wouldn't not enough output on each pulse signal of A N (ignoring B and Z)?

  If so, you can configure it with only one meter by making a simple change to the example of GenDigPulseTrain_Continuous.  The basic shipping example uses the CreatePulseChannelFrequency method.  You want to use the CreatePulseChannelTicks method to specify your low and high time regarding ticks of the external signal (regardless of the PFI line the A out of your encoder is connected to).  By default, the output of the meter will switch between high and low in a way the number of ticks high and low ticks that you specify (for example, you can set up the meter for the output up 2 ticks and low for 98 ticks, giving a boost all 100 ticks - 2 is the minimum value for high or low ticks).

  Best regards

• Timestamp of photon arrival times

  I would like to make a measure of cross-correlation of two photons.  Auto hardware correlators and crossed correlators are available, but expensive.  It seems that many other users resulted in the idea of using the 80 or clocks 100 MHz in the counter of entry for each desired channel, starting the counters at the same time and get every channel of photons in the door of the corresponding counter.  Each photon triggers so the meter to store the total of the clock in its internal register, that is, the time stamp for this photon. Since then carries on a 32-bit counter clocked at 100 MHz only occur every 42 seconds, and average rate of photons will be at least 100 Hz, excesses should be easily recognized and corrected in post processing.  So assume that all we have to do is get meter reads in a buffer.  Bursts of photons with separations of arrival can be as small as few clock cycles.  Average rates may be a few hundred kHz or more on each channel.  We can adjust this rate by turning the power of the laser to the top or to the bottom - the source for the broadcaster that produces the stream of correlated photons.  I suspect many others would like to know which system is better for these types of measures, the 6602 or the X-Series.  If FPGA is a good solution, perhaps we should start a new thread about it.  But for 6602 or X-Series: what is the fastest, it can do so for short bursts (speed for how long) and what is the sustainable rate?  I realize that the sustained rate will depend on the material.  I thought I only saw that the PXI beats the PCI bus in this type of application.  PXI versions are better?  In particular, what are the effects of the FIFO 128 sample on the X-Series compared to the 2 on 6602 buffer solution.  And I noticed something about the speed of the front end for these two choices could be a problem in this regard.  Pulses (photon) TTL on the door will have a width of 10 to 50 nsec.

  For the flow of the series X is going to be much faster than the 6602 mainly due to the FIFO aboard (but PCIe gives more throughput than PCI).  PCI or PXI should have the same flow (and PCIe vs SMU would also have the same flow).

  Forum user (and NOT used) Andrew S displayed some X series streaming of references here.  On a single meter, it was able to maintain the sampling frequency of ~ 20 MHz on PCIe X Series and ~ 8 MHz on USB of the X series.  6602 benchmarks are much lower, somewhere between 200 and 300 kHz (although the system used for benchmarks is old enough).

  The 6602 allows shorter pulses that the X series.  The specifications page indicates a minimum of 6.25 the 6602 ns pulse width.  I saw a specified number directly to the X series in fact.  X series devices include a maximum external base of 25 MHz clock frequency, which assuming duty cycle 50% would be 20 ns high and low times.  50 nsec would certainly long enough of a pulse, but 10 ns * could * be pushing.  You will probably need to do some tests to confirm or not the X series is able to detect all the impulses for your configuration - if not then I would suggest the X series (PCIe-6320 is the lowest cost one) on the 6602.

  Best regards

• Function DAQmxRegisterEveryNSamplesEvent can be used for the counter input channels

  Hi all

  I have a request to count the number of digital pulses. I want to know the time of impulses coming which start from 1 and an increase in later, 4 as 1, 5, 9, 13... The time interval between each pulse is not a fixed value. So I tried to use DAQmxRegisterEveryNSamplesEvent and DAQmxCreateCICountEdgesChan functions. But afterI calls the DAQmxStartTask function, it has always failed.  The advice that I used is the NOR-PCIe-6320. Here's the part of my code.

  DAQmxErrChk (DAQmxCreateTask("",&m_taskhandle));
  DAQmxErrChk (DAQmxCreateCICountEdgesChan (m_taskhandle, "Dev1/ctr0", "", DAQmx_Val_Rising, 0, DAQmx_Val_CountUp "));
  DAQmxErrChk (DAQmxRegisterEveryNSamplesEvent (m_taskhandle, DAQmx_Val_Acquired_Into_Buffer, 4, 0, EveryNSamplesCallback, this));
  DAQmxErrChk (DAQmxStartTask (m_taskhandle));

  I don't know the reason. Can someone give me help. Thank you.

  Yang

  DAQmxRegisterEveryNSamplesEvent only works with the buffered in memory tasks.  That's what you should do anyway (if you want to use the callback or not):

  1. make your external signal the sample clock (DAQmxCfgSampClkTiming).

  2. use one of the basics of internal time as the source (DAQmxSetCICountEdgesTerm).

  Each sample you read will give the count in ticks of the time base.  Multiply the number by the base of your time period and you now have a timestamp.  Keep in mind the counter roll to 2 ^ 32 therefore account for this in your program.

  The recall is not necessary, but it is useful that you can make sure that you block your main thread until the samples are available.

  Best regards

• Strict & Duty cycle value changes - every time

  Hi all

  IM using pcie 6320 to measure the frequency and the use of a signal.i factor tied my vi & data measured for reference. Values in red, is my frequency and duty cycle but values real changes for all the 1 sec. Please correct me if I am wrong.

  You must set the CI. Pulse. Freq.DigFltr.Enable and CI. Pulse. Freq.DigFltr.MinPulseWidth.

  You have selected CI. Freq.DigFltr.Enable CI. Freq.DigFltr.MinPulseWidth.

  These are two different types of task meter entry (although they are called unfortunately very similar to the other).

  Best regards

• Camera Link image, line, data valid bit locations

  Hi all

  (see also http://forums.ni.com/t5/Machine-Vision/How-can-I-know-if-the-PCIe-1433-sees-a-Frame-Valid/td-p/31769...)

  I'm trying to re-design code FPGA vendor to change a camera of 4 x 12 Medium to Full 8 x 8.

  The Camera Link standard is quite confusing. The way I read it, a Camera Link of 8 x 8 Full camera should affect the valid as follows:

  LVAL: bit 24 on three channels

  FVAL: bit 25 of the three channels

  DVAL: bit 26 on three channels

  For some reason, the provider asigned them like this (and IT WORKS!):

  LVAL: bit 18 on three channels

  FVAL: bit 19 in all three channels

  DVAL: bit 20 of three channels

  There is another format that corresponds to the valid Bit arrangement? If so, is there something in the Camera File Generator and. Files of CIM which defines the format?

  See you soon!

  Crazy

  Crazy,

  Yes, you are right the LVAL, FVAL and DVAL are on TX/RX24, 25 and 26 respectively.  These assignments of bits match with parallel interfaces on Channel Link Serializer/Deserializer chips.  The PCIe-1433 expect that framing signals are mapped to the signals to the camera.

  Not all cameras output a signal DVAL, so they can be ignored in the acquisition card (PCIe-1433) with a camera file parameter.  In addition, the polarity of the signals framing can be reversed with a camera file affecting as well.

  You may be interested in using Camera Link Logger with the PCIe-1433 to receive signals from the camera.   Camera link Analyzer will present the traffic camera link in a format easy to read Visual format that can help your development and debugging.

  http://www.NI.com/product-documentation/14301/en/

  Regards, Jeff

• Devices of simulations not support value 'ReadRelativeTo' to 'MostRecentSample '?

  I use a device to simulate in my proposed acquisition of analog signal, and when I try to set the property 'ReadRelativeTo' of the workflow to "MostRecentSample", it throws an error saying that I can't use "CurrentReadPosition".  This happens with a simulation PCIe-6320 and PCI-6034.  I used this value with PCI-6034 real cards before, so the device should support, right?  Is this a bug or I do something wrong?

  Here are my c# code:

  Task daqTask = new Task();
  daqTask.AIChannels.CreateVoltageChannel ("dev2 / ai0:5", String.Empty, AITerminalConfiguration.Differential, -10, + 10, AIVoltageUnits.Volts);
  daqTask.Stream.ReadRelativeTo = ReadRelativeTo.MostRecentSample;
  daqTask.Stream.ReadOffset = - 1;
  daqTask.Start (); / * Exception occurs here. */

  And here is the full text of the exception:

  Requested value is not supported for this property value.

  Property: NationalInstruments.DAQmx.DaqStream.ReadRelativeTo
  You asked: NationalInstruments.DAQmx.ReadRelativeTo.MostRecentSample
  You can select: NationalInstruments.DAQmx.ReadRelativeTo.CurrentReadPosition

  Task name: _unnamedTask<0>

  State code:-200077

  Urgh.  I == fool.  I was not put the sample clock before attempting to start the task.  Problem solved.

• Sampling rate higher for the measurement of precision meter

  I have a BNC 6259 M Series DAQ USB. I am currently using the DAQ Assistant to perform simple cash rising measured with the measuring mode single sample on request. I tested my VI with a known square wave with a function generator signal and it clearly lacks a few edges. I think that the solution lies in faster sampling. However, I was not able to understand how to use clocks to set up continuous sampling mode. I tried the forums and I found articles that were close, but not quite exactly the problem I am facing with as (http://forums.ni.com/t5/Digital-I-O/trying-to-use-NI-6251-s-DIO-port-as-input-and-output/m-p/448035#...) or (http://forums.ni.com/t5/Multifunction-DAQ/Using-Counter-of-PCI-6024E-with-Quadrature-Encoder/m-p/984...). Any guidance here would be great.

  In fact, the calendar should not have anything to do with the edges being detected.  Configuration of a sample clock for a county of just edge task allows you to enjoy deterministically in the account register and has no impact on the edges which can be counted.  Also, the analog examples really have nothing to do with what you seem to be asking questions on.

  ... So it leaves the question unanswered as to why you might miss the edges.  Perhaps the following information could shed some light on the question:

  1. it is possible that you do not configure the counter exactly as you think you are.  Can you post the VI you use?  As a point of reference, count digital events shipping example does not use any clock sample timing and just questioned the value of the register count with a software loop, but the meter should not miss all this edge on the input source.  There are examples that are timed by the material available as well, but this is not necessary, unless you need a constant specified dt between your counter samples.  To use the examples of the timed sample, you will need to generate a clock of either another subsystem on the map or use an external clock.

  2. assuming that the configuration of the counter is not the issue, there may be a problem with the method that you use to determine if you are away from the edges.  How do you know that you are away from the edges?  The function generator produces only a finite pulse amount?  You start the meter before start out impulses?

  3. If the two points above do not raise red flags, it seems likely that the meter is registered just not some of the impulses of your FGEN.  Can I assume that the output of the FGEN is 0 - 5V TTL?  What is its frequency and duty cycle?  The maximum external source for the meter on the M-series products: DAQ (like the 6259) is specced at 20 MHz, but this depends on a clean signal with good connections.  At frequencies above it, the bandwidth of the front-end of the PFI lines becomes limiting.  If you have an available specification document for your FGEN I'd like to be able to see it.

  I hope this gets you throw on the right track to solve the problem - impatience comes back with more information.

  Best regards

• How to replace the SCXI-1600?

  Since our IT obliges us to switch to Win7, 64-bit edition, our SCXI-1600 becomes unnecessary because there is no 64 bit driver (Sidenote: the device is still available in the online catalog without obvious by the lack of such a driver warning). in an another tread on this subject, Seth_B advise

  For example, the USB-6251 device mass termination that provides 5 x faster sampling with 7 x better accuracy, USB 2.0 transfer speeds of data transfer more reliable and is only about $300 more including the cable between the DAQ hardware and the SCXI chassis.

  I need more information - I don't understand how exactly who will replace the SCXI-1600 as a connection to the SCXI block, for me, it looks like an ordinary e/s USB device must connect directly to several types of e/s analog and digital through a CBS. What cable should I connect the chassis SCXI containing other maps, how she will turn upward in MAX - in short: I need to decide if the replacement is more trouble with respect to particular software rewriting labview and other efforts that fight OUR guys to keep the System 32 bits for this testbed.

  Hello MBohnet,

  To avoid work or acquisition of new equipment on your part then I would recommend against your IT Department to maintain 32-bit system.

  If you need to upgrade to Windows 7 64 bit then the 6251 is an option at your disposal to communicate and scanning information of you modules SCXI.

  There are steps for setting this up

  1. Remove the 1600 chassis.
  2. Fix a module SCXI-1349 in the back one of the SCXI modules. Then use an SH68-68-EPM cable (the cable is listed on the pricing for the device 6251 tab) to connect the SCXI-1349 module to the PCI-6251.
  3. Your configuration in Measurement & Automation Explorer would be alike in what concerns the addition of your device, but you will point to the 6251 as the digitizer.
  4. The quote above regarding the (5 x faster sampling rate) applies only when using the USB-6251 in parallel mode.
  5. You wouldn't have to make changes to code with switching on the material element.
  6. Also, if you are not connected to the USB take a look at the PCIe-6320 or PCIe-6341 with the SHC-68-68-EPM cable. They are less expensive than the USB-6251 housing alternatives.

  Kind regards

  Izzy O.

  Technical sales engineer

  National Instruments

  www.NI.com/support