Problem with task not writing to file

[Lorne.V.]

I have a problem where the file writing from a analog reading task will eventually stop working.  The acquisition will work normally but after a period of time (tens of seconds to tens of minutes) it will stop writing files.

The mode of operation is to continuously acquire and periodically switch to a new file.

The key functions are 'readTaskConfigure()' and 'AnalogInCallback()'.  The 'ShowWaveforms' flag is set to false.

I suspect the problem is with resource usage.  Any suggestions on how to make this more efficient would be greatly appreciated.

Thanks,

Lorne Vaasjo

[DECONN]

Hi Lorne.V.,

Does the acquisition portion work continuously? For example if you disable the file writes, does it acquire as expected with no issues? Are you noticing any memory leaks or CPU increases? Have you looked at, or tried running, one of the shipping examples yet?

Also, you may want to consider posting your questions to one of the text-based programming forums as they may have some helpful insight to add.

[Lorne.V.]

Thanks for the reply.  I did post the question as well on the text-based programming forum.

I do have a memory monitoring function built in and will get the client to check that.  The problem would likely go away if saving to file was disabled but that would defeat the purpose.

Thanks.

[DECONN]

Well what I meant by disabling the saving was that it could be a helpful troubleshooting step to determine exactly where the problem was emanating from. I often find that isolating and confirming functionality of separate portions of the code can be helpful in these situations. For example, the problems with the files you are seeing could just be a symptom of a problem with the data acquisition portion.

[Lorne.V.]

Right.  I've asked the client to try that and waiting for a response.  Unfortunately they are about 6 time zones away.