LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Problems with synchronous clocking with PXI 1010 and Chassis SCXI

I have a PXI 1010 whit SCXI chassis, and two SCXI-1531 modules in multiplexed mode with a 6030E DAQ,(SCXI slots 1 and 2) and two 1141 filters modules in parallel with a 6031E DAQ (SCXI slots 3 and 4).
I am using the 0 channel of a 1141 for trigger, but, the signals in the 1531 ICP modules (multiplex mode) are not synchronous with the signals of 1141 (parallel mode) filters, and is difficult to analyse them because the delay between the signals. How can I syncronize them?
0 Kudos
Message 1 of 11
(3,558 Views)
Since neither the 6030E or 6031E support analog triggering, I'm assuming that you are reading the 1141 channel 0 signal, and when it reaches some state, you start some buffered acquisition within your code?

Mark
0 Kudos
Message 2 of 11
(3,558 Views)
Mark

See the attach.

Thanks Bramatti
0 Kudos
Message 3 of 11
(3,558 Views)
I read your attachment. I don't think I made myself very clear in the first reply. I was really interested in how you acquire your data. First, how you trigger your acquisition. Second, how you acquire your data from the 6031E and your 6030E. Are you synchronizing them with a start trigger?

Also, keep in mind that there is an interchannel delay that LabVIEW calculates for multiplexed signals. If you dig into the analog input configuration VIs, you can actually set this interchannel delay rather than letting LabVIEW determine it. Usually it's fast enough that you don't see the types of delays that you may be seeing, but you may be able to change it. Consider, though, that the smaller it is, you may not be allowing for enough settling ti
me, so it's not recommended to change it for most applications.

Mark
0 Kudos
Message 4 of 11
(3,558 Views)
Mark (my english is no good, sorry)

I attach a simple VI in order to understand how PXI with SCXI works, when I am using parallel (two 1141 in a 6031 DAQ) and multiplexed (two 1531 boards in a 6030 DAQ).
Its important to me to correlate in time of all signals. The interchannel delay in the 1141 is not problem, the same for the 1531 boards (multiplexed, but the channel have sample and hold device). I am making analog software trigger - see the example in attach. The problem is the delay that exists beetwen the parallel boards and the multiplexed boards, and I need to correlate them in a same graph, and, for example, save the signal in a file in order to analyse orbit and harmonics (FFT).
0 Kudos
Message 5 of 11
(3,558 Views)
Simple VI for test and understand
0 Kudos
Message 6 of 11
(3,558 Views)
Hrm...I answered this yesterday, but it seems my post didn't make it.

I checked your VI, and saw several things.

If your VI is indicative of how you run your data acquisition in your actual VI, there are a few things to note. First, since your boards don't support hardware analog triggering, you must use software triggering, as you have done.

The difference between a hardware trigger and a software trigger is this. A hardware trigger doesn't start putting data in the buffer until the analog trigger occurs. A software trigger puts the data in the buffer always, but reads the data out of the buffer and checks for the trigger condition. If the trigger condition occurs, only the data specified (pretrigger data and post-trigger data) will actually be sent from the buffer out of the AI Read VI and into your LabVIEW program.

Why do I tell you this? Because your other acquisitions, the two without the trigger, are occuring all the time. When the first one sees the trigger, it will come back with data, but it most likely will be less data than the other two (unless the trigger occurs on the FIRST scan of the buffer, which is very unlikely). Therefore, your trigger acquisition may come back with 749 points, while the other two come back with 1000 points. Therefore, the data is skewed.

Adding to that, you're not starting all your acquisitions with a start signal. Therefore, they are starting at different times, depending on when your PC actually ran the data acquisition code for each one. What you need to do is to to set up a RTSI line (Real Time Sytem Integration). The RTSI bus is connected to all your MIO boards in your PXI chassis, due to the structure of the PXI backplane. Therefore, you can set up your acquisitions to start when a rising edge is seen on RTSI 1, for example. Then, what I do is use the Data Acquisition -> Calibration and Configuration -> Route Signal.VI to route a counter output to the RTSI line. Toggle the counter, and if your acquisitions have been started (they will be waiting for the toggle), they will actually all start running at the same time.

If you keep the same software analog triggering that you have now, when a trigger occurs, you'll have to do a check to see how much data comes back. You can then retrieve the same amount of data from the other two acquisitions. Since all your acquisitions would have started at the same time, and you're retrieving the same amount of data, all data should line up in the time domain, and that's what you want.

If you would like an example, maybe that would make it more clear.

Mark
0 Kudos
Message 7 of 11
(3,558 Views)
Mark

Thanks.

We use a NI example, and the two boards trigger at same time, BUT there are a delay between the parallel board and the mux board.

Is it possible send us a simple example using counter? After the trigger at same time, the acquisitions must start running at same time, in order to line up the sine in the time domain.

Bramatti
0 Kudos
Message 8 of 11
(3,558 Views)
Mark

Thanks.

We use a NI example, and the two boards trigger at same time (both in chan 0), BUT there are
a delay between the parallel board and the mux board (same sine signal, both in chan 1).

Is it possible send us a simple example using counter? After the trigger at
same time, the acquisitions must start running at same time, in order to
line up the sine in the time domain.

Bramatti

Trigger test.vi
<>
0 Kudos
Message 9 of 11
(3,558 Views)
Try something like the attached VI. Similar to yours, but look at the triggering.

Mark
0 Kudos
Message 10 of 11
(3,558 Views)