06-28-2012 02:41 PM
I am currently working a on a worksheet that uses measurement computing boards and there classic driver. After some adjustment I have it set so that it uses a single input output feature and also have the block size set at 1. Although I know I am supposed to have a smaller sampling rate to block size ratio,this seems to allow me to run the program at fairly high sampling rates. I am primarily concerned with the response time of the program (the time it takes for one data point to pass through the program and give an output to my DIO board).
/
Do you see any ways I may be able to decrease the response time (make the program run as fast as possible)? Are some of my modules slowing down the program, or is it possible that the problem is with the speed of the DIO board?
Can you tell if the worksheet I have would run faster in a program like Labview?
J
06-29-2012 08:43 AM
Jeff,
You don't mention the sample rate.
You can get a sense of what is taking time inside DASYLab by configuring the options.
Option menu, select Global Setup.
In Global Setup, select the Determine Module Process time setting (check the box).
Then, while running, go back to the Options menu, and select the Module process time item. It will display a list of the modules, and tell you how long each is taking, and what the overall loop time is....
Would it be faster in LabVIEW? Which driver? UL for LabVIEW or ULx for LabVIEW? You will have more control over the output loop than you do in DASYLab. Hands down, it would be faster to write your own program and only deal with the functions that you need.
Generally speaking, the modules that consume the most processing time are the chart modules - Chart Recorder, Y/t Chart, etc. They have to do the computation to render the data and accurately create the graphed data. That's compute intensive compared to a simple arithmetic operation.