09-30-2007 10:13 PM
10-01-2007 04:10 PM
You want to use two kinds of trigger individually so my guess is that you want to be able to switch while your code is running between “hardware trigger” and “software trigger”, am I understanding this correctly? Also I want to clarify, are you driving the PFI 1 line with two wires “externally” one from the clock to PFI 1 and your external signal to the PFI 1? Are you making any kind of internal (software) routing of the clock and the PFI 1 line? If you can include screen shoot of your enitre code that will help a lot? What version of NI-SCOPE are you using? Can you draw the external circuitury of what you are trying to do?
I will suggest trying this example “niScope EX Configured Acquisition.vi” and setting it up for extranal trigger (outside trigger). This example is included in the latest version of NI-SCOPE 3.3.1 that installs support for labview 7.1.1 and up. I have attached a screen shoot of the block diagram in case you are not able to open it.
10-01-2007 08:44 PM
Yes, I want to use two kinds of trigger individually, I want to be able to switch while the code is running between “hardware trigger” and “software trigger”, am I understanding this correctly? The PFI 1 line is programmed only for internel trigger, just wired once. But the fact is it seems also works from outside signal. I am using NI-SCOPE 3.3 with LV 8.2.1
For internal trigger, it will generate a 50Hz signal and wire to pf1.
Please see the screenshot.
10-02-2007 06:40 PM
Hi Turbot,
Were you be able to run the “niScope EX Configured Acquisition.vi” example since you are running NI-SCOPE 3.3. This example is located in the National Instruments. (I have attached a picture of the location), also this example is similar to what you want to do; while the program is running you can change between trigger types in this example. You should be able to follow the example as a guide and join both trigger types in only one; since you already said that you can get outside (external) and inside (internal) triggering working in separate Vis.
I did ask you for the “circuitry draw” of what lines are going to be connected to the PFI 1 line because if you are connecting two lines they might not work together if one of the lines is not set to “high impedance”, this is the case if you are double driving PFI1. Also can you attach your code? That might help me help you.
10-02-2007 09:14 PM
10-02-2007 09:15 PM
10-03-2007 05:34 PM - edited 10-03-2007 05:34 PM
Hi Turbot,
Answering one of your previous questions, there is not priority between an external signal and internal signal. What I think you are doing is double driving the PFI 1 line so it will trigger with the first pulse it receives. That is why I have been asking you to draw the circuit; I need to know if you are physically wiring the clock to the PFI 1 line and an external. I have attached two for the VI that I think you should be using to do an internal “trigger”. Also can you tell me why the example: “niScope EX Configured Acquisition.vi” does not work for you?
Message Edited by Jaime F on 10-03-2007 05:35 PM
10-08-2007 04:04 AM
For the internal trigger, I just use the 5102_pfi_output.vi, no physical wire, I think the wire is done by the program.
For Out source trigger, I connect the the out side signal to the small golden port, just near by the 2 BNC port.
It seems the outside trigger signal has higher priority, even the internal trigger program is running.
10-09-2007 01:12 PM
Hi Turbot,
If I understand correctly the issue you are running into is, you are trying to use both a software and hardware trigger. When you try to
use the software trigger you are triggering off of the hardware trigger. From the previous posts it appears that you are attempting to
trigger from PFI 1 in both cases. For a software trigger you should use the two VIs that Jaime F posted in the previous post. The
configure VI sets up the software trigger, and then the send software trigger will send the trigger when it is executed in your program.
I have linked to an example program that better illustrates this concept.
Software Triggering with NI-SCOPE and a High-Speed Digitizer
It also looks like you are mixing the NI-Scope and Traditional NI-DAQ API's, it is recommended that you only use one. While the
5102 technically can be programmed with the Traditional DAQ API, it is highly recommended to use the NI-Scope API only. I would
also appreciate a simple drawing of how your circuit is configured.
I hope this helps!
10-09-2007 09:36 PM