Software trigger with PCI-5122

I am going to program a board with PCI-6552 and in meantime in specific times capture the samples of the anolog output of the board by PCI-5122.
Is there any way to use software trigger and the data pattern of PCI-6552 (e.g. define a software event) to trigger the PCI-5122. If it is possible, how the software event can be defined and connected to the "send software trigger" block?

Whe using a software trigger with the 5122, you generate the trigger whenver you call the "Send Software Trigger" function. you can program the software events that cause this funtion to be called in any way you want.
In the simplest case, you could place the "Send Software Trigger" function in a while loop and only execute it when the user presses a button.
Jack

Similar Messages

  • Software trigger the PCI-5122

    hi
    I am going to program a board with PCI-6552 and in meantime in specific times capture just one sample of the anolog output of the board by PCI-5122.
    1) Can I use the digital output of one channel of PCI-6552 as trigger for PCI-5122 (to activate the fetching of PCI-5122) e.g. by connecting the output of PCI-6552 to the external trigger input of PCI-5122.
    2) Does it need to synchronize the two boards.
    2) Is there any example for software triggering the PCI-5122, and how long it takes from triggering to sampling the data.
    3) How I can capture just one sample in every triggering time and then wait for another trigger time.

    1) after programming the two output of the NI-6552 (DIO0 and DIO1) with the same pattern and connecting the DIO0 to Ch0 of PCI-5122 and DIO1 to external trigger of PCI-5122 and assigning the external trigger as the edge trigger source, the the signal is different from when the Ch0 is assigned as the trigger source. why are they different, also it does not accept two triggers sequentially. (Pic 1)
    2)I am using a loop for generating the data and a loop for aquisition, when I using two trigger in one cycle and select niscope repeat_time=4, the signal position for 8 aquisition should be the same but as you can see in figure 3 the first two pulse are correct but the other ones are different.
    Attachments:
    pic1.bmp ‏2305 KB
    pic2.bmp ‏2640 KB
    pic3.bmp ‏2305 KB

  • Software Trigger from CC1 on PCIe-1433

    Dear Sir or Madam,
    Now I am getting into trouble about NI Measurement Automation explore with my PCIe-1433. I like to make software trigger from this software into my cameralink camera. However I am not so familiar with this software. Is it possible to make software trigger ? If it is possible, I like to know how to generate it.
    Best regards,

    Hello,
    Check out this forum post. It goes through the steps necessary to set up triggering in MAX.
    -Erik S
    Applications Engineer
    National Instruments

  • Is it possible to start a PCI4472 and a PCI-MIO-16E-1 simultaneously using an analog trigger (with pre-trigger)?

    I would like to start several PCI 4472 and a PCI-MIO-16E-1 simultaneously. All boards are connected via a RTSI cable.
    My program works fine if I use software trigger, or an analog trigger from a PCI4472 channel. However, the analog trigger works only when I set pre-trigger (or pre-scan) to 0.
    Is it possible to start a PCI4472 and a PCI-MIO-16E-1 simultaneously using an analog trigger (with pre-trigger)?
    Thanks.
    Ian Ren

    Hi, Bill
    I think it is possible to set more than 38 pre-trigger scans on a single 4472 card. I've done this before. You can verify this by running the Labview example "Acquire N - Multi-Analog Hardware Trig.vi" which comes with LabView.
    What I try to do but without success/luck so far is to start data acquisitions of several 4472 cards and a PCI-MIO-16E-1 card using an anlog trigger (with pre-trigger).
    Thanks for your help.
    Ian

  • How can I set up a delayed analog trigger on PCI 6115 DAQ

    I have an S-Series PCI 6115 DAQ which I’m running with Labview. I’m using it to measure signals from an acoustic emission sensor and two force transducers. I’d like to set up a delayed analog trigger which will start acquisition on all three channels a period of time after a selected channel’s voltage exceeds a threshold.
    Currently I’m using the AI Config VI in line with the AI Start VI and AI Read VI to capture data after a analog hardware trigger occurs. A software trigger probably wouldn't work because I have to sample my data at 10MS/sec. My setup works fine for triggering without any delay or skip counts. However, if I set the delay or skip count in the additional trigger parameter field of the AI start VI, there is no effect, and the device still starts capturing data immediately after the trigger is received. What is the cause of this, and how can I get around it?
    Also, is it possible to sample the channels of a PCI-6115 DAQ at different rates? Right now, I’m sampling all my channels at 10MS/sec and throwing away data on all channels except one. However, this seems relatively slow and eventually I would like to attempt pseudo-real time control using my data.

    rpursley8 is right about needing to get the counters involved if you want a hardware timed delay in your application.
    Concerning whether or not you can sample at different rate, check this document out.
    Sampling Different Channels at Different Rates with NI-DAQmx
    Otis
    Training and Certification
    Product Support Engineer
    National Instruments

  • Hardware Clocking Error PCI-5122

    I tried to run the vi attached (which i've run many times before) and my computer bluescreen.  When it rebooted, I could no longer use my PCI-5122 digitizer card.  When I try to do a device test or device reset in MAX, it tells me that theres a hardware clocking error..   I was using an external trigger for the aquisition, but don't think I was using an external reference clock.  Could someone help me fix this?
    Thanks
    NI Hardware: PXI-7853R, PCI-5122, PCI-6733, PXI-1036, PCI-MIO-16E-4, PCI-6110
    Computer Hardware: Xeon Quad Core - 2.33 Ghz, 8 GB RAM
    Software: Labview 2009, Labview FPGA 2009, Vista 64-bit, MAX 4.6, DAQmx 9.0, NI-SCOPE 3.5
    Solved!
    Go to Solution.
    Attachments:
    OPO Monitor.vi ‏53 KB

    Hi,
    This error may be the result of a hardware failure where the only
    solution is a repair or replacement. There are however, some basic
    troubleshooting steps that have been known to correct this issue
    without a return.
    Reboot the PC or PXI controller.
    Try a different PCI or PXI slot.
    Update the driver to the latest version.
    If possible try the card on a different machine.
    If these steps to not correct the issue then it is likely the
    board requires repair which can be arranged by contacting National
    Instruments Technical support (in france: 01 57 66 24 24).
    Best regards,
    Thomas B. | CLAD
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    >> Inscrivez-vous gratuitement aux Journées Techniques : de l'acquisition de données au contrôle/com...

  • PCI-5122 Unregistered error -218802

    Hi,
    I am using the digitizer PCI-5122 (256 MB / channel) with Labview 8.2, NI-Scope 3.4 and windows XP.
    Starting off with the NI example "niScope EX Multi Record Fetch More Than Available Memory.vi"
    everything was running fine first, but now I encounter a problem with the following configuration:
    sample rate: 20 MHz
    external trigger (to start a record): 20 kHz
    min record length: any (I tried 1 or 1000)
    number of records: larger than 105,000 (the error does not occur for values < 100,000)
    The error message reads as follows:
    > Error occurred at:  niScope Multi Fetch Cluster.vi:1
    > <err>Driver Status:  (Hex 0xFFFCA94E)
    > Unregistered error -218802 occurred:
    > No error occurred.
    >
    > Component Name: nimxslu proxy
    > File Name: This is NOT an error in nimxslu. See nimxsl/tStatus2KernelProxyWrapper.cpp for information
    > Line Number: 290
    > Status Code: -218802
    Do you have any suggestions how to solve this problem? I need to acquire many more records
    and also will need to use the "records > available memory" function later on.
    Many thanks,
    Hanno

    Hi Hanno,
    The cause of this error is actually unrelated to its message. When
    acquiring a record of data into onboard memory, the record's timestamp
    must also be stored. There is a finite buffer on the host for these
    timestamps, and it can only hold 100,000 values. If the board attempts
    to store more than 100,000 records at once, an error will occur from
    the overwrite attempt.
    The solution to seeing this error is to use the timestamps on the host before they are overwritten. You can:
    Fetch records while the acquisition is in progress
    Fetch more records at a time, so that fewer are left in onboard memory after each fetch
    Decrease
    the trigger rate so that records can be fetched before their timestamps
    are overwritten. If the trigger is not under your direct ontrol, you
    can use the "Trigger Holdoff" property to throttle the trigger rate.
    regards,
    Tobias

  • Continuous, gap-free acquisition and processing with PCI-5142 and Labview

    I am trying to continuously acquire data from a PCI-5142 in Labview 7.0.  I have NI-SCOPE software installed, and right now, the best I can do is to acquire the data in chunks and then stitch the chunks together.  However, this results in a short (approx. 10ms) amount of data loss between chunks.  Since I am trying to do a cross-correlation of a function with my data, across chunks, I need the chunks to be contiguous.  Additionally, I need to do this processing in real time so I cannot just stream to disk. What are my options?

    Be sure that you are not stopping and re-starting the acquisition in between reads.  Also, be sure you are not reading from a new record each time.  There will be some time between separate acquisitions or separate records.
    The best way to acquire continuously is to configure a single record, set the Reference Trigger to Software, and never send a Software Trigger.  Set the Fetch Relative To attibute to Read Position.  That way, every time you read data, it will start at the first unread data point.  So you shouldn't see any gaps in the data (the chunks will be contiguous).
    Please refer to two examples included in the NI-Scope driver:
      - niScope EX Fetch Forever
      - niScope EX Fetch In Chunks

  • Position Control of compumotor linear servo table and GV-U6E with PCI-7344

    I'm referring PCI-7344 (not 7334).
    I have the GV-U6E which is a drive only and does not possess control functionality. the drive only version does not store or use programs. So, serial commands can not be sent through COM port by LabVIEW even though A few basic commands can be emulated.
    I am trying to do position control as I mentioned. For example, the motor should move A point to B point exactly with a certain speed. The points must be aboulte position.
    I would like you to see the reference comment that I have been contacting with in your website forum.
    http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=506500000008000000DD490000&USEARCHCONTEXT_CATEGORY_0=_14_&USEARCHCONTEXT_CATEGORY_S=0&UCATEGORY_0=_14_&UCATEGORY_S=0
    Regard,
    Jin Ho Lee
    ----- Original Message -----
    From:
    To:
    Sent: Thursday, September 26, 2002 5:00 PM
    Subject: Re: (Reference#1549-QYW196) "Position Control of linear servo table and GV-U6E with PCI-7344
    >
    > Note: Your reference number is included in the Subject field of this
    > message. It is very important that you do not remove or modify this
    > reference number, or your message may be returned to you.
    >
    >
    > JinHo. Compumotor is a very popular brand, and I know of several customers
    > who integrate our 7334 with Computmotor drives. However, when you say that
    > the MAX configuration doesn't fit in the compumotor drive settings, are you
    > referring to the specs from the 7344? It looks like the 7344 and the
    > Compumotor will work well together through a UMI break out box. If you're
    > referring to specific commands that the Compumotor receives, I'd have to
    > know more about the protocol. If the Compumotor needs serial commands,
    > then you can send them through the computer's COM port from LabVIEW.
    > Please let me know exactly what kind of configurations you're trying to
    > set. The 7344 can be completely configured in MAX and LabVIEW.
    >
    >
    > Best Regards
    >
    > Kyle Voosen
    > Applications Engineer
    > National Instruments
    > http://www.ni.com/support
    >
    > ------------------------------------------------------------------------------
    >
    > Problem Description :
    > "Position Control of compumotor 406LXR linear servo table and GV-U6E(motor
    > drive) with PCI-7344"
    >
    > "Since I had the answers referring:
    > http://exchange.ni.com/servlet/ ProcessRequest?RHIVEID=101&RPAGEID=135&
    > HOID=506500000008000000DD490000& USEARCHCONTEXT_CATEGORY_0=_14_&
    > USEARCHCONTEXT_CATEGORY_S=0& UCATEGORY_0=_14_&UCATEGORY_S=0
    >
    > Wiring step was done well. However, I still have a problem that MAX
    > configuration doesn't fit in compumotor drive settings. Therefore, the
    > setup is shown below, and I want to know how I can set up PCI-7344
    > configuration in MAX or LabVIEW VI.
    >
    >
    > -----------------------------------------------------
    >
    > Uploaded from device address 0
    >
    > Gemini GV Servo Drive Setup
    >
    >
    >
    > Motor Setup
    > DMTR 1703
    > Motor ID (406-x-LXR-M-x-D13-x-x-x-x-E5-x-x-x)
    > DMTIC 2.48
    > Continuous Current (Amps-RMS)
    > DMTICD 0.00
    > Continuous Current Derating (% derating at rated speed)
    > DMTKE 17.6
    > Motor Ke (Volts (0-to-peak)/krpm)
    > DMTRES 10.10
    > Motor Winding Resistance (Ohm)
    > DMTJ 119.300
    > Motor Rotor Inertia (kg*m*m*10e-6)
    > DPOLE 1
    > Number of Motor Pole Pairs
    > DMTW 40.5
    > Motor Rated Speed (rev/sec)
    > DMTIP 7.40
    > Peak Current (Amps-RMS)
    > DMTLMN 3.4
    > Minimum Motor Inductance (mH)
    > DMTLMX 3.4
    > Maximum Motor Inductance (mH)
    > DMTD 0.000000
    > Motor Damping (Nm/rad/sec)
    > DMTRWC 0.23
    > Motor Thermal Resistance (degrees Celsius/Watt)
    > DMTTCM 20.0
    > Motor Thermal Time Constant (minutes)
    > DMTTCW 0.33
    > Motor Winding Time Constant (minutes)
    > DMTAMB 40.00
    > Motor Ambient Temperature (degrees Celsius)
    > DMTMAX 90.00
    > Maximum Motor Winding Temperature (degrees Celsius)
    > DHALL 1
    > Disable Hall Sensor Checking
    > DMTLQS 0
    > Set Q Axis Inductance Saturation
    > DMTLDS 0
    > Set D Axis Inductance Saturation
    > DTHERM 0
    > Disable motor thermal switch input
    >
    >
    >
    > Drive Setup
    > DMODE 2
    > Drive Control Mode
    > DRES 8400
    > Drive Resolution (counts/rev)
    > DPWM 16
    > Drive PWM Frequency (kHz)
    > SFB 1
    > Encoder Feedback
    > ERES 8400
    > Encoder Resolution (counts/rev)
    > ORES 8400
    > Encoder Output Resolution (counts/rev)
    > DMEPIT 42.00
    > Electrical Pitch (mm)
    > SHALL 0
    > Invert Hall Sensors
    > DMTLIM 1.5
    > Torque Limit (Nm)
    > DMTSCL 1.5
    > Torque Scaling (Nm)
    > DMVLIM 119.000000
    > Velocity Limit (rev/sec)
    > DMVSCL 119.000000
    > Velocity Scaling (rev/sec)
    >
    >
    >
    > Load Setup
    > LJRAT 0.0
    > Load-to-Rotor Inertia Ratio
    > LDAMP 0.0000
    > Load Damping (Nm/rad/sec)
    >
    >
    >
    > Fault Setup
    > FLTSTP 1
    > Fault on Startup Indexer Pulses Enable
    > FLTDSB 1
    > Fault on Drive Disable Enable
    > SMPER 8400
    > Maximum Allowable Position Error (counts)
    > SMVER 0.000000
    > Maximum Allowable Velocity Error (rev/sec)
    > DIFOLD 0
    > Current Foldback Enable
    >
    >
    >
    > Digital Input Setup
    > INLVL 11000000
    > Input Active Level
    > INDEB 50
    > Input Debounce Time (milliseconds)
    > INUFD 0
    > Input User Fault Delay Time (milliseconds)
    > LH 0
    > Hardware EOT Limits Enable
    >
    >
    >
    > Digital Output Setup
    > OUTBD 0
    > Output Brake Delay Time (milliseconds)
    > OUTLVL 0100000
    > Output Active Level
    >
    >
    >
    > Analog Monitor Setup
    > DMONAV 0
    > Analog Monitor A Variable
    > DMONAS 100
    > Analog Monitor A Scaling (% of full scale output)
    > DMONBV 0
    > Analog Monitor B Variable
    > DMONBS 100
    > Analog Monitor B Scaling (% of full scale ouput)
    >
    >
    >
    > Servo Tuning
    > DIBW 1500
    > Current Loop Bandwidth (Hz)
    > DVBW 100
    > Velocity Loop Bandwidth (Hz)
    > DPBW 40.00
    > Position Loop Bandwidth (Hz)
    > SGPSIG 1.000
    > Velocity/Position Bandwidth Ratio
    > SGIRAT 1.000
    > Current Damping Ratio
    > SGVRAT 1.000
    > Velocity Damping Ratio
    > SGPRAT 1.000
    > Position Damping Ratio
    > DNOTAF 0
    > Notch Filter A Frequency (Hz)
    > DNOTAQ 1.0
    > Notch Filter A Quality Factor
    > DNOTAD 0.0000
    > Notch Filter A Depth
    > DNOTBF 0
    > Notch Filter B Frequency (Hz)
    > DNOTBQ 1.0
    > Notch Filter B Quality Factor
    > DNOTBD 0.0000
    > Notch Filter B Depth
    > DNOTLG 0
    > Notch Lag Filter Break Frequency (Hz)
    > DNOTLD 0
    > Notch Lead Filter Break Frequency (Hz)
    > SGINTE 1
    > Integrator Option
    > SGVF 0
    > Velocity Feedforward Gain (%)
    > SGAF 0
    > Acceleration Feedforward Gain (%)
    > -----------------------------------------------------
    >
    >
    > Regards,
    > JinHo"
    > NI Software :
    > LabVIEW version 6.0
    > NI Hardware :
    > Motion Control device PCI-7344
    > Driver Version :
    > no
    > OS :
    > Windows 2000
    > CPU :
    > Pentium
    > RAM :
    > 128
    > Vendor :
    > DELL
    > Customer Information :
    > Jin Ho Lee
    > North Carolina State Univ.
    > US
    > [email protected]
    > Ph: (
    > 919
    > )
    > 512-9929
    >
    >

    Yes, we used an NI PXI-7344 motion control card with an NI UMI-7764 box connected to a Gemini GV-U12E servo drive. (which is a drive only.)
    We did positional control in absolute position mode.
    I can send you an AutoCAD schematic detailing how to connect the UMI-7764 to the Gemini GV servo drive.
    In regard to the Rs232 interface to the GV servo drive,
    the GV drive only model is "configurable" not "programmable". You can create unique GV configuration files with Compumotor's Motion planner then download the configuration via Rs232 using LabVIEW as desired. Or, using LabVIEW via Rs232 you can change individual GV drive parameters on demand,
    or use the GV's two analog outputs back to LabVIEW's analog inputs to measure commanded motor current or torque, etc.etc.etc

  • DAQmx - Software trigger

    Hi all,
    I would like to knows if it's possible to start a task with a software trigger if an analog start trigger doesn't appear after a timeout (e.g. 2 seconds)?
    Kinds

    In fact you need to change trigger type of the task or to have different trigger types, I do not know how to do it directly
    The workarounds:
    1) Stop task if it gives timeout (= specified time), change trigger type and restart it. Be sure to commit task before first start to increase speed.
    2) It may work to connect internal 20MHz timebase to the trigger terminal (Daqmx routing palette) after the specified time

  • Why is the IEEE 1394 Standard for digital cameras difficult to synchronize/trigger with other devices?

    In the knowlege base, it generally says under "analog and digital cameras: advantages and disadvantags" that the IEEE 1394 is difficult to synchronize and trigger. Why is that exactly so and how can you solve that problem in DIAdem 8.0 when you would like to trigger your measurement inputs (accelerometers etc) together with a camera.

    I would guess it is difficult to synchronize because it provides a software trigger. Latencies in the communication would make it difficult to perfectly synchronize two separate events.
    Many firewire cameras also have a hardware trigger. If you were to use this with your other hardware, you would probably be able to get much better synchronization.
    Bruce
    Bruce Ammons
    Ammons Engineering

  • Is there any successful example of USRP RIO with PCIe adapter?

    Hi All,
           Can I ask who has ever had successful experience of achieving high IQ rate using USRP RIO with PCIe adapter? If so, what PC were you using?
           I am working on the USRP RIO. I tried to run the LabVIEW code for the USRP-2920 on the USRP 2950R but could not achieve a high IQ rate. The PC I am using has a mini-itx motherboard with H97 chipset, 16GB 1600MHz DDR3 memory, 256GB SSD, i7-4790K quad-core 4.0GHz CPU. Even if I connect the USRP-2920 to the PC, I could not achieve 20MS/s. When I was using a Macbook Pro with i7-3840QM, I could achieve 25MS/s IQ rate. But there is no way I installed a PCIe adapter to the laptop. 
           Thank you very much.

    I have a benchmarking utility that I will attach here that can run through a number of IQ Rates and the number of samples in each Write call.  Here are the results when I ran with an USRP-2940R over a x4 MXIe (PCIe) link.  I configured to run a 2-channel continuous generation for 10 s for each test.  
    Device connected over PCIe
    Conducting benchmarks for continuous writes (CDB, 16-bit).
    IQ Rate        363 726 1000 3000 6000 10000 100000
    1000000      0      0       0       0        0         0           0
    2500000      0      0       0       0        0         0           0
    5000000      0      0       0       0        0         0           0
    10000000    0      0       0       0        0         0           0
    20000000    39    0      0       0        0          0           0
    40000000    18    18    0       0        0          0           0
    60000000    9      36    15     2        0          0           0
    80000000    22    17    14     0        2          0           0
    90000000    15    22    15     9        9          9           9
    95000000    21    21     22    9        9          9           2
    97500000    16    14     31    9        9          9           9
    100000000  15    34     25    9        9          9          10
    The formatting may be hard to figure out, but the small numbers are the number of underflows.  So 0 is what you want.  As you can see, I can sustain rates up to 80 MS/s for at least 10 s IF my write size is big enough.  That is, if I write at least 10,000 samples with each call to niUSRP Write, I don't see underflows.  That's two channels, so we're talking 640 MB/s over the bus.
    Here are some tips to increase your Tx streaming throughput:
    0) Don't use a continuous generation at all.  For many applications you don't need to stream continuously- a finite transmission (and you can loop a finite transmission) will do and you will basically not underflow in that case if you provide all the data up front.
    1) As you can see from the chart, the bigger the data buffer you provide in each Write call, the faster you can stream.
    2) Write sizes in multiples of the maximum packet size seem to work well.  That number is 2044 for the USRP-294x/5x series (although that may change in future driver releases).  Try sending bursts of 10220 samples.
    3) If your application allows it, set a Start Trigger Time a little in the future.  Then start writing data before the device starts transmitting.  For example, set the Start Trigger Time to the (current device time + 1 second).  Then start writing data and you will have a second to pre-fill the on-device buffers.  This will substantially reduce the number of underflows.
    4) Be sure to do your data processing out of your write loop, to keep the write loop filling the pipleline as quickly as possible.

  • Help: Can you use software trigger on a digital line.

    Hi:
    We have a legacy DAQCARDard 700 which does not support hardware triggering.
    We have a trigger from our instrument that is 5 V+ and we would like to
    trigger when it drops to 0 V. We have several questions.
    1. Do we need to invert the signal in MAX or is that only for V that are
    negative?
    2. Is there a good example in the examples where the state of this digital
    line is used to trigger an analog acquisition? When we tried using the
    digital trigger examples, we had an error saying that the hardware did not
    support that mode.
    3. We have an analog software trigger mode (based on the Analog Software
    Trigger example) working which we would like to modify over to read the
    digital line, but we have done very little wi
    th digital I/O.
    4. The digital trigger has been assigned a virtual channel of dtrg.
    Any help would be much appreciated.
    Thanks in advance,
    Pete

    Thanks Doug,
    If we read the digital line instead of as an analog line would it improve
    the accuracy of the triggering. Everything works now except we have a
    little bit of timing jitter within about 1 data point scanning at 50 kHz.
    However, I've never done any digital i/o with LabView, but may I should work
    through some of the tutorials. If you thought that this might solve the
    jitter problem. Would checking the state of the digital line allow a faster
    response with softtrig, I guess is my question?
    Pete
    "Doug Norman" wrote in message
    news:[email protected]..
    > Hello Pete,
    >
    > You are correct that the DAQCard-700 has no digital (or analog)
    > hardware trigger. The analog trigger example t
    hat is working for you
    > is using conditional retrieval. This is where data is always being
    > acquired and the driver looks at the values to determine when to
    > "trigger" and read the data into LabVIEW. To answer your questions:
    > 1. I don't think you need to invert the signal. This is for when you
    > want a digital low (below 0.8 volts) to show up as a digital high, and
    > a high (above 2.0 volts) to be read as a low.
    > 2. I don't know of a good example. You would basically have to
    > monitor the digital line. When it goes from high to low you would
    > then start your analog acquisition.
    > 3. I think this could be your best bet. If you have enough analog
    > input lines, why not just connect this digital signal as one of your
    > analog inputs. Then use this example to trigger when the 5 volts
    > drops to 0. It won't hurt to acquire your digital signal on an anlog
    > input along with your other data.
    > 4. I don't understand this question.
    >
    > Best Regards,
    >
    > Doug Norman

  • How to measure frequency with PCI-4474 card

    Hi,
    I'm trying to measure frequency with PCI-4474 card.
    Any sample code available?
    Thanks.

    Hi,
    Thank you for posting the the NI forums.  There aren’t any example programs that ship with the DSA drivers.  Will you be using this with the Sound and Vibration Toolkit?  If so, there are numerous examples that install with this software package.  Check out the LabVIEW Example Finder >> Toolkits and Modules >> Sound and Vibration Toolkit. 
    In addition to this, you could also use the signal processing VIs that ship with LabVIEW.  There are also examples that ship with LabVIEW that use these VI in Example Finder >> Analyzing and Processing Signals FFT and Frequency Analysis.  There is an entire Signal Processing palette that should contain the functionality that you need.
    I hope this helps.  Post back if you have further questions. 
    Ed W.
    Applications Engineer
    National Instruments

  • Saving software trigger in project

    I created a project with Signal Express v3.0 where I use software trigger to start and stop acquisition. When I close signal express and then reopen the project the software triggers do not show up in the bar below the menus.
    Is there a way to keep the software triggers in the bar when we close the project and signal express?
    Thanks,
    Ben

    Duplicate post on Signal Express forum here
    Misha

Maybe you are looking for