11-30-2009 08:59 AM
Can someone tell me what the attached error log means? I got it after several hous of logging data to a binary file. The sample rate is 20 per second and there is four I32 numbers logged for each sample. The resulting binary file got up to a little over 23 MB and then the LV application crashed. I'm using Win-XP and LV 8.6.
Thanks,
DJ
11-30-2009 09:01 AM
11-30-2009 09:03 AM
That message reads as if you are attempting to add channels to a task that is being destroyed. So check your code to determine if the config happens once when the code starts and only kill the task when you are done.
if that does not float your boat, are you using a USB based DAQ device?
Ben
11-30-2009 09:35 AM
I'm logging two data values via a serial port. The other two values are for date and time. Attached is the initialization and read sub-vi's. The VISA Init TTR.vi is in the initialization sequence and the VISA Read TTR.vi is in a timed loop running at 50 mSec. I'm using a VISA Close function on the outside side of the of the timed loop.
There are other tasks (i.e. DAQmx and USB related) that are defined in this project. However, they are disabled using the project's Conditional Disable Symbols. Maybe I didn't properly disable something somewhere. If so, why is it taking several hours for the error to freeze the system?
Also, I cannot open the resulting binary file. Attempting to open it promptly freezes the application and there are no error messages.
I just changed this particular project to log the serial data and this is the first attempt to log data for several hours (i.e. over the weekend). It all works well when logging data for several minutes.
11-30-2009 11:14 AM
11-30-2009 11:45 AM
I'm sorry; it's not clear to me what is meant by higher level code. Attached is a screen shot of where the subvi's are used.
It it possible to determine from the error log what type of task is under question?
11-30-2009 03:00 PM
12-01-2009 11:44 AM
I've been doing much testing since getting the error and the problem has not recurred. At this point I'm considering it a fluke. The project is an over bloated application withover 200 subvi's, server vi's and type definitions and I wish not to send it via the public Discussion Forums. It became over bloated with time because of many changes and additions that was made over time. (OK, I admit it's a mess that I'm embarrassed to release.)
If the application proves successful, I'll strip it down and create a new dedicated project.
I appreciate the responses.
DJ
12-01-2009 12:10 PM
dj143 wrote:I've been doing much testing since getting the error and the problem has not recurred. At this point I'm considering it a fluke. The project is an over bloated application withover 200 subvi's, server vi's and type definitions and I wish not to send it via the public Discussion Forums. It became over bloated with time because of many changes and additions that was made over time. (OK, I admit it's a mess that I'm embarrassed to release.)
If the application proves successful, I'll strip it down and create a new dedicated project.
I appreciate the responses.
DJ
STOP!
Is there any difference between what you have now and what you had when you last saw the issue?
If so, therein lies your answer.
Ben
12-01-2009 01:07 PM
Hi Ben,
The only change I've made is the addition of code to automatically create and append smaller files. In other words, it now creates a series of files as it logs. I did this because I need to release this project soon and it's clear to me that the application significally slows down when it works with a very large file. I have made no changes to the task definitions or the conditional disable symbols.
DJ