DASYLab

cancel
Showing results for 
Search instead for 
Did you mean: 

Data-Save Timing

I have two separate topics going that I should combine into this thread, as they are now joined in my application.

 

The function of my worksheet is to save 30-sec of data at 250-Hz every 2:00-min. In addition, the Start button will display active data, but will not save to disk until the Start Test button is pressed. Measurement time is saved to each file. Measurement time is zeroed when Start Test is pressed.

 

CJ, from your file (20161130 Timing+filename-fixed2.DSB ‏382 KB), I moved the Counter to be activated by the “Start Test” button, so the Measurement Time increments only after the Start Test PB is pressed, and prevents it from resetting with every set of measurements. Then I added more channels to represent my application. When I use a Generator to simulate my data channels, the operation and timing are flawless. The actual Measurement Time is accurate, and Data Saving starts and stops within ms of when it should. The data saved to disk (bottom line) exactly matches the timing input to the relay (square wave)  [Screen 1].

 

20161130 Timing+filename-fixed2(5-chan)-A.DSB

 

However, when I replaced the Generator with the actual inputs (CombiTask from Measurement and Automation Explorer) it all goes to pot.   [Screen2]

 

20161130 Timing+filename-fixed2(5-chan)-B

 

The 1st file saved only 17 sec. of data (Should have been 0 to 30 sec.)

The 2nd file saved  from 40 to 43 seconds (should have been 120 to 150 sec.)

The 3rd file saved from 50.3 to 52 sec. (should have been 240 to 270 sec.)

 

There seems to be a delay right from the start that gets worse as is runs. Does any obvious cause stand out from this?

 

The details of my system and setup are:

DASYLab 2016 with Windows 7 Pro

MAX version 15.0

COMBI TASK with 4 analogue channels set at “n samples,  1000 samples, Rate = 10kHz”

Buffer is 500 samples

 

0 Kudos
Message 11 of 12
(1,316 Views)

The way that you're driving the relays results in a block size of 1, with an effective sample rate of 5kHz.

That's causing DASYLab to back up, and not get the data from MAX, leading to the overrun error. 

 

Let me study this some more to see if I can see a more effective way to do it. 

Measurement Computing (MCC) has free technical support. Visit www.mccdaq.com and click on the "Support" tab for all support options, including DASYLab.
0 Kudos
Message 12 of 12
(1,309 Views)