06-15-2010 12:19 PM
06-15-2010 03:42 PM - edited 06-15-2010 03:43 PM
06-15-2010 04:06 PM
Vincent DelMonte wrote:
The purpose of this program is to record voltage over an amount of time in order to replace a traditional strip chart recorder. This program functions well except for a few small bugs. Firstly, the time on the table does not reset when the program is paused through the Start/Stop Boolean. I know what causes this problem, however I have not been able to find an adequate solution.
You need to reset the offset when you start plotting again. Take a look at the "Real-Time Chart" VI that ships with LabVIEW.
In addition, the table flickers and flashes when the program is paused. I know that this is caused by the table constantly refreshing, however I do not know the best way to fix this.
Only update the table if you're actually collecting data. In other words, place the table update inside the main case structure. If you're not collecting data, what's the point of updating the table? Note that this means you'll need to place the save to file in there as well.
Other comments:
06-15-2010 08:48 PM
Thank you for the input, the only comment I have has to do with one of your suggestions.
@smercurio_fc wrote:
You need to reset the offset when you start plotting again. Take a look at the "Real-Time Chart" VI that ships with LabVIEW.
Only update the table if you're actually collecting data. In other words, place the table update inside the main case structure. If you're not collecting data, what's the point of updating the table? Note that this means you'll need to place the save to file in there as well.
The reason that we are encountering our problems is because we have case structures. If we put the save folder inside the case structure, then when the case structure is false, there is no way that we can save the data. I was wondering if there is a better way of approaching solving the problem, or if using case structures was the best option, and if so, how we should tweak our program.
Thank You
06-15-2010 09:01 PM
Well, if you are not acquiring data, what is there to save? If you do want to save, there is absolutely no reason you have to connect the write to file function to the output of the table. You can connect it to the daq data.