08-13-2007 12:43 PM
08-14-2007 02:14 PM
Hi Matt,
The reason why disconnecting PFI1 does not throw an error is because currently PFI1 is connected to the ‘sync pulse source’ of the ‘niscope configure clock.vi’. The LabVIEW Help describes this as “specifies the line on which the one-time sync pulse is sent or received.” Since the one time pulse has been sent, disconnecting PFI1 later will not be a problem. If you are wanting to use PFI 1 as a sample clock, use a scope property node and inputs for sampleclock timebase devisor, rate, & source. If you want to use PFI1 as a reference clock, than put this as an input to the ‘reference clock source’ node on the configure clock.vi you are currently using.
Question2:
The data is clocked in on the rising edge of the clock
Question3:
NI-SCOPE is the scope drivers, and is built upon NI-DAQmx, which is the reason for partial functionality and why you see your 5105 under NI-DAQmx devices in Measurement and Automation Explorer. NI-SCOPE is the required driver for full functionality on the 5105.
06-30-2009 03:19 PM
07-01-2009 05:30 PM
Douglas,
That appears correct to me, I could not be completely sure that it would work until you run it. You will only need to send the trigger and clock to one of the devices as since you are using T-CLK that will take care of the rest. I would suggest giving the code a try and then letting us know if something does not work correctly. Our office will be shutdown on Thursday and Friday for the holiday weekend, but we can do troubleshooting the following Monday if necessary. Thanks and have a great 4th of July!
07-07-2009 12:24 PM
My concern at the moment is the contradiction of Configure Horizontal Timing and Configure Clock. The "min sample rate" would seem to indicate that, if the external clock is too slow, the sampling rate would happen on its own. Do these two override one another?
I am unable to reset the "min sample rate" ahead of time (to be below the clock rate) because of the random nature of the signal for which we are using the Discriminator--I will not know the sampling rate dictated by the discriminator until afterward.
07-08-2009 06:36 PM
Douglas,
If I understand correctly you will be varying your sample clock with the device, is this correct? When providing an external sample clock to the scope device, the device needs to know approximately what rate of clock source to expect and that is where the 60 MHz would come into play in this case. Could you give me some more information about your overall application so I understand better exactly what you need the Scope cards to do? Also, could you estimate how much your external clock will vary and at what rate the clock will vary. Thanks!
07-08-2009 06:51 PM
The application is a radiation detection unit that generates pulses of varying height based on the strength and number of photons that strike the detector, which photons are generated by a scintillation crystal that absorbs beta particles and gamma rays. The number of pulses per second can be estimated by an external device which counts the pulses received (over a period of time) before the experiment begins. In other words, the number of pulses of the "clock" or "trigger" circuit can be estimated a few moments before the process begins.
Assuming a number of pulses per second between 1000 and 10000, and that we will know approximately how many pulses per second we have before the experiment, what other correction must be made? We can change the Min Sample Rate during the setup phase for each acquisition, because we use TClk subroutines, which reset the boards, during setup to precisely synchronize things.
07-09-2009 12:57 PM
Douglas,
Are you wanting to simply acquire this sample clock that your device will be generating or are you wanting to provide the scope cards this signal as an External Clock to provide a Clock supply for the Scopes?
If you want to use this signal as an External Clock and you know the rate of the clock a couple of seconds before the start of the scopes then you need to have a way to pass that information along to the Configure Clock VI, so it knows what clock frequency to expect. Is this an option for your system?
Thanks!
07-09-2009 01:14 PM
07-09-2009 01:16 PM
To clarify, the counting device and the digitizer connect to the RAW signal, which is also connected to a constant fraction discriminator.
The constant fraction discriminator then acts as the PFI1 clock signal, and it has the same pulse rate as the regular signal.